Menu management connects what the customer sees with what the kitchen can make. The POS or another nominated platform should hold controlled records for items, modifiers, prices, availability, tax treatment, station routing and customer-facing information.
This hub separates three related tasks: synchronising menus across channels, managing availability and sold-out rules, and diagnosing online menu design mistakes.
Related guides
- POS and Kitchen Systems — the main guide for the wider topic.
- How to Plan Menu Availability and Sold-Out Rules — a detailed next step for putting this guidance into practice.
- How to Sync Menus Across Channels — a detailed next step for putting this guidance into practice.
- Kitchen Display Systems — a closely related operational control to review alongside this page.
- POS Data and Reporting — a closely related operational control to review alongside this page.
- How to Handle Allergens Online — a connected decision that can change the recommended approach.
Define the source of truth
Choose the system authorised to create and change each field. The source may differ by field, but responsibility must be explicit.
| Field | Control required |
|---|---|
| Item and modifier IDs | Stable identifiers across integrations |
| Customer name and description | Clear language without unsupported claims |
| Kitchen name | Short, unambiguous production wording |
| Price and tax treatment | Effective date, channel rule and approval |
| Availability | Location, channel, daypart and ingredient dependency |
| Station route | Every component reaches the correct kitchen output |
| Allergen information | Named owner, recipe control and update process |
Use controlled menu changes
- Record the requested change and owner.
- Confirm affected items, modifiers, bundles and channels.
- Set an effective date and rollback plan.
- Test in a non-live environment or limited location where possible.
- Publish and verify customer-facing, POS and kitchen output.
- Monitor errors and customer contacts.
- Retain an audit trail of material changes.
Separate shared and channel-specific fields
Some differences are legitimate:
- channel-specific price or promotion;
- shorter marketplace description;
- delivery-only packaging option;
- location-specific availability;
- products intentionally excluded from a channel.
Store the reason for each exception. Uncontrolled exceptions become permanent inconsistencies.
Build modifiers around valid kitchen choices
Modifiers should represent combinations the kitchen can produce and the customer can understand. Avoid free-text fields when a structured choice is safer. Test defaults, maximum selections, extra charges, substitutions and preparation routing.
Control availability close to the operation
The person who learns that an ingredient, item or station is unavailable needs a quick, authorised method to change availability across affected channels. The system should show whether the update succeeded and provide a manual fallback when synchronisation fails.
Protect allergen information
Digital systems can distribute allergen information, but they do not replace recipe control, supplier updates, staff training or cross-contact procedures. The business must define who approves information and how urgent changes reach every active channel.
Choose the next guide
- How to Sync Menus Across Channels: design integrations, exceptions and verification.
- How to Plan Menu Availability and Sold-Out Rules: prevent unavailable orders and manage dayparts.
- Online Menu Design Mistakes: diagnose customer-facing structure, modifiers, pricing and information.
Weekly menu-control review
- items with different prices or names across channels;
- sold-out states that did not propagate;
- modifier errors;
- failed or delayed publishing jobs;
- refunds caused by menu data;
- items appearing at the wrong station;
- unapproved descriptions or dietary claims;
- orphaned products and old promotions.
Menu migration controls
Before moving to a new POS or menu platform:
- export the current menu and identifiers;
- archive price and tax history where required;
- remove obsolete items deliberately rather than accidentally;
- map modifiers and bundles at field level;
- test allergen information and dietary labels;
- confirm kitchen routes and receipt names;
- retain a known-good rollback file.
Permissions and segregation of duties
| Role | Typical authority |
|---|---|
| Shift manager | Temporary sold-out changes and controlled restoration |
| Menu owner | Items, modifiers, descriptions and routing |
| Finance or owner | Prices, tax mappings and promotion approval |
| Food-safety owner | Recipe and allergen-information approval |
| Supplier support | Time-limited technical access with an audit trail |
Measure menu-data quality
Track refunds caused by unavailable products, modifier corrections, failed publishing, items routed to the wrong station, price disputes and customer questions caused by unclear descriptions. These are operational costs of poor menu governance.
Practical next step: select ten high-volume and five complex products. Trace every field from the source system to customer display, kitchen output, receipt and report. Fix the ownership gaps before attempting a full menu migration.
Official UK guidance
- Food Standards Agency: Allergen guidance for food businesses
- Food Standards Agency: Starting your food business safely
Guidance checked: 24 July 2026. Official requirements and business processes should be rechecked when the menu, recipe, packaging or sales channel changes.
