Amazon Doesn't Do FIFO. Your Expiry Complaints Are the Proof.

UK food sellers are receiving expiry complaints on stock they know was fresh when it left — because Amazon picks for convenience, not date order. And once a product safety flag lands, getting it removed is a fight.

Amazon's position on this is documented and consistent: they do not practise FIFO (First-In-First-Out) for food products. As an Amazon seller, you can flag expiry dates when sending inventory to FBA, but the picking logic is driven by warehouse efficiency, not date prioritisation. The result is that food sellers regularly send correctly dated stock into FBA and receive expiry complaints anyway — because older units from a previous shipment are still in the warehouse and being picked ahead of the newer stock.

For most categories, a bad review is a bad review. For food, an expiry complaint is a potential product safety flag. Amazon treats these differently from standard negative feedback. A single complaint can trigger a listing review, a hold on inventory, or a suspension — and the appeals process for product safety flags is slower and less predictable than a standard listing issue.

"We had a product safety flag on a supplement we sell on Amazon UK. We knew the stock was fine — we'd just sent a fresh replenishment. But Amazon had older stock sitting in another fulfilment centre that they were still picking. It took six weeks and a full lot traceability submission to get the flag cleared."

The instinct is to manage expiry risk by sending smaller, more frequent replenishments — keeping older stock lower. But for food sellers working with minimum order quantities, supplier lead times, and FBA shipment costs, that's not always operationally feasible. And even when you do send smaller batches, you can't control which fulfilment centre Amazon stores your stock in or which unit they pick when an order arrives.

Selling food across multiple channels adds another layer of complexity. eBay and Shopify don't have the same expiry management infrastructure as Amazon. A product with a short shelf life that isn't moving on Amazon might be better redirected to another channel — but without visibility into stock age and channel performance simultaneously, that decision rarely gets made proactively.

The direct cost of a product safety suspension is lost sales for the duration of the hold — which, for high-velocity food products, can represent significant revenue depending on the length of the review. But the indirect costs are often larger. A product safety flag affects your seller metrics and can have a cascading effect on other listings if Amazon's system flags your account as having a pattern of safety complaints.

There's also the cost of the appeal itself — the time spent gathering lot traceability records, supplier certificates, and expiry documentation to submit to Amazon's product safety team. For food sellers who didn't have this documentation systematically organised, it becomes an urgent operational scramble rather than a straightforward submission.

"The problem isn't that the product was unsafe — it clearly wasn't. The problem is that once Amazon opens a product safety case, you're in their process and on their timeline. You can submit everything correctly and still wait three weeks to hear back."

The sellers managing expiry risk well are doing two things differently:

None of this requires a huge operational overhaul. It requires the right system in the middle of your selling operation — one that connects your inventory, your stock age data, and your channel performance in one place.

You've just read exactly how Amazon's non-FIFO fulfilment silently creates expiry risk for food sellers — even when the stock you sent was perfectly fresh. This is exactly the operational gap Vastyn was built to solve.