Operator reference

Amazon FBA Expiration Date Management

A working reference for the FBA expiration-date workflow — what it is, the lifecycle stages, the per-MSKU mechanics, and the levers a seller actually controls.

Last reviewed·2026-05-28

Short version

Amazon FBA expiration date management is the seller-side workflow of mapping a real expiration date and an Unsellable by Dateto every batch of inventory inside Amazon FBA, monitoring days remaining against Amazon's inbound record, running FEFO pricing on at-risk MSKUs, and submitting scheduled Disposal Requests on a date the seller chooses. The unit of work is the Merchant SKU (MSKU), not the ASIN, because one ASIN can have multiple expiration batches in FBA at the same time.

What FBA expiration management is, in operator terms

Amazon FBA expiration management is one of the few seller workflows where Amazon's automation is opaque and the seller's record is authoritative. Amazon stores an expiration date and an Unsellable by Date for every FBA unit at receiving; the seller is responsible for verifying both against the actual batch. When those dates diverge, the consequences are downstream — units may go FEFO-blocked early, Disposal Requests can fire on the wrong batch, and Subscribe & Save subscribers can lock onto inventory that quietly expired.

The work breaks into four levers a seller actually controls:

  1. Per-MSKU date mapping. One MSKU per expiration batch, with an expiration date and an Unsellable by Date attached to it. See FNSKU and MSKU expiration date tracking.
  2. Date reconciliation. A periodic check that the dates Amazon recorded at receiving match the dates the seller intended. Resolving discrepancies early prevents wrong-batch disposals.
  3. FEFO pricing. Discounting the soonest-expiring MSKU under a given ASIN so it sells before later-dated stock. This is a seller-driven sequencing tool, not an Amazon feature.
  4. Scheduled Disposal Requests. Filing a removal request on the Unsellable by Date (or earlier) so the unit clears Amazon's warehouse on a date the seller chose, rather than waiting for Amazon's own disposal cycle.

The four-stage lifecycle

1. Inbound (pre-receipt)

Expiration tracking starts before Amazon receives the case-pack. The shipping plan carries an expiration date per MSKU; Amazon will use that date when calculating Unsellable by Date at receiving. Sellers using a label format that prints both the expiration and the lot number give Amazon a fighting chance to record the date accurately. Sellers using a generic FNSKU label without an expiration print depend on shipping-plan data only.

2. In-FBA monitoring

Once the case-pack is received, the seller's job is to keep an authoritative record of every batch in FBA and reconcile that record against Amazon's inbound data on a cadence. Amazon's public reports surface inventory by MSKU but do not always reveal per-unit expiration discrepancies until much later — sometimes only at the moment a unit goes FEFO-blocked. Daily monitoring lets the seller catch divergence before it costs sales.

3. Approaching-expiry decisions

Inside the seller's chosen warning window (commonly 30, 60, 90, and 120 days before Unsellable by Date), the operator picks a path per MSKU: discount to clear via FEFO pricing, file a Disposal Request, or move subscribers to a later-dated MSKU under the same ASIN if Subscribe & Save is enrolled. The path depends on remaining stock, sales velocity, and whether the cost of disposal exceeds the residual margin.

4. Post-expiry handling

Units that pass Unsellable by Date without being cleared become Amazon's problem on Amazon's schedule. They sit in FBA accruing storage fees, eventually disposed by Amazon at Amazon's timing, with fees per Amazon's policy. The seller's audit-trail obligation does not end here — a record of which batch was disposed, when, and at what cost is what supports later Seller Support cases, accounting reconciliation, and any reimbursement appeal.

A working example

A skin-care seller has one ASIN (B0XYZ) with three MSKUs in FBA:

  • SKIN-B0XYZ-2026-03 — 1,200 units, expiration March 2026, Unsellable by Date Jan 10 2026.
  • SKIN-B0XYZ-2026-08 — 900 units, expiration August 2026, Unsellable by Date June 22 2026.
  • SKIN-B0XYZ-2027-02 — 1,500 units, expiration February 2027, Unsellable by Date Dec 14 2026.

The seller's 90-day warning fires on Oct 12 2025 for the March batch. Trailing-30-day sales for the ASIN are 220 units; at that velocity the March batch will sell through with ~300 units to spare before its Unsellable by Date. But the seller's FEFO logic is off — Amazon's commingled fulfillment is just as likely to pick the February-2027 stock as the March-2026 stock. With FEFO pricing on, the March MSKU is discounted enough to win the Buy Box and sell first. The remaining ~900 units sell through by mid-November; the residual goes to a scheduled Disposal Request for Jan 10 (the Unsellable by Date), and the seller's audit log records each step.

Without that workflow, the same seller has 1,200 units that may or may not clear, depending on commingling — and only finds out at Unsellable by Date when the rest go FEFO-blocked, costing both the disposal fee and the lost margin on every unit that could have sold at a small discount.

What goes wrong without it

The failure modes cluster into four categories:

  • Commingling-driven wrong-batch disposals. When Amazon's fulfillment picks a younger unit over an older one, the older unit ages out and Amazon eventually disposes it. The seller pays for the disposal of stock that could have shipped at full price.
  • Listing suppression from buyer complaints. A single buyer complaint about an expired product can suppress the entire ASIN. Repeat complaints become repeat-offender flags, which compound for years.
  • Date discrepancies caught too late. The expiration date Amazon stored at receiving does not match the date on the batch. The discrepancy is not visible in any public report until a unit goes FEFO-blocked — at which point the only remedy is a Seller Support case that may or may not succeed.
  • Subscribe & Save subscriber loss. When the active MSKU rotation does not move subscribers to a later-dated successor in time, subscribers churn when the current MSKU runs out — and Amazon does not move them automatically.

How Shelfdoc helps

Shelfdoc is software that supports each of the four levers without making business decisions for the seller. The seller authorizes Shelfdoc to Amazon SP-API; Shelfdoc reads FBA inventory, inbound plans, and Subscribe & Save program data, then surfaces decisions through a daily-monitored dashboard.

  • Map every MSKU to an expiration date and an Unsellable by Date in a workbench designed for batch-level intake. Bulk paste from your existing spreadsheet.
  • Daily reconciliation against Amazon's inbound record. Discrepancies queue for review with a one-click resolution path.
  • Configure FEFO pricing per ASIN. Shelfdoc submits the price update through the Listings Items API; the seller sets the discount.
  • Schedule Disposal Requests on the Unsellable by Date (or any earlier date the seller chooses). The request submits through the official Amazon seller integration; Amazon controls acceptance, processing, and the physical disposal.
  • Email alerts at 30, 60, 90, and 120 days before any Unsellable by Date, with the operator's preferred urgency mix configurable per account.
  • An audit trail of every action timestamped — one-click PDF and Excel export for the dates that matter.

What Shelfdoc does not do

The same software-supports-but-does-not-decide posture is named explicitly in the Terms of Service:

  • Shelfdoc does not guarantee any Amazon-side outcome — acceptance of a Disposal Request, timing of physical disposal, listing acceptance, search ranking, or Buy Box state.
  • Shelfdoc does not file Amazon Account Health appeals, plans of action, or Performance Notification responses.
  • Shelfdoc does not move Subscribe & Save subscribers — that action happens in Amazon's Subscribe & Save dashboard. Shelfdoc surfaces the rotation as a task; the seller completes it on Amazon.
  • Shelfdoc does not provide legal, tax, accounting, or regulatory advice.

Managing expiration in your category

Category-specific walkthroughs of this same workflow — the pain, the manual process, and where Shelfdoc helps — for the categories where expiration risk is sharpest:

Frequently asked questions

What is FBA expiration date management?
FBA expiration date management is the seller-side workflow of mapping a real expiration date and an Unsellable by Date to every batch of inventory under each Merchant SKU, monitoring days remaining against Amazon's inbound record, and submitting scheduled Disposal Requests for units that will not sell before they go FEFO-blocked. The work spans intake, in-FBA monitoring, removal planning, and post-removal reconciliation.
Why does Amazon FBA expiration tracking need to happen at the MSKU level, not the ASIN level?
A single ASIN can have multiple batches in FBA with different expiration dates — a re-up shipment from January has a different Unsellable by Date than a shipment that arrived in August. Tracking at the ASIN level loses that batch identity and forces Amazon's commingling logic to pick which unit ships. Tracking at the MSKU level (one MSKU per expiration batch) preserves the batch and lets the seller drive FEFO sequencing and per-batch Disposal Requests.
Does Amazon dispose of expired FBA inventory on its own?
Amazon will block expired units from sale (FEFO logic) and over time will dispose of them on Amazon's schedule, with Amazon paying or charging fees per Amazon's policy. The seller has no direct control over Amazon's disposal timing. Filing a seller-directed Disposal Request through the Selling Partner API lets the seller choose when the removal is filed — typically scheduled for the Unsellable by Date or earlier — which is the lever Shelfdoc automates.
What is the difference between the expiration date and the Unsellable by Date?
The expiration date is the manufacturer-printed date on the unit. The Unsellable by Date is Amazon's seller-facing field that determines when Amazon will stop fulfilling the unit. The two dates are not the same. Amazon typically derives Unsellable by Date by subtracting a category-specific buffer (often around 50 days) from the expiration. Sellers should map both per MSKU and reconcile periodically against Amazon's inbound record because the dates Amazon stored at receiving sometimes differ from the dates the seller intended.
What is FEFO pricing in the context of expiration-dated FBA inventory?
FEFO stands for First-Expiry-First-Out. For Amazon FBA sellers with multiple batches of the same product in FBA, FEFO pricing means discounting the soonest-expiring MSKU so it sells before later-dated MSKUs. The lever is per-MSKU price; the goal is to clear the at-risk batch through normal sales rather than through a Disposal Request. Shelfdoc can submit a coordinated FEFO price update per MSKU through the Listings Items API; the seller chooses the discount amount.
What is an expiration-date discrepancy and why does it matter?
A discrepancy is a difference between the expiration date the seller intended (or printed on the case-pack label) and the date Amazon stored in the inbound record. Discrepancies are common when Amazon's receiving operation misreads a label, when a shipping plan was edited after submission, or when multiple batches were commingled in transit. Resolving them early lets the seller correct the record before Amazon enforces an Unsellable by Date that is later (or earlier) than the actual batch warrants.

Bring your FBA expiration workflow under control

Map every MSKU. File Disposal Requests on the date you choose. Audit Amazon's inbound record against your own. Email support@shelfdoc.com if you want to talk through a setup before signing up.

Create account