· 2 min read · FoodChainAPI editorial
Build an FTL Classification Audit Trail That Survives Catalog Changes
An explainable FTL decision needs more than the current value of a product flag. Preserve what was reviewed, the evidence available at the time, and why the reviewer accepted or rejected a candidate category.
Save a decision packet
Record the stable product ID, exact query, candidate results, relevant specifications, FDA source links, review date, reviewer, and conclusion. Include the exclusions or exemption basis considered. A screenshot can supplement the record, but structured evidence is easier to search and compare.
Keep lookup time separate from source-verification time. Calling an API today does not prove its underlying category data was verified today. Check any data-version information actually returned; if it is absent, record that limitation rather than inventing a freshness date.
Version the evidence
When a formulation, supplier, or product form changes, create a new review record instead of overwriting the old one. Link it to the revised specification and identify which decision it replaces. Historical lots may still need the earlier product context.
Store candidate matches and the reviewed conclusion separately. A reviewer can reject a name match based on product-form evidence. If your integration later reruns the lookup, it should not silently replace that decision with the new first result.
- Capture the exact input and candidate output.
- Retain source specifications and authoritative references.
- Record who reviewed the evidence and when.
- Version changed decisions rather than overwriting history.
- Define triggers for reassessment.
Make reassessment selective
Useful triggers include changed ingredients, changed processing, new supplied form, updated FDA guidance, or a resolved ambiguity. Rechecking every SKU daily without better evidence can create noise. Review changed products and affected categories deliberately.
FoodChainAPI supplies category candidates and reference information; your application owns the decision history. During an internal drill, ask a second reviewer to explain one accepted match, one exclusion, and one unresolved item from the saved packets alone. Missing explanations identify the evidence fields you still need.
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.