Menu management for restaurants, a Zayos guide
Published July 2026 · Updated July 26, 2026
Restaurant menu management software is the single system of record for every item you sell: name, price, modifiers, tax class, availability and where each item is allowed to appear. Edit once, and every channel, register and printed ticket agrees by the next order.
Is your menu a document or a database?
Most independent restaurants have a menu that is a document. It exists as a designed PDF, a laminated card, a photo in a text thread with the printer, and a set of buttons somebody typed into the register two years ago. Every one of those is a copy, and copies drift.
The moment you sell online, your menu stops being a document and becomes a database, whether or not anyone in the building decides to treat it that way.
That shift is the entire job of menu management software. Not prettier layouts. A single record per item that everything else reads from: your ordering site, the kitchen screen, the register, each marketplace, the printed ticket. When there is one record, raising a price is one edit. When there are five copies, raising a price is a project, and the project is never finished, because somebody always forgets the one channel they do not check.
There is a smell test. Time yourself raising the price of one item everywhere it appears. Under a minute means you have menu management. Over ten minutes, or a note to yourself to do the rest tomorrow, means you have several menus that happen to agree today.
What is actually inside a menu item?
Ten fields. Most menu software shows you three of them and buries the rest, which is why the other seven are where the money leaks. Read this list against whatever platform you are evaluating and ask where each field lives.
Name and description
What the diner reads, and what a search engine indexes. Also the thing your staff will call something different at the pass.
Base price
One number per channel context. The price on your own site and the price you set to survive marketplace commission are not the same number and should not be forced to be.
Modifier groups
Where menus really break. Each group carries a minimum, a maximum, whether it is required, and whether each option is free or priced. Choose one protein, required, min 1 max 1. Add sauces, optional, max 3, first one free.
Tax class
Hot prepared food, cold grocery, bottled drinks and alcohol are not all taxed the same in every jurisdiction. Set it on the item, not on the order, or your filings will be wrong in a way nobody notices for a year.
Prep time
Per item, not per restaurant. It is what drives an accurate quoted time and the fire time on a scheduled order. A single global number is wrong for most of your menu.
Availability schedule
Breakfast until 11, the burger only after 4, the whole menu off on Mondays. If dayparting lives in a staff member memory, somebody will sell pancakes at 9pm.
Channel visibility
Some items belong on your own site and nowhere else. A high margin family platter you do not want to pay 30% commission on is a visibility rule, not a mistake.
Stock state
In stock, 86 for the shift, or off until you turn it back on. The distinction matters: an item 86ed for the night should come back tomorrow by itself.
Photo and alt text
One clean image per item lifts conversion more than any copy change. Alt text is how the item shows up in image search and how a screen reader user orders from you.
POS identifier
The key that ties this item to the register, so sales reports and your online menu are talking about the same thing. Miss it and reconciliation becomes a monthly hand exercise.
The field that breaks most often is the modifier group, because it is the only one with logic in it. A required group that lost its last option makes an item impossible to add to a cart, and nothing on your dashboard will say so.
Who should be allowed to change the menu?
This is the question that separates software an operator can hand to a team from software only the owner dares touch. Split rights by what it costs when the edit is wrong.
Owner or GM
Everything, including prices, new items, channel visibility and tax class. Should be a short list of people, usually one or two.
Kitchen manager
86 an item, restore it, edit prep times, adjust modifier availability. No pricing rights. This is the role most restaurants forget to create, so the chef either cannot 86 anything or can change your prices.
Shift lead
86 and restore only, for the current shift. That is genuinely all a shift lead needs at 7:15 on a Saturday.
Marketing or agency
Descriptions, photos and alt text. No prices, no availability. Copy edits should never be able to make you lose money.
Two more things belong here. Keep a change log, because "when did this price change and who did it" is a question you will ask on a Monday morning with a chargeback open. And make 86 rights easy to give, because a kitchen manager who has to text the owner to sell out of a dish will simply stop marking anything sold out.
How should a menu change through the day?
Dayparting is availability with a clock attached: breakfast until 11, the grill menu after 4, the family platter on weekends only. Done in software it is invisible and correct. Done by memory it produces the two worst outcomes in takeout, which are selling something you cannot make and hiding something you can.
Every availability rule should live on the item, read the same hours calendar as the storefront, and survive a clock change without a human intervening.
Be careful with the interaction between dayparting and scheduled ordering. If a customer books a Friday lunch on Wednesday, the platform has to check availability against Friday at noon, not against Wednesday at 3pm. Systems that check the wrong clock will either refuse a valid order or sell a breakfast item for a dinner pickup. If you take future orders, test this exact case before you launch, on a real order you refund afterwards.
How do you check your menu for drift?
Twenty minutes, once a week, ideally Tuesday morning. It catches more revenue than any promotion you will run that week.
- 01 Open your own ordering site on a phone like a customer and order your three best sellers. Not a preview mode. The real site, real checkout, refund it after.
- 02 Pull a price list from the register and read it against the online menu line by line. Ten minutes, once a week, catches the drift that costs the most.
- 03 Check every modifier group with a minimum of one. A required choice that lost its options is an item nobody can add to a cart, and it will show up as a mysterious dip in sales rather than as an error.
- 04 Look at what is still 86ed. Items left off from a busy Saturday are the most common cause of "our sales are down on that dish".
- 05 Confirm the dayparted items switch on and off at the right hour, including the day after a clock change.
- 06 Read the item photos on the smallest phone in the building. Half of menu photos fail on a 360 pixel wide screen, which is most of your traffic.
How does Zayos handle menu management?
One menu record per item, edited in one place. Names, photos, modifier groups, hours and scheduling all publish from the same screen out to your branded ordering site on your own domain. On Operator plus Marketplace, that menu also cascades to Uber Eats, DoorDash and Grubhub through Otter, so a price you set once is the price all four channels are selling.
The 86 flow lives on the kitchen tablet, next to the tickets, because that is where somebody is standing when the lamb runs out. The same tablet shows your direct orders, your marketplace orders and your phone ins in one queue, which is the point of running it as a system rather than a checkout widget.
Getting the menu in is usually the part operators dread. There are three routes: an AI import from a photo or PDF of your current menu, which lands around 80% accurate and leaves you tidying the rest, a pull from your register through Otter, or a CSV template. On the Concierge plan we load it for you and send screenshots to confirm, which is how a ninety item menu goes up in an afternoon instead of a fortnight.
Zayos is $499 per location per month for Operator, $599 for Operator plus Marketplace, $699 for Concierge. Month to month, no setup fee, no commission on your orders. The restaurant keeps 100% of food revenue and tips, and the diner pays $0.99 on pickup, $2.99 on delivery, nothing on dine in, and 10% on catering.
Naya Grill in Pompano Beach and West Palm Beach is live on Zayos and taking orders today, keeping $48k+ a year that used to go to commissions at 3,000 orders a month. Storefronts are built and ordering opens at launch for Shishka Lebanese Grill, La Vie Mediterranean, Yummy Grill, aura, Courtyard Cafe, Mr. Smoke and Yalla Market. Most operators are live in under two weeks. See how it works or what Zayos is.
Menu management, answered
What does restaurant menu management software actually do?
Why does a price change take three days to reach every channel?
Should marketplace prices match my own website prices?
Who on my staff should be allowed to change the menu?
How do I 86 an item in the middle of a rush?
How much does menu management cost with Zayos?
One menu. One price. Everywhere.
The free AI report shows what the marketplaces are taking before you change a thing. 60 seconds, no card.