Staff should be able to publish a correction immediately when it removes an immediate ordering problem or fixes a low-risk display error. Price changes, new offers, ingredient claims, and changes that affect several locations should normally go to the owner or a named backup first. For an urgent food-safety concern, staff should be able to remove the affected item from ordering while the facts are checked.
The useful dividing line is not who typed the edit. It is what the edit could cost, what it promises guests, and whether waiting creates a bigger problem. Put those limits in a short restaurant menu change approval process that the shift team can use without guessing.
Classify changes by risk and urgency
Start with three questions: Can a guest place a bad order if we wait? Does the edit change what a guest pays or receives? Does it make a claim about ingredients or preparation that needs verification? The answers determine whether staff should publish, temporarily remove an item, or request approval.
Routine changes can include fixing a misspelled dish name or correcting a broken line in a description, provided the edit does not change the meaning. A manager can also mark a sold-out item unavailable when the kitchen confirms it is gone. That is different from deleting a dish permanently or substituting an ingredient.
Urgent changes need a fast route. If the kitchen reports a possible problem with an ingredient, the shift lead can take the affected item out of ordering immediately and notify the owner. Restoring it or adding an ingredient statement should wait until the person responsible for the recipe confirms the facts. Do not have a staff member guess at an allergen description to get the item back online.
Financial changes include base prices, add-on prices, discounts, minimums, and delivery charges. Set a specific threshold if you want managers to handle small price corrections. Otherwise, require approval for every financial change. Either choice is workable; an unwritten limit is not.
The kitchen supplies availability and recipe information. The person responsible for pricing supplies the approved amount and effective time. The shift lead checks urgency and publishes within their authority. The owner sets the limits and names a backup. For a restaurant website connected to online ordering, also identify every place a guest might see the item: a menu page, an ordering screen, and any other channel the restaurant maintains.
Put authority and a backup in a matrix
The matrix below is a hypothetical starting policy for one restaurant. Adjust the roles and limits to fit your operation. “Publish” means making a change visible to guests; a staff member can prepare an edit for approval without publishing it.
| Change | Immediate action | Who approves publication | Follow-up |
|---|---|---|---|
| Spelling or formatting; meaning unchanged | Shift lead corrects it | No prior approval | Record and sample in the weekly check |
| Item sold out or potential ingredient concern | Shift lead makes item unavailable | No prior approval for removal | Notify owner; confirm facts before restoring |
| Small price correction below both $1 and 5% | Manager checks the approved price | Manager | Tell owner and record the source |
| Price change of $1 or more, or 5% or more | Prepare the change; do not publish yet | Owner or named backup | Record approval and effective time |
| New offer, ingredient claim, or permanent menu removal | Gather details; pause affected item if urgent | Owner or named backup | Verify terms or recipe before publication |
The price rule uses two triggers: reaching either limit requires owner or backup approval. For example, changing an item from $10 to $10.40 is a $0.40 increase, or 4%, so the manager can publish it under this policy after checking the approved price. Changing an item from $20 to $21.20 is a $1.20 increase, or 6%, so it needs owner or backup approval. These are price-change thresholds, not estimates of processing fees or operating costs.
Define the backup by name or role, not “whoever is available.” Give that person the same written limits and a way to reach the kitchen. If neither approver responds, the pending price or promotion stays unpublished. An urgent availability removal can still proceed; that exception should not become permission to rewrite prices or ingredient claims.
Also decide whether the threshold applies per item, per order, or per batch. A sensible policy is to assess each price change and send a group of changes for approval when the combined edit affects the menu broadly, even if each individual adjustment is small. Bundles, add-ons, and discounts deserve review because the guest's final price may change even when the main dish price does not.
Before relying on the matrix, ask your software provider who can edit and publish, whether permissions can be separated, and how a backup gets access. If the tool cannot enforce the distinction, use a shared approval message or another record outside the tool. Give publishing access only to people the restaurant trusts to follow the policy.
Keep a record that makes corrections possible
A useful change record is short enough to complete during service and detailed enough for another person to reverse the edit. Keep it in a shared location the owner and backup can reach. For each change, capture:
- The item, affected menu or ordering channel, and date and time.
- The previous and new wording, price, or availability status.
- The reason for the change and the person who requested it.
- The source of the information, such as the kitchen lead or an approved price list.
- The person who published it and, where required, the approver and approval time.
- The guest-facing check, any correction, and the person who completed it.
For example, a shift lead might record that the kitchen reported the soup sold out at 6:15 p.m., that the lead made it unavailable on the ordering menu at 6:18 p.m., and that the owner was notified. The next shift should record who confirmed it was ready to sell again and when it was restored. If another menu page still lists the soup, the record should identify that page and who will update it.
For a wrong price, preserve the old and intended values before correcting the listing. Record when the correction appeared and tell the manager about any orders that may need individual attention. Follow the restaurant's normal guest-resolution process; changing a menu listing does not automatically settle an existing order.
Keep the record limited to operational details. Avoid copying guest payment information or unnecessary personal details into a menu-change log. Ask your provider whether its own history shows previous values, publishers, and timestamps, and whether you can retrieve that history when needed. If it does not, the restaurant's record becomes more important.
Check a sample and practice before a live shift
At a regular interval, have someone other than the publisher review a sample of changes against the matrix and the guest-facing menu. A small restaurant might review several changes each week, including at least one urgent removal and one approved price change when those occurred. If the sample finds a problem, expand the review to similar edits rather than assuming the mistake was isolated.
Check four things: the edit had the right approval, the published value matches its source, the change appears in the intended channels, and the record shows who will handle any correction. Open the menu as a guest would, including on a phone. Read the item name, description, options, availability, and displayed price together; a correct main price does not help if an old add-on price remains visible.
Run a simulated check before assigning the policy to a new shift lead. Use a written scenario or a nonpublic practice environment: a dish is unavailable, an owner-approved price needs updating, and a recipe description is in question. Ask the lead which action can be published immediately, which needs approval, and what belongs in the record. The simulation must not create a real payment, guest message, or courier dispatch. If no safe practice environment is available, walk through the steps on paper.
A simulation checks whether the team understands the rule; it does not prove that the live menu will behave as expected. For a live service pilot, start with a limited set of authorized changes, have the owner or backup available, and check the published result promptly. Use real edits only when the restaurant actually intends to make them, and keep a correction route ready.
Use the matrix to review your current permissions and change log. Then ask Fleksa about online ordering, including whether the setup you need is available in the US and how your team would manage and verify menu edits.
Related guide: Choose Between an HTML Menu and a PDF Menu.
Frequently asked questions
Can staff mark an item unavailable without owner approval?
Yes, if your written policy gives them that authority. Require a reason, a record, and notification to the owner. Assign someone to confirm when the item can return.
Should every menu price change need owner approval?
Not necessarily. An owner can authorize a manager to make small, verified corrections within a clear limit. Larger changes, promotions, and broad batches can still require owner or backup approval.
What if our software cannot separate editing from publishing?
Use an external approval record and limit publishing access to trusted staff. Ask the provider what permissions and change history are available, then check published edits against the record.
