· 2 min read · FoodChainAPI editorial
Traceability Lot Code vs. SKU and GTIN: What Your Database Needs
A SKU or GTIN identifies a product. A traceability lot code identifies a particular traceability lot within its source's records. Treating those identifiers as interchangeable makes a recall query return either too much inventory or too little.
Keep product and lot identity separate
Two deliveries can have the same SKU and different traceability lot codes. Conversely, a single inbound lot can be split into multiple inventory positions without becoming multiple new traceability lots. FDA does not prescribe one universal TLC format; the identifier must work within the records of its source.
Model a product table for catalog information and a lot table for the original TLC and its source. Store event records against the lot. Your own internal row ID can simplify joins, but it should not replace the supplier-provided code in records exchanged downstream.
Preserve the original representation
Do not parse a lot code as a number. Leading zeros, punctuation, and case may matter to the supplier. Store the original string and maintain a separate normalized search key if your application needs forgiving search. Document any normalization rather than silently changing the code.
A practical internal uniqueness key includes the TLC source and the TLC, with additional product context where your business needs it. Do not assume code '1001' from two unrelated facilities refers to the same lot. Keep a source location identity that survives changes in a supplier's display name.
product_id: cucumber-case-12
source_location_id: supplier-facility-A
traceability_lot_code: 000142-B
internal_lot_id: lot_7f29Test the joins before a recall
Create test records with identical TLC strings from two sources, two TLCs for one SKU, and one TLC delivered in several shipments. A lot lookup should keep unrelated sources separate while finding every event associated with the selected lot.
FoodChainAPI can help flag products for an FTL review. It does not issue TLCs or resolve supplier identities. Keep classification results in the product-review layer and traceability identifiers in the operational record layer; changes to one should not rewrite the other.
Put the product review into practice
Start with a candidate category in the free FTL lookup. Check product form and exemptions against FDA sources, then save the evidence behind your decision.
API referenceUse in Chrome, ChatGPT, or ClaudeProduct review walkthrough
Sources and scope
FDA sources checked October 4, 2026. Workflow suggestions are implementation guidance; category matches do not establish exemption or compliance status. Check the current FDA requirements for your product and activities.