Amazon FBA Expiration Date SOP

Short version

The Amazon FBA expiration date SOP is built around four routines: an intake routine that creates one MSKU per expiration batch and maps it, a weekly rhythm that catches discrepancies before they cost sales, a scheduled removal pattern that fires Disposal Requests on the Unsellable by Date the seller chose, and a Subscribe & Save transfer pattern that prevents the missed-cycle failure mode. Below: the full playbook.

Five operating principles

1. One MSKU per expiration batch. The per-MSKU model is what makes everything else work. ASIN-level tracking loses batch identity; per-MSKU is the unit of work.
2. Reconcile the seller's record against Amazon's record weekly. Amazon's public reports don't surface expiration-date discrepancies until a unit goes FEFO-blocked — usually weeks too late.
3. Schedule decisions, don't make them on the day. Disposal Requests, FEFO pricing rotations, and Subscribe & Save transfers all benefit from being set up in advance.
4. Document every action timestamped. The Seller Support reimbursement case you need next month depends on the timeline you wrote down this month.
5. Amazon controls outcomes; the seller controls timing. Submission timing is the lever. Acceptance, fees, and physical action are Amazon's.

The intake routine — every new batch

Run this routine every time a new batch of expiration-dated inventory is about to ship to FBA. Budget 5-15 minutes per batch depending on how many MSKUs you're creating.

1. Determine the expiration date of the batch from the case-pack label. If multiple sub-lots in the same shipment have different dates, each sub-lot becomes a separate MSKU.
2. Create a new MSKU in Seller Central per the naming convention. See the how-to walkthrough.
3. Print FNSKU labels for the new MSKU.
4. Create the inbound shipping plan, declare the expiration date per the case-pack, and ship under the new MSKU.
5. Once Amazon receives the units, the new MSKU appears in your FBA inventory. Map it in Shelfdoc with the expiration date and the Unsellable by Date you want to manage against.
6. Set the scheduled Disposal Request at the time of mapping. The default is to fire on the Unsellable by Date itself; some operators schedule it 7 days earlier to give Amazon's processing time a head start.
7. Note any operator-specific flags — is this MSKU going to be the active Subscribe & Save offer? Will FEFO pricing apply? Mark the MSKU accordingly.

The weekly rhythm — every Friday

Pick a day and stick to it. Friday morning is the operator default because it leaves the weekend to absorb any Seller Support filings. Budget 45 minutes.

• Bin check (12-15 min). Reconcile expected quantity vs. Amazon's reported quantity per MSKU. Flag any delta exceeding your tolerance threshold. See the bin check page.
• Date discrepancy review (10 min). Check the Discrepancies queue for any MSKU where Amazon's stored Unsellable by Date doesn't match what you mapped. File Seller Support cases on the divergences.
• Scheduled removal review (5 min). Look at the Removal Orders tab. Confirm any orders that fired this week moved to Processing or Completed. Investigate any in Failed status.
• FEFO pricing decisions (5 min). For each ASIN with multiple mapped MSKUs, review velocity on the soonest-expiring MSKU. Adjust discount if needed.
• Subscribe & Save runway check (5 min). For each active Subscribe & Save MSKU, confirm projected exhaustion runway exceeds your transfer lead time.
• Log the result (2-3 min). Even a clean week is worth recording — the audit trail matters for reimbursement cases.

The scheduled removal pattern

The single highest-leverage routine in the SOP. The pattern: set the Disposal Request date when you map the MSKU; let the schedule fire automatically; review status next bin check.

1. At MSKU mapping, set the Disposal Request to fire on the Unsellable by Date.
2. For categories with longer Amazon processing windows, schedule 5-7 days earlier so the units submit before the FEFO block.
3. For the residual after FEFO pricing has cleared most of a batch, the same scheduled request handles the leftover automatically.
4. Once submitted, Amazon controls acceptance and processing. Status updates flow back through SP-API.
5. The bin check confirms that the scheduled request fired and that Amazon accepted it. If the order is in Failed status, the operator investigates.

See Amazon FBA Removal Order + expiration for the full mechanics.

The Subscribe & Save transfer pattern

The most expensive failure mode this SOP prevents. The pattern:

1. Keep one active Subscribe & Save MSKU per ASIN at a time. Don't run two in parallel.
2. Watch subscriber-demand runway, not inventory count. Subscriber demand divided by current weekly velocity gives the actual exhaustion runway.
3. Plan the transfer four weeks before exhaustion. The replacement MSKU should be mapped, in FBA, with at least 12 weeks of subscriber demand inventory.
4. Run the transfer inside Seller Central's Subscribe & Save dashboard. Software can't do this — the SP-API doesn't have a subscriber-migration surface.
5. After the transfer, let the predecessor MSKU sell down to non-subscribers, apply FEFO pricing if velocity is low, or file the scheduled Disposal Request on its Unsellable by Date.

See Subscribe & Save expiration risk for the full pattern.

Recovery actions

Episodic. Not part of the rhythm but the SOP includes them so the operator has a documented path when something breaks.

• Date discrepancy at receiving. Open a Seller Support case with the inbound paperwork. Reference the timestamped record showing when the seller noted the divergence — that record usually decides the case.
• Listing suppression from a freshness complaint. Respond to the Account Health notice. Address the underlying cause (often the date discrepancy above). Don't respond defensively; address the operator pattern that triggered the complaint.
• Failed Disposal Request. The status from Amazon usually names the reason (inventory mismatch, insufficient inventory, MSKU mismatch). Resolve the underlying cause; refile.
• Missed Subscribe & Save transfer. Document the missed-cycle window for the at-risk subscribers. Plan reactivation outreach where Amazon's tools allow. Update the SOP to schedule transfers earlier next time.
• Reimbursement case for incorrectly disposed inventory. File through Seller Support with the case-pack date evidence, the date-discrepancy timeline, and the audit log showing every action Shelfdoc submitted.

How Shelfdoc helps the seller run this SOP

• Per-MSKU mapping with explicit expiration date and Unsellable by Date — the data structure the SOP runs on.
• Bin check queue surfaces date discrepancies, quantity drift, and at-risk batches in one place.
• Scheduled Disposal Requests fire automatically on the date the seller picked. Submission goes through SP-API; Amazon decides acceptance.
• FEFO pricing rotation through SP-API per MSKU.
• Subscribe & Save runway tracking + transfer alerts before the active MSKU runs out. Deep link to the Subscribe & Save dashboard inside Seller Central.
• Audit log timestamps every action. Exportable to PDF and Excel for downstream cases.

What Shelfdoc does not do

• Shelfdoc does not create MSKUs in Seller Central — that's a seller action in Amazon's interface.
• Shelfdoc does not transfer Subscribe & Save subscribers — also a seller action inside Amazon.
• Shelfdoc does not file Seller Support cases or Account Health responses. It produces evidence; the seller writes the case.
• Shelfdoc does not change Amazon's acceptance, processing time, fees, or any other outcome Amazon controls.

Related topics

• Amazon FBA expiration date management — the hub.
• How to create a new MSKU in Seller Central.
• Amazon FBA Unsellable by Date.
• FBA inventory bin check.
• Amazon FBA Removal Order + expiration.
• Amazon FBA FEFO pricing.
• Subscribe & Save expiration risk.
• Expiration date glossary.
• Resources hub — every guide, glossary entry, calculator, and decision framework, organized by topic.
• Amazon FBA expiration date policy — the operator framework the SOP runs against.