Amazon FBA Expiration Date Policy — An Operator's Guide

Short version

Amazon's expiration date policy on FBA inventory has three layers operators have to navigate: the receiving-side date the warehouse records, the seller-facing Unsellable by DateAmazon derives from it, and the post-cutoff disposal cycle Amazon operates on inventory that passes Unsellable by Date. The seller's job is to map both dates per MSKU, reconcile against Amazon's record, and file scheduled Disposal Requests on the dates the seller chooses. This page describes the operator framework; Amazon's specific buffer values, fees, and disposal SLAs vary by category and time, and should be verified in Seller Central before relying on them for inventory decisions.

The three layers operators have to navigate

Layer 1 — The receiving-side date

Amazon's fulfillment warehouse records an expiration date when units arrive. The date comes from two sources: the case-pack label the seller printed, and the expiration date the seller declared in the inbound shipping plan. When both match, receiving is clean. When they don't, Amazon's receiving operation usually defaults to the shipping-plan value, but the exact behavior can vary by warehouse and category.

The receiving-side date is the foundation of everything downstream. If Amazon stored the wrong date at receiving, every downstream calculation — Unsellable by Date, FEFO blocks, disposal timing — uses the wrong foundation. The fix path is a Seller Support case with the inbound paperwork; the prevention is weekly bin checks that catch divergences early.

Layer 2 — The Unsellable by Date derivation

Amazon takes the receiving-side expiration date and subtracts a category-specific buffer to produce the Unsellable by Date. The buffer is the safety margin Amazon wants between when Amazon stops shipping the unit and when the unit becomes unsafe to use.

Buffer values are category-specific. They're commonly cited as around 50 days for non-meltable consumables; they can be shorter for perishables and longer for some pharmacy-adjacent categories. The exact values are documented in Seller Central, vary by marketplace, and update when Amazon ships product changes. The seller is responsible for verifying the current buffer for their categories.

Layer 3 — The post-cutoff disposal cycle

When a unit's Unsellable by Date passes, Amazon FEFO-blocks the unit from fulfillment. The unit remains physically in the warehouse — Amazon does not immediately dispose of it. Per Amazon's published policy, Amazon eventually disposes of FEFO-blocked units on Amazon's own schedule, with per-unit fees per Amazon's policy.

The seller's lever is to file a Disposal Request through the Selling Partner API before Amazon's automatic cycle reaches the unit. The submission is the seller's; Amazon controls acceptance, processing time, and the physical disposal. See Amazon FBA Removal Order + expiration.

Why “Amazon's policy” isn't one document

Sellers researching Amazon's expiration date policy often expect to find a single canonical document. The actual policy is distributed across:

• Seller Central help articles on inventory management.
• Seller Central help articles on Removal Orders and Disposal Requests.
• Seller Central help articles on category-specific compliance (food, beverage, supplements, beauty, baby, OTC).
• The published Removal Order fee schedule, which lives in a fee-reference page.
• The Selling Partner API documentation, which describes the technical interface to the policy.
• Periodic seller-update emails that announce changes.

No single page captures all of this in a way that stays current. Operators who want an authoritative read on their specific situation need to pull from the relevant Seller Central articles for their category and marketplace at the time of the decision.

How to verify your category specifics

Practical verification path:

1. Open Seller Central → Help in the marketplace you sell in.
2. Search for “expiration,” “Unsellable,” or “Removal Order” — whichever is closest to the decision you're making.
3. Read the article and note the last-updated date. If the article was updated in the current quarter, it's likely current. If it was last updated 18 months ago, cross-reference with recent seller-update emails before relying on it.
4. For category-specific buffers, look for the help articles that match your specific category. The general inventory-management article rarely names exact values; the category-specific articles often do.
5. For fees, the published Removal Order fee schedule is the authoritative reference. It updates periodically; verify against the most recent version when fee math matters.
6. Document what you found. The URL + last-updated date is what you'll need if Amazon changes the policy between when you decided and when the consequences play out.

How the disposal cycle works (operator framing)

When a unit's Unsellable by Date passes:

1. Amazon FEFO-blocks the unit from outbound fulfillment.
2. The unit remains in the warehouse, accruing storage fees on the case-pack volume.
3. Long-term storage fees apply if the batch crossed Amazon's long-term-storage threshold while still sellable.
4. Amazon's automatic disposal cycle eventually picks up the FEFO-blocked unit on Amazon's schedule. The exact timing isn't a published SLA; operators commonly observe windows of 30 to 60 days between FEFO-block and physical disposal, though specific cases vary.
5. Per-unit removal fees apply at physical disposal, per Amazon's current fee schedule.
6. Reimbursement is generally not offered for inventory Amazon disposes after the Unsellable by Date passes — Amazon's policy treats expiration as a seller-controlled attribute. The narrow exception is when evidence supports that Amazon's receiving operation recorded the wrong date.

The seller's alternative path: file a scheduled Disposal Request that submits through SP-API on the date the seller picked. Amazon's normal removal processing then runs through its standard SLA — typically faster than the automatic cycle. The per-unit fee is the same in both paths; the carrying cost between FEFO-block and physical disposal is what differs.

The seller's policy-side obligations

The seller carries specific obligations under Amazon's framework:

• Declare accurate expiration dates in inbound shipping plans. The date the seller declares is what Amazon uses to derive Unsellable by Date.
• Print and apply FNSKU labels correctly. A mislabeled FNSKU leads to wrong-MSKU receiving and broken downstream tracking.
• Maintain per-MSKU separation for batches with different expiration dates. See FNSKU and MSKU expiration date tracking.
• File Removal Orders for inventory the seller doesn't want Amazon to dispose on Amazon's automatic schedule.
• Respond to Account Health notices tied to listing suppression from freshness complaints. See Amazon FBA stranded inventory + expiration.
• Maintain a documentation trail sufficient to support Seller Support cases for date discrepancies, reimbursement appeals, and Account Health responses.

How Shelfdoc helps the seller comply

• Maps each MSKU's expiration date and Unsellable by Date in a single record.
• Reconciles Amazon's stored dates against the seller's record daily through SP-API. Discrepancies queue for review.
• Schedules Disposal Requests on the date the seller picks. Submission goes through SP-API on the scheduled date; Amazon decides acceptance.
• Maintains a timestamped audit trail of every action — submission, Amazon status transitions, completion timestamps. Exportable to PDF and Excel for downstream Seller Support cases.
• Surfaces the at-risk MSKUs every Friday so the operator can decide whether to FEFO-price, reschedule the Disposal Request, or take a category-specific action.

What Shelfdoc does not do

• Shelfdoc does not interpret Amazon's policy for legal purposes. The seller is responsible for verifying current policy values for their category and marketplace.
• Shelfdoc does not negotiate Removal Order fees, Reimbursement outcomes, or Account Health appeals with Seller Support. It produces the evidence; the seller writes the case.
• Shelfdoc does not change Amazon's acceptance decision, processing time, per-unit fees, or any other outcome Amazon controls.
• Shelfdoc does not provide legal, tax, accounting, or regulatory advice.

Related topics

• Amazon FBA expiration date management — the four-stage operator lifecycle.
• Amazon FBA Unsellable by Date — the date layer 2 produces.
• Amazon FBA expired inventory — what happens when units pass Unsellable by Date.
• Amazon FBA Removal Order + expiration — the seller's lever.
• Amazon FBA expiration date SOP — the operator playbook that runs against this policy framework.
• Expiration date glossary.
• Resources hub — every guide, glossary entry, calculator, and decision framework, organized by topic.