EU animal-origin rules add lot and dispatch data to one-step traceability

The regulation adds a consignment-level data set

The direct answer in Commission Implementing Regulation (EU) No 931/2011 is that food business operators handling covered food of animal origin must make a defined set of consignment information available to the operator receiving the food and, upon request, to the competent authority. The rule operates in addition to other applicable Union traceability information rather than replacing the general one-step-back and one-step-forward framework.

A traceability platform should preserve the legal entity and operating location responsible for the event, the recipient, food identity, quantity and unit, dispatch, and lot linkage as one dated record. A shipment header alone may omit the regulatory owner or product detail; a warehouse lot alone may omit the commercial handoff. The system needs a durable connection between the physical consignment, parties, ownership roles, lot reference, and source documents.

Operator and owner roles can differ

Article 3 requires the name and address of the food business operator from which the food was dispatched and the operator to whom it was dispatched. It also requires the consignor owner and consignee owner when either differs from the corresponding food business operator. That makes four party roles possible within one movement. Treating ship-from as seller or ship-to as buyer by default can erase the distinction.

A governed record should model each role explicitly and attach the identifier, name, address, effective date, and source used at the time. Third-party logistics, contract processing, storage, and other arrangements can create different operating and ownership parties. Master-data updates should not rewrite the historical name and address on an earlier consignment, and unresolved party identity should remain visible rather than being silently filled from the nearest account.

Lot reference and dispatch date make the handoff reconstructable

The required information includes an accurate description of the food, its volume or quantity, a reference identifying the lot, batch, or consignment as appropriate, and the date of dispatch. Those elements make the one-step relationship more useful during investigation: they narrow which material moved, how much, under which traceability reference, between which parties, and when.

The operational test is whether the receiving record reconciles with the sender's record without collapsing different identifiers. Supplier lot, internal lot, batch, consignment, shipment, handling unit, and customer reference can all coexist. The platform should preserve their types and relationships, units and conversions, splits and combinations, corrections, and event chronology. An editable free-text lot field may display a code yet fail to reconstruct the affected population.

Daily updates and retention need governed availability

Article 3 says the specified information must be updated daily and kept available at least until it can reasonably be assumed that the food has been consumed. The rule does not prescribe one software architecture, but it creates a test of currency and retrieval. Offline sites, partners, interfaces, and late corrections need monitored synchronization and a retained change history so today's view does not erase what was previously supplied.

Scope remains important. Regulation 931/2011 defines covered food of animal origin by reference to other EU law and excludes the described composite foods from this Regulation, while other traceability duties may still apply. This article does not classify a product, determine a retention period for a particular food, or provide legal advice. Operators must apply the complete current law and competent-authority guidance to their products, activities, and jurisdictions.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Food Traceability Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.