UK Allergen Labelling at the Register: Natasha's Law Compliance

What Natasha's Law Means for Small Food Retailers#

Natasha's Law — formally the UK Food Information Amendment — came into force in October 2021 following the death of Natasha Ednan-Laperouse from an allergic reaction to a Pret A Manger baguette that did not list sesame as an ingredient. The law requires any food that is prepacked for direct sale (PPDS) to carry a label listing every ingredient, with the 14 major allergens emphasised in bold, italics, or capitals. PPDS means food that is packaged at the same premises where it is sold before a customer selects it — sandwiches wrapped in a deli, salads boxed in a café, or cakes sliced and cling-filmed in a bakery. The penalty for non-compliance can reach an unlimited fine and, in serious cases, imprisonment. For small food retailers, compliance is not optional, but it is operationally complex. A café offering 15 sandwich varieties, each with different bread, fillings, and sauces, must maintain accurate ingredient lists for every combination. When a supplier changes a sauce recipe — swapping sunflower oil for rapeseed oil, for example — the label must update immediately. Manual label management using word-processing templates breaks down at this scale because there is no systematic link between the ingredient data and the point of sale. Items get sold with outdated labels, new menu additions go out unlabelled, and seasonal specials bypass the labelling process entirely because staff are too busy to create a new template during the morning rush.

Storing Allergen Data at the Product Level in Your PoS#

The foundation of PoS-driven allergen compliance is a product database where every PPDS item has its full ingredient list stored alongside the usual fields like price, category, and barcode. Each ingredient entry flags which of the 14 major allergens it contains: celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, nuts, peanuts, sesame, soybeans, and sulphur dioxide. When a product is created or edited, the system requires the allergen fields to be completed before the item can be marked as active for sale. This prevents the common gap where a new menu item is added to the PoS for pricing purposes but sold before anyone creates its label. The allergen data should be version-controlled so that when an ingredient changes — a new bread supplier whose flour contains soy, for instance — the old version is archived and the new version takes effect with a clear timestamp. This version history becomes critical during inspections or, in the worst case, an allergen incident investigation. Environmental health officers want to see not just today's label but the label that was in use on the date of a reported reaction. A PoS that maintains this history provides evidence of due diligence, which can be the difference between a warning and a prosecution.

Auto-Generating Compliant Labels From the PoS#

Once allergen data lives in the PoS product database, the system can generate labels that meet the formatting requirements of Natasha's Law automatically. The label must include the product name, a full ingredient list in descending order of weight, and every allergen emphasised so it stands out from the surrounding text. A thermal label printer connected to the PoS can produce these labels on demand or in batch runs at the start of the preparation shift. The workflow is straightforward: the kitchen or deli team prepares the day's PPDS items, scans or selects each product on the PoS, and prints the corresponding label. If the product record is incomplete — missing an ingredient, or containing an ingredient not yet mapped to its allergen flags — the system refuses to print and displays a warning. This hard block is the single most important compliance safeguard because it prevents unlabelled items from reaching the display case. For businesses with rotating menus or daily specials, the PoS should support recipe-based label generation. The operator enters the special as a combination of stored ingredients, the system compiles the full ingredient list, flags allergens, and prints a label — all within the time it takes to wrap the item. AskBiz includes a label-printing module designed for exactly this workflow, with templates that conform to UK Food Standards Agency guidance on font size, allergen emphasis, and layout.

Blocking Unlabelled Sales and Building an Audit Trail#

A compliant label on the shelf means nothing if staff can still ring up an unlabelled item at the till. The PoS should enforce a rule that any product flagged as PPDS cannot be sold unless its allergen label status is marked as printed and current. If the label was last printed before an ingredient change, the system should require a new label print before allowing the sale. This creates a closed loop: no label, no sale. The audit trail generated by this process is invaluable. Every label print event is logged with the product, the ingredient version, the timestamp, and the staff member who initiated it. Every sale of a PPDS item is linked to the label version that was active at that moment. If a customer reports an allergic reaction and environmental health officers investigate, the retailer can produce a complete record showing exactly which ingredients were listed, when the label was printed, and which staff member handled the transaction. Without this trail, the retailer is left arguing from memory and paper records that may or may not be complete. The Food Standards Agency has made clear that demonstrating a robust allergen management system — not just having labels — is central to proving due diligence. A PoS that enforces labelling rules and logs every action provides exactly this evidence.

Training Staff and Handling Supplier Ingredient Changes#

Technology alone does not guarantee compliance. Staff must understand why allergen labelling matters and how the PoS enforces it. Training should cover the 14 major allergens, the consequences of mislabelling, and the specific PoS workflows for creating products, printing labels, and handling label-block warnings. New staff should not be able to process PPDS sales until they have completed allergen training, a restriction the PoS can enforce through role-based permissions. Supplier ingredient changes are the most common source of labelling errors. A bakery sourcing sandwich bread from a local supplier may not discover that the recipe now includes milk powder until a customer with a dairy allergy reacts. The mitigation is a supplier-change workflow: when a delivery arrives with updated ingredient information, the staff member flags the affected products in the PoS, the system marks their labels as outdated, and no further sales are allowed until the ingredient list is updated and new labels are printed. This takes discipline, but the PoS makes the discipline enforceable rather than aspirational. AskBiz supports supplier-linked ingredient management, so when a supplier notifies you of a recipe change, the system automatically flags every product using that ingredient and queues new labels for printing before the next sales shift.