Allergens overview
CostingBrik tracks the 14 UK-regulated allergens at the ingredient level and rolls them up automatically to every recipe that uses them. The result is a verifiable, always-current allergen declaration for each menu item, built from the same supplier and recipe data you are already maintaining for costing.
Allergen tracking is available for UK businesses.
The 14 UK-regulated allergens
Brikly tracks the full Food Standards Agency list:
celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, nuts, peanuts, sesame, soybeans, and sulphur dioxide and sulphites.
How the model works
Allergen declarations live per supplier variant, not per ingredient. Two suppliers of the same ingredient can have different cross-contamination risks - for example, one brand of oats may be certified gluten-free while another is not - so each supplier on an ingredient carries its own declaration.
For each ingredient, recipes combine the allergens of every SKU you buy: every active supplier SKU, at every site, because the kitchen may use any of them. Archived SKUs don't count. Your preferred SKU sets the cost and the ingredients list printed on PPDS labels, and nothing else.
- The ingredient detail page's Allergens tab leads with the combined allergens, and lists every SKU you buy with how its allergens compare with your preferred SKU's.
- Recipes roll up the combined allergens of each ingredient they use.
- Sub-recipes contribute their own roll-up, so nested recipes are handled automatically.
An ingredient counts as declared only when every SKU you buy is declared. While one isn't, recipes using the ingredient read as allergens not fully known and their PPDS labels can't print, though the allergens known so far still show. Declare that SKU, copy a declaration onto it with Same as, or archive it if you no longer buy it. Switching the preferred SKU between SKUs you already buy changes nothing for allergens.
The exception: ingredients with no supplier. Some ingredients have no supplier at all, such as tap water, ice or bay leaves from the garden (see free ingredients). Your business declares their allergens on the ingredient itself, from the Allergens card on its Allergens tab. That declaration applies only while the ingredient has no active SKU: once you add a supplier, the supplier's declaration is used instead. See declaring allergens.
Brikly keeps a copy of each ingredient's combined allergens for its recipes to use. An ingredient only counts as declared when that copy is declared and matches what its SKUs declare now. Straight after a change the two can differ for a moment, and the ingredient reads as not declared until they match again.
Three states for a declaration
A declaration, on a supplier or on an ingredient with no supplier, can be in one of three states:
- Not yet declared - no one has reviewed this supplier (or, for an ingredient with no supplier, the ingredient) for allergens. Unless the supplier is archived, any recipe using it reads as allergens not fully known, is left out of "no ingredients containing" filters on the allergen matrix and kiosk, and can't print a PPDS label.
- Declared allergen-free - explicitly confirmed as containing none of the 14 regulated allergens. Stamped with a timestamp so you can see when it was last reviewed.
- Declared with allergens - one or more of the 14 allergens are recorded. Also stamped with a review timestamp.
The "not yet declared" state is deliberately distinct from "declared allergen-free" - silence is not a safe default. Recipes show an amber warning when any ingredient anywhere in the recipe, sub-recipes included, is still undeclared. Their allergens are not fully known until every ingredient is declared.
Where allergens appear
- Ingredient detail page - on its Allergens tab, the Allergens card shows the allergens recipes get from every SKU you buy, names the SKUs behind an allergen only some of them contain, and says how many recipes use the ingredient. Under Other SKUs you buy it lists every other SKU with its status (Same as preferred, Differs or Not declared), and says why recipes list an allergen your preferred SKU doesn't contain. An ingredient with one SKU (or none) that isn't declared yet gets the question straight away: Contains none of the 14 or Pick allergens. With several SKUs, each one not declared yet is named on the card with Declare, and Same as when there's a declaration to copy. For an ingredient with no supplier, the card is where you declare its allergens. Below it, the Ingredients list card shows what's actually in a packaged product, the way it prints on a PPDS label, and feeds allergens upward. See declaring allergens.
- Allergens form - where declarations are actually made or changed, in place of the Allergens tab's cards. Opened from the Allergens card, from a SKU under Other SKUs you buy, from the Ingredients list card, or from a supplier's allergen summary on Ingredient details. It asks what the product is, holds its ingredients list, then the allergens, one SKU at a time. Team members with view-only access can open it to read, but not change anything.
- Recipe Allergens tab - the consolidated contains / not fully known view, with a per-source breakdown showing which ingredient (or sub-recipe) contributed each allergen, and which still need review.
How this feeds into SafetyBrik
Allergen declarations made in CostingBrik are the source of truth for the wider Brikly platform. SafetyBrik consumes the same recipe roll-up to power allergen matrices, customer-facing menus, and staff training - so once you have declared a supplier in CostingBrik, every other surface stays in sync automatically.
The deep link from SafetyBrik back to a recipe's Allergens tab is the round-trip: review the matrix in SafetyBrik, jump straight into CostingBrik to fix any gaps, and the matrix updates within moments of the declaration being saved. While the change is applied, normally a few seconds, the affected recipes show as recomputing: allergens already on record stay on show, but nothing is shown as free from an allergen until the recompute finishes.