Ingredient Reviews & Shelf-Life: Keeping Supplier Data Current
The ingredient data in your system is not a one-off setup — it decays. Suppliers reformulate, change sites and update their allergen declarations, and every one of those changes can quietly make your labels and allergen matrix wrong. This guide explains why ingredient and allergen data drifts out of date, the compliance risk that creates, how to run a practical review cycle, and how FoodCore's ingredient review reminders keep the whole thing on schedule.
Why ingredient data goes out of date
When you first set up an ingredient — say a bag of ready-grated cheese or a bought-in brioche bun — you record its allergens, its ingredients declaration and, often, its cost and pack size. At that moment the record is accurate. The problem is that the world behind that record keeps moving, and nothing on your shelf tells you when it has.
Three forces cause ingredient data to drift out of date, and understanding them is the first step to controlling them:
- Reformulations. Manufacturers change recipes constantly — to cut costs, substitute an oil, add a stabiliser, or respond to their own supply issues. A reformulation can add or remove an allergen, change the order of the ingredients list, or alter a "may contain" statement, all without a visible change to the pack.
- Supplier and site changes. A manufacturer may move production to a new site or a new co-packer that handles different allergens, changing the cross-contamination profile. You might also switch to a cheaper "like-for-like" supplier whose product in fact carries a different allergen set.
- Specification and shelf-life updates. Suppliers periodically reissue specifications with new nutrition figures, new date-coding advice or a changed shelf life. These updates are easy to miss if you are not actively looking for them.
The common thread is that the change originates outside your business, arrives without fanfare, and only becomes visible if you have a process that goes looking for it. That process is an ingredient review cycle.
The compliance risk: your labels are only as current as your ingredients
Under Natasha's Law, every PPDS product must carry a full ingredients list with all 14 allergens emphasised. In any modern system, that label is generated from the recipe, and the recipe pulls its allergens and ingredient declarations from your ingredient records. This chain is the reason ingredient data currency is a compliance issue, not an administrative one.
Consider the sequence: a supplier reformulates a chocolate coating to add sesame. You are not notified, or the notification sits unread in an inbox. Your ingredient record still says "no sesame." Every recipe using that coating still declares no sesame. Every PPDS label you print for those products understates the allergens. If a sesame-allergic customer relies on that label, the consequences can be severe — and the audit trail will show that your ingredient data had not been reviewed.
This is why the Food Standards Agency expects food businesses to keep allergen information accurate and to be able to demonstrate that their procedures are working. A documented review cycle — showing when each ingredient was last checked against the current supplier specification — is exactly the kind of evidence that demonstrates active, current allergen management rather than a static setup left to rot.
Ingredient review versus shelf-life review
The two are related but distinct, and it helps to keep them separate in your head:
- Shelf-life review concerns your finished product: how long it stays safe and of good quality, which drives your date coding and stock rotation. This is informed by your own testing and by supplier guidance on ingredient life.
- Ingredient data review concerns bought-in ingredients: whether the allergens, ingredients list and specification you hold are still accurate against the supplier's current spec.
They connect at the edges. A supplier changing an ingredient's shelf life is often a signal that something else — a preservative, a process — has changed too, which should trigger an ingredient data review. And your finished-product shelf life depends on ingredient data being right in the first place. Run both on a schedule; do not assume that reviewing one covers the other.
How to run an ingredient review cycle
A review cycle does not need to be elaborate. It needs to be defined, risk-based and consistent. Here is a practical structure for a small UK food business.
1. Set a review window
Decide how often each ingredient should be reviewed. A sensible default is every 12 months for standard ingredients, tightened to every 6 months for anything carrying one of the 14 allergens or supplied by a manufacturer prone to reformulation. The window should reflect risk, not convenience.
2. Trigger reviews on events, not just the calendar
Beyond the scheduled window, certain events should force an immediate review: a supplier change notification, a switch to a new supplier, a delivery that arrives with different packaging or a changed declaration, or any customer allergen query that exposes uncertainty.
3. Check against the current supplier specification
When an ingredient comes up for review, compare your stored record against the supplier's latest specification sheet — not the one you filed two years ago. Confirm the allergens, the ingredients list, the "may contain" statement, and any nutrition or pack-size details you rely on.
4. Record the review and the date
Mark the ingredient as reviewed and record the date. This is the step that turns an activity into evidence. Without a dated record, you cannot demonstrate to an auditor that the review actually happened.
5. Propagate any changes to recipes and labels
If the review turns up a change — a new allergen, a reworded declaration — update the ingredient, let it flow through to every recipe that uses it, and regenerate the affected labels before those products go on sale.
A simple review schedule
How FoodCore keeps ingredient data current
The weak point in any manual review cycle is memory. Nobody remembers that a specific ingredient was last checked 14 months ago. FoodCore is built to remove that dependence on memory by tracking review status for you and surfacing what is overdue.
Set a review window, then let the Alerts tab do the watching
In FoodCore you set a review window for your ingredients. The Ingredients → Alerts tab then lists anything that has not been updated or reviewed within that window — the overdue queue, always current, without you having to scan a spreadsheet of dates. A banner on your dashboard links straight to it, so an overdue ingredient is visible the moment you log in rather than buried in a settings page.
One-click "Mark reviewed"
When you have checked an ingredient against the current supplier specification, you press Mark reviewed. That single click resets the review clock for that ingredient and stamps the review date. There is no separate log to maintain — the act of confirming the review is the act of recording it.
Fast re-checking with barcode scan import
When a reformulation lands and you need to refresh an ingredient, FoodCore's barcode scan import reads the product barcode and pulls in the full nutrition and allergen data, so most of the re-entry is done for you. You still confirm the imported data against the supplier specification — barcode databases can lag a manufacturer's latest formulation — but it removes the manual typing. Once refreshed, the ingredient re-enters the review cycle like any other.
A note on the bulk-buying helper
FoodCore also includes a bulk-buying helper: enter how many packets are in a bulk pack and it shows you the per-packet size and cost. This is a purchasing convenience for planning your shopping — it is guidance only and never affects your recipe costings. It is worth knowing it exists, but it sits alongside, not inside, the ingredient review process.
Ingredient review checklist
- Have you set a review window that reflects each ingredient's risk?
- Do you check overdue ingredients against the supplier's current specification?
- Do you review immediately on a supplier switch, reformulation notice or changed delivery?
- Do you record the date each ingredient was reviewed?
- When a review finds a change, do you propagate it to recipes and regenerate affected labels before sale?
- Can you produce a dated record of your reviews for an EHO or auditor?
- Are new suppliers reviewed before their ingredient is first used in a recipe?
Ingredient reviews and shelf-life: frequently asked questions
Why does ingredient and allergen data go out of date?
Ingredient data drifts out of date for reasons outside your control. Suppliers reformulate products, change manufacturing sites, switch co-packer, or alter their "may contain" statements. You may also switch supplier for a like-for-like ingredient that carries a different allergen profile. Each event can change the allergens or ingredients declaration of a product without any visible change on the shelf. Unless you review supplier specifications on a regular cycle, the data in your system slowly diverges from reality.
How often should I review ingredient and supplier data?
There is no single legal interval, but a practical baseline is to review every ingredient at least once every 12 months, and high-risk ingredients — anything carrying one of the 14 allergens, or from a manufacturer prone to reformulation — every 6 months. Review immediately whenever a supplier notifies you of a change, whenever you switch supplier, and whenever a delivery arrives with different packaging or a different declaration. Set a review window that reflects your risk, then run the cycle consistently.
What is a shelf-life review versus an ingredient data review?
A shelf-life review concerns how long your finished product stays safe and of good quality, and drives your date coding and stock rotation. An ingredient data review concerns whether the information you hold about a bought-in ingredient — its allergens, ingredients list and specification — is still accurate. Both should run on a schedule. A supplier changing an ingredient's shelf life is one of the events that should trigger an ingredient data review, because reformulations often accompany changes to product life.
How does keeping ingredient data current affect Natasha's Law compliance?
Natasha's Law labels are only ever as accurate as the ingredient data behind them. A PPDS label is generated from your recipe, and the recipe pulls allergens and ingredient declarations from your ingredient records. If a supplier adds sesame in a reformulation and you have not reviewed that ingredient, your label will understate the allergens — a serious compliance failure. Keeping ingredient data up to date through a review cycle is the foundation of accurate labelling and allergen declaration.
How do FoodCore's ingredient review reminders work?
In FoodCore you set a review window — for example, every 12 months. The Ingredients → Alerts tab then lists anything not updated or reviewed within that window, and a banner on your dashboard links straight to it. When you have checked an ingredient against the current supplier specification, you use the one-click "Mark reviewed" button to reset the clock. Ingredient exports include Last Updated and Last Reviewed dates, so you can produce a dated record of your review activity for an EHO or auditor.
Can I import ingredient and allergen data automatically?
Yes. FoodCore's barcode scan import reads a product barcode and pulls in the full nutrition and allergen data for that ingredient, which speeds up initial setup and re-checking after a reformulation. You still confirm the data against the supplier specification, because barcode databases can lag behind a manufacturer's latest formulation, but it removes most of the manual typing. Once imported, the ingredient enters your review cycle like any other record.
Does software replace my legal duty to manage allergens?
No. Software like FoodCore assists you in running and documenting an ingredient review process — it flags what is overdue, records when you reviewed each ingredient, and keeps your labels in step with your recipe data. But the legal responsibility for accurate allergen information and safe food remains with the food business operator. Software is a tool that makes it far easier to meet that duty consistently; it does not transfer or replace it.
Further resources
FoodCore is kitchen management software built for small UK food businesses. We handle recipe costing, Natasha's Law labels, allergen matrices and order tracking.
Start free trial →