How V5 Ultimate runs a produce packing site, end to end.

Outbreak after outbreak — romaine, cantaloupes, cucumbers, onions — has resolved on the same lesson: the brands that could walk the chain backwards from a positive sample to a block, an irrigation event and a harvest crew were the brands that contained the recall. The brands that couldn't, lost the listing.

FSMA 204 (21 CFR 1.1300–1.1455) makes this concrete for foods on the Food Traceability List — leafy greens, melons, herbs, sprouts, tropical tree fruits, tomatoes, peppers, cucumbers (in certain forms), and more. Critical Tracking Events (CTEs) must be captured with Key Data Elements (KDEs) and produced as a sortable electronic spreadsheet inside 24 hours. Paper packing slips do not meet the bar.

V5 Ultimate treats the Traceability Lot Code as a property of the pack run, the field, the harvest crew, the cooler and the case — written into the same immutable ledger as everything else. A mock recall that took a 4-hour binder hunt resolves in under a minute.

Every node carries forward block, harvest date, crew, cooler, pack-run, operator and equipment context from the node before it. Nothing is re-keyed; nothing is reconciled at the end.

21 CFR 112 governs everything from agricultural water and biological soil amendments to worker health and equipment hygiene. V5 holds every grower as a structured object: scope by commodity × ranch × block, GAP / GLOBALG.A.P. IFA / USDA Harmonized GAP Plus+ certificates with expiry, agricultural water test history (per 112.43–112.47), biological soil-amendment records, animal-intrusion logs, and the last three sets of pre-harvest residue tests.

Re-qualification is calendar-driven and portal-led; an expired water test or GAP audit blocks inbound automatically. Grower risk scoring drives the depth of incoming inspection — a high-risk lot gets every truckload micro-tested for STEC and Salmonella; a long-trusted block ships against a reduced sampling plan with the supporting evidence kept on the ledger.

Whether field-packed or shed-packed, V5 mints a goods-receipt lot ID at the dock and ties it to the harvest tag (block, crew, date, time-window). Pulp temperature is captured at receiving; an out-of-band temperature trips a deviation and holds the lot. The supplier lot, the GAP cert in effect that day, the pre-harvest interval check, the in-field sanitation log — all link back from the receipt.

Identity verification — visual grading, sample weights, occasional pre-cooling micro testing — runs on the same kiosk. The result links to the receipt lot, the test method, the instrument, the analyst e-signature and any field documentation captured by the harvest crew.

V5 maintains cooler attributes: temperature band, commodity compatibility (ethylene-producers separated from ethylene-sensitive), organic segregation, allergen profile for fresh-cut lines that handle tree-nut toppings or dairy dressings. The pick list shown to the cooler crew only includes lots compatible with the pack run being built.

FEFO is enforced by default; overrides require a documented reason and a second e-signature. Continuous temperature monitoring is bound to the lot — every probe reading is on the ledger, with out-of-band events automatically tied to the lots in residence at that time.

Each pack plan holds: commodity mix and BOM (lettuce varieties, dressing sachet, fork pack), routing with step-by-step instructions, in-process control plan (chlorine ppm in the wash flume, brush-roller cleanliness, weight per clam, atmosphere in MAP bags), packaging routing, label artwork version, and the Nutrition Facts panel for the SKU. Every field is queryable.

Effectivity is two-signature: a developer signs the change, the Food Safety Plan owner signs the validation impact. New pack runs pick up the new revision; in-flight runs keep the snapshot they were released against.

If the pack plan is revised mid-shift, the pack run keeps the snapshot it was released against. The auditor sees exactly the plan the run was built to, with the sha256 of the snapshot recorded against the release event. There is no 'which version did they actually use' question.

For fresh-cut, the wash-flume free-chlorine and ORP are streamed live; a drop below target trips an in-process deviation that the operator must resolve before the kiosk advances. For whole produce, the line shows the pack rate, the weight-per-case verification, and the case-label print confirmation.

Commodity changeovers are explicit, signed gates. The kiosk shows the previous run's commodity, the incoming run's commodity, the required cleaning protocol from the master, and the ATP swab result or visual verification. Both the operator and a second qualified verifier sign.

21 CFR 117 preventive controls require verification monitoring. V5 implements it as a schedule — IPC sample requests are raised by the pack run at the configured interval (every N cases, every 30 minutes, every changeover). The sample label prints with a traceable ID; the analyst's result enters at the kiosk or arrives via a LIMS bridge.

Finished-product testing — STEC, Salmonella, Listeria where required, weight, MAP gas check, sensory — runs on the same flow. Out-of-spec results auto-open a deviation, place the lot on hold, and notify QA. Statistical control limits trigger CAPA before drift becomes a failure.

A single deviation register categorises by hazard type (biological, chemical, physical, allergen, sanitation, equipment, labelling). Root-cause workflow uses the structured fields the auditor expects. CAPAs link automatically to the deviation, the affected lots, the operators on shift, the equipment, and any related complaints.

Effectiveness checks are calendar-driven — V5 reopens the CAPA at the configured interval, prompts evidence upload, and only closes once the QA reviewer signs.

The Produce Traceability Initiative (PTI) defines the GS1-128 case label that retailers and distributors expect: GTIN, lot/batch, pack date, and (where applicable) harvest date. V5 carries those fields from the pack-run release through to the printed label — no manual artwork edits at packaging.

Under FSMA 204, the Traceability Lot Code is assigned at the FTL-defined CTE (initial packing for whole produce, transformation for fresh-cut). V5 propagates the TLC on every case and pallet and exports the FDA-preferred sortable CSV inside 24 hours.

Review-by-exception is only safe if the record is complete and immutable. V5's pack record is built from the ledger as the line runs — every step accounted for, every deviation linked, every IPC result attached. The QA reviewer's queue surfaces only the items the system can't auto-clear: open deviations, OOS, missing verifications, unsigned changeovers.

Release requires two qualified e-signatures (a preparer and an approver). The released run is then disposition-locked — any future change is a deviation, not a quiet edit.

Every case ships against an ASN that carries the TLC. Distribution events (ship, transfer, return) are CTEs under FSMA 204. When a recall trigger fires — internal QA disposition, grower withdrawal, retailer complaint, FDA Class I — V5 walks the ledger in both directions in seconds: every case made from this block, every customer DC it shipped to, every adjacent run that shared the wash flume.

The Reportable Food Registry submission, the recall press release draft, the mock-recall test result for the next GFSI / PrimusGFS audit — all assemble from the same ledger.

Hazards link to preventive controls, to monitoring procedures, to corrective-action procedures, to verification activities, and to the PCQI (for fresh-cut) or qualified individual (for the farm) who owns each. Re-analysis is calendar-driven (every three years or on significant change per 117.170), and the prior period's monitoring data assemble into the re-analysis workspace automatically.

Draft → Review → Approved → Effective → Periodic Review → Superseded / Retired. Two qualified signatures effect every release. Operators see only the effective revision; superseded revisions are retained for the retention period (typically two years per 117.190 / 112.7 plus any GFSI overlay).

V5 maintains a training matrix per role × line × hazard. Worker hygiene and health training are mandatory per 21 CFR 112.21–112.30 and 117.4. New hires move through onboarding → competency assessment → signed-off → live, with the assessor's e-signature linked to the kiosk badge.

Every pack run's quality signals, every CAPA, every grower scorecard, every internal-audit finding, every customer complaint, every environmental swab — all stream into the management-review workspace as they happen.

V5's audit module schedules internal audits (area scope, risk-based frequency, finding classification) and external audits (PrimusGFS, GLOBALG.A.P., USDA Harmonized GAP Plus+, customer 2nd-party). When FDA arrives, the inspector's request list is a query — the Food Safety Plan, the last three months of water-quality and EMP records, supplier verification — assembled in minutes.

Hazards are identified by category and source. Each gets a severity × likelihood score, a documented decision on whether a preventive control is required, the CCP / OPRP classification, the monitoring procedure and frequency, the corrective-action procedure, and verification. The kiosk enforces CCP monitoring as a hard gate — a missed CCP check holds the lot until QA resolves it.

Agricultural water testing per 21 CFR 112.43–112.47 (for the farm), and process-water free-chlorine / ORP / pH for the wash flume, are tracked as scheduled events. Results trend; an excursion ties forward to every pack run that used the water in the affected window.

V5 holds sanitation procedures per zone × equipment × commodity, with frequency, agent, concentration, contact time, and verification (visual + ATP + microbiological swab on a defined cadence). Sanitation events are kiosk-led; results bind to the equipment record.

Chlorine analysers, ORP probes, cooler thermocouples, dispense scales, metal detectors, X-ray rejectors — each is a tracked asset with calibration interval, certificate of last calibration, tolerance, and an out-of-tolerance impact-assessment procedure. An out-of-tolerance result triggers a back-look across every run processed since the last passing calibration.

Sample sites, frequency, indicator and pathogen testing, and corrective actions on a positive (vector swabbing, intensified cleaning, re-test) are all scheduled and tracked. A Listeria positive in Zone 1 auto-holds product and opens a CAPA with a defined effectiveness check.

Complaints enter via portal, email-to-ticket or customer-service handoff. The intake form asks the questions the FDA investigator will ask later: TLC, pack date, place of purchase, nature of complaint. V5 binds the complaint to the matching pack run on intake, surfaces adjacent runs that share equipment, and trips a deviation if the pattern crosses a threshold.

Every signed event carries the actor's verified identity, the meaning of the signature, the time, and a sha256 of the record being signed. The signature row is append-only. PDF renders are deterministic from the snapshot. ALCOA+ is a property of the data model, not a feature you opt into.

CoAs per lot, GAP certificates, country-of-origin documentation, FSMA 204 TLCs for the cases the customer received — all on the portal. Audit-trail of who downloaded what is automatic.

A typical packing house onboards in 4–8 weeks: master data import, pack-plan migration, kiosk training, a parallel-run validation against the existing paper record, and cutover. The validation pack (URS → IQ → OQ → PQ) is built into the implementation.

This is the abbreviated mapping. Each link opens the full readiness guide.