Restaurant food traceability records: build a usable one-step chain

A traceability record answers a movement question. What arrived, from whom, in what unit, when, and at which location? What happened to it next? The European Commission General Food Law guidance places responsibility on food operators to maintain the information needed for this one-step-back and one-step-forward approach. That does not prescribe one universal spreadsheet or one software screen for every restaurant. It means the operator should design a chain that matches the sites, products, suppliers, transfers, and records actually used. Begin with the smallest useful record and expand only when the operation has a reason to connect another event.

Define the incoming record before choosing a tool

National Restaurant Association traceability guidance gives a practical starting set of fields: supplier, product description, quantity and unit, receipt date and location, lot or other reference documents, and a way to retrieve the record. Add fields that your operation needs, such as an internal item code, delivery document reference, storage area, receiving person, or transfer destination. Keep the original wording from supplier documents where it matters. If a product is described as a case, tray, bag, or each, record that unit and store the conversion separately rather than silently changing it. A clean record is one another operator can interpret without asking the person who made it.

• Use a product description that distinguishes the item from a broad category such as dairy, produce, or dry goods.
• Record quantity and unit as received, then add an explicit conversion only when the site has verified what the unit contains.
• Capture receipt date and location for multi-site operations; a central purchasing record alone may not show where food went.
• Attach or reference the supplier document, lot, delivery note, or other source identifier instead of copying only a convenient summary.
• Name the person or role responsible for correcting an incomplete receipt, and retain the correction history in the system your site uses.

Continue one step forward without pretending the chain is automatic

The forward link depends on the restaurant's actual flow. A received case may remain in a storage area, be issued to a prep batch, move to another site, or be used across several service periods. Choose a forward record that already exists or can be added without creating an unusable burden: a stock issue, prep sheet, transfer note, production batch, waste record, or service allocation. The link can be a document reference, batch label, date-and-location key, or another locally defined identifier. State the limits. If the operation cannot connect an ingredient beyond a prep batch, say so and decide whether a more granular record is needed.

Clearly labeled illustrative example: a receiving-to-prep chain

A repeatable traceability-record process

1. 1Map the real flow. List the receiving locations, storage points, prep activities, transfers, and onward recipients that exist in your operation. Mark where a source document or internal record is created.
2. 2Set the minimum fields. Choose supplier, product description, quantity, unit, receipt date, location, lot or reference document, and the forward-link field. Add only fields the operation can keep accurate.
3. 3Capture at receipt. Record the product as received and attach the delivery or supplier reference. Do not normalize away a meaningful unit or replace a missing identifier with a guess.
4. 4Link the next movement. Connect storage, prep, transfer, waste, or service records using the site's chosen key. If one receipt splits across destinations, create each link and reconcile the quantities.
5. 5Practice retrieval and decide. Run a bounded search with an operator-entered record, note missing or ambiguous links, and choose a deliberate response: keep the supplier, consolidate, renegotiate, substitute, or switch only after the evidence and current authority checks support that choice.