A traceability plan under FDA's food traceability rule is a short written document with five parts, listed in 21 CFR 1.1315: how you keep the required records, how you identify which of your foods are on the Food Traceability List, how you assign traceability lot codes, who to contact about the plan, and, if you grow a listed food, a farm map. It has to be kept current, and the previous version kept for two years after an update. It's a description of what you do, not a manual. Two pages is plenty for a small business. The template below has the five parts with a creamery's answers filled in.
The short version
- Five parts: record procedures, listed foods, lot codes, a contact, and a farm map if you grow.
- Describe what you really do. An inspector will compare the plan with the records.
- Update it when a product, a system or the contact changes, and keep the old one two years.
- The rule covers foods on the Food Traceability List; check whether yours are on it and whether an exemption fits.
- TaroStack keeps the records the plan describes: lots at receiving, in each batch and on each shipment. More below.
The date, said carefully
The rule's original compliance date was January 20, 2026. FDA has proposed moving it to July 20, 2028, and Congress directed FDA not to enforce the rule before that date; FDA says it intends to comply. I read FDA's page on November 19, 2026, and it was current as of November 4. Buyers are asking for plans now regardless, because their own suppliers' records are what they'll rely on.
The five parts
| Part | What 21 CFR 1.1315 asks for |
|---|---|
| 1. Record procedures | A description of the procedures you use to maintain the records the rule requires, including their format and location |
| 2. Listed foods | A description of the procedures you use to identify foods on the Food Traceability List that you manufacture, process, pack or hold |
| 3. Lot codes | A description of how you assign traceability lot codes, if that applies to you |
| 4. Point of contact | A statement identifying a point of contact for questions about the plan and records |
| 5. Farm map | If you grow or raise a listed food (other than eggs): a map showing the location and name of each field or growing area, with geographic coordinates |
An example: a creamery making fresh cheese
North Fork Creamery is a made-up Long Island creamery I use in these examples. Fresh cheeses are on the list ("cheeses, other than hard cheeses"); its aged cheddar isn't.
1. Record procedures. Receiving, batch and shipping records are kept in the inventory system. Paper delivery slips are scanned the same day and filed by month in the office. Records are kept two years.
2. Listed foods. Fresh mozzarella, ricotta and chèvre. The item list marks each product that's on the Food Traceability List, and it's reviewed whenever a product is added.
3. Traceability lot codes. A code is assigned when milk is made into cheese: product code, make date and vat, such as MOZ-1116-2. It's printed on every tub and case and written on the shipping record.
4. Point of contact. The plant manager, by name, with a phone number and email. Backup: the owner.
5. Farm map. Not applicable: the creamery buys milk and doesn't grow a listed food.
Updates. Reviewed each January and whenever something changes. Old versions stay in the same folder, dated.
That's the whole plan. Notice what it doesn't do: it doesn't repeat the rule, and it doesn't promise anything the creamery doesn't already do every day.
What the plan points to
The plan is the map; the records are the territory. The rule asks for specific records at specific events (the key data elements for receiving, transforming and shipping), and on request FDA can ask for them as an electronic sortable spreadsheet. The rule lets certain small farms, and retail food establishments and restaurants under a sales threshold, provide them in another form. What goes in those records is in FSMA 204 key data elements, how codes work in traceability lot code, and who's exempt in food traceability list exemptions.
This is general information, not legal advice; FDA and your own counsel have the last word.
Get the template
Download the traceability plan template. Two sheets and a read-me: the plan, with the rule's wording beside a place for your answer, and an updates log with the date each old version is kept until. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
Writing the plan takes an afternoon. Living up to part 1 is the work: a plan that says "lot codes are on every shipping record" is only true if someone writes them there on the busy days too. And "an electronic sortable spreadsheet within 24 hours" is hard to produce from a binder.
How TaroStack does it
TaroStack keeps the records your plan describes, as a side effect of doing the work.
Receiving records the supplier and lot. Each delivery comes in with the supplier's lot and dates, typed or scanned from a GS1-128 case label.
A batch is the transformation. Recording a batch takes ingredients off their lots, notes which lots were used, automatically, and gives the cheese its own lot code and date.
A shipment names its lots. Each order records which lots went to which customer, and how much.
One trace, both ways, as a file. Any lot opens a trace back to its ingredient lots and forward to its customers. The recall report downloads as one CSV file, with where to find each customer and supplier.
Practice is recorded. A timed traceability drill is saved, and Home reminds you a month before a year passes without one.
| The plan says | On paper | In TaroStack |
|---|---|---|
| Records are kept, and where | Binders and a spreadsheet | One system, nothing deleted |
| Lot codes are assigned at making | A stamp and a logbook | A lot for every batch |
| Shipping records carry the lot | When someone writes it | On every order |
| A sortable file on request | Typed up from the binder | A CSV download |
TaroStack doesn't write the plan for you, and it doesn't make anyone compliant by itself. Lots, batches and recalls are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
