Serial number and expiry date tracking in a WMS is the practice of recording a unique identifier or a shelf-life date against individual units of stock, not just against the SKU as a whole, so a warehouse always knows exactly which unit is where and how much time it has left. In Shipider, that identity gets attached the moment a unit is scanned into receiving, follows it through putaway to a warehouse location, and stays visible all the way through picking and dispatch on a real audit trail.
Most inventory systems are built around the SKU. That works fine until two units of the same SKU are not actually interchangeable: one has a serial number tied to a warranty, or one expires next week while the other has six months left. Once that distinction matters to your business, SKU-level counts stop being enough and you need tracking at the unit level.
Why unit-level tracking matters more than most teams expect
A warehouse that only tracks quantity per SKU can tell you "we have 40 units of Product X." It cannot tell you which of those 40 units is closest to its expiry date, or which serial number went to which customer last month. That gap shows up in three places: compliance audits, warranty disputes, and expiry write-offs.
Serial numbers matter most for electronics, equipment, medical devices, and anything with a warranty or a recall risk. Expiry dates matter most for food, beverage, cosmetics, supplements, and pharma-adjacent goods where selling expired stock is a legal problem, not just a customer service one. Some categories, like cold chain products, need both: a serial or batch identifier and a hard expiry date on the same unit.
Without unit-level tracking, a recall or a warranty claim turns into a manual search through paper logs or scattered spreadsheet tabs. With it, you filter by serial number or expiry window and get an answer in minutes, including which pallet the unit sat on and who handled it.
Serial number tracking versus lot, batch, and expiry tracking
These terms get used loosely, and that causes confusion when teams are comparing WMS options. The table below separates them by what they actually track and where each one is used.
| Tracking type | What it identifies | Typical use case | Key question it answers |
|---|---|---|---|
| Serial number | One specific, individual unit | Electronics, equipment, tools, warranty items | "Where is this exact unit right now?" |
| Lot or batch | A group of units made together | Manufactured goods, supplements, apparel runs | "Which units share this production batch?" |
| Expiry date | A shelf-life limit on a unit or batch | Food, beverage, cosmetics, pharma-adjacent goods | "How much usable time does this stock have left?" |
| Serial plus expiry | Individual unit with its own shelf life | Cold chain, medical supply, some equipment | "Which specific unit expires first, and where is it?" |
A single warehouse can legitimately need all four, sometimes on different SKUs within the same building. That is one reason unit-level tracking has to be flexible rather than hardcoded to one model.
How this works day to day in Shipider
Capturing identity at receiving
Serial numbers and expiry dates get captured the moment stock hits the dock, using in-browser camera barcode scanning on any phone, no dedicated scanner gun required. If a supplier label already carries a serial number or a printed expiry date, the receiver scans it directly. If not, the identifier gets entered once and attached to the unit's record going forward.
Putaway ties identity to a physical location
Once a serialized or dated unit is received, putaway assigns it to a specific warehouse location, and that pairing (serial or expiry plus location) is what makes traceability useful instead of theoretical. A report that says "unit SN-4471 expires in nine days" is far more actionable when it also says "and it's sitting in Rack B, Shelf 3."
Maker-checker verification catches mismatches before they ship
Because Shipider runs order processing through a two-step maker-checker workflow, a picker scanning the wrong serial number or an expired unit gets flagged before the checker confirms the pick, not after the customer complains. That second scan is the same mechanism that prevents mis-ships generally, and it works the same way for serialized and dated stock. For a deeper look at how that verification step functions across the floor, see what a maker-checker workflow actually is.
FEFO picking logic for expiry-driven stock
For expiry-tracked goods, picking logic can prioritize first-expired-first-out (FEFO) rather than simple first-in-first-out, so the unit closest to its expiry date gets picked and shipped first. That reduces write-offs and keeps aging stock from sitting untouched in a corner location.
The audit trail ties it all together
Every scan, every location change, every pick against a serialized or expiry-dated unit gets logged on a real audit trail. That means when a customer disputes a warranty claim, or an auditor asks for proof of FEFO compliance, the answer already exists as a timestamped record rather than something someone has to reconstruct from memory. This is the same audit trail infrastructure covered in the warehouse audit trail software guide, which is worth reading if you want the fuller picture of how audit logging works across receiving, putaway, and dispatch.
What breaks without it
Warehouses that skip unit-level tracking usually feel the cost in a few predictable ways: expired stock discovered during a cycle count instead of before it went bad, warranty claims that take hours to trace because the serial number was written on a sticky note instead of scanned, and recall responses that require physically opening boxes because there is no record of which units went where. None of these are hypothetical. They are the normal failure mode of SKU-only inventory once a business grows past a handful of product lines.
Root cause investigations get harder too. If you are already chasing down SKU discrepancies without unit-level identifiers, adding serial and expiry data gives you one more filter to narrow down exactly where and when a mismatch happened, rather than guessing across an entire SKU's history.
Where this fits for 3PLs and multi-site operations
For a 3PL running several customers under one roof, serial and expiry tracking has to respect tenant boundaries. One client's electronics warranty program should never surface in another client's dashboard, and expiry alerts for a food brand shouldn't mix with a different customer's industrial parts inventory. Shipider's structural multi-tenant isolation keeps that separation intact by design, so unit-level tracking scales across customers without manual workarounds. If you're evaluating a WMS specifically for 3PL operations, the 3PL solutions page covers how isolation, onboarding, and billing fit together.
For a single-brand warehouse or an e-commerce operation running multiple fulfillment sites, the same logic applies across locations: a serial number or expiry date attached to a unit in Site A is visible and searchable from Site B, because inventory is tracked across sites rather than in isolated silos.
Getting started without a big rollout
Adding serial number and expiry tracking to an existing warehouse setup does not require new hardware or a long implementation. Because scanning runs in the browser on any phone, and because Shipider's pricing is token-based rather than tied to per-seat licenses or long contracts, teams can turn on unit-level tracking for the SKUs that need it (electronics, perishables, regulated goods) without re-architecting the whole operation. Most of the setup is just deciding which SKUs need serial capture, which need expiry dates, and which need both, then scanning them in as they arrive. This approach is part of the broader inventory accuracy and traceability practices that keep a warehouse audit-ready without extra headcount.
Frequently asked questions
What is the difference between serial number tracking and lot tracking?
Serial number tracking identifies one specific individual unit, useful for warranties and equipment. Lot or batch tracking identifies a group of units produced together, useful for manufactured goods where units within a batch are interchangeable but the batch itself needs to be traceable.
Can a single unit have both a serial number and an expiry date?
Yes. Cold chain products, some medical supplies, and certain equipment need both: a unique serial number for warranty or compliance purposes, plus a hard expiry date that governs when the unit can no longer be sold or used. Shipider supports capturing both against the same unit record.
Does expiry tracking require special hardware or scanners?
No. Shipider captures expiry dates and serial numbers through in-browser camera barcode scanning on any phone, so there is no dedicated scanner gun or extra hardware to buy or maintain.
What is FEFO and why does it matter for expiry tracking?
FEFO stands for first-expired-first-out, a picking method that ships the unit closest to its expiry date before units with more shelf life remaining. It matters because it reduces write-offs from expired stock and keeps aging inventory from sitting untouched in a location no one checks.
How does maker-checker verification help with serialized inventory?
Maker-checker requires a second scan to confirm a pick before an order ships. For serialized inventory, that second scan catches a picker grabbing the wrong serial number or an expired unit before it reaches the customer, rather than after a complaint or a return.
Ready to see serial number and expiry tracking running on your own floor? Create a Shipider account and set it up on the SKUs that need it first.