By Bernardo Campelo, Forbes Business Council E-Commerce Leader, Amazon SPN Certified provider, Amazon SP-API authorized partner, and Founder of PrepVia.
The message arrives the same way every time. A seller opens Seller Central on a normal morning and finds a notice that a few thousand units of a supplement or a pet treat have been flagged as expired and scheduled for automated removal. He walks to his sample shelf, picks up the exact product, and reads the jar. The printed date is more than a year out. The product is fine. Amazon is about to destroy or return perfectly sellable inventory anyway.
Here is the part almost nobody explains: Amazon is not reading the jar. For date-tracked products, Amazon runs on a date that lives in its own database, and when your shipment did not hand that database a real date at check-in, the system invented one. That invented date is called a virtual expiration date, and when it lands months before the real one, the automated removal machinery treats your good inventory exactly the way it would treat genuinely expired stock.
Everything downstream of the bad date works exactly as designed: the removal is a correct action taken on incorrect data. The fix has two halves: correcting the date on inventory already inside, and running date prep on the way in so the database never has to guess. This post covers both.
The 60-second version
The mechanism: for expiration-dated ASINs, Amazon tracks a date in its system, not the date printed on your unit. If your inbound shipment does not declare the expiration date, or the receiver cannot read it, the system assigns a virtual expiration date calculated from the shelf life value on file plus the receive date. A wrong or defaulted shelf life value means a virtual date that can land months before the physical one.
The damage: FBA treats units as unfulfillable when they get close to the recorded date, roughly 50 days out for most categories, and the automated unfulfillable removal setting then returns or disposes of them.
The repair: a Seller Support case with the ASIN and FNSKU, photos of the physical date on the unit, and lot documentation. Ask for the virtual date to be corrected, and pause automated removals while the case runs.
The prevention: declare the date at shipment creation, print it in MM-DD-YYYY or MM-YYYY, put it on every unit and on the carton in 36-point font, one date per ASIN per box, and land with comfortably more than the minimum shelf life, which is 105 days at check-in for most date-tracked products as of 2026.
What a Virtual Expiration Date Actually Is
Once units are received, every downstream system at Amazon works off database records: quantity, condition, location, and, for date-tracked ASINs, expiration date. The date is supposed to come from you: the Send to Amazon workflow asks for it at shipment creation, and receiving is supposed to confirm it against what is printed on the units and cartons.
When that chain breaks, the system does not leave the field blank. It computes a date: the shelf life value stored on the ASIN, added to the date the inventory was received. That computed value is the virtual expiration date, and from that moment it is the only date Amazon believes.
The chain breaks in mundane ways. The shipment was created without entering the date. The date was printed in a format the receiver could not parse. The carton had no date label, so receiving captured nothing at the box level. Or, the most common structural cause, the shelf life attribute on the ASIN is wrong: a placeholder someone entered years ago, a default value, or a number that describes the wrong pack size. A product with a 24-month shelf life and a 6-month value on file gets a virtual date 18 months early, on every shipment that fails to declare the real date.
How a Wrong Date Turns Into an Auto-Removal
The removal is the end of a pipeline, and it helps to see each stage, because you can intervene at every one of them.
First, proximity. Amazon does not wait for the recorded date to arrive. For most date-tracked categories it treats inventory as at-risk when it comes within roughly 50 days of the recorded expiration date, because units need time to sell and reach a customer with usable life remaining. Inside that window, units flip to unfulfillable. They stop selling.
Second, the removal setting. Every FBA account has automated unfulfillable inventory settings. If yours is set to dispose, units flagged as expired are destroyed on Amazon's schedule. If it is set to return, they ship back to the address on file, at removal fees. Either way, inventory you paid to manufacture, freight, prep, and inbound is now leaving the network because of a date nobody ever printed on it.
Third, silence. Nothing in this pipeline asks whether the recorded date is real. The forums are full of sellers who discovered the problem only when the removal notice landed. Some had unit counts in the thousands. All of them held physical stock a year or more from actually expiring. If you sell anything date-tracked, the recorded dates deserve a place in your weekly review, the same way the inventory ledger does.
Date Prep Errors and What Each One Costs
Every virtual date problem we have traced back started as one of a small number of inbound errors. Here is the map from error to consequence to repair.
| Date prep error | What Amazon does | The fix |
|---|---|---|
| No expiration date declared at shipment creation for a date-tracked ASIN | System assigns a virtual date from shelf life on file plus receive date, which can land months before the printed date | Enter the real date in the Send to Amazon workflow every time; treat it as required, because for these ASINs it is |
| Wrong or placeholder shelf life value on the ASIN | Every virtual date generated from it is wrong by the same offset; the error repeats on every future shipment | Correct the shelf life attribute through a support case, then request correction of dates already assigned |
| Date printed in an unsupported format, such as year first or a lot code | Receiver cannot parse it; the unit checks in without a usable date and the system falls back to a virtual one | Sticker over the original with MM-DD-YYYY or MM-YYYY before shipping |
| Date on the unit but missing from the master carton | Box-level capture fails at receiving; shipment can be flagged as a prep problem and dates go unrecorded | Print a carton-level date label in 36-point font or larger on every box, as of 2026 requirements |
| Two lots of the same ASIN mixed in one box | One date is captured for the whole box, so part of the batch inherits a date that is not its own | One expiration date per ASIN per box, always; split lots into separate boxes |
| Units arriving with too little remaining shelf life | Refused or marked unsellable at check-in; the minimum is 105 days remaining for most products as of 2026 | Plan production and inbound so units land with months of margin, not days |
| Automated unfulfillable removals set to dispose | Units flagged expired, correctly or not, are destroyed before you can inspect them | Set the preference to return and review pending removals weekly |
Notice that only one row involves Amazon doing anything unusual. The rest are inbound discipline, which is why this problem is so preventable and so persistent at the same time. The formal rules behind these rows live in Amazon's prep requirements, which we walk through in the 2026 prep requirements checklist.
Fixing a Virtual Date on Inventory Already Inside
If the removal notice has already arrived, or you have found a wrong date before it triggers anything, the repair runs through Seller Support. It works, but it works on evidence, and the order of operations matters because the removal pipeline does not pause on its own.
- Freeze the automation first. Before anything else, check the automated unfulfillable removal setting and the pending removals page. If a removal is scheduled, you are working against a clock. Switching disposal to return protects the units even if the date case takes weeks.
- Pull the exact records. ASIN, FNSKU, the shipment IDs that inbounded the affected lot, and the quantity flagged. The stronger your specificity, the faster the case moves past the first template reply.
- Open a case stating the mismatch plainly. The recorded expiration date on this FNSKU does not match the physical date printed on the units. State the recorded date, state the physical date, and ask for the virtual expiration date to be corrected to match the physical one.
- Attach the proof Amazon actually responds to. Clear photos of the physical expiration date printed on the unit, ideally alongside the FNSKU label in the same frame. Add lot documentation if you have it: a supplier invoice, certificate of analysis, or production record tying the lot to its real date. Cases with photos resolve; cases with descriptions loop.
- Ask for a bin check if support pushes back. Amazon can physically inspect units at the fulfillment center and read the printed date. It is a slow request, but it is the request that ends the argument, because the evidence is sitting in their own building.
- If the correction stalls and the clock is short, remove a sample yourself. A small removal order to a domestic address gets units in hand for photos that are indisputably from the affected lot. If you use a prep center, have it received, photographed, and documented there. This is the same inspect-and-reenter loop we describe for misgraded returns, applied to dates instead of condition.
Support can correct the virtual date, and sellers get this done routinely. What support will not do is restore the selling days you lost while the units sat unfulfillable. And reimbursement for stock already destroyed under a wrong date is a much harder case than a correction. Speed matters. The day the notice arrives is the day the case opens.
The Date Prep That Prevents All of It
Everything above is repair. Prevention is cheaper, and it is a checklist, not a skill. As of 2026, this is what a date-tracked unit needs to enter FBA cleanly.
The format
MM-DD-YYYY or MM-YYYY. Amazon also accepts the month spelled as a three-letter abbreviation, in the style of 15-JAN-2027. What it does not reliably accept is year-first formats, day-first European formats, or manufacture-date codes that require a decoder ring. If your supplier prints anything else, the fix is a sticker with the compliant format applied over the original, on every unit, before it ships to Amazon.
The placement
The date goes two places: on each individual sellable unit, and on the master carton in 36-point font or larger, as of 2026 requirements. Carton-level dates are the ones sellers skip most often, because the units already show a date and it feels redundant. It is not. Receiving works at box level first, and a missing carton date is how a whole box of correctly labeled units still ends up with no captured date.
The lot discipline
One expiration date per ASIN per box. Mixed lots in one box means one captured date for the whole box, which quietly assigns a false date to every unit from the other lot. Split lots into separate boxes even when it costs box efficiency. This is exactly the kind of rule a good prep partner enforces without being asked, and it is part of what you are actually buying with a labeling service rather than a roll of stickers.
The shelf life math
The floor is 105 days of remaining shelf life at the moment of check-in for most date-tracked products, as of 2026. Products meant to be consumed over a period, like a 90-count daily supplement, need the consumption window plus an additional buffer on top, so their effective floor is higher. And the floor is not a target. Amazon starts treating units as at-risk roughly 50 days before the recorded date. A unit that checks in at 110 days has about two months of sellable life before the system starts pulling it. Land with six months or more of runway and the whole category of problem disappears.
Shelf life math also has a seasonal edge. In Q4, check-in queues stretch and dwell time grows, which eats runway on both ends. If you sell anything that is simultaneously date-tracked and temperature-sensitive, the calendar gets even tighter, and the inbound window logic in our meltables Q4 plan applies to your dates as much as your chocolate.
Products That Are Date-Tracked Even When They Do Not Look It
The virtual date trap catches a specific kind of seller: the one who does not think of his product as expiring. Amazon's definition is broader than intuition. If a product is consumed, ingested, or applied to the body, or its effectiveness degrades over time, Amazon treats it as expiration-dated, whether or not the packaging makes a point of it.
That includes supplements and vitamins, all grocery and consumables, pet food and treats, baby food and formula, and topicals: cosmetics, skincare, sunscreen, and much of personal care. It reaches into less obvious corners too, like anything with an active ingredient that loses potency.
Where a Prep Center Sits in This
Date prep is unglamorous work: reading printed dates at receiving, catching lot splits before boxes close, stickering over noncompliant formats, and refusing to let a shipment leave with an undeclared date. None of it is hard. All of it has to happen every single time, on every box, including the ones packed at 4 PM on a Friday in November.
That consistency is the actual product. At PrepVia in Miami, FL, date verification is a receiving step, not a favor: printed dates are checked against the shipment plan at arrival, mismatches stop the line, and lots are boxed separately by default. Whether you prep in-house or outsource, the standard to hold is the same one Amazon's database holds you to: every unit that enters FBA carries a date the system can read, and the date it carries is true.
Frequently Asked Questions
What is a virtual expiration date on Amazon FBA?
A virtual expiration date is a date Amazon's system assigns to date-tracked inventory when the real date was not declared or could not be read at check-in. It is calculated from the shelf life value stored on the ASIN plus the date the inventory was received. From that point on, Amazon makes every decision about that inventory using the virtual date, not the date printed on the product.
Why did Amazon remove my inventory as expired when it was not?
Almost always because the recorded date in Amazon's system was wrong, usually a virtual date generated from a missing declaration or an incorrect shelf life value on the listing. Amazon flags inventory as unfulfillable when it gets within roughly 50 days of the recorded date, and the automated removal setting then returns or disposes of it. The removal is the system working correctly on bad data, which is why the fix is correcting the date, not appealing the removal itself.
What is the minimum shelf life for FBA check-in?
As of 2026, most expiration-dated products must have at least 105 days of shelf life remaining when they are received at the fulfillment center, and products consumed over a period need the consumption window plus an additional buffer. Units arriving under the floor can be refused or marked unsellable. Treat the minimum as a floor rather than a target, because Amazon begins restricting inventory roughly 50 days before the recorded date.
How should expiration dates be labeled for FBA?
Print the date in MM-DD-YYYY or MM-YYYY format, on each sellable unit and on the master carton in 36-point font or larger. A three-letter month abbreviation is also accepted, and if the manufacturer printed a different format you cover it with a compliant sticker. Keep one expiration date per ASIN per box, splitting different lots into separate boxes, and declare the date when you create the shipment.
Talk to PrepVia about expiration-dated prep →
Date verification at receiving · Lot-split boxing · No minimums · Amazon SPN Certified · Miami, FL
Related Reading
- Amazon Removal Orders 2026 Guide: what happens after inventory leaves the network
- FBA Prep Requirements 2026 Checklist: the full rulebook, dates included
- The FBA Meltables Window and Q4: when date-tracked meets temperature-sensitive
- FBA Labeling Service: compliant date labeling as a receiving step, not an afterthought
