Book a call

FSMA 204 traceability: what the rule means for your Cin7 inventory system

Your lots are tracked and your expiry dates are entered, but could you hand the FDA a sortable record of one lot's journey inside 24 hours? This post maps the FSMA 204 requirements onto a Cin7 Core setup and shows what to fix first.

Fiskal7 min readUpdated
On this page
  1. What is the FSMA 204 traceability rule?
  2. Does the rule apply to your foods?
  3. When do you have to comply?
  4. What does FSMA 204 ask of your inventory system?
  5. Can Cin7 Core support FSMA 204 traceability?
  6. Where do Cin7 traceability setups break down?
  7. How to prepare your Cin7 setup this week
  8. Should you patch, reconfigure, or rebuild?
  9. How Fiskal approaches traceability in Cin7
  10. Frequently asked questions

TL;DR

  • FSMA 204 (the FDA Food Traceability Rule) requires businesses that make, process, pack, or hold foods on the Food Traceability List to keep Key Data Elements for each Critical Tracking Event and produce them for the FDA within 24 hours of a request.
  • The compliance date is July 20, 2028, and the requirements themselves have not changed, so the data you create at receiving today is the data you will rely on later.
  • Cin7 Core tracks batch numbers and expiry dates natively, but the traceability it gives you depends on costing method, receiving discipline, and clean integrations.
  • The most common gaps are lot numbers entered inconsistently, expiry dates dropped at transfers and production jobs, supplier lot codes that never reach the system, and sales channels that bypass batch allocation.
  • A mock recall on one lot, run this month, shows you every gap in about an hour, and a governance rhythm keeps them closed.

It is the middle of a retailer onboarding call and someone asks whether you can show lot-level traceability for your best-selling SKU. Your system has batch numbers, your warehouse team scans them, and still nobody can say whether the lot on the pallet matches the lot on the purchase order, or whether the expiry date survived the transfer to your 3PL. Your physical process and system process are no longer in sync, and FSMA 204 gives you the reason to bring them back together.

This post covers what FSMA 204 requires, how those requirements land on a Cin7 Core setup, where the gaps usually sit, and the steps an operator or bookkeeper can take this week. It is built for food and beverage inventory businesses turning over $1m to $100m a year.

What is the FSMA 204 traceability rule?

FSMA 204 is the common name for the FDA's Food Traceability Rule, formally titled Requirements for Additional Traceability Records for Certain Foods. It establishes traceability recordkeeping requirements beyond existing regulations for anyone who manufactures, processes, packs, or holds foods on the Food Traceability List (FTL). It implements Section 204(d) of the FDA Food Safety Modernization Act.

At the centre of the rule is a simple pattern. You record Key Data Elements (KDEs) tied to Critical Tracking Events (CTEs), such as receiving, transformation, and shipping, and you keep the records so the FDA can trace a food through the supply chain quickly during an outbreak or recall. Each lot gets a traceability lot code, and that code is the thread every record hangs from.

Does the rule apply to your foods?

It applies if you handle a food on the list, or a food that contains a listed food as an ingredient in the same form. The Food Traceability List covers foods such as soft and unpasteurized cheeses, shell eggs, and nut butters, along with items like fresh produce and certain seafood. Some cheeses fall outside it, including hard cheeses and those that are shelf stable at ambient temperature.

The nuance that catches growing brands is the ingredient clause. A prepared food that uses a listed ingredient in its original form can be pulled in. Check the full list against your catalogue, ingredient by ingredient, before you decide you are out of scope. Exemptions exist for some small operations and for foods that pass a validated kill step, so confirm your position against the FDA's guidance rather than assuming.

When do you have to comply?

The date to plan against is July 20, 2028. The FDA extended the compliance date by 30 months and left the final rule's requirements unchanged. The extra time exists so every partner in the chain can prepare, because each business depends on accurate data from the one before it.

That dependency shapes the commercial picture. Some retailers and distributors already write traceability into supplier terms, so your customers may ask for lot-level data well before any regulator does. The businesses that win those conversations are the ones whose lot data is already clean, and building that now makes 2028 a non-event.

What does FSMA 204 ask of your inventory system?

It asks your system to hold the right data per lot and to hand it over fast. The FDA's rule requires that records and any information needed to understand them reach the FDA within 24 hours of a request, and, unless exempt, as an electronic sortable spreadsheet when the FDA is working an outbreak or recall. Records are kept for two years.

For an inventory team, that translates into five practical questions, answered per lot:

  • Which supplier lot code arrived, and on what date
  • Where the lot was received and where it sits now
  • Which production runs consumed it
  • Which customer orders it shipped on
  • Whether any adjustment or transfer changed its quantity or expiry

You also need a written traceability plan that describes how you assign lot codes and manage the records. The plan lives on paper, but the proof lives in the system.

Can Cin7 Core support FSMA 204 traceability?

Cin7 Core gives you the building blocks, and your configuration decides whether they hold up. Cin7 Core's dedicated Batch/Lot Recall function lets you enter a batch, lot, or serial number and see every affected customer order, fulfilled or not. Cin7's help documentation also covers production component tracing, so you can follow an ingredient lot into the finished goods it went into.

Setup is where it gets tricky. Batch tracking is switched on through each product's costing method (FIFO, FEFO, or Special), not a separate toggle, so the decision is made when the product is created. Cin7 Core also does not check whether a serial number already exists before it registers a new one, and the same uniqueness gap applies to the numbering discipline around batches. Receiving rules, naming convention, and integration mapping decide whether the data going in is data you can trace.

Where do Cin7 traceability setups break down?

They break at the handoffs, at the batch field itself only rarely. The table below shows the symptoms we see most often in food and beverage setups, traced to a root cause and a fix.

SymptomLikely root causeFix
One lot appears under two spellingsNo numbering convention, free-text entry at receivingDocument a lot format and enforce it at the receiving screen
Expiry date missing after a transfer or production jobExpiry captured at receiving but not carried through downstream workflowsTest each workflow with a live lot and add the step to the SOP
Supplier lot code is on the paperwork but not in Cin7Team keys an internal batch number and skips the supplier's codeDecide where the supplier lot lives and make it a required receiving step
Recall report shows fewer orders than expectedOrders from a sales channel or 3PL bypass batch allocationMap the channel and 3PL flows so lot data survives the sync
Margin on a batch does not match the booksCosting method differs from how the warehouse picksAlign FEFO or FIFO with the pick rule and review COGS by batch

Every row in that table traces back to the same pattern. A lot number that is sometimes typed by hand and sometimes scanned produces a record that is sometimes right.

Lot tracking and costing share one setting, so a traceability project is also a margin project. Cin7 offers FIFO by batch, first expired first out (FEFO) by batch, and special batch costing. If you sell the oldest expiry first but cost by another rule, cost of goods sold lands on the wrong batch. The same discipline that makes a recall report trustworthy makes your gross margin by batch trustworthy.

When the number changes without a transaction

A supplier invoice authorised after stock has already shipped can rewrite cost journals for that lot. Cin7 cancels the original estimated cost journals and rewrites them using actual FIFO or FEFO costs, with no new stock movement. This is designed behaviour, and it is the reason traceability records and financial records need one owner who reads them together. We unpack the mechanics in why Cin7 inventory valuation changes without new transactions.

How to prepare your Cin7 setup this week

Start with one lot and follow it from receiving to shipment. The steps below suit an operator and their bookkeeper working together, and each one stands on its own.

  1. Confirm scope. List every SKU and ingredient, check each against the FDA's Food Traceability List, and record the result in a shared sheet with the reason for each yes or no.
  2. Pick one live lot and run a mock recall. Choose a lot received in the last 90 days, run it through Batch/Lot Recall in Cin7 Core, and time how long it takes to list suppliers, production runs, and customers.
  3. Compare the report to the paperwork. Match the supplier lot code, quantities, and dates in Cin7 against the bill of lading and the supplier's certificate. Every mismatch is a gap to log.
  4. Write the lot numbering rule. Set one format, one place for the supplier lot code, and one owner. Put it on the receiving station as a one-page reference.
  5. Test every downstream workflow. Push the lot through a stock transfer, an adjustment, a production job, and a 3PL shipment, then check that batch and expiry survive each step.
  6. Review costing against picking. Confirm the product's costing method matches the rule your pickers follow, and check COGS for the lot in QuickBooks Online (QBO) or Xero.
  7. Set the governance rhythm. Run a monthly mock recall on a different lot, review lots with missing expiry dates weekly, and log every correction so retroactive changes stay controlled.

Behaviour change carries most of the weight here. The system can enforce a required field, but only your receiving team can decide to scan the supplier's code every time. Training and ownership belong in the plan from day one.

Should you patch, reconfigure, or rebuild?

The answer depends on how many gaps the mock recall shows and where they sit.

What the mock recall showsBest responseTypical scope
One or two missing fields, otherwise cleanPatchSOP update and retraining at receiving
Lots lost across transfers, production, or a 3PLReconfigureWorkflow settings, integration mapping, and costing alignment
Products set up with the wrong costing method, or lot data missing across the catalogueRebuildProduct data and costing structure, planned before changes touch history

If you are unsure which row you are in, the Fiskal Score maps your financial operating system across People, Systems, and Finance, including inventory management, purchasing and receiving, and product data integrity. It gives you a baseline before you commit to a fix.

How Fiskal approaches traceability in Cin7

Food and beverage owners usually arrive with a software question and leave with a setup question. The software already tracks lots, expiry dates, and bills of materials. What no longer matches is how the business makes, stores, and sells stock. Fiskal's Cin7 onboarding support starts with a system audit across usage, sync errors, and connections to QBO, Shopify, and 3PLs, then builds the SOPs and ownership that keep lot data clean. Where the gaps run deeper, a Cin7 implementation rebuilds the product and costing structure. After go-live, the same discipline applies to reconciling Cin7 Core and QuickBooks Online, because a lot is only traceable if its cost and its quantity agree in both systems.

Frequently asked questions

What is FSMA 204 traceability in simple terms?

It is the FDA requirement to record specific data for each lot of a listed food at key points like receiving, transformation, and shipping, and to produce those records within 24 hours of a request. The July 20, 2028 compliance date applies, and your system needs to hold the lot-level data well before then.

Do I need new software to meet FSMA 204?

Not necessarily. The FDA states you do not need to duplicate records you already keep, and you may supplement existing records to cover the required information. If your inventory system tracks lots and expiry dates, the work is usually configuration, receiving discipline, and integration mapping rather than a new platform.

Can Cin7 Core handle lot traceability for food?

Yes, within limits set by your configuration. Cin7 Core supports batch tracking with expiry dates, FEFO costing, a Batch/Lot Recall function, and production component tracing. It does not check batch or serial uniqueness for you, so your numbering convention and receiving process carry that responsibility.

What is a traceability lot code?

It is the identifier assigned to a lot of a listed food, which links the Key Data Elements recorded at each Critical Tracking Event. In practice, it is the lot number your team assigns or receives, so it needs one format, one location in the system, and one owner.

What should I do first to prepare?

Run a mock recall on one recent lot. Time how long it takes to list the supplier, production runs, and customers, then compare the result with your paperwork. The gaps you find become your work list, and the exercise takes about an hour.

The Fiskal Score //

Want this sorted in your business?

We start with the Fiskal Score, a 100 point read on your people, process and technology.

Keep reading

Cin7 Core vs Cin7 Omni: which one fits your business

Cin7 Core is the self-serve platform with published plans, and Cin7 Omni is the customisable platform quoted by demo. This post shows how to pick between them by tracing one order through to QBO or Xero.

Fiskal6 min read