Custom software for BRCGS traceability and mass balance
BRCGS requires a traceability test that shows you can trace both forwards and backwards, including mass balance, within four hours. Most companies manage it, but with two people, a stack of printouts and an afternoon. Four hours is not a performance requirement; it is a test of whether the data is held together.
Where the four hours fall apart
BRCGS Food Safety is on Issue 9, mandatory for audits since early 2023. That version has a limited set of fundamental requirements, and traceability is one of them. A major non-conformity against a fundamental requirement is a different kind of problem from an ordinary deviation: it affects the certification itself, not just the grade.
The test has two halves, which fail in different ways. Tracing forwards and backwards is a search: which raw material batches went into this finished product, and where did that finished product go. That usually works, provided everything has been recorded. The mass balance is the calculation around it: does what came out match what went in, including waste and rework. That is where it more often fails, because rework and residual batches are precisely the things nobody records.
What the four hours really measure is whether the link between batches was recorded at the moment it arose. If that relationship is there, the trace is a lookup that takes seconds. If it is not, it becomes a reconstruction from production lists, weighing slips and a shift leader's memory, and four hours is tight. No reporting package fixes that after the fact.
How we build this
The link between incoming and outgoing batch is the whole job. The trace is then just a lookup.
Every step where a batch is combined or split must record that relationship. One missing link makes the entire chain unusable, even if everything else is perfect.
Leftover batches that go back onto the line are the most common break. We start there, because that is where a mass balance fails to close in practice.
Not once a year at the test, but per production order. That way a deviation surfaces on the day itself, while someone still remembers what happened.
We run the traceability test on random batches from the past and measure how long it takes. Anything that gets stuck now will get stuck with the auditor later too.
What the software actually does
The register of batches and their relationships underpins everything. What else you need depends on your process and on what is already being recorded.
Batch linking recorded at the point of handling
Which inbound batch ends up in which outbound batch is recorded at the moment it happens. Reconstructing it afterwards is the reason the test takes four hours.
Forward and backward traceability
From finished product to all raw material batches, and from raw material batch to all customers, in a single query. That is the half of the test that simply works when there is no gap.
Mass balance per order
What went in against what came out, including waste and rework. Continuous calculation shows a deviation on the day itself rather than at the annual test.
Root cause analysis with preventive action
After an audit, short deadlines apply for correction, root cause analysis and a prevention plan. Under BRCGS, a correction without a root cause is not accepted as closed.
Post-audit deadline monitored
From the end of the audit, a short period runs in which everything must be submitted. That deadline belongs in the system, not in someone's diary.
Connecting to production and inventory
Batches originate in your production system or your connected systems. We pull them from there, because a second entry creates a second version of the truth.
Who we build for
Where the chain breaks differs per process. Four situations.
Production and processing
Blending, rework and leftover batches make the balance difficult. Here the gain lies in recording what goes back onto the line.
Storage, repacking and distribution
Batches are split into smaller units and go to many customers. The challenge is keeping the outbound side complete, not the inbound.
Private label for retail
Your customer sets its own traceability requirements on top of the standard and tests them as well. Two frameworks on one record is then the difference between work and double work.
Sites with multiple production lines
A batch that moves between lines or sites is where the chain usually breaks. Checks on the shop floor run through the batch linking app.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
Standards are revised and clause numbers shift as a result. Everything to do with requirements, deadlines and tolerances should be configurable and stored per version.
Why Appfront
The trace is created while the work is done
We build the batch link recording to happen at the moment itself. A reporting package cannot invent a missing link after the fact.
The mass balance is where it goes wrong
We have it calculated continuously rather than once a year. A deviation from last week can still be investigated; one from last quarter cannot.
The cause belongs with the correction
We build root cause analysis and preventive action into the flow, because a correction without a cause does not count as closed.
We rehearse the test
We run the trace on random batches and measure the time. That is the only way to know whether four hours is achievable.
Security and privacy
A batch register exposes your recipes and your suppliers: anyone who can see which raw material batches went into which finished product knows your composition. We set access by role, give a customer in a portal only their own shipments, and log every view.
For traceability, the record itself is the evidence. A batch link that can be changed after the fact makes the whole chain worthless, and in a recall it is the first thing a regulator looks at. That is why we record batch links immutably, with a timestamp and the person responsible, and turn any correction into a visible correction alongside the original value. How we handle security ourselves is set out in our information security policy; external reports go through our coordinated vulnerability disclosure policy.
Frequently asked questions about BRCGS and traceability
From the BRCGS standard itself. The traceability test must show that full traceability forwards and backwards, including a mass balance, can be completed within four hours, and this test should be carried out at least annually. The exact wording is in the current version of the standard; check it against your own situation.
The IFS page covers the KO requirements and the unannounced audit: the two mechanisms that can cost you your certificate there. This page is about traceability and the mass balance, where BRCGS is particularly strict. If you hold both standards, you build them on a single record.
An audit file with non-conformity management collects evidence and follows up findings. This page is about one specific requirement that depends on your production data rather than on your document management. That is a different kind of problem with a different solution.
Usually because of rework and residual batches. Material that goes back onto the line is often not recorded as a batch, so more appears on the outgoing side than was registered incoming. Waste and sampling also fall out of view. These are not calculation errors but missing records.
A short period follows in which you must submit a correction, a root cause analysis and a preventive action plan for the non-conformities found. With BRCGS the root cause analysis is an explicit requirement: a correction without a substantiated cause is not accepted as closed. That deadline needs to be monitored.
A public consultation has been held for the next issue and work is under way, but there is no publication date yet. When a new issue is released, clause numbers and sometimes requirements shift. That is why we keep the requirements list as a setting and store, for each piece of evidence, which version it was recorded against.
Usually yes, and it is the best route. Batches already originate there: on receipt, on a production order and on dispatch. We pull that data in and fill in what is missing, usually the link between batches and the recording of rework.
That depends on how many links your process has, whether batches are already recorded and whether there is a production system to connect to. The batch register with the trace is generally usable quickly; the mass balance with rework takes more. We give a substantiated estimate after the discovery phase.
Why not actually measure those four hours?
Pick a finished product from last month and find out which raw material batches went into it and where it went. Put a clock on it. That figure is what the auditor will measure. We build this as a standalone application and as part of a broader custom software project.