Amazon FBA Unsellable by Date

Short version

The Amazon FBA Unsellable by Dateis the seller-facing cutoff Amazon stores per FBA unit, derived from the expiration date minus a category-specific safety buffer (commonly around 50 days for consumables and beauty). After the cutoff, Amazon stops shipping the unit (FEFO block) and eventually disposes of it on Amazon's schedule. The seller's job is to make sure the date Amazon stored matches the actual batch and to file a scheduled Disposal Request before — or on — that date to control the timing of removal.

What "Unsellable by Date" means

The Unsellable by Date is not the same as the expiration date. The expiration date is the manufacturer-printed date on the unit; the Unsellable by Date is what Amazon uses to decide when to stop fulfilling. Amazon derives it from the expiration date by subtracting a category-specific buffer, then stores it in the inbound record at receiving. From that point forward, every fulfillment decision (whether to ship to a buyer, whether to include the unit in FEFO sequencing, whether to commingle it) keys off the Unsellable by Date.

Sellers see the Unsellable by Date inside Seller Central's FBA inventory reports and through the SP-API. Whether the date Amazon has on file actually matches the unit in the warehouse is the seller's responsibility to verify.

How Amazon calculates the Unsellable by Date

Amazon's buffer between expiration and Unsellable by Date varies by category. As a practical guide:

• Consumables / food / beauty — typically around 50 days of buffer. A unit expiring March 1 has an Unsellable by Date around mid-January.
• Other categories — the buffer can be longer; Amazon's documentation is the authoritative source for any individual product. Sellers should not assume a single number across the catalog.

The data Amazon uses to calculate the Unsellable by Date comes from two places: the expiration date the seller declared in the shipping plan, and any expiration labels Amazon's receiving operation could read on the case-pack itself. When those two sources disagree, the value Amazon stores depends on Amazon's internal reconciliation rule (which is not exposed to sellers in real time). This is why reconciliation matters — the value Amazon stored may not be what the seller expected.

What happens when the Unsellable by Date passes

Three things, in roughly this order:

1. FEFO block. Amazon stops shipping the unit immediately. Existing orders complete; new orders fall through to younger-dated inventory if any exists under the same ASIN. If no younger inventory exists, the listing may show as out of stock on the SKU even though the FBA quantity report still shows units.
2. Stranded status. The unit becomes part of Amazon's stranded inventory cycle. Storage fees continue to accrue against the seller; Amazon will surface the stranded status in stranded-inventory reports.
3. Amazon-controlled disposal. On Amazon's schedule (which varies by warehouse, season, and product category), Amazon will dispose of the unit and charge or pay the seller per Amazon's disposal policy. The seller has no direct control over Amazon's timing once the unit is stranded.

The lever that returns control to the seller is a scheduled Disposal Request filed before — or on — the Unsellable by Date. That puts the timing and the audit trail in the seller's hands.

Worked example

A vitamin seller shipped 600 units of one ASIN into FBA on August 15. The expiration date printed on the case-pack is April 30 of the following year. Amazon's buffer for this category is approximately 50 days, so the Unsellable by Date Amazon stores is around March 10.

The seller's trailing-30-day sales rate is 12 units per day. At that velocity, the 600-unit batch will sell through in roughly 50 days — comfortably before Unsellable by Date. So far so good. But the seller has a second batch of the same ASIN expiring in February of the following year — 800 units, Unsellable by Date around mid-December. Without FEFO pricing, Amazon's commingled fulfillment may pick either batch on any given order; the older batch could age out while the newer batch sells.

The seller's correct move: enable FEFO pricing on the ASIN, with the older batch discounted to win the Buy Box first. Schedule a Disposal Request on the older batch's Unsellable by Date for any residual. The newer batch carries forward at full price.

Common mistakes

• Treating Unsellable by Date and expiration as the same date. They are not. Planning Disposal Requests against the expiration date instead of Unsellable by Date burns the buffer — by the time the disposal files, the unit is already FEFO-blocked.
• Not reconciling against Amazon's stored value. The Unsellable by Date Amazon stored at receiving may differ from what the seller declared. Sellers who skip reconciliation find out only when Amazon FEFO-blocks units earlier than expected.
• Filing a single Disposal Request for an ASIN. Disposal Requests are MSKU-scoped, not ASIN-scoped. If the ASIN has two batches (two MSKUs) in FBA, the seller needs two Disposal Requests with two scheduling decisions.
• Forgetting that Disposal Requests, once submitted to Amazon, cannot be cancelled. Amazon's SP-API does not offer a cancel operation for FBA removal orders. A scheduled Disposal Request that has not yet submitted can be withdrawn in Shelfdoc; once it submits to Amazon, the disposal is permanent.

How Shelfdoc helps

Shelfdoc maps the Unsellable by Date as a first-class field per MSKU, separate from the expiration date. The dashboard surfaces days-until-Unsellable-By and color-codes urgency. Daily reconciliation against Amazon's inbound record flags discrepancies before they bite. Disposal Requests can be scheduled for the Unsellable by Date or any earlier date the seller chooses; the request submits through the official Amazon SP-API on the scheduled date and records Amazon's order ID in the audit log.

When the seller wants to confirm a Disposal Request before it submits, the seller can set the workflow to Approval-queue mode — Shelfdoc queues the request and emails the seller for explicit approval. The same workflow can run in automatic-submission mode for sellers who prefer the request to fire without confirmation. Both modes are seller choices, switchable per account.

What Shelfdoc does not do

• Shelfdoc does not change Amazon's Unsellable by Date calculation. The buffer Amazon uses is Amazon's policy.
• Shelfdoc does not cancel a Disposal Request that has already submitted to Amazon. Amazon's SP-API does not expose a cancel operation; once submitted, the disposal is permanent.
• Shelfdoc does not appeal stranded-inventory issues with Amazon Seller Support — but the audit log Shelfdoc maintains gives the seller a clean record to file a case with.
• Shelfdoc does not guarantee Amazon-side timing, acceptance, or outcome of any Disposal Request.

Related topics

• Amazon FBA Expiration Date Management — the full workflow this date is one component of.
• FNSKU and MSKU expiration date tracking — why Unsellable by Date must be tracked at the MSKU level.
• Unsellable by Date calculator — estimate the date for any printed expiration.
• Amazon FBA expired inventory — what happens once Unsellable by Date passes.
• Amazon FBA Removal Order + expiration — scheduling Disposal Requests on this date.
• Amazon FBA FEFO pricing — the right response in the warning window.
• Amazon FBA stranded inventory + expiration.
• FBA inventory bin check.
• Expiration date glossary — definitions of every term used on this page.
• Amazon FBA expiration date policy — operator framework for the three layers.
• What Shelfdoc does (and does not) — capability boundary in plain language.
• Pricing.
• Resources hub — every guide, glossary entry, calculator, and decision framework, organized by topic.