Expiry date tracking in Cin7 Core: how to set up FEFO, picking rules, and reports that hold up
Your lots are tracked and your expiry dates are entered, yet the oldest stock still ships last and the write-offs keep arriving late. This guide walks through setting up expiry date tracking in Cin7 Core so shelf life lives in the system and the ledger, not in someone's memory.
On this page
- How does expiry date tracking work in Cin7 Core?
- Which costing method should you use for expiring stock?
- How do you capture expiry dates at receiving?
- How do you enforce FEFO picking in the warehouse?
- How do you report on stock that is about to expire?
- What does expired stock do to your books?
- Symptom, root cause, and fix at a glance
- What can your team do this week?
- When is it time to bring in a specialist?
- Frequently asked questions
TL;DR
- Expiry dates that nobody trusts mean the wrong stock ships and write-offs surface after the month closes. In Cin7 Core, expiry tracking runs through the FEFO (first expired, first out) batch costing method, and an expiry date is mandatory for any product set to it.
- The costing method is the decision that matters most, so choose it when the SKU is created. Serialised methods cannot be applied to an existing non-serialised product later, which means a new SKU. We see this one regularly, and the fix is cheap when it is planned before the product is built and costly when it is found after stock has moved.
- Capture batch and expiry at Stock Received on the purchase order, then enforce rotation in the warehouse settings. By default, WMS pickers can scan any batch, with no check that it is the first to expire, so the newest run can ship while older stock sits at the back of the rack.
- Run the Lot Expiry Report on a fixed rhythm and write off or discount stock before it expires. Stock near expiry carries full cost in inventory value until someone decides otherwise.
- Cin7 Core does not block duplicate batch numbers, so a written numbering convention and an owner for receiving data are part of the setup.
A pallet of the newest production run ships to a customer while a case with 40 days left sits at the back of the rack. Finance finds the write-off three weeks later, after the month has closed. Nobody did anything unusual. The system was told the stock had arrived, but it was never told, or never made to care, when it would expire.
This post covers how expiry date tracking works in Cin7 Core, the Cin7 Core costing choice that drives it, how to enforce rotation on the warehouse floor, how to report on stock before it expires, and the governance that stops the data drifting after go-live. It is written for operators and their bookkeepers running food, supplements, cosmetics, or any other stock with a shelf life.
How does expiry date tracking work in Cin7 Core?
Cin7 Core, the inventory platform formerly called DEAR Systems, tracks expiry through the batch costing methods. Setting a product to FEFO (Batch) means batch-numbered stock is picked first expired, first out, and the expiry date becomes a required field.
There is no separate expiry toggle. Tracking is tied to the costing method, which is why it shapes how stock is picked and how its value lands in your accounts. Tracking is switched on through a product's costing method (FIFO, FEFO, or Special), so the decision belongs at product creation.
The same logic carries into manufacturing. Components with an expiry date are consumed according to the FEFO costing method in production orders, and expiry is entered on finished products when a production operation completes.
Which costing method should you use for expiring stock?
Use FEFO for anything that expires. Use batch FIFO only where you track lots for traceability but sell oldest-received first, and treat Special batch costing as a deliberate exception rather than a default.
The costing method also decides where cost of goods sold lands. If the warehouse sells the earliest expiry first but the product is costed by another rule, COGS lands on the wrong batch, and the margin on last month's run stops matching the books.
| Costing method | Pick order | Expiry date | Use it when |
|---|---|---|---|
| FEFO (Batch) | First expired, first out | Mandatory | Food, supplements, cosmetics, any dated stock |
| FIFO (Batch) | First received, first out | Batch tracked | Lot traceability without shelf life |
| Special (Batch) | First in, first out, but no order is enforced | Batch tracked | Rare cases with a documented reason |
How do you capture expiry dates at receiving?
Capture batch and expiry at the Stock Received stage of the purchase order, every time. The serial or batch number must be specified at the Pick stage of the sales process as well as the Stock Received stage of the purchase process, and if none is entered, Cin7 Core generates batch numbers automatically.
That auto-generation is where shelf life quietly goes missing. A receiver in a hurry skips the field, the system invents a batch number, and the real supplier lot and best-before date never reach the record. Fix this at the receiving dock with a rule that no PO line is received without the supplier lot and date.
Existing stock needs care too. When you switch a product over, the batch number and expiry date will only be applied to stock that has no previous batch or serial record. Stock adjustments also accept a batch and expiry, which is how you correct opening stock during a cleanup, as the stock adjustment screen asks for batch or serial number and expiry date where applicable.
Why uniqueness is your job
Cin7 Core does not check for duplicate batch numbers. A documented numbering convention and consistent data entry are essential, because two lots sharing one number cannot be separated on recall day. The same pattern shows up with serials, as in this look at a duplicate serial number in Cin7.
How do you enforce FEFO picking in the warehouse?
Turn on the product and measurement setting that recommends and enforces first-expired picking. By default, WMS lets pickers scan and select any batch or serial number, and there is no validation that the item picked is the first to expire. The result is newer stock leaving first, older stock ageing in the bin, and a write-off that traces back to a pick nobody was prompted to question.
The control sits in Settings, General settings, Product and measurement settings. In recommend and enforce mode, the system directs the WMS picker to bins holding the first in or first expired stock, and a warning appears at pick authorisation if the picked stock is not first expired. The picker can still ignore the warning, so the warning needs a supervisor behind it.
This is where behaviour change matters more than configuration. A setting does nothing if the floor learns to click past the warning. Pair the setting with a short SOP and a weekly review of overrides. For wider warehouse discipline, see this Cin7 WMS warehouse accuracy guide.
How do you report on stock that is about to expire?
Use the Lot Expiry Report. It shows all product batches with their expiry dates, so you can check quantity on hand for each batch number and when it expires. Pair it with the Inventory Movement Details Report when you need cost values for expiring stock.
The report is only as good as the receiving data feeding it. A clean report on a Monday gives your team time to run a promotion, move stock to another channel, or book a write-off in the right period. For recall readiness, Cin7 Core also has a Batch/Lot Recall report that traces a batch used in production through to finished products with their expiry dates.
What does expired stock do to your books?
Stock close to expiry carries full cost in your inventory value until someone decides to write it off. The balance sheet shows an asset that is quietly turning into a loss, and the write-off hits whichever month someone finally notices.
The expiry date has to be visible at the moment of decision, not at month end. A monthly review is too slow for short-life stock, because by the time the number reaches a report the choice to discount, transfer, or write off has already passed.
In the Play Pits customer story, untracked lot numbers turned into painful write-offs before Cin7 was set up properly. The same shape appears in health and beauty and food and beverage setups: lots tracked outside the system, dates entered but unwatched, and a margin on last month's batch that does not match the books. The cause sits upstream of the ledger, so a manual journal only hides it.
Lot data also has a longer shelf life than the stock itself. The FDA proposed moving the Food Traceability Rule compliance date by 30 months to July 20, 2028, and the lot records you will rely on then are the ones your team creates at receiving today. If those records are accurate now, a recall is a report. If they are not, it is a reconstruction.
Symptom, root cause, and fix at a glance
| Symptom | Likely root cause | Fix |
|---|---|---|
| Newest stock ships before older stock | Pick validation not enforced | Set recommend and enforce, review overrides weekly |
| Batch numbers that nobody recognises | Receiving skipped the batch field, so Cin7 auto-generated one | Make supplier lot and date mandatory on PO receipt |
| Two lots share one number | No duplicate check in Cin7 Core | Written numbering convention, one data owner |
| Write-offs land in the wrong month | No expiry review rhythm | Weekly Lot Expiry Report with a write-off decision date |
| Margin on a batch looks off | Costing method differs from how you sell | Align costing method to pick rule, then review COGS |
What can your team do this week?
Work through these steps in order. Each one stands on its own, and together they close the common gaps.
- List every SKU with a shelf life. Export your product list and mark each item that expires, including raw materials and packaging components used in production.
- Check the costing method on each one. Anything dated should sit on FEFO (Batch). Where a SKU needs a change, plan a new SKU if the method change is blocked.
- Audit the last 30 receipts. Open recent purchase orders and confirm each line has a supplier lot and a real expiry date, not an auto-generated batch.
- Switch picking to recommend and enforce. Update the product and measurement setting, then brief pickers on what the warning means.
- Write the numbering convention. One page: format, who assigns it, and what happens when a supplier lot repeats.
- Schedule the Lot Expiry Report. Pick a weekly slot, a cutoff window such as the next 60 days, and a named person who decides discount, transfer, or write-off.
- Set the governance rule. No retroactive edits to batch or expiry on received stock without a logged reason and a second approver, so closed months stay closed.
- Reconcile one expired batch end to end. Trace it from PO receipt to pick to the accounting entry in your accounting system, and note where the data stops matching.
If step eight surfaces gaps you cannot explain, that is a configuration question rather than a bookkeeping one. Your team's read of where inventory management, purchasing and receiving, and valuation are weakest will tell you whether to patch or rebuild, and the Fiskal Score maps those areas across People, Systems, and Finance if you want a structured view alongside it. For a regular rhythm of checks, Cin7 inventory audit procedures give a structure to follow.
When is it time to bring in a specialist?
Bring one in when the settings are right on paper and the data still disagrees: expiry dates entered but ignored at pick, COGS landing on the wrong batch, or a closed month that keeps changing. Those are signs your physical process and system process are no longer in sync.
Fiskal's Cin7 onboarding support covers system audits, SOPs by role, and retraining where usage has slipped, and a new build is scoped under Cin7 implementation. Shelf life should be visible in the warehouse and in the ledger. When it is, the system runs the way it was designed to, and your team stops working around it.
Frequently asked questions
How do you track expiry dates in Cin7 Core?
Set the product to the FEFO (Batch) costing method, then enter batch numbers and expiry dates at Stock Received on the purchase order. Cin7 Core then picks the earliest expiry first, and the Lot Expiry Report shows what is due to expire.
Is an expiry date mandatory in Cin7 Core?
Yes, for products on the FEFO costing method, an expiry date is mandatory. Products on other batch methods track batch numbers without requiring a date.
Can Cin7 Core stop staff picking the wrong batch?
It can warn and direct them. The recommend and enforce setting sends pickers to the bins with the first expired stock and shows a warning if they pick otherwise, but a picker can ignore the warning, so you need a review of overrides as well.
How do you see which stock is about to expire in Cin7 Core?
Run the Lot Expiry Report, which lists batches with their expiry dates and quantity on hand. Use the Inventory Movement Details Report alongside it when you need the cost of the expiring stock.
Can you change an existing product to batch or serial tracking?
Batch and expiry details apply only to stock with no previous batch or serial record. Moving a non-serialised product to a serialised method generally means creating a new SKU, so plan the costing method before the product is built.


