Can I manage FBA expiration entirely inside Seller Central?

Yes — Seller Central gives you the raw tools. You enter expiration dates on inbound shipments, you can pull FBA inventory reports that include expiration and aged-inventory columns, you can create manual removal (disposal or return) orders, and you can set automated unfulfillable-inventory removal settings. A disciplined seller with a small catalog can manage expiration this way. The gap is not capability — it is that the native flow is manual, reactive, and spread across several screens, with no per-MSKU forward view of when each batch becomes unsellable.

Doesn't Amazon's automated unfulfillable removal already handle expired stock?

Amazon offers automated removal settings for unfulfillable inventory, which can dispose or return units after they become unfulfillable. The catch is the timing: those settings act after units are already unfulfillable — at or past the expiration point — which is typically a full-cost loss. They are a safety net for stranded stock, not a way to sell through or remove inventory before it expires on a schedule you choose. Confirm your account's current automated-removal behavior in Seller Central; Amazon's settings and timing change and vary by category.

Do the FBA inventory reports show expiration dates?

Some FBA inventory and inventory-age reports include expiration and time-in-warehouse columns. You can export them and sort. What the reports do not do is map a single source-of-truth Expiration Date and a derived Unsellable by Date per MSKU, watch the calendar for you, reconcile your record against Amazon's inbound record, or turn any of it into scheduled action. A report is a snapshot you have to pull, read, and act on manually each time.

How do I handle a wrong expiration date in Amazon's record manually?

You compare Amazon's reported date against your own supplier paperwork, then open a Seller Support case asking Amazon to review the record, attaching your evidence. It works, but you have to notice the mismatch first — which means manually cross-checking dates — and you have to compose and track each case yourself. Shelfdoc flags the discrepancy for you and generates a case template you review and file; it never submits the case automatically, and Amazon controls whether any date is updated.

If Seller Central can do it, why pay for software?

For the same reason sellers use repricers and forecasting tools instead of doing everything by hand: the native tools are capable but manual, and manual does not scale. As SKU count and expiration batches grow, the work of pulling reports, cross-checking dates, watching the calendar, and filing removals on time becomes the failure point. Shelfdoc turns that recurring manual work into a per-MSKU forward view, alerts, FEFO pricing, and a Disposal Request you schedule and review. If your catalog is tiny and your habit is strong, the native flow may genuinely be enough today.

Does Shelfdoc replace Seller Central?

No. Shelfdoc works on top of your Amazon account through SP-API — it reads your FBA inventory and submits Disposal Requests on the date you choose. You still use Seller Central for everything else, and Amazon still controls acceptance and timing of every removal. Shelfdoc organizes the expiration workflow so the calendar drives consistent action; it does not replace Amazon's console or its decisions.

Managing Amazon FBA Expiration Dates in Seller Central

Short version

Seller Central gives you everything you need to manage FBA expiration by hand: you enter expiration dates on inbound shipments, pull FBA inventory and inventory-age reports, create manual removal orders, and set automated unfulfillable-removal rules. For a small catalog with a disciplined operator, that is enough. The native flow breaks down not on capability but on scale and timing — it is manual, reactive, and spread across several screens, with no single per-MSKU view of when each batch hits its Unsellable by Date, no forward calendar, and no way to act before the loss. Shelfdoc systematizes exactly that lifecycle on top of your account through SP-API — you still decide, and Amazon still controls acceptance. US marketplace.

What Seller Central gives you natively

Credit where due: Amazon does not leave you empty-handed. Working entirely inside Seller Central, a seller can:

Enter expiration dates at inbound. When you create a shipping plan for expiration-dated products, Amazon asks for the expiration date and uses it for its own FEFO handling and the Unsellable by Date.
Pull FBA inventory and inventory-age reports. Several reports include expiration and time-in-warehouse columns you can export and sort.
Create manual removal orders. You can create a disposal or return order for specific MSKUs or FNSKUs whenever you choose.
Set automated unfulfillable removal. Amazon offers settings that automatically dispose or return units once they become unfulfillable.
Open Seller Support cases. If Amazon's expiration record looks wrong, you can ask Seller Support to review it with your evidence attached.

All of this is real and usable. The honest point of this page is not that Seller Central can't do it — it is what the native flow costs you in manual effort and missed timing as volume grows. Amazon's tools, settings, and timing change and vary by category; confirm current behavior in your own account before relying on any specific step.

The manual process, step by step

Done entirely by hand, a careful seller's expiration routine looks like this:

Record the date at inbound and keep your own copy (supplier invoice, lot/batch) in case Amazon's record differs.
Pull an inventory report on a regular cadence — weekly or so — and sort by expiration or inventory age.
Eyeball what's approaching the danger zone and decide: discount to sell through, or remove.
Discount the soonest-dated stock first by hand (FEFO), adjusting prices in Manage Inventory.
Cross-check Amazon's expiration record against your paperwork and open a Seller Support case for any mismatch.
Create a removal order before the unsellable window so you recover units instead of taking a full-cost auto-disposal.
Repeat, every week, forever — the clock never stops, and a single missed week can turn a price-down sale into a write-off.

Per Amazon's published FBA policies, units that reach their expiration date are removed from sellable inventory and auto-disposed, and expired units are generally not returnable — in practice often within roughly 50 days of the expiration date. So the manual routine is not busywork; missing it is frequently a full-cost loss. Confirm current timing in Seller Central and Amazon's FBA policy documentation.

Where the manual flow breaks down at scale

No single forward view. The native tools show snapshots; nothing tells you, in one place, which MSKUs cross their Unsellable by Date in the next 30/60/90 days.
Per-ASIN, not per-batch. One ASIN can hold several expiration batches under different MSKUs. Managing that distinction by hand in a report is error-prone — and the expiration problem lives at the MSKU/FNSKU batch grain.
Reactive, not scheduled. Automated unfulfillable removal fires after units are already lost. There is no native way to schedule your own removal on a date you choose, ahead of the window.
Discrepancies go unnoticed. You only catch a wrong Amazon date if you manually cross-check — at volume, most never get checked.
No audit trail. Manual actions across several screens rarely leave a consistent, timestamped record of why each unit was handled the way it was.
It depends on a person not missing a week. Coverage is only as reliable as the operator's calendar discipline.

How Shelfdoc fits on top of Seller Central

Shelfdoc does not replace Seller Central — it reads your FBA inventory and submits removals through SP-API, and you keep using Amazon's console for everything else. What it adds is the system the native flow lacks:

Auto-detect expiration-dated ASINs from FBA history via Inventory Intelligence, routed into an Unmapped queue.
One forward view of Expiration and Unsellable by Date per MSKU — color-coded by urgency, sortable, with 30/60/90/120-day buckets.
Date Discrepancy flagging against Amazon's inbound record, with a Seller Support case template you review and file.
FEFO pricing keyed to expiration — discount the soonest-dated batch first. See FBA FEFO pricing.
Scheduled Disposal Request on a seller-chosen, seller-reviewed date — submitted through SP-API ahead of the unsellable window. See Removal Order expiration.
Bin Checks and an Audit Log so the workflow is verifiable and repeatable regardless of who operates it.

Pricing is Starter $29/mo (10 active mapped SKUs), Operator $49/mo (50), and Scale $149/mo (250); 250+ is custom — contact us. Support is at support@shelfdoc.com.

What Shelfdoc does not do

Does not replace Seller Central — it works on top of your account through SP-API.
Does not submit Seller Support cases on your behalf — it generates a template you review and file.
Does not control Amazon's decisions — it submits Disposal Requests on the date you choose; Amazon decides acceptance and timing.
Does not do restock forecasting, PO/supplier management, or profit/fee/margin analytics.
Does not cover marketplaces outside the US, and does not manage AWD inventory.

When the native Seller Central flow is enough

You have a small catalog and can reliably stay ahead of every expiration by hand.
Your expiration risk is low — few dated SKUs, slow accumulation, generous shelf life.
You have a disciplined weekly habit and never miss the report-and-act cadence.
You don't sell expiration-dated inventory at all — then none of this applies.

If that is you, a paid subscription may not earn its keep yet. Shelfdoc is for the point where the manual routine starts slipping under volume.

Spreadsheet & software alternatives — spreadsheets, inventory suites, analytics, agencies.
Amazon FBA expiration date management — the full lifecycle.
Amazon FBA Removal Order expiration — the scheduled Disposal Request.
Unsellable by Date — the date that drives every decision.
Expiration-date self-audit — score your current process.
What Shelfdoc does (and does not) — the explicit capability statement.
Pricing — Starter, Operator, Scale.

Frequently asked questions

Can I manage FBA expiration entirely inside Seller Central?: Yes — Seller Central gives you the raw tools. You enter expiration dates on inbound shipments, you can pull FBA inventory reports that include expiration and aged-inventory columns, you can create manual removal (disposal or return) orders, and you can set automated unfulfillable-inventory removal settings. A disciplined seller with a small catalog can manage expiration this way. The gap is not capability — it is that the native flow is manual, reactive, and spread across several screens, with no per-MSKU forward view of when each batch becomes unsellable.
Doesn't Amazon's automated unfulfillable removal already handle expired stock?: Amazon offers automated removal settings for unfulfillable inventory, which can dispose or return units after they become unfulfillable. The catch is the timing: those settings act after units are already unfulfillable — at or past the expiration point — which is typically a full-cost loss. They are a safety net for stranded stock, not a way to sell through or remove inventory before it expires on a schedule you choose. Confirm your account's current automated-removal behavior in Seller Central; Amazon's settings and timing change and vary by category.
Do the FBA inventory reports show expiration dates?: Some FBA inventory and inventory-age reports include expiration and time-in-warehouse columns. You can export them and sort. What the reports do not do is map a single source-of-truth Expiration Date and a derived Unsellable by Date per MSKU, watch the calendar for you, reconcile your record against Amazon's inbound record, or turn any of it into scheduled action. A report is a snapshot you have to pull, read, and act on manually each time.
How do I handle a wrong expiration date in Amazon's record manually?: You compare Amazon's reported date against your own supplier paperwork, then open a Seller Support case asking Amazon to review the record, attaching your evidence. It works, but you have to notice the mismatch first — which means manually cross-checking dates — and you have to compose and track each case yourself. Shelfdoc flags the discrepancy for you and generates a case template you review and file; it never submits the case automatically, and Amazon controls whether any date is updated.
If Seller Central can do it, why pay for software?: For the same reason sellers use repricers and forecasting tools instead of doing everything by hand: the native tools are capable but manual, and manual does not scale. As SKU count and expiration batches grow, the work of pulling reports, cross-checking dates, watching the calendar, and filing removals on time becomes the failure point. Shelfdoc turns that recurring manual work into a per-MSKU forward view, alerts, FEFO pricing, and a Disposal Request you schedule and review. If your catalog is tiny and your habit is strong, the native flow may genuinely be enough today.
Does Shelfdoc replace Seller Central?: No. Shelfdoc works on top of your Amazon account through SP-API — it reads your FBA inventory and submits Disposal Requests on the date you choose. You still use Seller Central for everything else, and Amazon still controls acceptance and timing of every removal. Shelfdoc organizes the expiration workflow so the calendar drives consistent action; it does not replace Amazon's console or its decisions.

Stop running the expiration routine by hand

Shelfdoc turns the manual Seller Central routine into a per-MSKU forward view, discrepancy flagging, FEFO pricing, and a Disposal Request you schedule and review — on top of your account, through SP-API. You decide; Amazon controls acceptance. US marketplace.

Create account