When does an FBA seller need to create a new MSKU?

Any time you ship a new batch of inventory that has a materially different expiration date from your existing batches. The per-MSKU model only works if each MSKU represents one expiration batch — sharing an MSKU across two batches with different dates merges them into the same FBA inventory line, which means Amazon can't distinguish them at fulfillment, FEFO pricing breaks, and Disposal Requests fire against the wrong inventory.

What MSKU naming convention should I use?

Pick a convention that encodes the information you'll need at a glance. Common patterns include a product abbreviation + a date or quarter + a lot identifier — for example COFFEE-Q126-LOT44 or VIT-2026-03-A. The exact format doesn't matter; consistency does. Once you commit to a pattern, every new MSKU should follow it so the dashboard sorts predictably.

Can I change the expiration date on an existing MSKU?

The expiration date is stored per inbound shipment, not on the MSKU itself. You can update the shipping plan's declared expiration date for a future inbound. For units already in FBA, Amazon's stored value can sometimes be corrected through a Seller Support case if it was wrong at receiving — the outcome depends on the supporting documentation. The safe pattern is to ship the next batch under a new MSKU instead of trying to update an existing one.

Should I use Add a Product or bulk inventory file upload?

Add a Product is faster for one or two new MSKUs and walks you through every field. Bulk inventory file (FlatFile) is the right call when you're creating five or more new MSKUs at once — for example when you receive a quarterly shipment with multiple lots. Mixing the two within a single inbound plan is fine. The MSKUs are equivalent once created either way.

When does the new MSKU get its FNSKU barcode?

Amazon assigns the FNSKU at MSKU creation. You can download it immediately from Inventory → Manage FBA Inventory → click the MSKU → Print Item Labels. The FNSKU is what gets physically printed on each unit going to FBA; the same FNSKU stays with the MSKU for as long as the MSKU exists.

How long does it take Amazon to activate a new MSKU?

For a new MSKU under an existing ASIN, the listing is typically active within minutes to a few hours. For a new MSKU under a new ASIN (a new product), activation takes longer and may require category-specific approval. The expiration-tracking workflow only depends on MSKUs under existing ASINs, so the typical waiting period is short.

How to Create a New MSKU in Amazon Seller Central

Short version

For Amazon FBA sellers managing expiration-dated inventory, every new batch with a materially different expiration date should get its own MSKU. Create the MSKU in Seller Central through either Add a Product (fast for one or two) or a bulk inventory file (FlatFile) upload (right call for five or more). Amazon assigns the FNSKU barcode at creation; you print labels from Manage FBA Inventory and ship under the new MSKU with the correct expiration date in the inbound plan.

Why a new MSKU per expiration batch

Amazon's FBA inventory record is tracked at the MSKU level. If two batches with different expiration dates share an MSKU, Amazon can't distinguish them at fulfillment — they're interchangeable inventory. The downstream consequences are concrete:

Disposal Requests fire against the wrong inventory. Scheduling a Disposal Request for the soonest-expiring batch ends up clearing units from both batches.
FEFO pricing breaks. Per-MSKU price updates can't target the soonest-expiring batch when the batches share the MSKU.
Subscribe & Save subscriptions get attached to whichever batch Amazon picks at fulfillment, with no way to control which one.
The audit trail loses batch boundaries. When a Seller Support case asks “which batch was disposed,” the answer is ambiguous.

The setup cost is real — creating a new MSKU adds a few minutes per batch. The operational payback is large. See FNSKU and MSKU expiration date tracking for the underlying model.

Two paths in Seller Central

Amazon provides two routes for creating MSKUs. They produce equivalent MSKUs; the difference is interface and bulk speed.

Add a Product — a guided form. Faster for one or two new MSKUs.
Bulk inventory file (FlatFile) — a spreadsheet upload. Faster for five or more new MSKUs.

Below: both paths walked through.

Path 1 — Add a Product

Open Catalog → Add a Product in Seller Central.
Search for your existing product. You're creating a new MSKU under an existing ASIN, so the ASIN already exists.
Click I have an offer for this product next to the matching catalog result.
On the offer page, set the Seller SKU field to your new MSKU per your naming convention (e.g. VIT-2026Q2-LOT81).
Fill in price and condition. Set Fulfilled by Amazon.
Save. Amazon assigns the FNSKU barcode automatically.
Go to Inventory → Manage FBA Inventory, find your new MSKU, click Print Item Labels, and download the FNSKU label PDF.
Print the FNSKU labels and ship the new batch under this MSKU.

Time: about 3-5 minutes per MSKU once you've done it once or twice.

Path 2 — Bulk inventory file

Open Inventory → Inventory Reports in Seller Central.
Download the appropriate Add Products via Upload template for your product category (food, beauty, supplements, etc.). The template name is something like Inventory Loader or category-specific (e.g. Food & Beverage Flat File).
Open the downloaded file. Fill in one row per new MSKU:
- sku — your new MSKU.
- product-id — the ASIN you're creating a new offer against.
- product-id-type — ASIN.
- price — your offer price.
- quantity — leave blank for FBA inventory (Amazon will set it at receiving).
- fulfillment-center-id — AMAZON_NA (or the equivalent for your marketplace).
Save as a tab-delimited .txt file.
Open Inventory → Add Products via Upload → Upload your inventory file and upload the file.
Wait for processing (usually a few minutes). Check the upload status for errors and resolve any.
Once processed, each new MSKU has an FNSKU assigned. Print labels from Manage FBA Inventory the same way as Path 1.

Time: about 15-20 minutes for the first 10-20 MSKUs (including learning curve). Faster on subsequent batches.

Linking the new MSKU to a shipping plan

The MSKU itself doesn't carry an expiration date. The expiration date is declared per shipping plan — meaning each time you send inventory under that MSKU to FBA, you declare the case-pack expiration date in the shipping plan. Amazon stores that date for the units received as part of that inbound.

Practical implication: if you ship the same MSKU twice with different expiration dates, you've violated the one-MSKU-per-batch rule. Create a new MSKU for the second shipment. This is the discipline the operator carries every time a new batch arrives.

Common mistakes

Reusing the same MSKU across batches with different expiration dates. The single most common cause of broken per-MSKU expiration tracking. The fix is to create a new MSKU before the next shipping plan goes out.
Inconsistent MSKU naming. Mixing VIT-Q1-LOT44 with vit_2026_lot_44 with vitamin-2026Q1-44 makes the dashboard sort chaotically. Pick a pattern and enforce it.
Printing the wrong FNSKU on units. If you mix up FNSKUs across MSKUs at the print step, Amazon receives the units under the wrong MSKU. The remedy is a Seller Support case with the inbound paperwork; outcomes vary.
Forgetting to set the expiration date in the shipping plan. Without an expiration date declared, Amazon may not record one — which means no Unsellable by Date calculation downstream.

How Shelfdoc helps once the MSKU is created

The Unmapped page surfaces every new MSKU Amazon shows in your FBA inventory. The seller maps each new MSKU to an expiration date and an Unsellable by Date.
Per-MSKU date mapping is exactly the unit-of-work model the dashboard runs on — every scheduled Disposal Request, every FEFO pricing rotation, and every Subscribe & Save migration prompt fires per MSKU.
The Audit Log records the date the MSKU was first mapped, every subsequent edit, and every action Shelfdoc submitted to Amazon — exportable for Seller Support cases and accounting reconciliation.

What Shelfdoc does not do

Shelfdoc does not create MSKUs in Seller Central. MSKU creation is a seller action inside Amazon's interface.
Shelfdoc does not print FNSKU labels. The labels come from Amazon's Manage FBA Inventory tool.
Shelfdoc does not file Seller Support cases on the seller's behalf when an FNSKU mislabel happens. It produces the audit-trail evidence; the case is the seller's.

FNSKU and MSKU expiration date tracking — the underlying per-MSKU model.
Amazon FBA expiration date management — the workflow the new MSKU plugs into.
Amazon FBA Unsellable by Date — the date you'll map to each new MSKU.
Amazon FBA expiration date SOP — the full operator playbook.
Expiration date glossary.
Resources hub — every guide, glossary entry, calculator, and decision framework, organized by topic.

Frequently asked questions

When does an FBA seller need to create a new MSKU?: Any time you ship a new batch of inventory that has a materially different expiration date from your existing batches. The per-MSKU model only works if each MSKU represents one expiration batch — sharing an MSKU across two batches with different dates merges them into the same FBA inventory line, which means Amazon can't distinguish them at fulfillment, FEFO pricing breaks, and Disposal Requests fire against the wrong inventory.
What MSKU naming convention should I use?: Pick a convention that encodes the information you'll need at a glance. Common patterns include a product abbreviation + a date or quarter + a lot identifier — for example COFFEE-Q126-LOT44 or VIT-2026-03-A. The exact format doesn't matter; consistency does. Once you commit to a pattern, every new MSKU should follow it so the dashboard sorts predictably.
Can I change the expiration date on an existing MSKU?: The expiration date is stored per inbound shipment, not on the MSKU itself. You can update the shipping plan's declared expiration date for a future inbound. For units already in FBA, Amazon's stored value can sometimes be corrected through a Seller Support case if it was wrong at receiving — the outcome depends on the supporting documentation. The safe pattern is to ship the next batch under a new MSKU instead of trying to update an existing one.
Should I use Add a Product or bulk inventory file upload?: Add a Product is faster for one or two new MSKUs and walks you through every field. Bulk inventory file (FlatFile) is the right call when you're creating five or more new MSKUs at once — for example when you receive a quarterly shipment with multiple lots. Mixing the two within a single inbound plan is fine. The MSKUs are equivalent once created either way.
When does the new MSKU get its FNSKU barcode?: Amazon assigns the FNSKU at MSKU creation. You can download it immediately from Inventory → Manage FBA Inventory → click the MSKU → Print Item Labels. The FNSKU is what gets physically printed on each unit going to FBA; the same FNSKU stays with the MSKU for as long as the MSKU exists.
How long does it take Amazon to activate a new MSKU?: For a new MSKU under an existing ASIN, the listing is typically active within minutes to a few hours. For a new MSKU under a new ASIN (a new product), activation takes longer and may require category-specific approval. The expiration-tracking workflow only depends on MSKUs under existing ASINs, so the typical waiting period is short.

Map your new MSKU before the first sale

Once Amazon receives the batch and the MSKU shows up in inventory, map it in Shelfdoc with the expiration date and the Unsellable by Date you want to manage against. Scheduled Disposal Requests, FEFO pricing, and Subscribe & Save monitoring all key off the mapped date.

Create account