Written by: JJ Tan, Founder, Jelly | Last updated: 12 August 2026
Key takeaways for UK allergen compliance and margins
- UK operators must comply with Natasha’s Law for PPDS items, with full ingredient lists and the 14 mandatory allergens clearly emphasised.
- Live QR menus and connected inventory systems remove the lag and errors that come with static allergen matrices or spreadsheets.
- Platforms that join allergen data with real-time costing protect gross margins by flagging price changes as soon as supplier invoices arrive.
- Fast onboarding and tablet-friendly interfaces cut admin time, with Jelly delivering a complete workflow in as little as one week.
- Ready to replace manual spreadsheets with a single source of truth? See how Jelly connects allergen data to live margins.
UK list of the 14 mandatory allergens
UK food law requires declaration of 14 mandatory allergens whenever they are present in food sold to consumers. The full list is:
- Celery
- Cereals containing gluten (wheat, rye, barley, oats)
- Crustaceans (prawns, crab, lobster)
- Eggs
- Fish
- Lupin
- Milk
- Molluscs (squid, mussels, cockles, whelks, snails)
- Mustard
- Tree nuts
- Peanuts
- Sesame seeds
- Soya beans
- Sulphur dioxide and sulphites (above 10 mg per kg or litre)
For PPDS food, allergens must be emphasised within the full ingredients list using bold, italics, a different font size or a contrasting colour. Ingredients must be listed in descending order of weight using their designated legal names, and the minimum font height is 1.2 mm (0.9 mm where the largest surface area of the packaging is under 80 cm²). For loose food served on plates or packaged after ordering, allergen information must be available verbally or in writing, with written confirmation signposted if given orally.
Static allergen matrix vs live QR allergen menu
A static allergen matrix, whether printed, PDF or spreadsheet, records which allergens appear in each dish at a fixed point in time. Spreadsheet-based allergen systems lack version control, audit trails and alerts, causing silent drift in accuracy that compounds across multiple sites. When a supplier reformulates an ingredient, the matrix stays wrong until someone manually updates it, and multi-unit operators using manual methods see an average lag of 3–7 days.
A live QR menu updates the moment a recipe or ingredient changes. Platforms that tie allergen labels to each dish’s product card push updates instantly to the live QR menu without reprinting the QR code. The margin protection argument stays simple. When ingredient costs change, a live system updates both the allergen declaration and the dish’s gross-profit percentage at the same time. A static matrix updates neither automatically.
Allergy alerts have risen significantly in recent years, and digital allergen management systems provide defensible evidence in the event of an incident in a way that manual processes cannot. For operators running substantial revenue across one or more sites, that combination of live propagation and defensible records creates a strong operational and legal case over a static matrix.
Ready to move from a static matrix to a live system? See the live QR workflow in action and watch allergen updates propagate in real time.
Best allergen and costing app for single-site restaurants
Allergen-specific tools suit single-location restaurants with stable menus and low supplier variability, but they handle compliance on its own. The qualification criteria that matter for a single-site operator are PPDS label generation, live QR menu output, onboarding speed and whether the tool connects to inventory so allergen data and dish costs update together.
Allergenius and MenuIQ both onboard within one to two weeks and handle their respective label or QR functions adequately for a simple, stable menu. FoodCore covers PPDS labelling but requires two to four weeks of setup. Apicbase generates compliant PPDS labels from a central recipe database and suits multi-site groups, but its four-to-eight-week onboarding and enterprise pricing feel disproportionate for a single site. Kitchen CUT carries similar complexity and cost.
For a single-site operator at the £500k+ revenue threshold, margin leakage from undetected ingredient price changes already matters. Jelly onboards in one week and immediately surfaces Price Alerts the moment a supplier invoice arrives. Sushi Revolution used Jelly to set separate target gross profits on dine-in and delivery menus, accounting for 30% delivery commissions, and achieved gross profits 2–3% higher on average. That margin uplift does not appear with a standalone allergen tool.
Understanding which features matter for single-site operators requires clarity on what the law mandates and what remains best-practice guidance.
Natasha’s Law and Owen’s Law software needs in 2026
Natasha’s Law came into force on 1 October 2021 and remains the core statutory requirement for full ingredient and allergen labelling on PPDS food sold by restaurants, pubs, cafés and contract caterers as of 2026. It applies to food packaged on the same premises before the customer selects it, such as sandwiches, salads, pastries, sushi and pasta pots.
The label must include the name of the food, a full ingredients list ordered by weight, and the 14 major allergens emphasised as described earlier. For non-PPDS food, the March 2025 FSA out-of-home guidance recommends providing allergen information in writing and requiring staff to actively ask customers about allergies at the point of order. This guidance remains best practice rather than statute.
Owen’s Law, if enacted, would require the 14 major allergens listed in writing on menus, staff to ask every customer about allergies, and mandatory documented allergen training for all food-handling staff, with a possible timeline of 2027–2028. The FSA began its review of business uptake of the March 2025 guidance in Spring 2026 and will report to ministers later in the year. Operators that already embed written allergen information into live menus will sit in the strongest position regardless of the legislative outcome.
This regulatory direction sets the baseline for how deeply allergen records need to connect with day-to-day kitchen and costing workflows.
Joining allergen data with inventory and costing
Multi-unit operators require centralised control, ingredient-level tracking and the ability to push one change across all locations simultaneously, otherwise allergen data must be reconciled manually across sites and accuracy drifts. Siloed allergen tools that lack a live connection to invoice data cannot detect when a supplier substitutes an ingredient or reformulates a product.
A connected workflow removes that silo by linking allergen accuracy to financial control. Every supplier invoice can be scanned automatically by photo or email, and the system digitises line items without manual entry. When an ingredient price changes, the platform updates both the dish cost and the allergen declaration in every recipe that uses it, because both draw from the same ingredient record. That dual update protects margin and compliance in the same step.
Manual allergen recording introduces three common failure modes: typos in ingredient names, missed updates when recipes change and overlooked allergen sources in compound ingredients. These errors often persist until someone manually audits the records, which usually happens only after a near miss or incident. Automating the link between invoices and recipes removes that manual step, so invoice changes flow through to recipes, PPDS labels and QR menus without extra data entry.
See the full invoice-to-margin workflow in action. Explore Jelly’s invoice-to-margin demo with the team.
Pricing and onboarding speed for allergen platforms
Some platforms charge a flat rate per site per month with no variable charge per user or feature. Onboarding can complete quickly when suppliers email invoices to a dedicated address or the kitchen photographs invoices into the app. POS connections can also follow a straightforward setup.
FoodCore, Allergenius, Apicbase, Kitchen CUT and MenuIQ all publish pricing on application. Apicbase is a paid platform for multi-site groups with an onboarding timeline of four to eight weeks. Kitchen CUT targets large chains with dedicated office teams and carries equivalent complexity and cost. Allergenius and MenuIQ onboard in one to two weeks but do not publish flat-rate pricing. FoodCore requires two to four weeks of setup.
Operators comparing total cost of ownership should add the monthly licence fee to the cost of admin hours that remain manual. When teams spend many hours each month on manual allergen and invoice work, a tool that automates those tasks often becomes cost-effective once revenue reaches a certain level.
Staff tablet access and defensible audit trails
Digital allergen management systems provide defensible evidence in the event of an incident, significantly strengthening operational control. A defensible audit trail needs timestamped records of every recipe change, ingredient substitution and allergen update, which paper folders and spreadsheets cannot credibly produce at scale.
Regulators increasingly design inspection processes on the assumption that digital records created at the point of task will be available. Jelly’s interface suits even the least tech-confident chef, with a clean, tablet-friendly layout where dish costing takes three minutes rather than the industry average of 28 minutes per item. Management and ownership see the same live data independently, which removes the friction of verbal reporting between kitchen and office.
Calorie tracking sits alongside allergen data within the recipe builder. Because ingredient costs, allergen flags and calorie counts all draw from the same scanned invoice and recipe data, a single update flows consistently across every output, including PPDS labels, QR menus, Flash Reports and Xero. With Owen’s Law review under way in 2026 and mandatory documented allergen training a likely future requirement, a system that logs every change with a timestamp gives operators the lowest-risk position for EHO visits or insurance claims.
If your current process relies on verbal assurances or a shared spreadsheet, the audit trail gap already creates a liability. See how Jelly’s timestamped records stand up to inspection.
Frequently Asked Questions
Does Natasha’s Law apply to every dish on a restaurant menu?
No. Natasha’s Law applies specifically to prepacked for direct sale (PPDS) food, which means items packaged on the same premises before the customer selects them, such as pre-made sandwiches, salads, pastries and pasta pots. Dishes cooked to order and served on a plate are not PPDS and are not subject to the full on-pack labelling requirement. However, allergen information for those dishes must still be available verbally or in writing, and the FSA’s March 2025 best-practice guidance for the out-of-home sector recommends written allergen information on menus or via QR code as standard practice.
Who in the business should own allergen management?
Ownership usually sits with the head chef or executive chef for recipe-level accuracy, and with the owner or operations manager for compliance oversight and audit trail integrity. In practice, both functions need to share a single system. If allergen data lives in a chef’s spreadsheet and margin data lives in the finance team’s accounts package, neither party has a complete picture. A platform that connects invoice scanning, recipe costing and allergen declaration in one workflow removes the handoff risk and gives both roles live access to the same verified data.
How much should a restaurant budget for allergen management software?
Standalone allergen tools vary widely and most publish pricing on application, which makes direct comparison difficult. The more useful budget frame is total cost, meaning licence fee plus the staff hours that remain manual. When manual allergen and invoice administration takes considerable time, a tool that automates the full workflow can cost less overall than a cheaper licence that leaves significant manual work in place. Operators should also factor in the cost of a single allergen incident, including legal exposure, reputational damage and insurance implications, when assessing whether a free or low-cost tool provides adequate protection.
What is the difference between a PPDS label and a QR allergen menu?
A PPDS label is a physical on-pack label required by Natasha’s Law for food packaged before the customer orders it. It must include the food’s name, a full ingredients list in descending order of weight and all 14 mandatory allergens emphasised in bold, italics or a contrasting colour. A QR allergen menu is a digital menu accessed by scanning a code at the table, and it displays allergen information for dishes cooked to order. It is not a statutory requirement under current law, though it satisfies the FSA’s March 2025 best-practice guidance for written allergen disclosure. The operational advantage of a live QR menu over a printed allergen matrix is that it updates instantly when a recipe or ingredient changes, without reprinting.
Will Owen’s Law change what software restaurants need?
If the proposed Owen’s Law requirements described earlier are enacted, with a possible timeline of 2027–2028, operators will need written allergen information on menus, staff prompts at order and documented training. Businesses already using a platform that generates live written allergen information on digital menus and maintains a timestamped audit trail of every recipe change will require minimal adjustment. Those relying on verbal assurances or static printed matrices will face significant remediation work. The FSA is reporting its review of current business uptake to ministers later in 2026, so the legislative direction should be clearer by early 2027.
If this guide has highlighted a gap in your current allergen and margin workflow, the next step is a direct conversation. Talk to Jelly and see the invoice-to-margin workflow on your own menu data.