Book a call

Food traceability software: what inventory businesses need before they buy

Your lots are tracked, your expiry dates are entered, and last month's batch margin still does not match the books. This post covers what food traceability software has to do, where inventory systems and accounting systems fall short, and how to set up lot data so it holds up on the day a recall or an FSMA 204 request arrives.

Fiskal6 min readUpdated
On this page
  1. Why does traceability fall apart after the software goes live?
  2. What does food traceability software need to do?
  3. Cin7 Core vs QuickBooks Online: who holds the lot data?
  4. Which costing method should a food business choose?
  5. What does lot traceability look like when it breaks?
  6. How to make traceability audit-ready this week
  7. When should you patch, reconfigure, or rebuild?
  8. Frequently asked questions

TL;DR

  • Traceability lives or dies at the receiving dock. The lot number and expiry date captured there have to carry through production and transfers, and trace every lot forward to customers and backward to suppliers. For most inventory businesses between $1m and $100m, that capability already sits inside an inventory platform such as Cin7 Core.
  • The FDA's Food Traceability Rule has a compliance date of July 20, 2028, and the lot data it needs is created at your receiving dock every day. Some retailers already write traceability into supplier terms.
  • QuickBooks Online (QBO) values inventory on a FIFO basis but holds no lot or expiry fields, so lot-level traceability has to live in the inventory system and reach the ledger through clean mapping.
  • The costing method you pick when you create a product decides how picking, cost of goods sold, and recall reports behave. Choose first expired first out (FEFO) for anything with a shelf life.
  • Run a mock recall each quarter, run a duplicate lot check each month, and give one person ownership of lot naming rules.

Why does traceability fall apart after the software goes live?

It falls apart because the physical process and the system process drift out of sync. A receiver skips the expiry field on a busy Friday, a transfer drops the batch number, and a production job consumes an ingredient from the wrong lot. The software still shows green, and nobody finds out until a customer, a retailer, or an auditor asks which lots went where.

The usual next move is a search for new software. In most cases the software is not the gap. These businesses already own a system that tracks lots, expiry dates, and bills of materials, and the setup around it no longer matches how they make, store, and sell stock. A reconfigured setup closes the gap, and that is where Fiskal's methodology starts. This post covers what to demand from food traceability software, how Cin7 Core and QBO split the work, and a checklist you can run this week.

What does food traceability software need to do?

Food traceability software needs to record where every lot came from, what happened to it, and where it went, then produce that record quickly. The FDA's rule is built on the same idea: covered businesses keep Key Data Elements tied to Critical Tracking Events and provide information to the FDA within 24 hours, or within a reasonable time the FDA has agreed.

In practical terms, that breaks down into six capabilities:

  • Lot and expiry capture at receiving, so the data exists from the first touch
  • Component to finished goods mapping, so a recall can trace an ingredient lot into every batch that used it
  • Forward and backward lot reports, covering customers, stock on hand, and suppliers
  • Expiry-aware picking, so the oldest expiry ships first
  • Costing that follows the lot, so margin lands on the batch that was sold
  • A clean handoff to the ledger, so finance and operations see the same numbers

Cin7 covers most of this natively. Cin7 Core tracks batches for freshness and compliance and manages FEFO, its production records map component batches to finished product batches, and its Batch/Lot Recall report lists customers, stock on hand, and suppliers for a selected lot. Configuration decides how much of that you get, and it is where most setups stall. If you run a food business, see how Fiskal works with food and beverage operators.

Cin7 Core vs QuickBooks Online: who holds the lot data?

Cin7 Core holds the lot data and QuickBooks Online holds the financial result. That split is the right design, and it fails when people expect the accounting system to do the inventory system's job.

QBO always treats the first units purchased as the first units sold, and its costing method cannot be changed later. QuickBooks lot and serial numbers with expiration dates sit in a different product: QuickBooks Desktop Enterprise offers them once Advanced Inventory is on. A QBO-only business therefore needs an inventory platform to carry lot-level detail.

QuestionCin7 CoreQuickBooks Online
Lot and expiry fieldsNative, tied to the product costing methodNot available, lot detail lives elsewhere
Expiry-aware pickingFEFO costing picks by first expiryFIFO by purchase order
Recall reportingBatch/Lot Recall reportNot designed for lot recall
Role in the stackWarehouse record of what movedLedger record of financial impact

The financial side still matters. When Cin7 and QBO fire at different moments, timing differences appear, and unmanaged ones show up as inventory and COGS gaps. You meet that gap the first time you reconcile Cin7 Core and QuickBooks Online.

Which costing method should a food business choose?

Choose FEFO for anything with an expiry date, and make the costing method match how the warehouse picks. Cin7 offers FIFO by batch, FEFO by batch, and special batch costing, and tracking is switched on through that costing method rather than a separate toggle. If you sell the oldest expiry first but cost by another rule, cost of goods sold lands on the wrong batch.

That is also why this decision belongs at product creation. In Cin7, a non-serialised product cannot be converted to a serial method later, so the SKU has to be planned before it is built. Treat the costing method as a one-way door.

What does lot traceability look like when it breaks?

It looks like a symptom in finance that has a root cause in operations. The table below shows the patterns Fiskal sees most on food and beverage setups, written as diagnostics.

SymptomLikely root causeFix
Recall report misses a customerLot number typed differently at receiving or transferWritten lot naming rule, scanner-first receiving
Batch margin does not match the booksCosting method differs from the picking ruleAlign FEFO costing with picking, review open batches
Two live records for one lot or serialNo uniqueness check at entryMonthly duplicate report, numbering convention
Production variance lands in the ledgerRecipe does not match real yieldUpdate the bill of materials from floor data
Margins look low across a rangeLanded cost sitting in expenses instead of inventoryRemap landed cost to inventory

Two of these deserve a closer look. Cin7 Core does not check whether a serial number already exists, so duplicates appear silently through imports, transfers, and returns. Batch numbers carry the same exposure, so the numbering convention is yours to own. The second is landed cost: freight and duty that never reach inventory distort every lot's margin, which is why landed cost mapping decides whether your margins add up.

The date stamp on a milk carton makes the point. It only works if the shelf is rotated the way the stamp says, and if the till charges the right batch cost. Software gives you the stamp. Process and governance rotate the shelf.

How to make traceability audit-ready this week

Run these steps with your operations lead and your bookkeeper. Each one stands alone, and together they give you a traceable setup.

  1. Pull a lot inventory list. Export every product with a shelf life and confirm each has a batch or FEFO costing method, because anything on the wrong method needs a planned fix rather than a quick toggle.
  2. Test one recall. Pick a received ingredient lot and run the Batch/Lot Recall report, then check that every finished batch and customer the lot touched appears. Time it, since the FDA's rule expects records within 24 hours.
  3. Check expiry capture at receiving. Sample 20 recent receipts and count how many carry an expiry date and a lot number in the right format.
  4. Look for duplicates. Search for repeated lot and serial values across receiving, adjustments, and transfers, and trace each one back to its entry point.
  5. Compare costing to picking. Confirm that the costing method, the pick rule, and the way the warehouse physically rotates stock all say the same thing.
  6. Reconcile the ledger. Tie Cin7 stock on hand to the QBO inventory asset, and trace any difference to its source rather than to a manual journal.
  7. Set the governance rule. Name one owner for lot naming, set a retroactive change policy, and schedule the recall test every quarter so the setup holds.

Governance is what keeps the rest in place. Without a named owner, the setup drifts after go-live, which is the pattern behind a Cin7 system that gets worse over time. A structured Cin7 inventory audit gives you the baseline to compare against.

When should you patch, reconfigure, or rebuild?

Patch when the data is clean and one rule is wrong, reconfigure when the costing method or mapping is wrong across a range, and rebuild when lot data was never captured at receiving. A missing expiry field on a few SKUs is a patch. A costing method that conflicts with picking across your catalogue is a reconfigure. Months of receipts without lot numbers is a rebuild, because the history cannot be recreated from the system alone.

The Fiskal Score measures People, Systems, and Finance, including product data integrity, purchasing and receiving, inventory valuation, and ERP to accounting reconciliation, so the result points at the exact area that needs work. If your setup is live but not working, Cin7 onboarding support covers receiving discipline and team adoption, and Cin7 implementation covers a rebuild of costing, mapping, and the accounting handoff.

Frequently asked questions

What is food traceability software?

Food traceability software records lot numbers, expiry dates, and every movement of an ingredient or finished batch, then reports them forward to customers and backward to suppliers. For most inventory businesses, an inventory platform like Cin7 Core already does this when configured correctly. The accounting system receives the financial result.

When is the FSMA 204 compliance date?

The FDA's Food Traceability Rule has a compliance date of July 20, 2028, moved from January 20, 2026. Some retailers and distributors already write traceability into supplier terms, and the lot data you need in 2028 is the data you create at receiving today.

Does QuickBooks Online track lot numbers and expiry dates?

QuickBooks Online uses FIFO costing but has no lot or expiry fields, and QuickBooks documents lot and expiry tracking for QuickBooks Desktop Enterprise with Advanced Inventory. A QBO business needs an inventory platform for lot detail, with a clean integration into the ledger.

Which costing method works best for expiry dates in Cin7 Core?

FEFO by batch suits stock with a shelf life, because it picks the first expiry first and relieves cost from the same lot. Pick the method when you create the product, since changing it later is difficult.

How often should we test a recall?

Run a mock recall each quarter on one ingredient lot and time it. Track how long the report takes, which customers or batches it missed, and the cause of each gap. That record becomes your evidence of control.

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