Food Traceability Software: Track Lot, Expiry, and Recall Readiness

You make, blend, pack, or distribute food. Your books live in QuickBooks Online or Xero, and your orders come through Shopify, WooCommerce, or a wholesale channel a spreadsheet still holds together. For a long time that stack did the job. Then a retailer’s onboarding form asked for lot and expiry data on every line. Or a customer called about a specific batch and you spent an afternoon reconstructing where it went. Or a recall notice from another brand in your category made you ask the one question that actually matters: if that were our product, which units would we pull, from which customers, and how fast?

That is the wall. Your accounting platform is good at accounting; your storefront is good at selling. Neither was built to follow a batch of raw ingredient from a supplier receipt, through a production run, to the customer who bought the finished case. For perishable, lot-tracked food, that trail is the whole game, and closing that gap is what food traceability software does.

What is food traceability software?

It turns the link between “what a supplier sent us” and “what a customer received” into a queryable record instead of something that lives in people’s heads, email threads, and paper packing slips. It assigns and tracks lot and batch numbers, records expiry dates and locations at every movement, and can reproduce the full path of any lot on demand, both directions. It’s the food-and-beverage expression of lot control software, tuned for perishables, shelf life, and the recall pressures specific to what people eat and drink.

What it actually tracks: lots, batches, expiry dates, and movement records

A lot number (or batch number) identifies a group of units that share an origin or production run: a thousand jars from Tuesday’s run, or a pallet of raw material from one supplier delivery. The two words describe the same thing at different points in the chain: “lot” is more common in food distribution and regulation (FSMA uses “lot code”); “batch” is more common in manufacturing, where a batch is a production run. Under both, the software records, for each group: the supplier and inbound receipt it came from, the quantity received and remaining, its expiry or best-before date, the locations it sits in, the production run it fed into (if you manufacture), and every outbound shipment it left on.

Those records are what make forward trace, backward trace, FEFO picking, and recall isolation possible. A system that stores a lot number in a text field but can’t tie it to movements isn’t traceability. It’s a label.

What is the difference between food traceability software and food safety management software?

These two categories get lumped together, but they solve different problems. Food safety management software, HACCP plan builders, digital food-safety forms, supplier audit questionnaires, helps you design and document a safety program. Food traceability software tracks the physical movement of inventory so you can trace a lot end to end. A full food-safety operation usually needs both, but they are not the same purchase. Qoblex is a traceability tool, not a HACCP platform. More on that boundary below.

What inventory software has FEFO and lot tracking for food brands?

For food, beverage, and supplement brands, the distinguishing capability is FEFO enforcement at the lot level: the software has to surface the nearest-expiry lot at pick time, not just store an expiry date in a field. Platforms that win this query fall into two groups.

Full inventory operations platforms with native FEFO and lot genealogy handle purchasing, multichannel orders, BOM-based production, and lot traceability in a single system. Qoblex is in this group. It enforces FEFO across warehouse locations, carries lot genealogy through bills of materials so a raw-ingredient recall traces forward to every finished batch it fed, and syncs with QuickBooks Online, Xero, Shopify, and WooCommerce rather than replacing them. The lot and expiry tracking module is a paid add-on, not part of the base plan; see the FAQ below for what’s included. Other platforms in this tier include Cin7 Core, Unleashed, and inFlow Manufacturing, which each have lot tracking with varying depth of FEFO enforcement and BOM integration.

Food-and-beverage-focused ERP platforms include those purpose-built for food manufacturers, such as Wherefour and Aptean Food and Beverage ERP, which treat FEFO as a native default, and broader mid-market ERPs with dedicated F&B modules, such as DOSS, which offers FEFO enforcement and lot genealogy alongside modules for other industries. They go deeper on food-industry-specific workflows (catch weight, allergen management, GMP batch records) but are typically priced and scoped for larger or food-specialist operations and don’t offer the same accounting-platform integrations (QBO, Xero) as a middle-tier inventory operations tool.

The practical filter: if your operation runs on QuickBooks Online or Xero, needs multichannel order management, and also needs lot and expiry traceability, a platform with native accounting integration is the more direct path than a food-specific ERP that requires re-implementing your books.

Do I need food-specific software, or an inventory platform with lot tracking?

The right answer depends on where your operation sits.

A food-specific platform makes sense if food is your entire business and you need deep food-industry features: catch weight management, allergen tracking, GMP-aligned batch records for nutraceuticals, or regulatory reporting for a food manufacturer at scale. Tools like Wherefour are built for that world and treat FEFO as a default, not a feature.

An inventory operations platform with lot and expiry tracking makes sense if you make or distribute food but also need to manage purchasing, multichannel sales across Shopify and wholesale, and keep your existing accounting software intact. Here the question is whether lot genealogy (ingredient to finished batch through the BOM) and FEFO enforcement exist in the platform, not whether the platform was purpose-built for food. Qoblex, Cin7, and similar platforms answer that question.

When neither is yet the right investment. If your operation is small, non-perishable, single-SKU, with no lot or expiry requirement from a customer or regulator and no recall exposure, a well-kept spreadsheet may genuinely cover you for now. See the “when is a spreadsheet sufficient” section below.

The supplement and nutraceutical case has an additional layer: GMP-aligned batch records, Certificate of Analysis links, and serial-number tracking for certain high-value SKUs. If that is your situation, the supplement and nutraceutical inventory software guide covers it in detail.

How does inventory software help with FSMA 204?

The most common regulatory reason a US food operator lands here is the FDA’s Food Safety Modernization Act (FSMA) Section 204, the Food Traceability Rule.

What the rule requires: KDEs, CTEs, and the Food Traceability List

FSMA Section 204 requires businesses that make, process, pack, or hold foods on the FDA’s Food Traceability List (FTL) to keep records of specific Key Data Elements (KDEs) at defined Critical Tracking Events (CTEs): the points where food is grown, received, transformed, or shipped. In plain terms: at each key handoff, you record a standardized set of data (including the lot code) so the food can be traced quickly during a safety event.

The Food Traceability List covers items such as fresh produce, soft and semi-soft cheeses, shell eggs, nut butters, seafood, and ready-to-eat deli salads. If your specific food is not on the FTL, FSMA 204’s additional recordkeeping requirements do not apply to you. The FDA’s page is the authoritative source for whether a specific food is covered.

Compliance date: July 20, 2028

The rule’s compliance date is July 20, 2028, extended from January 20, 2026. The FDA proposed a 30-month extension in August 2025, and that extension was recorded in the Federal Register (doc. 2025-14967). The practical read for an operator: this is a preparation window, not a fire drill, and time to put the recordkeeping in place before it’s required.

What traceability records you need, and how software produces them

When a covered event happens, you receive an FTL food, transform it, or ship it, the rule expects the relevant KDEs to be captured and available to the FDA within 24 hours of a request. Traceability software produces those records because the KDEs (lot code, quantity, location, dates, linked supplier and shipment) are captured as a byproduct of normal receiving, production, and shipping, so the record is a report you run, not a project you staff.

For a full walkthrough of KDEs, CTEs, and how a lot-tracking system generates the records FSMA 204 expects, see the FSMA 204 traceability guide.

Who needs food traceability software, and who does not yet

What types of F&B businesses need lot tracking software?

If you make or distribute food, beverages, or ingredients, lot-level traceability is usually not optional. It shows up three ways: as a regulatory obligation (see FSMA 204 above), as a condition of a food-safety certification, or as a flat requirement from the retailers and distributors you sell to. Grocery, foodservice, and pharmacy buyers increasingly won’t onboard a supplier who can’t provide lot and expiry records on every line. The operators who need this are food manufacturers running recipes and production batches, beverage brands, co-packers, and perishables distributors: anyone whose product carries a shelf life or whose customers expect to trace a batch.

When is a spreadsheet, your platform’s fields, or a HACCP tool sufficient?

Not every food business needs this yet, and it would be dishonest to pretend otherwise. If your operation is small, sells a single non-perishable SKU, has no lot-number or expiry requirement from a customer or regulator, and has never had a reason to recall product, a well-kept spreadsheet may genuinely cover you for now. Spreadsheets got a lot of good food businesses off the ground, and there’s no prize for buying software before you need it. And if your real gap is a documented food-safety program, HACCP plans, audit prep, inspection forms, that’s a food-safety management tool’s job, not this one’s.

Food traceability inventory software starts paying for itself at specific moments:

• A customer or auditor asks you to trace a lot back to a supplier batch, and you can’t answer from a report.
• You carry stock with expiry or best-before dates and you’re picking by guesswork instead of by expiry.
• You’ve added a second location, a co-packer, or enough SKUs that “someone remembers” stops working.
• A retailer or distributor makes lot and expiry data a condition of doing business.

If none of those describe you, keep the spreadsheet. If one or more do, the manual workaround has quietly become the risk.

When is a food-service or restaurant tool the right answer instead?

A separate category sometimes surfaces in this search: restaurant and food-service inventory tools like Toast POS Inventory, MarketMan, or Craftable. These are kitchen and food-service management platforms designed to manage ingredients, recipe costing, and waste for restaurants, cafes, and hospitality operations, not for wholesale or manufacturing lot traceability. If you are running a restaurant or multi-location food-service operation and need kitchen inventory control, prep-list management, and COGS visibility at the dish level, those tools are built for you. If you are a food manufacturer, beverage brand, or distributor who ships lot-tracked product to retailers and needs an audit trail from supplier to customer, those kitchen tools are not the right fit, and this page is.

What capabilities must food traceability software have?

These five separate real traceability from an inventory tool with a lot-number field.

1. Lot and batch number assignment at receiving and production. The software has to capture the lot or batch number and expiry date at the moment stock arrives from a supplier, and assign a batch number to each production run, so every unit is tied to its origin from the start.

2. Expiry date tracking and FEFO picking enforcement. FEFO, First Expired, First Out, means the stock with the nearest expiry date gets picked first, regardless of when it arrived. It differs from FIFO, which picks by arrival order; for perishable goods, expiry order is the one that matters. The software has to surface expiry at the moment of picking, not just store it.

3. Supplier-to-customer forward and backward trace. Backward: from a finished case or shipment, trace to the supplier lot it came from. Forward: from a supplier lot, trace to every customer who received it. You need both, because a recall can start at either end: a supplier flags a bad ingredient (trace forward to your customers), or a customer reports a problem (trace backward to the source). See supplier-to-shelf food traceability for the full chain.

4. Recall isolation: identify an affected lot in minutes. Given a lot number, the system should return every inbound and outbound movement of that lot and the quantity still on hand, fast enough that a mock recall is a routine exercise, not a lost day.

5. BOM-level traceability: from raw ingredient lot to finished product batch. If you manufacture, the system has to connect raw-material lots to the finished-goods batch they went into. Without that link, a recall on an ingredient can’t be traced forward to the products that contain it. This is where a lot of lightweight tools stop. They track finished goods but lose the thread at the bill of materials (BOM). See food and beverage lot and batch tracking for the detail on how BOM lot traceability works end to end.

The integration gap: why QBO, Xero, Shopify, and WooCommerce don’t cover food traceability

This is the situation most buyers on this page are in. Your existing platforms work fine for what they’re for. They just weren’t built for lot-level food operations.

Can QuickBooks Online track lot numbers for food products?

QuickBooks Online doesn’t track lot or batch numbers, doesn’t record expiry dates, and doesn’t enforce FEFO picking natively. That’s not a knock on QBO. It’s an accounting platform doing that job well. But the physical trail of which units came from which supplier lot, and which went to which customer, isn’t something it holds. That’s the layer you add on top while QBO stays your book of record. US operators can see the detail on lot and expiry tracking for QuickBooks Online.

Does Xero have food lot tracking, even with Inventory Plus?

Xero doesn’t natively track lot or batch numbers, record expiry dates, or enforce FEFO picking. Even the Xero Inventory Plus add-on, which as of mid-2026 is US-only and USD-only, doesn’t close the traceability gap: it adds no lot tracking, batch tracking, or expiry date tracking. So whether you’re on core Xero or the paid add-on, the food-traceability layer is still missing. AU/NZ/UK operators can see the detail on lot tracking for Xero users.

Can Shopify or WooCommerce track expiry dates and lot numbers?

Shopify’s inventory model treats every unit of a variant as identical. There is no native lot or batch identity and no expiry date field, and it doesn’t enforce FEFO. WooCommerce likewise has no native lot/batch tracking and no expiry date tracking. Your storefront knows how many units you have; it doesn’t know which lot they belong to or when they expire.

How to keep your existing platforms and add real traceability

You don’t have to rip out your accounting system and move to a full ERP. The gap is operational, not financial. The better middle path is to keep QuickBooks Online or Xero as your book of record, keep Shopify or WooCommerce as your storefront, and add a dedicated inventory operations layer between them: one that owns lots, batches, expiry dates, locations, purchasing, and manufacturing traceability, and syncs the financial results back. That’s the role Qoblex is built for: the operational system between a spreadsheet and a bloated ERP, integrated with your accounting and ecommerce tools rather than replacing them. Your accounting platform stays your single source of truth; Qoblex owns the lot, expiry, and recall layer on top: no re-implementing your books, no retraining your bookkeeper.

How food traceability works in practice with Qoblex

Here’s the workflow.

Receiving. When stock arrives against a purchase order, you capture the lot or batch number and expiry date at the point of receipt, so from that moment, every unit is tied to its origin.

FEFO picking across locations. As orders come in, Qoblex surfaces the nearest-expiry lots first, across all your warehouse locations, so pickers work by expiry rather than by memory, with lot quantities visible everywhere at once, not one site at a time.

BOM traceability. Because Qoblex ships lightweight MRP and bill-of-materials natively, a finished batch carries the lots of every ingredient in it, so a recall trace passes cleanly through production instead of stopping at the finished-goods shelf.

Running a recall drill. This is the moment the whole system earns its place. To trace an affected lot:

1. Enter the affected lot or batch number.
2. Trace backward to the supplier and inbound receipt it came from.
3. Trace forward to every customer shipment, and, if you manufacture, every finished batch it fed into via the BOM.
4. Read off the quantity still on hand and where it’s located, so you know exactly what to isolate.

A trace like that should take minutes. Running it as a mock recall, before you ever need it for real, is how you find out whether your records hold together.

Traceability reports. The same trace comes out as a report, for an auditor, a retailer’s onboarding, your quality review, or an FDA request, without stitching spreadsheets together the night before. For the full picture of what the supply chain looks like end to end, see food and beverage inventory management software.

Is Qoblex the right food traceability software for your operation?

Food traceability software is one layer of a food-safety system, not the whole thing, and being straight about that boundary is how you buy the right tool.

The operator Qoblex is built for. A food manufacturer, beverage brand, co-packer, or perishables distributor with lot-tracked or shelf-life-limited inventory, running QuickBooks Online or Xero for the books and Shopify or WooCommerce for orders, who needs real lot tracking, expiry management, FEFO picking, recall isolation, and ingredient-to-finished-product traceability, without moving to an enterprise ERP. That’s the middle Qoblex fills.

When a HACCP or food-safety audit platform is what you actually need instead. If your primary need is HACCP plan templates, supplier audit questionnaires, or digital food-safety forms for inspections, a dedicated food-safety management platform is designed for that and Qoblex is not. Many operations run both: a food-safety platform for the program, an inventory layer like Qoblex for the physical trace. We’d rather tell you that than pretend Qoblex is a HACCP tool.

When a food-service tool is the right fit. If you’re running a restaurant or food-service operation and your need is kitchen inventory, recipe costing, and waste management, platforms like Toast Inventory and MarketMan are built for those workflows. They are not lot-traceability tools for manufacturers and distributors, but for their actual job, they’re the right answer.

When your current setup is sufficient for now. If you’re small, non-perishable, single-SKU, with no lot or expiry requirement and no recall exposure, your spreadsheet may be enough for now. And on the other common question: Qoblex does not replace your accounting software. It integrates with QuickBooks Online and Xero and keeps them as your book of record, you add traceability, you don’t switch accounting. (Some food-adjacent regulated products, such as medical nutrition and certain supplements, are tracked by serial number rather than by lot; if that’s you, see serial number tracking software.)

How to evaluate food traceability software: a practical checklist

The five capabilities above are the must-haves. A few questions cut through a vendor demo quickly: Can you trace a lot both directions in one query? Does FEFO surface at pick time, or is expiry just stored in a field? Does the trace pass through the bill of materials to raw-ingredient lots? Can it produce the records FSMA 204 expects? Does it sync with your accounting platform and connect to your sales channels, so you don’t re-key data? And what’s included versus a paid add-on? (For Qoblex, see the FAQ below and qoblex.com/pricing.) Price is a supporting detail; the reason to look is the capability gap the table below shows.

FAQ