When a supplier calls about a contaminated ingredient, you have 24 hours to hand over your traceability records as a sortable spreadsheet. Lotpath keeps the chain joined while you work, so the answer already exists when you need it.
No card. The demo is a working facility with eight months of batches and shipments, two past drills, one real recall — and a pepper lot that reached seven customers.
Most small producers can tell you what they bought and what they shipped. What takes the weekend is joining the two — working out which of last quarter’s batches used the suspect drum, and which customers got those batches.
Receiving logs, batch sheets and invoices each live in their own file. Nothing links a drum of oil to a pallet that left in March.
A base sauce becomes a filled jar becomes a case. Two or three transformations in, the manual trace quietly stops being reliable.
21 CFR 1.1455(b)(3) gives you 24 hours to produce records in an electronic sortable spreadsheet. Not a filing cabinet, not a photo of a logbook.
Lotpath is not an ERP. It records the three events that traceability law actually cares about, and does one thing with them extremely well.
What arrived, from whom, under whose lot code. The supplier’s own lot number is the field that lets their recall notice find your stock.
Log a batch: the lots you consumed and the lots you created. That single record is what every future trace walks across.
Which finished lots went to which customer. Now a lot code resolves to a phone list, automatically.
Forward from an ingredient to every customer, backward from a finished jar to every supplier — across as many transformation steps as your process has.
Run the exact computation a live recall runs, without touching your stock. Every drill is timed and kept — that timing is what an auditor asks for.
One flat CSV of every receiving, transformation and shipping event with the Key Data Elements filled in. The 24-hour request, answered in a click.
Scores your records against the KDEs and names the exact lots with holes in them, so you find the gap on a quiet Tuesday instead of during the recall.
A held lot cannot be consumed in a batch or shipped. Not a note in a spreadsheet — a rule the software enforces.
Who was told, who answered, how much came back — plus a printable recall report with the effectiveness check already worked out.
Lots, batches, shipments, traces, recalls and exports are unlimited on every plan. Metering a food safety tool during an actual recall would be indefensible.
One facility, up to 3 people.
Everything in Starter, plus:
14-day trial with every feature. No card up front.
Sauce and condiment makers, bakeries, roasters, co-packers, supplement blenders, meal-prep kitchens — anyone who buys lots, mixes them, and ships the result under a lot code of their own. Typically 3 to 60 people, currently doing this in Excel.
It is not an ERP and does not want to be. There is no purchasing, no costing, no accounting integration. If you need those, keep them — Lotpath only claims the chain.