HACCP as an executable object
CCP monitoring tasks are issued at the frequency the plan specifies, to a named owner, and a missed check raises a deviation automatically.
• Food & Beverage
CCPs are monitored at the specified frequency, corrective actions are tied to the affected product, and every lot traces end to end. The plan runs, it does not sit in a binder.
Supported frameworks, not certifications. Regulatory updates included.
Why now
At audit, a plant has to prove the check happened, how often, against a validated limit, and what followed any drift.
The 2020 Codex revision put validation into principles three and six.
FSSC 22000 and BRCGS are usually stricter than statutory requirements.
A missed check has to raise a deviation, not sit empty until someone notices.
What is tailored
Where the Food & Beverage pack changes how the core behaves.
CCP monitoring tasks are issued at the frequency the plan specifies, to a named owner, and a missed check raises a deviation automatically.
Allergen status travels with the material, with changeover and cleaning enforced between incompatible runs.
Each exercise produces the trace, the reconciliation and the elapsed time as a record, not a fire drill.
Built for food and beverage
These features switch on with the food and beverage pack. The checks run on the same batch record as production and quality.
01 / Quality · CCP monitoring
Monitoring tasks go to a named owner at the planned interval. Results are checked against validated limits, and a reading out of limit raises a deviation and holds the affected product.
Each CCP check is issued to a named owner at the interval the HACCP plan sets.
A check not done on time raises a deviation, instead of sitting as a blank cell until verification.
A reading out of limit holds the batch or time window it affected, with the corrective action and disposition on the record.
02 / Production · Allergen changeover
A changeover between incompatible products adds its own allergen checks to line clearance. The next run cannot start until each check is done and the clearance is signed.
Each material carries its allergen status, so the system knows when the next run is incompatible with the last.
An incompatible changeover adds allergen checks to line clearance, each answered with its evidence.
The next run stays locked until every check is done and QA signs the clearance.
03 / Inventory · One up, one back
The trace map shows every supplier lot, receipt, batch and customer a lot touched. Recall reach lists the batches on hold, the customers to notify and the stock to quarantine, ready for the 24-hour test.
Every lot keeps its supplier and customer records, so the trace builds from receipts, batches and dispatch.
Recall reach lists the batches to hold, the customers to notify and the stock to quarantine.
A scheduled mock recall saves the trace, the reconciliation and the elapsed time, with a sortable export.
04 / Facility · Hygiene zones
Temperature, humidity and hygiene readings are recorded by zone, from sensors or by hand. A reading out of limit raises an action with an owner, and the evidence stays on the room’s record.
Each zone carries its own limits for temperature, humidity and hygiene, from the area’s storage conditions.
Sensor readings and manual checks land on the same zone record, with the time and who took them.
A reading out of limit raises an action with an owner and a re-read, and the evidence stays with the room.
Traceability, precisely
The baseline is the same in India, the US and the EU. FSMA 204 raises it for listed foods, and the FDA can ask for the proof within a day.
The baseline, everywhere
Know your immediate supplier and your immediate customer, on every lot.
FSMA 204 · listed foods
A data discipline problem, and the one that catches manufacturers out.
The 24-hour test
The FDA can ask for an electronic, sortable spreadsheet of critical tracking events and key data elements, due within a day. Factro produces it from the lot records you already have.
Controls
Every control below runs on the Compliance Engine. The same record carries the evidence across the plant.
Append-only, hash-chained audit trail capturing old value, new value, author, time and reason
HACCP plan as an executable object, with hazards, control measures, CCPs and validated critical limits held as records
CCP monitoring tasks issued at the frequency the plan specifies, to a named owner
A missed check raises a deviation automatically, rather than surfacing as a blank cell at verification
Corrective action bound to affected product, with the batch or time window held and the disposition recorded
Prerequisite programme records covering hygiene, pest control, sanitation and maintenance
Allergen status travelling with the material, with changeover and cleaning enforced between incompatible runs
Allergen declaration checked against actual formulation, across the eight Indian, nine US and fourteen EU lists
One-up, one-back supplier and customer records on every lot
Mock recall as a scheduled exercise, producing the trace, the reconciliation and the elapsed time as a record
Recall plan with classification, notification and effectiveness checks
Role-based access control, down to the individual field
Segregation of duties enforced in the system, maker is never checker
FoSTaC supervisor ratios tracked live, one certified supervisor per 25 food handlers or part thereof
Training tied to document version, reassigned on every revision
Supplier approval and incoming material verification with certificate capture
Calibration of monitoring equipment blocking the stage when overdue
Environmental and product testing scheduled, with results attached to the lot
Automated redundant backup with point-in-time disaster recovery
Regulatory change
The Compliance Engine tracks the rules that apply to you, works out what a change touches, updates the system and re-validates before release. You file no change request.
The US Food Safety Modernization Act moved FDA from reacting to contamination towards preventing it, with preventive controls and traceability duties.
The 2020 revision's principles three and six — a critical limit has to be justified, not just set — were folded into CCP monitoring before FSSC 22000 and BRCGS auditors started asking for it.
The Food Traceability Rule set the key data elements and critical tracking events for listed foods. The compliance date has since moved to 20 July 2028.
Basic registration runs to ₹1.5 crore, state licence from ₹1.5 crore to ₹50 crore, central licence above ₹50 crore.
Moving prerequisite programmes onto the ISO 22002 2025 series.
For foods on the Food Traceability List.
Validation readiness
Available on the Dedicated tier, mapped to your workflows. URS, IQ, OQ, PQ, RTM and GAMP 5.
Certification in progress. Encryption, access control and backups are described on Security & Trust.
The Compliance Engine scores inspection readiness continuously, with guidance on each open gap.
Make it your workflow
Bring the regulation that keeps you up at night. We will show you the control that answers it, on a batch from your plant.