Dira Catalog · Menus, pricing and availability
One menu system. Every channel.
Dira Catalog holds your master menu, modifiers, prices and availability in one place, then publishes the right version to each channel and store group. Every change is versioned, validated and recorded before it reaches a guest.
- Toggle to mark an item 86 across every channel.
Classic chicken sandwich
itm-1042v42 draft vs v41 live
- 3 price changes · 1 new item · 1 item retired
- Approved by menu ops · awaiting publish
Illustrative interface · sample data. Uber Eats menu publishing is integrated today; DoorDash and Grubhub adapters are in development.
Menus multiply faster than teams can check them.
A price change touches every channel and every store group. Done by hand, small differences pile up until guests notice them first.
The same item, five versions
Each marketplace holds its own copy of the menu. Edits made in one place quietly drift from the rest.
Prices that vary by location
Airport, urban and franchise stores need different prices. A spreadsheet cannot show which store sees which number.
86ing is slow and partial
When an item runs out, staff turn it off channel by channel. Some menus stay live, and orders arrive for food the kitchen cannot make.
No record of who changed what
Without versions and approvals, a bad publish is hard to trace and harder to undo.
Control without the spreadsheet.
The menu work multi-location teams do every week, in one system with a full history.
Master menu and modifiers
Categories, items, modifier groups, combos and dayparts live in one catalog hierarchy. Edit an item once and every menu that uses it follows.
Channel and store-group pricing
Set a base price, then override it by store group or by channel. The item pane shows the exact price each location and channel will publish.
Base · store group · channel
Availability and 86
Mark an item or modifier unavailable for one store, a store group or the whole network. The change reaches every connected channel without editing menus one by one.
Versions and approvals
Every edit lands in a draft version. Compare it with what is live, route it for approval and restore an earlier version when a change needs to come out.
v42 draft compared with v41 live
Validation before publish
POS mapping, modifier rules, daypart windows and price coverage are checked before anything goes out. A failed check blocks the publish and names what to fix.
Scheduled publishing and read-back
Publish now or at a set time, per channel and store group. After publishing, Dira reads the menu back from the channel to confirm it matches.
From draft to every channel, on schedule.
Review the diff, clear validation, choose store groups and schedule the publish. Try it with the sample menu.
- PriceClassic chicken sandwichAirport stores$9.29$9.49
- PriceSpicy chicken sandwichMetro stores$7.99$8.09
- PriceBreakfast taquito comboUber Eats$6.89$6.99
- New itemSeasonal peach shakeAll storesnone$4.99
- RetiredSummer berry lemonadeAll stores$3.49none
Illustrative interface · sample data
Review the diff
See every price, item and retirement in the draft against what is live, before anyone approves it.
Clear validation
Mapping, modifier rules, dayparts and price coverage must pass. A gap blocks the publish until it is fixed.
Schedule per channel and store group
Choose where and when. Channels whose adapters are still in development stay visible but cannot be selected.
Confirm with read-back
After publishing, Dira reads the menu back from the channel and records the result in the version history.
Technical details
The data Catalog manages, how it publishes and what it records.
Architecture and APIs- Menu model
- Menus, categories, items, modifier groups, modifiers, combos, dayparts and store groups.
- Pricing
- Base price with store-group and channel overrides, resolved for each item before publish.
- Availability
- Item and modifier availability per store, store group or network, including one-tap 86 from Dira Store.
- Versioning
- Every change is made in a draft version. Published versions stay in history and can be restored.
- Validation
- POS mapping, modifier rules, daypart windows and price coverage, checked for each selected store group.
- Publishing
- Per channel and store group, immediately or scheduled. Read-back confirms what the channel received.
- Channels
- Uber Eats menu publishing integrated. DoorDash and Grubhub adapters in development, targeted next.
- Audit history
- Who edited, approved and published each version, and when.
- Interfaces
- Strict OpenAPI 3.1 contracts. Connect reads the live mapping to validate orders; Bridge uses it for POS identifiers.
Questions buyers ask
Bring every menu under one system.
See how Catalog handles your pricing, store groups and publishing schedule.