Let's start with the math. A 3PL warehouse signs a food client. Their WMS has no lot tracking or expiration date management worth the name. Six months in, a customer complains about a short-dated shipment and demands full traceability records for that lot within 48 hours. Three people spend four days digging through paper receiving slips and spreadsheets. They can't produce it. The entire lot — over 20,000 units — gets returned and destroyed. Product value, labor, and the client's penalty wipe out roughly $30,000 of margin on the account. All of it avoidable: one extra question during selection — "what's your lot traceability granularity?" — plus two hours of live demo verification. Money spent for nothing.
Food and pharma clients pay better than general e-commerce, but one lot incident can eat a year's profit. Lot and expiry capability in your WMS is the insurance policy for this business. Here are the eight questions. Make the vendor demo each one live during selection. Anything they can't demo counts as a "no."
1. What Is the Lot Traceability Granularity?
Pallet level, case level, or each level? Plenty of WMS vendors claim "lot tracking support," then the demo reveals pallet-level only — three lots mixed on one pallet, and traceability is useless. Food distribution usually needs case level. Pharma often needs each level, especially for serialized products.
Cost of not asking: during a recall you can't pull a precise list, so you destroy the whole lot. The difference between destroying 200 cases and 20,000 units can be tens of times the product value.
2. Is FEFO System-Enforced or Honor System?
First-expired-first-out sounds simple until human nature gets involved. Can the system automatically suggest the earliest-expiry lot at pick time and hard-block the wrong lot? Or does it merely "suggest" while pickers grab whatever's convenient?
In 2023, a California food distributor had FEFO as a suggestion, not an enforcement. During peak season, pickers grabbed the easiest pallets, short-dated stock kept getting buried, and four pallets ended up 15 days from expiry. The client rejected the whole shipment. The data was in the system. Nobody looked at it — which is the same as not having it. Cost of not asking: the written-off product value, plus your client's trust in your quality control dropping to zero.
3. How Far Ahead Do Expiry Alerts Go? Per-Client Thresholds?
Every client defines "short-dated" differently: 90 days for one, 180 for another. Can the system set alert thresholds per client and per product category? Do alerts just turn a field red on screen, or do they push email and mobile notifications?
Cost of not asking: short-dated product gets rejected at the client's dock — you pay the return freight and sit on unsellable stock. Knowing 60 days ahead versus 3 days ahead is a completely different cost equation.
4. Can You Pull a Full Inbound/Outbound History for a Lot in One Click?
This is the life-or-death line for food and pharma. When a recall hits, how fast can you answer: when did this lot arrive, how much, who got it, what's left and where? Ten minutes, or four days of digging?
Cost of not asking: every day of slow response is another day the affected product sits in the market. Worse, if you can't produce complete records, you won't even make the shortlist at the next bid.
5. Can Audit Reports Export Directly?
Food and pharma clients audit regularly, and the auditor's first request is usually: "Export the last six months of lot movements for this SKU." Can the system do it in one click? Is the output format something auditors accept? Or does the ops manager pull an all-nighter building spreadsheets before every audit?
Cost of not asking: two to three people spending a week preparing for every audit — the labor is the small part. When the auditor sees handmade Excel, your quality-system score takes a hit before they read a word.
6. Are Lot Numbers Isolated Between Clients?
In a 3PL, Client A and Client B may buy from the same supplier with identical lot numbering. Are lot numbers globally unique in the system, or isolated per client? Can Client A's lot get picked for Client B's order?
Cost of not asking: shipping the wrong client's lot means return freight at best, a quality-claim dispute at worst. Demo this with two live client accounts — don't take the salesperson's word for it.
7. Does Label Printing Support Lot + Expiry Barcodes?
At receiving, can the pallet label automatically encode lot number, production date, and expiry into the barcode? Or is it hand-labeled and hand-written? Can the downstream client's scanners even read the format?
Cost of not asking: one hand-written digit wrong and every downstream trace is built on bad data. Get the data wrong at the source and the most expensive system in the world won't save you.
8. Does Lot Data Reconcile Automatically with the ERP?
Month-end is where this hurts. Finance reconciles inventory with the ERP and the totals match but the lots don't. Can the WMS reconcile receipts, issues, and balances against the ERP at lot level? Can variances be traced to specific lots?
Cost of not asking: two to three days of manual reconciliation every month, with variances nobody can explain. That's how finance's trust in you erodes, one month at a time.
The Full Ledger: With vs. Without
| Cost item | Full lot/expiry capability | Missing or partial |
|---|---|---|
| Lot incident loss | Precise recall, contained to affected lots | Whole-lot destruction, multiples of product value |
| Expired write-offs | Early alerts, divert to promo or vendor return | Discovered near expiry, write off |
| Audit prep | One-click export, half a day | 2-3 people, one week, every year |
| Month-end reconciliation | Automatic, variances traced to lots | 2-3 days manual, variances unexplained |
| Client trust | Audit plus, leverage at renewal | One incident can lose the account |
Every row in the "without" column is something I've watched happen. You do the math on whether that money was well spent.
One counterintuitive judgment to close: the WMS with the most complete lot functionality isn't necessarily the most expensive — the most expensive is the one where you didn't ask during selection and discovered the gap after go-live. Two extra hours of live demos on these eight questions cost almost nothing. Bolting on missing functionality later — or replacing the system — costs dozens of times more, plus the risk of losing clients. Print the eight questions, walk through them one by one at selection, and treat any "yes, we support that" without a live demo as a no.
By Lao Zhou, Logistics Cost Analyst
