Short version
Beauty and personal care carries two expiration problems at once. Regulated items like sunscreen and OTC-style topicals are treated as expiration-dated by Amazon and may be pulled a window before the printed date — often described as around 50 days, though you should confirm the current rule in Seller Central. And because beauty runs heavily through Subscribe & Save, committed subscriber demand can stay anchored to a Merchant SKU that's approaching its Unsellable by Date. Shelfdoclets you map a real Expiration Date and an Unsellable by Date to each batch by MSKU, surfaces when Subscribe & Save demand is pointed at a soon-dated SKU, flags the soonest-dated batch for FEFO pricing, and submits Disposal Requests on the date you choose. It also compares your mapped date against Amazon's reported date and gives you a Seller Support case template to file. You review every action; Amazon decides acceptance.
The beauty pain — regulated dates and Subscribe & Save exposure
Beauty & Personal Care — skincare, cosmetics, sunscreen, hair care, fragrance, OTC-adjacent topicals — mixes two problems. First, regulated items such as sunscreen and OTC-style topicals are treated as expiration-dated by Amazon and fall under the same pull window as supplements (often described as around 50 days before the printed date; confirm in Seller Central). Second, beauty is heavily run through Subscribe & Save, which creates a quiet trap: subscribers stay anchored to an MSKU that's approaching its Unsellable by Date, so demand is committed to a batch that's about to stop shipping.
Add per-unit prices high enough that a FEFO block on a single batch is a meaningful loss, and the category punishes anyone tracking dates loosely. Many products also carry a Period-After-Opening symbol or a printed expiration, so the catalog mixes genuinely date-controlled SKUs with PAO-only SKUs that need to be separated by hand.
The workflow today, by hand
- Separate the genuinely expiration-dated SKUs (sunscreen, actives) from PAO-only SKUs by hand.
- Track printed dates per batch in a spreadsheet, re-keyed each restock wave.
- Check Subscribe & Save subscriber counts against the soonest-dated MSKU to see if committed demand is pointed at a batch that's about to go unsellable.
- Discount the soonest-dated batch manually and monitor velocity.
- Compare label dates to Amazon's record by hand when something looks off.
- File Disposal Orders in Seller Central for batches that won't clear before the pull window.
How Shelfdoc helps
- Per-MSKU date mapping keeps each restock wave's batch distinct, with its own Expiration Date and Unsellable by Date — critical for high-value beauty SKUs. See FNSKU and MSKU expiration date tracking.
- Subscribe & Save monitoring surfaces when committed Subscribe & Save demand is anchored to an MSKU approaching its Unsellable by Date, so you can plan the move to a longer-dated batch. See Subscribe and Save expiration risk.
- FEFO pricing flags the soonest-dated batch first, so a high-value batch gets discounted before it blocks. See Amazon FBA FEFO pricing.
- Inventory Intelligence auto-detects expiration-dated beauty ASINs from recent FBA history and routes new MSKUs into the Unmapped queue.
- Date Discrepancies compares your mapped date against Amazon's reported date and produces a Seller Support case template.
- Scheduled Disposal Requests fire on your chosen date, submitted through SP-API; Amazon decides acceptance and timing.
What Shelfdoc does not do
- Does not decide which beauty SKUs Amazon treats as expiration-dated — you map dates where they apply.
- Does not migrate Subscribe & Save subscribers between MSKUs; that action lives in Amazon's Subscribe & Save dashboard. Shelfdoc surfaces the risk as a task.
- Does not file the Seller Support case for a date discrepancy — it provides the template.
- Does not guarantee a discounted high-value batch clears before its Unsellable by Date.
Related topics
- Amazon FBA expiration date management — the full date-control lifecycle.
- Unsellable by Date — the date that drives pricing and disposal decisions.
- FNSKU and MSKU expiration date tracking — per-MSKU tracking across restock waves.
- Subscribe and Save expiration risk — committed demand anchored to a soon-dated MSKU.
- Amazon FBA FEFO pricing — discounting high-value batches before they block.
- Amazon FBA expired inventory fees — the cost of a lost beauty batch.
- Disposal vs return orders — disposal vs return for beauty stock.
- Expiration date glossary — Unsellable by Date, FEFO, Subscribe & Save risk defined.
- Resources hub — guide hub and calculator.
Frequently asked questions
- Which beauty products does Amazon treat as expiration-dated?
- Many beauty products carry a Period-After-Opening symbol or a printed expiration, and regulated items — sunscreen and OTC-style topicals with active drug facts — are firmly treated as expiration-dated by Amazon and fall under the same pull window as supplements (often described as around 50 days before the printed date; confirm the current rule in Seller Central). Shelfdoc does not decide which SKUs Amazon treats as dated — you map dates where they apply.
- How does Subscribe & Save create a hidden expiration trap in beauty?
- Beauty runs heavily through Subscribe & Save, so committed subscriber demand can stay anchored to a Merchant SKU that is approaching its Unsellable by Date — demand is committed to a batch that is about to stop shipping. Shelfdoc surfaces when Subscribe & Save demand is anchored to a soon-dated MSKU so you can plan the move to a longer-dated batch. The subscriber transfer itself happens in Amazon's Subscribe & Save dashboard; Shelfdoc surfaces the risk as a task.
- Why does per-MSKU mapping matter more for high-value beauty?
- Beauty skews higher-priced per unit than food, so a single FEFO block on one batch is a meaningful loss. Per-MSKU date mapping keeps each restock wave's batch distinct, with its own Expiration Date and Unsellable by Date, so a high-value batch does not commingle and quietly go unsellable. FEFO pricing then flags the soonest-dated batch first so you can discount it before it blocks.
- I restock the same hero SKU in waves — how do I keep batches straight?
- Each restock wave is a distinct batch with its own date. Shelfdoc maps an Expiration Date and an Unsellable by Date per MSKU so waves stay separate, and Inventory Intelligence auto-detects expiration-dated beauty ASINs from recent FBA history and routes new MSKUs into the Unmapped queue so a fresh wave shows up as a mapping task. You confirm and map each one.
- What if Amazon's date differs from my label?
- Date Discrepancies compares your mapped date against Amazon's reported date and produces a Seller Support case template you file yourself. Shelfdoc does not file the case and does not control whether Amazon changes its record — it gives you the template and the timestamped record.
- Will a discount clear a high-value batch before it blocks?
- Shelfdoc flags the soonest-dated batch for FEFO pricing and lets you monitor velocity, but it does not guarantee a discounted high-value batch clears before its Unsellable by Date. You set the price move and review it; Shelfdoc does not set prices on Amazon's behalf without review.
- Does Shelfdoc submit the disposal for a beauty batch that will not clear?
- You choose the disposal date per MSKU; Shelfdoc submits the Disposal Request through SP-API on that date. Amazon decides acceptance and timing. Shelfdoc submits and surfaces the status — it does not control the Amazon-side outcome.
Map your beauty batches and watch your Subscribe & Save risk
Per-MSKU date mapping across restock waves. Subscribe & Save exposure monitoring. FEFO pricing on high-value batches. Date Discrepancy case templates. Scheduled Disposal Requests on the date you choose. You review every action; Amazon decides acceptance. US marketplace.
Create account