GenFrontier homeScope a project
Menu
Reader questionUnder FSMA 204, when must we assign a traceability lot code, and when must we carry the supplier's code unchanged?

FSMA 204 traceability lot codes: when to assign, when to keep

When FSMA 204 requires a new traceability lot code, when a distributor must keep the supplier's code, and how to store the TLC and TLC source in your WMS.

field-notes / traceability-standards / fsma-204-traceability-lot-codes
Three stacked wooden crates of leafy greens, each stamped with the same red dot-pattern stencil mark, the stencil plate lying beside them

Under FDA’s Food Traceability Rule (FSMA 204), you assign a new traceability lot code in only three situations: when you initially pack a raw agricultural commodity, when you are the first land-based receiver of food from a fishing vessel, and when you transform a food. There is one receiving case as well: if you receive a listed food from a supplier the rule does not apply to and no code has been assigned yet, you assign one. In every other situation, including receiving, storing, picking, cross-docking and shipping, you must carry the code you received, together with its traceability lot code source, without changing it.

For a distributor or 3PL that only receives, stores and ships, that means your own lot numbers can exist for FEFO (first expired, first out) picking and stock control, but they sit next to the supplier’s traceability lot code, never in place of it. The rest of this note turns the rule into decisions for the dock, the WMS and the customer feed. This note is not legal advice. Whether the rule applies to your products and sites, and which exemptions you qualify for, are questions for your counsel and for FDA’s own guidance.

Where enforcement stands in November 2026

FDA will not enforce the Food Traceability Rule before July 20, 2028, under a congressional directive. That is the accurate summary as of November 21, 2026. It is worth stating precisely, because older dates are still in circulation: the “Getting Started” section of FDA’s own rule page still says “The compliance date is January 20, 2026.”

The sequence, from FDA’s rule page (content current as of November 4, 2026) and the Federal Register:

  1. The original compliance date for the recordkeeping requirements was January 20, 2026.
  2. On August 7, 2025, FDA proposed extending the compliance date by 30 months, to July 20, 2028 (90 FR 38084).
  3. The Continuing Appropriations, Agriculture, Legislative Branch, Military Construction and Veterans Affairs, and Extensions Act, 2026 directed FDA not to enforce the rule before that same date. FDA says it “intends to comply with this Congressional directive.”

A Federal Register search on November 21, 2026 showed no final rule completing the proposed extension. The lot code requirements below are quoted from the eCFR text of 21 CFR part 1, subpart S as of November 1, 2026. Large customers can also set their own supplier deadlines, so ask them directly what they expect and when.

What the rule means by a traceability lot code

A traceability lot code (TLC) is the identifier that ties every required record about one lot of a listed food together. The rule calls each required piece of information a key data element (KDE) and ties it to a critical tracking event (CTE) such as receiving, shipping or transformation. The definitions in 21 CFR 1.1310 are short and precise, and each one has a consequence for your systems.

Term Definition in 21 CFR 1.1310 What it means for your data
Traceability lot “a batch or lot of food that has been initially packed…, received by the first land-based receiver…, or transformed” A lot only exists at the three creation events. Receiving does not create one.
Traceability lot code “a descriptor, often alphanumeric, used to uniquely identify a traceability lot within the records of the traceability lot code source” The code is unique only inside the records of whoever assigned it. Two suppliers can use the same string.
Traceability lot code source “the place where a food was assigned a traceability lot code” A physical place, described with a location description, not a company name alone.
Traceability lot code source reference “an alternative method for providing FDA with access to the location description for the traceability lot code source” For example, an FDA Food Facility Registration Number or a web address that shows the location description.
Location description Business name, phone number, physical location address (or geographic coordinates), and city, State and zip code, or comparable foreign information including country Several fields, not one free-text line.

FDA’s Traceability Lot Code page adds that a TLC “is similar to what industry currently refers to as a ‘lot’ or ‘lot code’.” The rule does not prescribe a format. It also does not require the TLC to appear on the food’s label or packaging; FDA lists a bill of lading, an advance shipment notice, a separate email or a QR code as ways to pass it on.

TLC source and TLC source reference

The TLC source answers the question “where was this code created?” It travels with the code at every later step. Under 21 CFR 1.1340(a)(7) and 1.1345(a)(7), shipping and receiving records must include either the location description for the TLC source or the TLC source reference.

The source reference exists so that a supplier does not have to reveal its packer to every customer down the chain. FDA’s page says a web address used as a source reference may sit behind “reasonable security measures,” provided FDA can get the information at no cost and without delay. For your systems, that means a TLC source field can hold either a full location description or a reference, and you need to know which one you have.

What a TLC is not

A TLC is not your internal lot number, your license plate number (LPN), your purchase order number or your receipt number. Those identifiers can be useful reference documents, and FDA’s own distribution center example builds a TLC out of some of them, as described later. But when a covered supplier has already assigned a code, none of your internal identifiers replaces it.

The events that create a new code

21 CFR 1.1320 is two sentences long. Paragraph (a) says you must assign a TLC when you “initially pack a raw agricultural commodity other than a food obtained from a fishing vessel; perform the first land-based receiving of a food obtained from a fishing vessel; or transform a food.” Paragraph (b) says that, except as otherwise specified, you “must not establish a new traceability lot code when you conduct other activities (e.g., shipping).”

The “otherwise specified” exception that matters most to distributors is in 21 CFR 1.1345(b). When you receive a listed food from a person to whom the subpart does not apply, your records must include the TLC, “which you must assign if one has not already been assigned.” Retail food establishments and restaurants are excluded from that assignment duty.

Event Who usually performs it New TLC? Who becomes the TLC source Rule
Initial packing of a raw agricultural commodity (not from a fishing vessel) Packinghouse, grower-packer Yes The place where the food was initially packed 1.1320(a), 1.1330
First land-based receiving of food from a fishing vessel Dock, first receiver of the catch Yes The first land-based receiver 1.1320(a), 1.1335
Transformation Processor, fresh-cut plant, repacker, relabeler Yes, for the output The place where the food was transformed 1.1320(a), 1.1350
Receiving from a supplier not subject to the rule, with no code assigned Distributor, processor, DC Yes, unless you are a retail food establishment or restaurant The place where the food was received 1.1345(b)
Receiving from a covered supplier Anyone downstream No Unchanged, as received 1.1320(b), 1.1345(a)
Shipping Anyone No Unchanged 1.1320(b), 1.1340
One lot's path: where the code changes Grower farm Harvest and cooling. No traceability lot yet. No code yet Packinghouse Initial packing assigns the code. TLC source: the packinghouse. PK-0611-A (new) Distributor DC Receives, breaks pallets, ships. TLC source: still the packinghouse. PK-0611-A (kept) Fresh-cut plant Transformation into salad kits. New TLC source: the plant. Input linked. FC-26162-3 (new) input: PK-0611-A Retailer DC Receives and ships to stores. TLC source: still the plant. FC-26162-3 (kept)
Fictional supply chain and codes for illustration. Rule basis: FDA, 21 CFR 1.1320(a), 1.1340, 1.1345 and 1.1350, checked November 2026.

Transformation covers more than cooking

The 1.1310 definition of transformation is broader than the word suggests. It is “an event in a food’s supply chain that involves manufacturing/processing a food or changing a food (e.g., by commingling, repacking, or relabeling) or its packaging or packing, when the output is a food on the Food Traceability List.” Initial packing and the steps before it are excluded.

So a repacker that sorts tomatoes by ripeness into new cases transforms them. A distributor that puts its own brand label on cases of leafy greens transforms them. FDA’s February 2026 draft guidance of questions and answers says that “changing a brand name on a food’s labeling would be a type of relabeling,” and therefore transformation. That guidance is a draft and nonbinding, but it is the most direct statement of FDA’s current thinking on warehouse cases.

There is one softening. The same draft guidance notes that a repacker “could decide to keep the same TLC if the tomatoes are repacked within the same traceability lot (repacking ‘like into like’),” citing the preamble to the final rule. The repacking is still a transformation, so the transformation records are still kept. Treat that option as a decision to document in your traceability plan, not as a default.

Receiving from a supplier the rule does not apply to

Some suppliers are outside the rule. Examples from 21 CFR 1.1305 include produce farms whose average annual produce sales over the previous three years are no more than $25,000 (adjusted for inflation from a 2020 base) and shell egg producers with fewer than 3,000 laying hens at a farm. When you buy a listed food from such a supplier and it arrives with no TLC, the code starts with you.

FDA’s Traceability Plan Example for Distribution Center (March 2025) shows how a distributor might handle this. The fictional distribution center in FDA’s example states that most products arrive with TLCs already assigned, and that “the only situation in which our firm assigns TLCs is when we receive FTL foods from exempt entities.” Its code combines the supplier’s name or number in the WMS, the purchase order number, the SKU and the date of receipt. Your receiving location then becomes the TLC source under 1.1345(b)(5).

When you must keep the supplier’s code

You keep the supplier’s code whenever you receive, store, pick, consolidate onto pallets or ship a listed food without transforming it. FDA’s TLC page puts it plainly: “Once a TLC is assigned, it must stay the same as the food moves through the supply chain; it can only be changed if the food is transformed.”

Assign a new code, or carry the one you received? A listed food is in your hands 1. Initial packing of a raw agricultural commodity, or first land-based receiving of fish? Yes Assign a new TLC. You are the TLC source. No 2. Transformation: processing, commingling, repacking or relabeling, with a listed food as the output? Yes Assign a new TLC. Link every input TLC to the output lot. No 3. Received from a supplier the rule does not apply to, with no TLC assigned yet? Yes Assign a TLC. Your dock is the source. (Not retail or restaurants) No Keep the supplier's TLC and TLC source exactly as received. Record receiving and shipping KDEs. Pallet breaks, case picks, internal stickers, license plates and moves between docks at one street address do not change the code.
Simplified for illustration; exemptions and the like-into-like repacking option are not shown. Source: FDA, 21 CFR 1.1320, 1.1310 and 1.1345(b); FDA draft Q&A guidance (February 2026), checked November 2026.

Pallet breaks, case picks and license plates

Breaking a pallet does not create a new lot. FDA’s draft Q&A guidance says that if a distribution center “breaks a pallet to remove one case (or breaks a case to remove an item…)” to fill an order, “the TLC would not change, and the distribution center would not become the TLC source.” The 1.1310 definition of holding already includes “breaking down pallets” as an activity performed for distribution.

Internal labels are also safe. The same guidance says that a sticker a distribution center puts on each incoming case “to help with internal tracking” is not relabeling, and neither is “adding a pallet license plate or other type of designation on a pallet.” Your LPN and your case sticker can carry your internal identifiers, as long as the record behind them still points to the supplier’s TLC.

Cross-docking and consolidation

A cross-dock that moves cases from inbound trailers to outbound trailers without opening them is receiving and shipping. You record the receiving KDEs, you record the shipping KDEs, and the TLC passes through unchanged. Building a mixed outbound pallet from cases of several lots is still holding and shipping; each case keeps its own code, and the shipping record lists every TLC on the pallet.

The line is crossed when the food itself is combined. Packing product from two lots into one new case is repacking, and combining two lots into one container is commingling. Both are transformation under the 1.1310 definition, and the output needs a new TLC with links to both inputs. A partial exemption for certain commingled raw agricultural commodities in 1.1305(h) does not cover produce subject to FDA’s produce safety standards; if you handle shell eggs or seafood, check it with counsel.

Moves between your own buildings

Shipping and receiving include intracompany shipments “from one location at a particular street address of a firm to another location at a different street address of the firm.” A transfer from your Kansas City building to your Wichita building therefore needs shipping and receiving records, but the TLC does not change. A move from one dock to another inside the same building at one street address is not a shipping event at all, as FDA’s draft Q&A guidance explains.

Warehouse activities that look like transformation

Several common warehouse tasks change the food or its packaging a little. The test is the 1.1310 definition: is the food being processed, commingled, repacked or relabeled, with a listed food as the output? The table below applies FDA’s text and its draft Q&A answers to tasks a distributor or 3PL actually performs.

Warehouse activity Transformation? What happens to the TLC Basis
Break a pallet to pick cases No Unchanged Draft Q&A 19; “holding” in 1.1310
Break a case to pick inner units (for example, jars of nut butter) No Unchanged Draft Q&A 19
Apply an internal sticker or LPN No Unchanged Draft Q&A 23
Cull damaged product from a lot without repacking No Unchanged; the received and shipped quantities differ Draft Q&A 20
Sort and repack produce into new cases Yes New TLC in most cases; you become the TLC source 1.1310; draft Q&A 19
Repack like into like within the same lot Yes May keep the same TLC, recorded as transformation Draft Q&A 19, citing the preamble
Combine two lots into one container Yes (commingling) New TLC linked to both inputs 1.1310
Relabel under your own brand Yes (relabeling) New TLC; you become the TLC source 1.1310; draft Q&A 23
Freeze, cut, mix or otherwise process Yes, if the output is on the list New TLC linked to inputs 1.1310, 1.1350

Culling deserves a closer look because it is easy to get wrong in software. FDA’s draft guidance says that if food is removed from a lot “due to poor quality, but the original lot is not repacked or otherwise transformed,” the change is not a transformation. It shows up as a difference between the quantity on your receiving record and the quantity on your shipping record. Your WMS should post the culled quantity as an adjustment against the supplier’s TLC, with a reason code, and not create a new lot to hold the good product.

Two further points matter for 3PLs. First, under 21 CFR 1.1455(b), a covered company may have another entity keep its records, but it stays responsible for ensuring they can be retrieved and provided onsite within 24 hours of a request for official review. Second, FDA’s draft guidance says there is no “safe harbor” for a firm that receives incomplete or inaccurate records from its supplier. If a supplier’s ASN carries the wrong code, your receiving record is still your responsibility.

A data model that keeps the supplier’s code intact

The rule’s demands on your data come down to four ideas. Store the code you received exactly. Store where it came from. Keep your own lot numbers separate. Link outputs to inputs whenever you transform.

Lot fields in an ERP or WMS exist for internal stock control. They can be short, uppercased on entry, stripped of leading zeros, or reused as a key for expiry and FEFO picking. Those habits are fine for an internal lot and harmful for a TLC.

Field Example (fictional) Populated at Rule of thumb
tlc 0412-RM-07B Receiving, or at assignment if you create it Store as text, exactly as received. No trimming, case change or padding.
tlc_source_type location or reference Receiving Tells you which of the two forms the supplier sent.
tlc_source_location Business name, phone, street address or coordinates, city, state, zip, country Receiving Separate fields, matching the location description definition.
tlc_source_reference An FDA Food Facility Registration Number, a web address or another reference your customer accepts Receiving Kept as sent; do not resolve it into a location yourself.
tlc_assigned_by_us true or false Assignment True only for initial packing, first land-based receiving, transformation or 1.1345(b) receipts.
assignment_event transformation Assignment The reason you created the code, for your traceability plan and audits.
internal_lot L26-1187 Receiving or production Your stock-control lot. Can drive FEFO and holds. Never sent as the TLC unless you assigned it as one.
transformation_inputs A list of input TLC, TLC source, product and quantity used Transformation One row per input lot, linked to the output TLC.

The code is unique only within its source

The definition says a TLC identifies a lot “within the records of the traceability lot code source.” Two packers can both use 240611-01. If your system keys traceability records on the code alone, a recall query for one packer’s lot will pull the other packer’s product too.

The safe key for a received lot is the pair of TLC and TLC source (or source reference). You can add the supplier and item as well, because that is how people search. The point is that the TLC alone is not a primary key.

Keep codes exactly as received

Every transformation of the string is a risk. A spreadsheet import that turns 00731 into 731, a scanner profile that drops a trailing letter, or a database column limited to 10 characters can all change the code. When FDA or a customer later searches for the supplier’s code, your record will not match theirs.

Two practical rules help. Store the TLC in a text field long enough for the longest code you have seen from any supplier, with room to spare. And capture it by scan or electronic message wherever you can, so that nobody retypes it.

Under 21 CFR 1.1350(a), the record for each new lot must include, for each listed-food input, its TLC, its product description and the quantity used from that lot, plus the new TLC, the TLC source, the completion date, the product description, the quantity and the reference document. In data terms, that is a one-to-many link from the output lot to its input lots, with quantities. Most production modules already record component consumption. The gap is usually that they record the internal lot, not the supplier’s TLC.

Example (fictional). A regional distributor, Northbank Foods, receives romaine (item EX-20118) from two packers. Its WMS has a single lot field, 12 characters, uppercase only, and receiving clerks type in whatever the case label shows. Packer A uses codes like rm0611-02b; packer B uses 240611-01, and so does a third packer of cucumbers. In a mock recall for packer A’s lot, the query returns RM0611-02B, which no longer matches packer A’s records, and misses two receipts where the clerk dropped the final letter. The fix in the requirements: a separate TLC text field of 40 characters with no case conversion, a TLC source field set from the supplier’s ASN, the internal lot kept for FEFO, and a uniqueness check on TLC plus TLC source instead of TLC alone. The acceptance test is a query that returns every receipt of one packer’s lot and nothing else.

Capturing the code at the receiving dock

The receiving dock is the first place a TLC can get lost, because it is the first time your systems see it. The receiving KDEs in 21 CFR 1.1345(a) are the TLC, the quantity and unit of measure, the product description, the location description for the immediate previous source (other than a transporter), the location description for where you received it, the receiving date, the TLC source or source reference, and the reference document type and number.

FDA’s distribution center example describes a flow familiar from ASN-based receiving:

  1. The supplier sends an ASN to the distributor’s EDI gateway, or emails the shipment details, including the shipping KDEs and the TLC.
  2. The WMS creates a pending arrival from the ASN.
  3. When the truck is unloaded, staff record a warehouse receipt transaction that captures the receiving KDEs.
  4. The receipt can correct products, quantities and TLCs if what was unloaded differs from the ASN.
  5. Paper documents handed over by the driver are scanned and linked to the receipt number in a document system.

The rule allows records in more than one place. 21 CFR 1.1455(g) says you do not have to keep everything “in a single set of records,” but your traceability plan must state the format and location of each. FDA also says, on its TLC page, that linkage can be achieved by putting the TLC “in the same row of a spreadsheet or database that documents the required KDEs.”

Where the code arrives from

In practice the supplier’s code reaches you through one or more of these channels, and your receiving design should name the one you trust first:

  • The ASN. The best source for a system, because it arrives before the truck. The structure of the ship notice, and where your trading partner puts lot data in it, is covered in our note on EDI 856 ship notice structure.
  • The case label. A supplier that uses GS1 case labels carries the lot under Application Identifier (10). GS1 defines AI (10) as “Batch or lot number,” with up to 20 characters from a restricted character set. A supplier whose TLC is longer than that cannot carry the whole code in AI (10).
  • The bill of lading or invoice. FDA’s published examples show a TLC and TLC source on both. Useful as a reference document, slow as a data source.
  • A QR code or a link. FDA mentions a QR code on the packaging or a related document as one way to pass the code.

Receiving rules worth writing down

Turn the dock decisions into requirements before anyone configures a screen. These are easy to leave unwritten:

  • Missing code. A listed food received without a TLC goes to a hold status, not to a pick face. The exception is a supplier on your list of suppliers the rule does not apply to, where your 1.1345(b) assignment routine runs instead.
  • Mismatch. When the scanned case label and the ASN disagree, which wins, who decides, and how is the correction recorded?
  • Multiple lots on one pallet. The receipt must split into one line per TLC, with a quantity for each.
  • Exempt supplier list. Who maintains it, from what evidence, and how often is it reviewed?
  • Listed foods. Which items are flagged as on the Food Traceability List, with an effective date, so that the rules above apply only where they should?

The scan sequence at the dock, what the handheld shows when a code is missing, and what your own outbound case labels carry are the core of our barcode, RFID and labeling work.

Passing the code to your customer

When you ship a listed food, 21 CFR 1.1340(b) requires you to provide the immediate subsequent recipient (other than a transporter) with the information in 1.1340(a)(1) through (7). That is the TLC, the quantity and unit of measure, the product description, the location description for the recipient, the location description for where you shipped from, the ship date, and the TLC source or source reference. The reference document type and number in (a)(8) is a record you keep; it is not on the list you must send.

The format is up to you and your customer. Large customers may publish their own requirements, which need not match the rule field for field. Walmart’s published Food Traceability KDE Requirements sheet, checked in November 2026, lists the transmission method as “ASN via EDI (or) EPCIS via API” and asks for more than the rule does.

Walmart sheet data element Nearest rule KDE Where it usually lives in your systems
Lot/Batch Number Traceability lot code (1.1340(a)(1)) The TLC field, not the internal lot
Traceability Lot Code Source or Traceability Lot Code Source Reference (GLN, FFRN, USDA Est Number) TLC source or source reference (1.1340(a)(7)) The TLC source fields captured at receipt
Ship-From Location, GLN, Address, Phone Location shipped from (1.1340(a)(5)) Site master
Ship-To Location, GLN, Address Immediate subsequent recipient (1.1340(a)(4)) Customer ship-to master
Ship Date Date shipped (1.1340(a)(6)) Shipment confirmation
GTIN, Product Description Product description (1.1340(a)(3)) Item master
Case Quantity, Pallet Quantity Quantity and unit of measure (1.1340(a)(2)) Shipment lines
PO Number, SSCC-18, Bill of Lading Not required by the rule as shipping KDEs; useful as reference documents Order, pallet label, carrier documents
Production, harvest or pack, best before, sell by and expiration dates (all available) Not required by the rule Lot attributes

Two design consequences follow. First, one shipment line per item is not enough; you need one line per item and TLC, because a single order can draw cases from several lots. Second, the TLC source you send must be the one you received for that lot, not your own ship-from address, unless you assigned the code yourself.

The SSCC on the Walmart list ties the pallet to the ASN. If your pallet labels are not yet generated from the same data as the ASN, our note on SSCC pallet labels covers numbering and label layout.

Assigning your own codes

If you are a packer, a processor, a repacker, or a distributor receiving from suppliers the rule does not apply to, you will create TLCs. The rule does not prescribe a format. FDA’s TLC page says your traceability plan must describe “the process used to assign a TLC (e.g., Julian date plus product code, randomized generated code, etc.),” as required by 21 CFR 1.1315(a)(3).

FDA also notes that several industry traceability initiatives identify a lot with “a combination of a globally unique product identifier, firm-assigned internal lot code, and standard date code.” In GS1 terms, that is the GTIN in AI (01), the lot in AI (10) and a date such as the pack date in AI (13), printed together on a case label. The rule does not require GS1 identifiers, but your customers may.

Design rules for a code you create

These are design choices, not requirements of the rule. Each one removes a way for a lot lookup to fail:

  1. Make it unique within your site’s records, forever. Do not reset a daily sequence in a way that repeats last year’s codes.
  2. Fit the carriers you use. If the code will travel in GS1 AI (10), keep it to 20 characters or fewer from GS1’s allowed set. If it will travel in an EDI field, check the maximum length in your partners’ guides.
  3. Keep it readable. People will read it aloud on the phone during a recall. Avoid characters that look alike, such as O and 0, or I and 1.
  4. Decide the lot size deliberately. FDA notes that “smaller traceability lots might lead to less food being affected in the event of a recall.” A lot per production run, per line per shift, or per day are all defensible; pick one and write it down.
  5. Record why you assigned it. Store the event (initial packing, transformation, receipt from an exempt supplier) with the code, so that the traceability plan and the data agree.

Example (fictional). A fresh-cut plant, Riverbend Cut Produce, makes a diced pepper mix (item EX-20230) from red and green peppers supplied by two packers. Each run is a transformation, so each output needs a new TLC. The team writes the rule into its traceability plan as: site code, two-digit year, three-digit Julian day, line number and run sequence, for example RB26172L2R03, 12 characters. At run start, the line lead scans each input case; the run cannot close until every input has a supplier TLC and TLC source on record. The output case label prints the GTIN in AI (01), the new code in AI (10) and the pack date in AI (13). The traceability record links RB26172L2R03 to both packers’ TLCs with the quantity used from each.

The 1.1345(b) case needs the same care. FDA’s fictional distribution center builds its code from the supplier number, purchase order, SKU and receipt date. That works because each of those values is already in the WMS at receipt. Whatever you choose, the code is created once, at the receipt, and never changed while the food is in your building.

Testing the design before FDA does

The real test of lot code handling is whether you can answer a question about one lot quickly and completely. Under 21 CFR 1.1455(c), records must be available within 24 hours of a request, or within a reasonable time FDA agrees to, and in some situations as an electronic sortable spreadsheet. When and how that spreadsheet is required is the subject of our note on the FSMA 204 sortable spreadsheet.

Write the test cases before you configure anything. A minimal set for a distributor or 3PL:

  1. Receive a listed food from a covered supplier by ASN; confirm the TLC and TLC source are stored exactly as sent.
  2. Receive the same item with a case label that disagrees with the ASN; confirm the mismatch rule.
  3. Receive from a supplier the rule does not apply to; confirm a TLC is assigned once and the receiving location becomes the source.
  4. Break a pallet and pick single cases to three customers; confirm all three shipping records carry the original TLC.
  5. Cull damaged product; confirm an adjustment against the original TLC, with no new lot.
  6. Repack or relabel, if you do either; confirm a new TLC with links to every input.
  7. Transfer stock to another of your own buildings; confirm shipping and receiving records with the same TLC.
  8. Query one supplier’s lot by TLC and TLC source; confirm the result contains every receipt and shipment of that lot and nothing else.

Our UAT test plan template has a format for writing these as pass or fail tests with expected results.

What to do next

Start with the facts you already have. The first piece of work is finding where each code and source field lives today, and where it gets changed or dropped.

  • List every Food Traceability List item you handle, and flag it in the item master with an effective date.
  • For each site, mark which events you perform: receiving, shipping, transformation (including repacking and relabeling), and receipt from suppliers the rule does not apply to.
  • Find the field where the supplier’s TLC lands today. Check its length, case handling and whether anyone retypes it.
  • Confirm where the TLC source or source reference is stored, or whether it is stored at all.
  • Separate the supplier’s TLC from your internal lot in the data model, and key traceability records on TLC plus TLC source.
  • Write down your assignment rule for the codes you create, and add it to your traceability plan.
  • Map the shipping KDEs to each large customer’s published requirements.
  • Run the eight test cases above as a mock request for one lot.

The FSMA 204 KDE worksheet lists the required data for each critical tracking event, so you can mark which of your systems holds each one. For how the capture and export fit around an existing ERP and WMS, see our page on food traceability records. If you want help turning the checklist into written requirements, in our engagements we start by walking the dock and writing the requirements before anything is built; you can describe your process to us.

Working on this problem?

If this field note describes a process you need to fix or build software around, tell us about it. We start with your process, your systems and your deadline.