Why Your Inventory System Can't Track Expiry

Your inventory system knows you have 340 units of organic granola. It has no idea that 80 of them expire in six weeks.

This is the gap. It exists in Shopify. It exists in WooCommerce. It exists in QuickBooks. It exists in every major inventory management platform built for small and mid-size retailers, because every one of them was designed to answer a specific set of questions — how much stock do I have, what did I pay for it, when should I reorder — and none of those questions involve the dimension of time as it applies to product shelf life.

The platforms are not broken. They are doing exactly what they were built to do: manage quantity, cost, and replenishment. The problem is that if you sell anything with an expiry date — food, supplements, cosmetics, pet food, OTC medications, beverages, baby formula — quantity management is only half the job. The other half is knowing which units expire when, ensuring the shortest-dated stock moves first, and taking action before expiry converts inventory into waste. Your inventory system handles the first half. The second half is a gap, and the gap is expensive.

The architectural reason every major platform misses this

This is not a feature request that Shopify or WooCommerce has been ignoring. It is an architectural limitation rooted in how these platforms model inventory.

In Shopify's data model, a product has variants, and each variant has an inventory quantity at each location. When you sell a unit, the quantity decrements by one. When you receive stock, it increments. The system tracks the total pool of units. It does not track individual batches within that pool. There is no native field for lot number, no field for expiry date, no mechanism to distinguish between 80 units that expire on March 15th and 260 units that expire on August 30th. To Shopify, they are all the same 340 units.

WooCommerce follows the same pattern. The product object has a stock_quantity field. It goes up when you add stock. It goes down when you sell. There is no batch dimension. You can add custom fields manually or through plugins, but the core inventory engine — the part that handles stock deduction during checkout — does not consider expiry. You can store the data in a custom field, but the system will not act on it.

QuickBooks, in both its Online and Desktop variants, tracks inventory by item with quantity on hand, average cost, and reorder point. Enterprise editions add serial number and lot tracking, but even there, the lot tracking is primarily a traceability mechanism — it records which lot was sold to which customer — rather than an operational system that prioritizes lots by expiry date or generates alerts when lots approach their shelf life limit.

Square, Lightspeed, Cin7, Vend — the pattern repeats across the mid-market inventory landscape. Quantity is a first-class citizen in every one of these platforms. Expiry is either absent entirely or available as metadata that the system records but does not operationalise.

The reason for this architectural choice is straightforward. The majority of retail SKUs do not expire. Electronics, apparel, housewares, hardware, books — they have no shelf life constraint. The platforms were built for the general case, and the general case does not require batch-level expiry tracking. Perishable goods retailers are a segment of the user base, not the design center. The platforms serve the segment with workarounds, plugins, or custom integrations rather than core capabilities. This is a reasonable product decision for the platform. It is an expensive reality for the retailer.

What the gap actually costs (with the numbers most people do not calculate)

The direct cost of expired inventory is the number everyone knows. Industry data from the Food Marketing Institute puts grocery shrinkage from perishables at 4.7% of sales for the average US supermarket. For a store doing $3 million in annual revenue with 40% of that in perishable categories, that is $56,400 in annual waste. For a smaller specialty retailer doing $800,000 with 60% perishable, it is roughly $22,500. These are real numbers that hit the P&L directly.

But the direct cost understates the actual damage because it ignores three compounding factors.

The first is the labor cost of managing expiry manually. Without system support, someone in the store walks the shelves checking dates. For a 2,000-square-foot grocery or supplement store, a thorough shelf check takes 3-4 hours. If done weekly, that is 150-200 hours per year of staff time dedicated to a task that a system should automate. At $16-18/hour, you are spending $2,400-3,600 annually on manual date checking that still misses items, because no human scanning thousands of products catches everything.

The second is the opportunity cost of markdowns that happen too late. A product with 14 days remaining has markdown options — discount it 30%, feature it in a clearance bin, push it through a foodservice channel. A product discovered with 2 days remaining has no viable path except the dumpster. The difference between a 30% markdown recovery and a 100% write-off is the difference between losing $0.30 on the dollar and losing $1.00. Across hundreds of SKUs and thousands of units annually, the gap between timely markdowns and late discovery accounts for 40-60% of total waste at retailers without batch-level tracking. The product was not unsalable. It was unidentified in time.

The third compounding factor is regulatory exposure, and this one is increasing. The FDA's FSMA 204 Food Traceability Rule, which became mandatory on January 20, 2026, requires lot-level tracking for specific food categories through the supply chain. If you sell fresh produce, cheeses, shell eggs, nut butters, fresh-cut fruits, or seafood, you are now required to maintain lot-level records at the receiving point and produce them within 24 hours of an FDA request. An inventory system that does not track lots cannot generate these records. The compliance gap compounds the financial gap.

The specific failure modes (what goes wrong and when)

No FEFO enforcement at the pick or ship point. FEFO — First Expiry, First Out — is the principle that the unit closest to expiry should sell first. Every food safety textbook teaches it. No standard e-commerce or retail inventory platform enforces it. When an order comes in through Shopify and the warehouse picker fills it, they grab the most accessible unit, which is usually the newest because that is what sits on top of the most recent received pallet. The unit expiring in three weeks stays in the back. This pattern repeats across every pick until the short-dated units are discovered during a shelf check or, more commonly, after they have already expired. The system deducted inventory correctly — 340 became 339 — but the wrong physical unit left the building.

No receiving workflow that captures batch and expiry. When a shipment arrives at your warehouse or back room, someone counts the cases, verifies the PO, and updates the quantity in the system. The lot codes and expiry dates printed on the cases are not captured because the system has no field for them. Even if a staff member wanted to record this information, the standard receiving workflow in Shopify, WooCommerce, or QuickBooks does not accommodate it. The data exists physically — it is printed on every case and often included on the invoice or bill of lading — but it never enters the digital system. From the moment the boxes hit the shelf, the system is blind to expiry.

No alerts before the point of no return. Perishable inventory management is about windows of action. At 90 days before expiry, you can return to the supplier (if your vendor agreement permits). At 60 days, you can run a promotion or discount. At 30 days, you can markdown aggressively or divert to a secondary channel. At 7 days, your options have narrowed to donation or disposal. Without a system that knows batch-level expiry dates, there is no mechanism to trigger action at the 90-day or 60-day window. You discover the problem at the 7-day window, or the 0-day window, when the options are gone.

No visibility into the real cost of supplier decisions. When you have two suppliers for the same product — one delivering product with 8 months of remaining shelf life and another consistently delivering 4-month product at a 5% lower cost — which supplier is actually cheaper? Without batch-level expiry data, you cannot answer this question. The 5% cheaper supplier might be costing you 15% in accelerated waste, but the waste shows up as a general shrinkage number, not attributed to the specific supplier whose shorter-dated product caused it. Supplier evaluation without shelf-life data is incomplete, and incomplete evaluations perpetuate the problem.

Why plugins and add-ons only solve part of the problem

The Shopify App Store has expiry tracking plugins. WooCommerce has batch management extensions. QuickBooks has third-party lot tracking integrations. These tools address the data capture gap — they give you a place to record batch numbers and expiry dates. This is necessary but insufficient.

The limitation of most plugins is that they add data fields without adding intelligence. You can record that Lot 4472 of organic granola expires on April 15th, 2026. The plugin will store this information. Some will display it in a report. A few will send a basic alert when the date approaches. But they do not analyze your sales velocity to predict whether Lot 4472 will sell through before expiry. They do not calculate the optimal markdown date based on remaining shelf life and historical demand curves. They do not correlate your receiving patterns with your waste patterns to identify which suppliers consistently deliver shorter-dated product. They do not generate FEFO pick lists for your warehouse team.

Data capture is the starting line, not the finish line. The finish line is operational intelligence — the system not only knowing what you have and when it expires, but telling you what to do about it, when to do it, and quantifying the cost of inaction.

What an AI-powered add-on layer looks like in practice

The architecture that solves this problem has three components, and understanding the architecture matters because it explains why a standalone plugin is not enough while a full platform replacement is not necessary.

The first component is data integration. The add-on reads inventory data from your existing platform — Shopify, WooCommerce, QuickBooks, or whatever you run — through API connections. It ingests purchase orders, receiving records, sales transactions, and current stock levels. It also provides a structured way to capture the data your platform does not: lot numbers and expiry dates at the receiving point, either through manual entry with validation or through OCR-based invoice scanning that reads lot codes and dates from supplier documentation.

The second component is the intelligence engine. This is where AI transforms data into decisions. Sales velocity analysis at the lot level determines whether each batch is on track to sell through before expiry. Demand forecasting adjusts for seasonality, promotions, and day-of-week patterns. Supplier shelf-life benchmarking compares the average remaining shelf life at delivery across your vendor base. Markdown optimization calculates the revenue-maximising discount point — deep enough to move the product, shallow enough to preserve margin, timed early enough that the product is still salable.

The third component is the action layer. Alerts delivered through channels your team actually uses — email, SMS, Slack, or push notifications — at thresholds that matter: entering the return window, optimal markdown date, last viable sale date. FEFO-prioritized pick lists that tell warehouse staff which lot to pull for each order. Dashboard views that show total inventory value at risk by time horizon (expiring in 30/60/90 days), enabling financial planning for markdowns and write-offs before they hit as surprises.

ShelfSense AI implements this three-layer architecture. It connects to your existing inventory platform, adds the batch-level data capture your platform lacks, and layers intelligence on top that converts expiry data into daily operational decisions. Your team does not learn a new inventory system. They keep using Shopify or WooCommerce or QuickBooks for what it does well. ShelfSense AI handles the expiry dimension that those platforms were not built to address.

The FDA compliance angle that makes this urgent in 2026

FSMA Section 204 is not theoretical. The compliance date was January 20, 2026. If you sell any foods on the FDA's Food Traceability List — and that list includes leafy greens, fresh herbs, tomatoes, peppers, cucumbers, melons, fresh-cut produce, shell eggs, certain cheeses, nut butters, tropical fruits, and most seafood — you are required to maintain lot-level traceability records and produce them in a sortable electronic format within 24 hours of an FDA request.

Your standard Shopify or WooCommerce installation cannot generate these records because it does not capture lot-level data. This is not a matter of configuration. The core data model does not support it. A plugin that captures lot numbers at receiving and links them to your inventory movements is no longer a nice-to-have operational improvement. It is a regulatory requirement with enforcement consequences including warning letters, civil penalties, and import refusal.

The overlap between expiry tracking and FSMA 204 compliance is substantial. Both require lot-level data capture at receiving. Both require linking lots to specific transactions. Both require the ability to query and report on lot-level data quickly. A system that solves the expiry tracking gap simultaneously addresses the FSMA 204 compliance gap. This is not a coincidence — both problems stem from the same architectural absence of lot-level tracking in standard retail platforms.

ShelfSense AI addresses both dimensions through a single integration. Lot-level data captured for expiry management purposes also serves as your FSMA 204 traceability record. The same data feeds both operational intelligence (what to do with expiring stock) and compliance reporting (proving lot-level chain of custody to the FDA). One data capture workflow, two critical outcomes.

The ROI calculation most retailers get wrong

When retailers evaluate expiry tracking tools, they typically calculate ROI based on waste reduction alone. Current waste times expected reduction percentage. This understates the return because it ignores three additional value streams.

Recovered returns are the first. Many supplier agreements include return provisions for slow-moving or near-expiry stock. Without batch-level tracking and return window alerts, these provisions go unused. Retailers with batch-level visibility typically recover 15-25% of what would have been total waste through timely supplier returns. For a retailer currently writing off $40,000 annually in expired inventory, recovered returns of $6,000-10,000 represent value that did not exist before.

Improved margins through earlier markdowns are the second. A product marked down at 25% off with 21 days remaining will sell. The same product marked down at 50% with 3 days remaining might not. The difference in recovery rate between early and late markdowns ranges from 40-65% of product value. Across all near-expiry markdowns over a year, earlier identification shifts the average recovery rate meaningfully upward.

Supplier negotiation leverage is the third. When you have data showing that Supplier A delivers product with an average of 7.2 months remaining shelf life while Supplier B averages 4.1 months, you have a concrete basis for negotiating price adjustments or switching suppliers for specific SKUs. This data does not exist without batch-level tracking. With it, procurement decisions improve in ways that compound over time.

The total ROI typically runs 3-5x the cost of an add-on solution in the first year, accelerating as historical data improves forecasting accuracy and the team develops more refined operational responses to expiry risk.

Measuring the gap in your own operation

Your inventory system is not failing at what it was designed to do. It is failing at something it was never designed to do. Quantity management and expiry management are different problems requiring different capabilities. The first is solved by Shopify, WooCommerce, QuickBooks, and their peers. The second requires a purpose-built layer that adds batch-level visibility, intelligent alerting, and operational decision support on top of your existing platform.

The cost of leaving the gap open is measurable: it shows up in your shrinkage numbers, your write-off reports, your missed supplier return windows, and now, potentially, in your FSMA 204 compliance record. The cost of closing the gap is a fraction of the waste it prevents.

Pull your last 12 months of inventory write-offs for perishable categories. Add back any markdowns that happened after the optimal window (products that sold at 50-70% off because they were discovered late). Add the labor hours your team spends on manual shelf checks. That total is the cost of not having batch-level expiry tracking. Compare it to the cost of adding it.

The arithmetic tends to be persuasive.

[ShelfSense AI](/shelfsense/) adds batch-level expiry tracking, FEFO enforcement, and intelligent alerts to the inventory platform you already use. [Start a free trial](/shelfsense/get-started/) and connect it to your Shopify, WooCommerce, or QuickBooks data in under 10 minutes.

ShelfLifePro is purpose-built to close the expiry tracking gap — batch-level FEFO, tiered alerts, and markdown automation on top of your existing inventory system. Start free at shelflifepro.net