Food Traceability Plan Template for Small Food Businesses

Educational template disclaimer

This is an educational template structure, not a complete ready-to-use traceability plan. A real plan must be customized to your products, ingredients, suppliers, co-packers, software, records, customers, and applicable requirements.

Use this article with the FSMA 204 traceability guide, Mock Recall Checklist, Recall Plan Template, and templates hub.

Traceability plan table of contents

A practical traceability plan can include:

1. Company and product scope.
2. Lot coding system.
3. Supplier records.
4. Receiving records.
5. Processing or transformation records.
6. Finished product records.
7. Shipping records.
8. Recall connection.
9. Record retention and review.
10. Mock traceability exercise.
11. Corrective action process.
12. Review and approval.

Company and product scope

Define which facility, products, brands, co-packers, and product categories are covered. Include private label products and customer-specific SKUs if the business ships them.

If FSMA 204 may apply, document the product review and link to the current FDA Food Traceability List.

Lot coding system

Describe how lot codes are assigned. Include:

• Raw material lot identification.
• Work-in-process lots, if used.
• Finished product lot format.
• Date code or best-by code relationship.
• Repack or relabel lot rules.
• Who can create or change a lot code.

Lot codes should be readable, consistent, and connected to production records.

Supplier records

Supplier records should identify the supplier, product, lot, quantity, date received, and documentation reviewed. This section should connect to the Supplier Approval Program.

Receiving records

Receiving records should show what arrived, when it arrived, who received it, what lot was assigned or recorded, and whether the product was accepted, rejected, or placed on hold.

Processing or transformation records

Transformation records connect incoming lots to finished lots. This can include batch sheets, blend sheets, production logs, packaging records, rework records, or repack logs.

If a batch combines multiple ingredient lots, the record should show all lots used and the finished product lots created.

Finished product records

Finished product records should connect the product name, SKU, lot code, production date, quantity produced, packaging version, label version, and release status.

Shipping records

Shipping records should identify the customer, address or ship-to location, date, product, finished lot, quantity, and carrier or shipment reference.

Recall connection

The traceability plan should connect directly to the recall procedure. If a trace identifies affected customers, the recall plan should define notification, product hold, regulatory consultation, effectiveness checks, and recordkeeping.

Record retention and review

Define where records are stored, how long they are retained, who reviews them, and how quickly they can be retrieved. If records are split across paper logs, spreadsheets, accounting software, and shipping platforms, document where each record lives.

Mock traceability exercise

Run a mock traceability exercise at a planned frequency. Select a lot, trace it back to suppliers and forward to customers, check mass balance, record the time required, and open CAPA for gaps.

Practical checklist

• Define product and facility scope.
• Standardize lot code format.
• Verify supplier lot capture at receiving.
• Connect ingredient lots to batch records.
• Connect batch records to finished product lots.
• Connect finished lots to shipping records.
• Maintain customer contact lists.
• Test one-step-back and one-step-forward traceability.
• Document mass balance.
• Review gaps through CAPA.

Common mistakes

Common mistakes include changing lot code formats without documentation, losing ingredient lot data during batching, failing to record rework, shipping mixed lots without detail, and storing critical records in one person’s email.

Another mistake is running a mock recall but not correcting the gaps found.

QA perspective

From a QA perspective, traceability should survive employee turnover, software changes, and busy production days. The plan should make clear where records live and how a backup person can retrieve them.

If a lot cannot be traced when nothing is wrong, it will be harder when a complaint or recall is active.

Source notes

For official traceability requirements and current dates, verify:

• FDA FSMA Final Rule on Requirements for Additional Traceability Records for Certain Foods.
• FDA Food Traceability List.
• FDA Tracking and Tracing of Food.
• eCFR 21 CFR Part 1 Subpart S.

Businesses should verify the current Food Traceability Rule compliance and enforcement timing with FDA before finalizing records and customer commitments.