Approvals & publishing

Change with confidence.
Roll out without breaking the line.

Every change is reviewed, versioned, and published as a snapshot. Publish to everyone at once or stage it store-by-store — the current revision stays live until the new one lands.

Staged rollout · v4 Allergen update
  1. Test store

    West · 6 stores

  2. 2

    Pilot region

    West + Central · 84 stores

    Promoting now — old revision stays live

  3. 3

    All locations

    Every region · 412 stores

Isolated per-brand database · full audit trail

Review & approval

Creators submit changes for an approver to sign off before they publish; approvers and admins can also publish directly when speed matters. Nothing reaches the line as an untracked edit.

Copy-on-write versioning

Every edit creates a new version. Published snapshots are immutable, so the line always reads a complete, consistent revision.

Staged, store-by-store rollout

Publish to a test store, confirm it lands, then roll to the rest. The previous revision stays live at each store until it updates.

Scheduled menus & version pins

Build menus with date-scheduled versions and per-store pins for staggered or seasonal rollouts.

Per-store overrides

Add a local special or drop an item at one location without forking your master menu.

Bulk operations

Change type, assign a station, submit, approve, or archive across many recipes at once — every action respects the same review-and-approval workflow.

Questions

Good to know

How does approval work?

Creators submit a change and an approver signs off before it publishes. Approvers and brand admins can also publish directly when they need to move fast. Either way, every change is versioned, so the line always reads a complete, approved revision.

What happens to the line while a change is being edited?

Nothing changes on the line until you publish. Edits create a new version; the current published snapshot keeps running until the new revision is approved and rolled out.

Can I roll a change out to just a few stores first?

Yes. Publish to a test store or subset, confirm it lands, then promote to the rest. Each store keeps its previous revision until the update reaches it.

Can single-unit operators skip approvals?

Yes — at a single location one person can author and publish. The approver step turns on when you're ready, e.g. as you add managers or locations.

See it on your menu

Make change management effortless

See the full approve-and-publish loop on your own menu — book a demo.