Code-Date Acceptance Windows: Why DCs Reject Loads
Why retailer DCs reject deliveries for short code dates, and a distributor method: record each customer's window, allocate by expiry, route short lots.
ShelfLifePro Editorial Team
Inventory management insights for retail and pharmacy
The rejection at the dock
Your truck backs into the retailer's distribution center. The receiver pulls a case, checks the code date, checks it against a number on their screen, and refuses the pallet. The driver calls you from the dock. The load comes back, the freight is wasted, and a few weeks later a deduction shows up on the remittance.
Nothing was wrong with the product. It was in date, stored right, and correctly picked against the order. It just didn't have enough life left for that customer. That gap between "in date" and "acceptable to this retailer" is the code-date acceptance window, and it's where a lot of distributor margin quietly leaks.
Why in-date stock still gets refused
A retailer's DC isn't the end of the line. Product still has to move from the DC to stores, sit on a shelf, and get sold before the date. So each retailer writes a minimum remaining shelf life into its supplier requirements, the vendor guide or routing guide you signed when you got the listing. If the stock arrives with less life than that, the DC is protecting its own stores by refusing it.
The windows aren't standard. Each retailer sets its own in its vendor guide, and they can differ by category, by item, and sometimes by whether the product is going to a DC or direct to store. There's no industry number you can plan around, so don't treat any figure you've heard as the rule. The only number that counts is the one in that customer's current guide.
How a window gets missed
The failure is rarely one big mistake. It's a chain of small ones that each look reasonable:
- The picker grabs the most accessible pallet, not the right lot for that order.
- The warehouse runs FIFO by receipt date, but an older shipment from the supplier arrived later with an earlier date.
- Someone knows "Retailer A is strict," but it lives in a supervisor's head, not on the pick ticket.
- The window was checked when the order was entered, but the order sat for a few days and the stock aged past the cutoff.
- The supplier sent you short-dated stock in the first place and nobody caught it at receiving.
That last one matters more than it looks. If you don't record the expiry when product comes in, you can't allocate against it later. The rules for doing that cleanly are in our post on capturing expiry dates at receiving.
Building the customer window table
Start with one simple record: every customer, every item or category where their rule differs, and the minimum remaining life they require at delivery. Pull it from the actual vendor guide, not memory, and note the guide's version or date so you know when to recheck it.
For example, a basic table might carry these columns:
- Customer and ship-to (a DC and a store-direct account can have different rules)
- Item or category the rule applies to
- Minimum remaining days at delivery, as written in the vendor guide
- Whether the rule is stated as days or as a share of total shelf life
- Source document and the date you last checked it
- Transit days from your warehouse to that ship-to
That transit column is the one people skip. The window is measured when the product arrives, not when it leaves your dock. So the date you actually pick against is the window plus transit plus any buffer for the load sitting in a yard.
If the rule is written as a share of total shelf life, convert it to days per item once, so pickers aren't doing arithmetic on the floor.
Allocating by expiry at the pick face
Once the table exists, allocation becomes a rule rather than a judgment call. For each order line, you work out the earliest code date that will still pass at that customer's dock, then pick the oldest lot that clears it.
That's FEFO with a floor. Plain first-expiry-first-out sends your oldest stock out first, which is right for waste and wrong if the oldest stock happens to be going to your strictest customer. If you want the background on why FEFO beats FIFO for dated goods, the FEFO definitive guide covers it.
The pick ticket should show the lot and code date to pick, not just the item and quantity. If a picker has to choose, they'll choose whatever's nearest.
Get the distributor expiry claim register
What you credit retailers downstream vs what you actually recover from principals upstream β claim-by dates per batch, and every filed claim aged against the credit note that came back. See what's inside.
Instant download. No spam, unsubscribe in one click.
Routing short-dated lots to looser windows
Here's where a window table starts paying for itself. A lot that fails one customer's window may be fine for another. Smaller independents, foodservice accounts, or your own outlet channel may accept shorter life than a big chain DC, depending on what their terms say.
So instead of asking "is this lot good?", ask "which customers can still take this lot?" Allocate the longest-dated stock to the strictest windows and push shorter-dated stock toward the looser ones while it still qualifies. When a lot no longer fits anyone's window, that's your trigger for a markdown, a supplier return, or a liquidation channel, before it's actually expired.
Doing this well means knowing which lot went to which customer. If you ever need to trace it back, our post on lot traceability across multiple customers walks through the record-keeping.
Worked example: one lot, three customers
Suppose you hold a lot of shelf-stable snacks with 75 days of life left today. You have three orders, and the windows below are illustrative, not any real retailer's terms:
- Chain DC A requires 90 days remaining at delivery, with 2 days transit. The lot fails: it would arrive with 73.
- Chain DC B requires 60 days remaining at delivery, with 3 days transit. The lot passes: it arrives with 72.
- An independent grocer requires 30 days remaining, with 1 day transit. The lot passes easily.
A picker working plain FEFO might send this lot to DC A because that order was first in the queue. It gets rejected. The right move is to give DC A your fresher stock, give DC B this lot, and keep the independent's slot open for stock that gets even shorter next month.
Same inventory, same orders. The only difference is that the window decided the allocation instead of the queue.
Preventing the chargeback after the rejection
A rejection isn't just a returned pallet. Depending on the retailer's terms, it can bring a deduction for the refusal, the freight, or a missed delivery slot. Those terms are in the same vendor guide as the window, so read both sections together.
Keep a record of each rejection: the customer, item, lot, code date at arrival, the window that applied, and the reason. Patterns show up fast. Maybe one item keeps coming in short from the supplier, or one ship-to has longer transit than you planned for. For the dispute and deduction side, see preventing expiry-related vendor chargebacks.
Running it on paper or in a system
You can run this on a spreadsheet. A tab for the window table, a tab of on-hand lots with code dates, and a formula that flags which customers each lot still qualifies for. The expiry-tracking spreadsheet template is a reasonable starting point for the lot side.
What a spreadsheet won't do is keep up on its own. Lot dates change every day, someone has to refresh the sheet before every pick wave, and the check only happens if a person remembers to look. It also won't stop a picker from grabbing the wrong pallet. The spreadsheet tells you the right answer; it can't make sure the right answer goes on the truck.
That's the point where moving the window check onto the pick ticket, automatically, starts to matter. It's also when receiving accuracy becomes non-negotiable, because every allocation depends on the code date captured at the door.
Where software fits
If you're doing this across dozens of customers and hundreds of lots, the table and the allocation logic belong in a system, not in a supervisor's memory. ShelfLifePro serves FMCG distribution, and you can see how it handles expiry-aware stock for distributors on the FMCG page. Every plan comes with a 14-day free trial, no credit card required, so you can load your own customer windows and see what it flags before your next DC delivery.
ShelfLifePro Editorial Team
The ShelfLifePro editorial team covers inventory management, expiry tracking, and waste reduction for pharmacies, supermarkets, and retail businesses worldwide.
One question, optional
What would stop you from trying ShelfLifePro?
See what batch-level tracking actually looks like
ShelfLifePro tracks expiry by batch, automates FEFO rotation, and sends markdown alerts before stock expires. 14-day free trial, no credit card required.
Prefer to talk it through? Book a 30-min call
The monthly expiry-tracking brief
One short email a month, only when there is something worth reading. FEFO tactics, markdown math, and real-world waste-reduction wins. Unsubscribe anytime.
No spam. Unsubscribe in one click.