Food Traceability in a Short Supply Chain: How Software Tracks a Crate From Grower to Doorstep

What does traceability legally require in a short food supply chain?

In the EU, Regulation 178/2002 requires every food business to know its direct supplier and its direct business customer, the "one step back, one step forward" rule, and to produce that information to authorities on demand. Sales to final consumers are exempt from the forward step, but the backward step still applies.

That single sentence hides a lot of practical work for a co-operative or food hub. If you buy from 40 growers and sell to consumers, restaurants and a school kitchen, you are a food business operator in your own right. You need records of what you received, from whom, in what quantity and when, plus records of what you dispatched to each business customer. Consumer orders do not need forward traceability by law, but most operators keep it anyway because it is the fastest way to answer a complaint.

Some products carry extra obligations on top of the baseline. Fresh fruit and vegetables sold under EU marketing standards need the producer, packer or dispatcher identified on the packaging or documents. Eggs carry producer codes. Beef has its own dedicated traceability regime. Organic certification adds a parallel audit trail: the certifier wants to see that the organic quantity you sold never exceeded the organic quantity you bought. If you run a shared kitchen or process anything, HACCP records join the pile. National rules vary, so treat this as the shape of the obligation and confirm specifics with your competent authority.

What data has to be captured at each hop from field to doorstep

A traceable crate needs four anchors: who produced it, which batch or lot it belongs to, how much of it existed, and which orders consumed it. Everything else, temperature, harvest date, certification status, hangs off those four. Capture them at the moment the crate changes hands, not in a Sunday evening catch-up session.

The practical trick in a short chain is that there are only three or four handovers, so each one can be a deliberate, recorded event rather than an inference from paperwork. A grower confirms what they are bringing. A hub operator receives and checks it. A picker assigns quantities to orders. A driver confirms the drop. Each of those touchpoints already happens; traceability just means writing down the identifiers while the crate is in front of someone.

The unit of traceability matters as much as the fields. A batch that means "everything Marko brought on Tuesday" is easy to record and gives you a recall scope of one delivery day. A batch that means "the 09:00 cut from the north polytunnel" is more work at intake and narrows a recall to a handful of orders. Small operations should pick the coarser unit first and tighten it for high-risk products such as leafy greens, raw milk products and sprouts.

Intake: producer ID, product, batch or lot reference, quantity received, date, unit of measure, condition notes, certification status at time of receipt
Storage: location or zone, any repacking or splitting event that creates a child batch from a parent batch
Picking and packing: which batch fed which order line, in what quantity, packed by whom
Dispatch: route, driver, vehicle, departure time, cold chain notes if applicable
Delivery: timestamp, recipient confirmation, pickup point or address, any refusal or substitution
Documents attached to the above: delivery notes, invoices, certificates, lab results, photos of labels

How software turns those records into a one-hour recall

A recall is two queries. Forward: given a batch, list every order, customer and delivery that received any of it. Backward: given a complaint about one delivered item, name the batch, the producer and every other order that shares that batch. Software answers both in seconds because the link between batch and order line was written at pick time.

On a spreadsheet the same questions take hours of cross-referencing between an intake sheet, an order sheet and a delivery list, and they usually end in a phone call to whoever packed that day. The gap is not effort, it is that spreadsheets store the three events in three places with no enforced key between them. A shared batch identifier that every app writes to is the whole mechanism.

Once the queries are instant, a few useful behaviours become cheap. You can send a targeted notice to only the 23 households that got the affected batch instead of alarming your entire customer list. You can tell the producer exactly how much of their lot is still in the cold room versus already delivered. You can hold the remainder of a batch with one action so pickers stop assigning it mid-recall. And you can export the whole chain, intake to doorstep, as a single document for the authority handling the incident.

What an inspector actually asks for, and what to hand over

Inspectors rarely ask to see your software. They ask a question about a specific product and time frame, then judge how quickly and consistently you can answer it. A typical challenge is: show me where this batch came from, where it went, and prove the two quantities reconcile. Have that as an exportable record, not a screen you have to narrate.

Prepare three artefacts in advance. First, a written traceability procedure describing your batch unit, who records what at each step, and how long you retain records. Second, a mock recall you have actually run, with the date, the batch chosen, the time taken and the list of affected customers. Regulators and certifiers respond well to evidence that you have tested the system rather than described it. Third, a live certificate register: organic certificates, HACCP documentation, registration numbers and their expiry dates, each attached to the producer it belongs to so an expired certificate is visible before an inspection, not during one.

The reconciliation point deserves attention because it is where paper-based operations usually fail. If you received 120 kg of a batch and your order lines total 138 kg, something is wrong: a mislabelled crate, a manual override, or product from a second producer sold under the first one's name. Software that decrements batch quantity as orders are picked makes that impossible to do accidentally and surfaces it immediately when someone tries.

A one-page traceability procedure naming your batch unit and record retention period
Intake records with producer, batch, quantity and date for the requested period
Dispatch and delivery records linking those batches to customers and timestamps
A dated mock recall report showing scope and elapsed time
Certificates on file per producer, with expiry dates and the products they cover

Turning the same data into a selling point on the product page

The records you keep for compliance are also the most credible marketing asset a local food business has. The same producer and batch fields that answer an inspector's question can populate a product page that names the farm, the village, the harvest week and the certification, without anyone retyping it into a CMS.

Shoppers in short chains buy on provenance, and vague provenance claims are increasingly easy to distrust. "Local" is a word anyone can print. "Harvested 12 June by Obitelj Kovač, Baranja, organic certificate valid to March" is a claim tied to a record. Because the data is entered once by the producer at intake, the storefront statement and the compliance record cannot drift apart, which is exactly the failure mode of hand-maintained producer bios.

A QR code on the delivery box or crate label that resolves to the batch's public page closes the loop. Consumers see origin and date. Restaurant buyers get the documentation they need for their own menu claims and their own inspections. And the co-operative gets a reason for producers to keep intake records accurate, because those records are what their customers read. Plodie's producer, admin, shopper and delivery apps write to one shared record for exactly this reason: the batch a grower confirms in the morning is the batch a driver marks delivered in the afternoon and the batch a customer reads about on the label.

Key Takeaways

EU law requires one step back and one step forward traceability; consumer sales are exempt from the forward step, but everything you receive still needs a supplier record.
Capture four anchors at every handover: producer, batch, quantity and the orders that consumed it. Everything else attaches to those.
Choose a coarse batch unit first, such as one producer's delivery on one day, and tighten it only for high-risk products like leafy greens and raw milk.
Run and document a mock recall. Inspectors and certifiers trust a tested system more than a described one.
The same producer and batch data that satisfies an audit can populate provenance claims on the product page without duplicate data entry.

If your intake, order and delivery records currently live in three separate spreadsheets, our 6-week migration plan for food co-operatives covers how those columns map into a single traceable record.

Frequently Asked Questions

Do small farms and market stalls need traceability records, or is it only for big producers?

Primary producers selling small quantities directly to final consumers or to local retailers are treated more lightly under EU rules, and member states set their own detailed requirements for that activity. But once you sell through a co-operative, food hub or another business, that business needs a record of you as its supplier, and you need to be able to identify what you supplied and when. In practice a simple delivery note per drop, with product, quantity and date, satisfies most of it.

How long do I have to keep food traceability records?

The common guidance in the EU is five years from the date of manufacture or delivery for most products, with shorter periods allowed for highly perishable goods with a durability under three months, often set at the shelf life plus six months. Check your national authority, because implementation differs. Digital records make retention trivial compared to boxes of delivery notes.

Can I do traceability with a spreadsheet instead of software?

Yes, and many small operations legally do. A spreadsheet fails on speed and on reconciliation: cross-referencing intake, orders and deliveries by hand during an actual incident takes hours, and nothing stops you selling 138 kg of a 120 kg batch. Software is worth it once you handle multiple producers, since the shared batch identifier is what makes the recall query instant.

What is the difference between traceability, HACCP and organic certification?

Traceability is knowing where food came from and where it went. HACCP is a hazard control system for processing operations, identifying critical control points such as chilling temperatures and setting limits and monitoring for them. Organic certification is a third-party audit that your products and quantities match certified organic inputs. They overlap in the records they need, which is why one well-structured data set can feed all three.

What should a QR code on a local food product actually show the customer?

Useful content is the producer name and location, the harvest or production date, the batch reference, any certifications with their validity, and how the product reached the customer. Avoid pages that only show marketing copy, because the point is that each claim maps to a stored record. Restaurant and retail buyers often use the same page as supporting documentation for their own menu and shelf claims.