Lot and batch tracking in Cin7 for food brands: how to set it up so the ledger agrees
Your lots are tracked and your expiry dates are entered, yet last month's batch margin still does not match the books. This post shows where lot tracking in Cin7 Core tends to drift, and the setup and governance that keep warehouse and ledger in sync.
On this page
- How does lot tracking work in Cin7 Core for food?
- Why does lot data go missing between receiving and the pick?
- Why do batch margins not match the books?
- How do you run a recall drill in Cin7 Core?
- Why start lot discipline before the FDA compliance date?
- How to set up lot and batch tracking this week
- When should you patch, reconfigure, or rebuild a lot-tracking setup?
- Frequently asked questions
TL;DR
- Lot data in Cin7 Core goes missing at the dock and surfaces at the worst moment, in a recall or a retailer query. FEFO (first expired, first out) by batch is the costing method that protects any SKU with a shelf life.
- Expiry dates and lot numbers have to be captured at receiving and carried through production, transfers, and adjustments, because a lot that loses its data at one step cannot be traced after it.
- Cin7 Core does not check batch or serial numbers for duplicates, so a written numbering convention is part of the configuration.
- If you sell oldest-expiry first but cost on a different rule, cost of goods sold lands on the wrong batch and batch margins stop agreeing with the ledger.
- The FDA's food traceability rule has a compliance date of July 20, 2028, and the lot data you need then is the data your receiving team creates today.
Food brands on Cin7 Core lose traceability at the dock, and nobody finds out until a recall call or a retailer query lands. Fiskal is the Cin7 specialist that closes that gap, and the work starts with how lots are configured, captured, and costed. The lot number exists in Cin7, but the dock and the ledger are telling different stories. Your physical process and system process are no longer in sync.
This post covers how Cin7 Core, the inventory platform formerly called DEAR Systems, handles lots and batches for food brands, where the setup usually drifts, and how to configure it so traceability and costing agree. It finishes with a checklist your operations lead and bookkeeper can run this week.
How does lot tracking work in Cin7 Core for food?
Cin7 Core tracks lots through the costing method on each SKU, so the decision is made when the SKU is created. Cin7 supports batch tracking and FEFO inventory rotation for food and beverage, and a lot is a group of units produced or received together, sharing a lot number and usually an expiry date.
The choice that matters is the costing method. Batch-numbered stock can be picked first in, first out or first expired, first out, and an expiry date is mandatory on a product with the FEFO method. A third option, Special costing, leaves the pick to the user. That suits some goods, but it is the wrong default for perishables.
| Costing method | How stock is picked | Fits food when |
|---|---|---|
| FEFO (batch) | Earliest expiry first, expiry date mandatory | Any item with a shelf life, which covers most food and beverage |
| FIFO (batch) | Oldest received first | Shelf-stable goods where received date and expiry run in the same order |
| Special (batch) | The picker chooses the batch | Retailer-specified lots or promotional dating, with a rule for who chooses |
Where stock is auto-picked on a FEFO SKU, the batch cannot be changed at the pick. That protects rotation, and it also means any exception has to be designed in rather than improvised on the floor.
Why does lot data go missing between receiving and the pick?
Lot data goes missing when a step in the flow accepts stock without a lot number or expiry date, so the record exists but cannot be traced. The usual gaps are receiving, stock adjustments, transfers between locations, and production outputs.
The first symptom is not an error message. It is a stock take that reconciles on quantity while the batch view looks wrong, or a recall query that returns a lot with the wrong location. Cin7 will not warn you at the point of entry, because Cin7 Core does not check whether a serial number already exists before it registers a new one, and the same absence of a uniqueness check applies to the way batch numbers are entered.
Symptom, root cause, and fix
| Symptom | Likely root cause | Fix |
|---|---|---|
| Two live records for one lot | Free-typed lot numbers at receiving, no convention | Written lot format, receiving scan or paste, never retype |
| Short-dated stock shipped while longer-dated stock sat | SKU set to FIFO or Special, not FEFO | Reset costing method on new SKUs, plan a controlled migration for existing ones |
| Batch margin does not match the books | Pick rule and cost rule disagree, or landed cost sits in expenses | Align pick and costing rules, allocate additional costs to the purchase |
| Finished lot has no ingredient history | Production output saved without lot and expiry | Make lot and expiry entry part of the production run close |
Production deserves its own mention. Cin7 lets a team add a finished product with a batch number and expiry date to the production run output, and that step links ingredient lots to the finished lot a customer receives. If the floor skips it, the genealogy ends at the kitchen door.
Why do batch margins not match the books?
Batch margins drift from the books when the way you pick stock and the way you cost it disagree. If the warehouse sells the earliest expiry first but the costing rule assigns cost on another basis, cost of goods sold lands on the wrong batch, and the margin on a lot looks wrong even though nothing in the warehouse went missing.
The fix starts at the root rather than the report. A manual journal closes the gap and hides the cause. We trace the difference back to the lot, the receiving record, and the cost attached to it. Landed cost is a frequent culprit, since freight and duty that sit in expenses rather than inventory never reach the batch. The mechanics are covered in how to configure landed costs in Cin7.
A lot with a missing entry is a gap a recall team will find first.
When quantity is right but value is not, the next step is reconciliation. That gap shows up the first time you reconcile Cin7 Core and QuickBooks Online, and a stock take on its own will not close it, because stock takes reconcile quantity, not necessarily value.
How do you run a recall drill in Cin7 Core?
You run a recall drill by picking a real lot and asking Cin7 to show where it came from and where it went. The Batch/Lot Recall report shows customers, stock on hand, and suppliers for selected lots and batches, and Cin7 can prepare recall letters for customers from the same view. A companion Lot Expiry Report shows quantity on hand by batch with its expiry date.
Treat the drill as a test of your data, not of the software. Choose one finished lot, trace it back to the ingredient lots and suppliers, then forward to every customer and location. Anything that cannot be answered in a few minutes points at a step where lot data was not captured.
Why start lot discipline before the FDA compliance date?
Start now because the lot-level data the rule needs is created at receiving, and fixing habits takes longer than fixing settings. The FDA's food traceability rule requires records of key data elements tied to critical tracking events for foods on the Food Traceability List, with information provided to the FDA within 24 hours or a reasonable agreed time. The compliance date has moved to July 20, 2028, and some retailers and distributors are already writing traceability into supplier terms.
The rule has a practical consequence for a Cin7 setup. Whatever your lot format and receiving process look like today will be the record you produce later, so a clean convention now saves a rebuild. Whether a given food is on the list is a question for your quality lead, and this post does not assess it.
How to set up lot and batch tracking this week
Work through these steps in order. Each one stands on its own, and together they cover configuration, behaviour, and governance.
- Audit the costing method on every perishable SKU. Export the SKU list and flag anything with an expiry date that is not on FEFO (batch).
- Write a lot number convention. Agree one format, for example a production date plus a site code plus a sequence, and publish it where receiving can see it.
- Make expiry mandatory at receiving. Train the receiving team to enter lot and expiry on every line before stock is booked in, and refuse to book stock without them.
- Close production runs with outputs. A run is not complete until the finished lot, its number, and its expiry are saved against the output.
- Align pick rule and cost rule. Confirm that the order you pick in is the order your costing follows, and test it with one sale per SKU family.
- Allocate landed cost to the purchase. Move freight and duty from expenses into the additional costs on the purchase order, so lots carry their true cost.
- Run a recall drill monthly. Pick one lot, trace it both ways, and log the time it took and every gap found.
- Set a governance owner. Name one person who reviews the Lot Expiry Report weekly, signs off exceptions, and owns the numbering convention.
Behaviour change carries most of this list. A setting can enforce FEFO at the pick, but only a trained receiving team keeps lot and expiry data clean. Cin7 onboarding support includes the people and process side, not only the configuration. For brands with ingredients and recipes, the same discipline applies to bill of materials accuracy.
When should you patch, reconfigure, or rebuild a lot-tracking setup?
Patch when the settings are right and a few records are wrong, reconfigure when a costing method or receiving flow is wrong, and rebuild when lot data has been missing for long enough that history cannot be trusted. The costing method is the deciding factor, since tracking is set through it and some choices are hard to unwind once stock has moved.
| Situation | Approach | Why |
|---|---|---|
| Settings correct, scattered missing expiry dates | Patch | Fix records, add the receiving rule |
| Perishables on FIFO or Special, mixed lot formats | Reconfigure | Costing method and convention need to change going forward |
| No lot data for months, margins unexplained | Rebuild | Trace and restate before layering new rules on top |
Run the Fiskal Score to see where your setup stands. It gives a measured view of your configuration, inventory management, and costing before anyone changes a setting, and it looks across People, Systems, and Finance, so the result points at the exact part that needs work. Fiskal's food and beverage inventory and accounting work follows the same order: diagnose first, then fix.
Frequently asked questions
How do you track lots for food inventory in Cin7 Core?
Set the SKU's costing method to FEFO (batch), capture the lot number and expiry date at receiving, and carry both through production, transfers, and adjustments. Cin7 then picks the earliest-expiring lot first and reports on lots and recalls.
Does Cin7 Core support FEFO for food brands?
Cin7 offers FEFO (batch) costing, which picks batch-numbered stock by earliest expiry and requires an expiry date on the SKU. Auto-picked FEFO batches cannot be changed at the pick, so plan exceptions in advance.
Can Cin7 Core run a product recall?
Cin7 has a Batch/Lot Recall report that shows customers, stock on hand, and suppliers for selected lots, and it prepares recall letters. The report is only as complete as the lot data your team captures at receiving, production, and the pick.
Does Cin7 Core stop duplicate batch numbers?
Cin7 Core does not check for duplicate batch numbers. It does not check whether a batch or serial number already exists when you enter it. A written numbering convention and scan or paste entry at receiving close that gap.
Why do my batch margins not match my accounting system?
The usual causes are a pick rule and a costing rule that disagree, landed cost sitting in expenses instead of inventory, and lots saved without cost at adjustment. Trace the difference to the lot and its receiving record, then fix the rule, not the report.
Book a diagnostic conversation with Fiskal if lot tracking is live and your margins still do not agree with the books, or start with the Fiskal Score to see where the setup stands.


