For groups with 30+ locations
Menu management software for one master menu across every brand, POS and channel
One item list for every brand, with local prices and availability, mapped to the codes in each POS. Change it once, and the app, website, kiosk, boards and delivery apps follow.
Every location on one POS? Its own menu tools are enough
Takes two minutes. Max replies within 1 business day, and an engineer joins the call.
In short
Menu management software keeps a restaurant's items, modifiers, prices and availability in one place and publishes them to the POS, website, app and delivery apps. For a group, the problem is a master menu: one item list with local prices and availability, mapped to item codes that differ in every POS. dev.family builds that master menu on top of your POS systems and runs it. If every location runs one POS, its multi-location menu tools are enough.
What's inside
What's inside a master menu
Master menu
One item list
Every dish, modifier and combo for every brand, defined once.
Overrides
Local prices and availability
By location, region or franchisee, without copying the menu.
Mapping
Codes for every POS
Each master item is mapped to its code in every POS database.
Publishing
Every channel at once
App, website, kiosk, boards and delivery apps from one change.
Rules
What franchisees can change
HQ owns the core menu. Franchisees change only what you allow.
History
Who changed what
Every price and item change logged with author and time.
Prices and timelines
What menu management costs and how long it takes
Menu tools and middleware charge per location each month. A master menu across different POS systems is a one-time project plus support.
| Option | What you pay | Source |
|---|---|---|
| Order and menu middleware (Otter) | $79–278 per location a month | tryotter.com pricing, checked November 9, 2026 |
| Online menus with POS integrations (RestoLabs) | $79 a month billed annually for the plan with POS integrations; $55–159 across plans | restolabs.com/pricing, checked November 9, 2026 |
| Deliverect, Checkmate, Chowly | Pricing on request | Vendor pricing pages, checked November 9, 2026 |
| Toast enterprise menu management | Quote for multi-location groups | pos.toasttab.com/restaurant-pos/enterprise, checked November 9, 2026 |
| A master menu across your POS systems | Fixed estimate after the Assessment . First release usually in 8–16 weeks | dev.family · checked |
How it works
One master menu, every channel
The POS stays the register. The master menu feeds everything else.
- App
- Website
- Kiosk
- Delivery apps
Master menu: items, modifiers, prices and availability, with local overrides
- Brand A POS
- Brand B POS
- Franchisee POS
Which systems
Works on top of your POS and delivery partners
The master menu maps to each POS and publishes to each channel.
- Toast
- Square
- Lightspeed
- Zonal
- Olo
- Deliverect
- DoorDash
- Uber Eats
- Your franchisees' own POS
Our approach
A master menu above your POS systems, not a new POS
Locations keep the registers they have. The master menu sits above them: it holds the item list, prices and rules, and it knows each item's code in every POS. Channels read from it, orders go back to each POS under its own codes, and a new brand on a different register adds one mapping instead of a new menu.
Compare
POS menu tools, menu middleware or a master menu
| Criterion | POS multi-location menu | Menu middleware | Spreadsheets and a person | dev.family |
|---|---|---|---|---|
| Different POS systems | One POS | Supported POS only | By hand | Yes |
| Local prices and franchisee rules | Yes, within that POS | Partly | By hand | Yes |
| Publishes to app, kiosk and boards | That POS's channels | Delivery apps mostly | No | Every channel |
| Who's responsible after launch | The vendor | The vendor | Your team | Run under an SLA |
dev.family
Our approach- Different POS systems
- Yes
- Local prices and franchisee rules
- Yes
- Publishes to app, kiosk and boards
- Every channel
- Who's responsible after launch
- Run under an SLA
Other options
POS multi-location menu
- Different POS systems
- One POS
- Local prices and franchisee rules
- Yes, within that POS
- Publishes to app, kiosk and boards
- That POS's channels
- Who's responsible after launch
- The vendor
Menu middleware
- Different POS systems
- Supported POS only
- Local prices and franchisee rules
- Partly
- Publishes to app, kiosk and boards
- Delivery apps mostly
- Who's responsible after launch
- The vendor
Spreadsheets and a person
- Different POS systems
- By hand
- Local prices and franchisee rules
- By hand
- Publishes to app, kiosk and boards
- No
- Who's responsible after launch
- Your team
Honestly
When your POS's menu tools are enough
Every location on one POS: use its multi-location menu tools. Delivery menus only: menu middleware will do. Call us when locations run different POS systems or franchisees need their own prices within your rules.
What we find on menu projects · November 2026
Where it usually hurts
One dish, many codes. The same item had different names and codes in different POS databases. The mapping is most of the work, and it needs an owner after launch.
Slow syncs sell sold-out dishes. A sync that takes hours means guests order what the kitchen no longer has. Channels should read availability from the master menu, not from a nightly copy.
Mistakes surface in public. Mismatches showed up when a guest saw them on the website or someone noticed them in a report. Unmapped items now need to raise a task, not wait to be found.
After launch
How we run the master menu after launch
Publishing
Every menu change is logged per channel and location.
Mapping
New POS items without a match raise a task, not a silent gap.
Incidents
Alert, on-call engineer, fix under the SLA.
Questions
Didn't find your answer? Ask on the call.
Menu management software keeps a restaurant's items, modifiers, prices and availability in one place and publishes them to the POS, website, app, kiosk and delivery apps. Some tools with the same name manage recipes and food cost instead; that's a different job. For a group, menu management means a master menu that every location and channel reads from.
Keep the master list outside any single POS and map each master item to its code in every POS database. Channels read the master menu; orders go back to each POS under its own codes. When a franchisee adds an item, the mapping flags it instead of letting it slip through.
Modifier trees are mapped the same way as items, group by group. Prices live in the master menu with overrides by location, region or franchisee, so a local price change doesn't need a new menu.
From the master menu, either directly through each platform's menu API or through middleware such as Deliverect. One change goes to DoorDash, Uber Eats and your own channels together, with the right prices for each location.
Menu tools and middleware charge a monthly fee, usually per location; the numbers with sources are in the table above. A master menu across different POS systems is a project we price after the Assessment.
Sizl, a dark-kitchen chain in Chicago, is our US project. For a 16-brand restaurant group in Saudi Arabia, Kuwait, the UK and the US, we're launching its own ordering and delivery. Our Lisbon workday matches the UK and overlaps with US mornings.
Show us your brands and POS systems
We'll tell you what a master menu would take across every location and channel.
a free call, then a 2–3 week Assessment, then Build. The Build estimate is fixed after the Assessment. How our packages work: How we work
Own tech team?Already have a tech team? We build the piece you're missing — the mobile app, the UX, a module — at a fixed price, then hand it over or run it.
Max will reply within 1 business day and suggest a time for a call.


