What does "short-dated" mean for Amazon FBA inventory?

Short-dated FBA inventory is stock whose Unsellable by Date leaves less time than your historical sell-through window for that MSKU. A 12-month-expiry batch isn't short-dated if you typically clear it in 4 months. The same 12-month-expiry batch is short-dated if your historical clearance is 11 months — the math says you'll FEFO-block residual units. "Short-dated" is a property of the seller's velocity, not the printed expiration date.

Can I refuse an inbound shipment of short-dated FBA inventory at the supplier?

Yes — the strongest move is the one you make before the units ship. If the supplier sent product with less time than your contracted minimum (most supplier agreements specify a minimum-remaining-life clause), refuse the shipment or negotiate a discount that covers the carrying-cost exposure. Amazon doesn't have a refuse-on-inbound mechanism for short-dated units once they enter FBA — the decision shifts from your warehouse to Seller Central. Refuse upstream when you can.

How do I calculate sell-through velocity for short-dated decisions?

Pull the last 90 days of unit sales for the ASIN from your Business Reports or the FBA Inventory report. Divide by 90 to get a daily run rate. Multiply that daily rate by the days between today and the Unsellable by Date. The result is your projected sell-through against this batch. If the projected sell-through is meaningfully below the unit count, you have surplus that will FEFO-block. Plan the disposal or channel-shift now, not later.

How much should I discount short-dated FBA inventory?

The discount depends on how much velocity you need to add. There's no universal rule. A common operator framework: calculate the carrying cost per unit per day (storage on cubic feet, divided by units in the case-pack, times days remaining). The discount should be at minimum that carrying-cost number plus enough margin compression to plausibly accelerate the Buy Box velocity. Higher discounts move more units faster; the trade-off is per-unit margin. Verify storage rates in Seller Central before relying on a specific carrying-cost number.

When should I schedule a Disposal Request for short-dated FBA inventory?

Schedule it for the Unsellable by Date the moment you map the MSKU. Even if you intend to sell every unit, the scheduled Disposal Request is a safety net — if your velocity assumptions don't play out, the residual units submit through SP-API on the cutoff instead of sitting in FBA accruing storage on units Amazon won't pick. Amazon decides acceptance and processing time on the Disposal Request; the seller controls only submission timing.

Amazon FBA Short-Dated Inventory

Short version

A batch is short-dated when its Unsellable by Date leaves less time than your historical sell-through window for that MSKU. The decision isn't emotional — it's a sell-through velocity calculation. Daily run rate times days remaining gives projected sell-through. If projected sell-through is below unit count, you have surplus that will FEFO-block. Plan the five-way decision (refuse / inbound + FEFO price / Subscribe & Save handoff / scheduled disposal / channel-shift) the day the MSKU is mapped, not the week before Unsellable by.

What “short-dated” means on FBA

“Short-dated” is not a property of the printed expiration date. A bottle with 18 months of printed expiration left can still be short-dated for an FBA seller whose ASIN clears in 22 months. The same 18-month bottle is long-dated for a seller whose ASIN clears in 6 months.

What makes a batch short-dated for your Amazon FBA operation: the Unsellable by Date (printed expiration minus Amazon's category-specific buffer) leaves you less time than your historical sell-through window for the MSKU. Everything else is naming — the operative number is whether projected sales clear the unit count before the Unsellable by Date.

See Amazon FBA Unsellable by Date for the cutoff Amazon FEFO-blocks at and how to calibrate the category buffer.

The sell-through velocity math

The single calculation that decides every short-dated question.

Pull 90 days of unit sales for the ASIN from Business Reports or the FBA Inventory report.
Divide by 90 to get a daily unit-sale run rate.
Multiply by (Unsellable by Date − today) to project sell-through against this batch.
Compare projected sell-through to the on-hand + inbound unit count.

If projected sell-through is meaningfully below unit count, you have surplus. The surplus is the number to plan for — not the full unit count.

The math has two honest caveats. First, your 90-day run rate is historical; promotions, seasonality, and competitor stockouts move it. Second, FEFO-pricing the soonest-expiring MSKU pulls velocity above the historical rate. Treat the calculation as a planning anchor, not a forecast.

The five decisions on receipt

When a batch arrives short-dated, the seller picks one of five paths. None is right in every case; the calculation above tells you which.

1. Refuse the inbound at the supplier

The strongest move is the one you make before the units ship. Most supplier contracts include a minimum-remaining-life clause — typically expressed as months of life remaining on receipt. If the supplier sent product short of that minimum, refuse or renegotiate. Amazon has no refuse-on-receipt mechanism for short-dated units once they enter FBA; the decision shifts from your warehouse to Seller Central, where your options narrow.

2. Inbound with FEFO pricing

When the velocity math says projected sell-through clears the unit count only if velocity rises, the lever is price. Lower the price on the short-dated MSKU through the SP-API Listings or Feeds API; the Buy Box rotates velocity toward the lower-priced MSKU on the same ASIN. See Amazon FBA FEFO pricing for the per-MSKU pricing mechanics.

3. Subscribe & Save subscriber handoff

When the short-dated MSKU is also your active Subscribe & Save subscriber MSKU, the rotation has to happen before the MSKU runs out. Set up a longer-dated replacement MSKU on the same ASIN, FEFO-price the short-dated active MSKU down so subscribers consume it faster, and let the new MSKU take over the subscriber base. Get the timing wrong and Amazon cancels subscribers instead of rolling them. See Subscribe & Save expiration risk.

4. Inbound with a scheduled Disposal Request

When velocity math says projected sell-through is below unit count even with FEFO pricing, schedule a Disposal Request for the Unsellable by Date the moment you map the MSKU. The request submits automatically on the date through SP-API; the residual units don't accrue carrying cost on Amazon's automatic disposal cycle. See Amazon FBA Removal Order + expiration.

5. Channel-shift

When the recovery path on Amazon is too compressed, the play is to recover the units off-Amazon. File a Return Order rather than a Disposal Request; ship the returned inventory to a discount channel (B-stock, regional grocers, donation with tax recovery, samples for the next marketing push). Per-unit return fees and outbound shipping apply; the recoverable value off-Amazon has to clear those costs plus the original unit COGS. Verify current Return Order fees in Seller Central.

A real-shaped example

A supplements seller receives an inbound of 1,200 units of MSKU NUT-B26-LOT08. The printed expiration date is December 31. Amazon's category buffer is roughly 90 days for this category (the seller verifies in Seller Central), so the Unsellable by Date is approximately October 2. Today is May 29 — there are about 126 days until Unsellable by.

The ASIN's 90-day unit-sale total is 540 units. Daily run rate: 540 / 90 = 6 units per day. Projected sell-through against this batch: 6 × 126 = 756 units.

Surplus: 1,200 − 756 = 444 units that will FEFO-block at the historical rate.

The seller picks two of the five decisions: FEFO pricing on the MSKU to lift the daily run rate to roughly 8 units per day (target sell-through 1,008 units), and a scheduled Disposal Request for the residual ~192 units. The Disposal Request fires on October 2 automatically. If velocity overperforms, fewer units dispose; if velocity underperforms, the schedule still closes the carrying-cost window.

Common mistakes

The five mistakes operators repeat on short-dated inventory:

Assuming the printed expiration date is the cutoff. It isn't. The Unsellable by Date is the cutoff, and it's earlier than the printed expiration. Plan against the Unsellable by Date.
Calculating sell-through against the ASIN, not the MSKU. When multiple MSKUs share an ASIN, only the soonest-expiring one is at risk. The math has to be at the MSKU level.
Discounting too late. A FEFO price drop in the final 30 days doesn't have time to compound; the Buy Box rotation needs runway. Drop the price 60 to 90 days out, not 14.
Skipping the scheduled Disposal Request because “we'll definitely sell through.” The schedule is a safety net. Setting it costs nothing if the units sell. Not setting it costs storage fees if they don't.
Forgetting the Subscribe & Save subscriber base. When the short-dated MSKU is the active subscriber MSKU, running it out without a successor MSKU cancels subscribers Amazon won't roll forward for you.

How Shelfdoc helps

Every mapped MSKU shows days-remaining against its Unsellable by Date directly in the dashboard so the velocity math is a glance, not a spreadsheet pull.
The FEFO pricing surface sequences per-MSKU prices on a shared ASIN; submissions go through the Amazon SP-API.
Scheduled Disposal Requests can be set per MSKU on the day it's mapped — the safety net for residual units is in place from day one.
Daily reconciliation against Amazon's inbound record catches Unsellable by Date discrepancies before they shift the math the seller planned against.

What Shelfdoc does not do

Shelfdoc does not negotiate supplier minimum-remaining-life clauses or refuse inbound shipments at the warehouse.
Shelfdoc does not guarantee Amazon's Disposal Request acceptance, processing time, fees, or Buy Box assignment.
Shelfdoc does not migrate Subscribe & Save subscribers on the seller's behalf. The migration is an operator action in Seller Central.
Shelfdoc does not provide accounting, tax, or legal advice on inventory disposal.

Amazon FBA Unsellable by Date — the cutoff every short-dated decision is measured against.
Amazon FBA FEFO pricing — the per-MSKU pricing lever.
Amazon FBA Removal Order + expiration — scheduled Disposal Request mechanics.
Subscribe & Save expiration risk — subscriber handoff pattern.
Amazon FBA expired inventory fees — the carrying-cost stack.
Amazon FBA expiration date SOP — the operator playbook.
Resources hub — every guide, glossary entry, calculator, and decision framework, organized by topic.

Frequently asked questions

What does "short-dated" mean for Amazon FBA inventory?: Short-dated FBA inventory is stock whose Unsellable by Date leaves less time than your historical sell-through window for that MSKU. A 12-month-expiry batch isn't short-dated if you typically clear it in 4 months. The same 12-month-expiry batch is short-dated if your historical clearance is 11 months — the math says you'll FEFO-block residual units. "Short-dated" is a property of the seller's velocity, not the printed expiration date.
Can I refuse an inbound shipment of short-dated FBA inventory at the supplier?: Yes — the strongest move is the one you make before the units ship. If the supplier sent product with less time than your contracted minimum (most supplier agreements specify a minimum-remaining-life clause), refuse the shipment or negotiate a discount that covers the carrying-cost exposure. Amazon doesn't have a refuse-on-inbound mechanism for short-dated units once they enter FBA — the decision shifts from your warehouse to Seller Central. Refuse upstream when you can.
How do I calculate sell-through velocity for short-dated decisions?: Pull the last 90 days of unit sales for the ASIN from your Business Reports or the FBA Inventory report. Divide by 90 to get a daily run rate. Multiply that daily rate by the days between today and the Unsellable by Date. The result is your projected sell-through against this batch. If the projected sell-through is meaningfully below the unit count, you have surplus that will FEFO-block. Plan the disposal or channel-shift now, not later.
How much should I discount short-dated FBA inventory?: The discount depends on how much velocity you need to add. There's no universal rule. A common operator framework: calculate the carrying cost per unit per day (storage on cubic feet, divided by units in the case-pack, times days remaining). The discount should be at minimum that carrying-cost number plus enough margin compression to plausibly accelerate the Buy Box velocity. Higher discounts move more units faster; the trade-off is per-unit margin. Verify storage rates in Seller Central before relying on a specific carrying-cost number.
When should I schedule a Disposal Request for short-dated FBA inventory?: Schedule it for the Unsellable by Date the moment you map the MSKU. Even if you intend to sell every unit, the scheduled Disposal Request is a safety net — if your velocity assumptions don't play out, the residual units submit through SP-API on the cutoff instead of sitting in FBA accruing storage on units Amazon won't pick. Amazon decides acceptance and processing time on the Disposal Request; the seller controls only submission timing.
How does Subscribe & Save change the short-dated math?: Subscribe & Save attaches each active subscription to a specific MSKU. If the short-dated MSKU is currently the active subscriber MSKU, every monthly auto-ship draws from it — which is helpful velocity. If the short-dated MSKU is *not* the active subscriber MSKU, Subscribe & Save doesn't help. The operator move when an active subscriber MSKU runs short: set up a longer-dated replacement MSKU on the same ASIN now, FEFO-price the short-dated active MSKU down so it clears faster, and plan the transfer so the longer-dated MSKU takes over the subscriber base before the active one runs out. Getting the timing wrong cancels subscribers Amazon won't roll forward on your behalf. The seller completes the actual transfer in Amazon's Subscribe & Save dashboard.

Run the short-dated calculation against every mapped MSKU automatically

Days-remaining against the Unsellable by Date on every row. Scheduled Disposal Requests as the safety net. FEFO pricing as the velocity lever. The whole operator framework in one dashboard.

Create account