If you are researching how to change SKU in an Amazon listing, the key limitation is that Amazon does not let you rename an existing seller SKU. Create a replacement offer with the desired seller SKU against the same ASIN, then retire the old offer only after its inventory and connected systems are accounted for. For FBA, creating that replacement is not evidence that Amazon has moved the old units to it.
Amazon’s Build your inventory file documentation states: “An existing SKU cannot be changed.” This guide separates the listing change from the stock handoff, so a naming cleanup does not become stranded inventory or duplicate sellable stock.
Sources checked November 15, 2026: public US Seller Central help pages and an Amazon staff reply. No logged-in account migration was performed.
Decide Whether a New Seller SKU Is Worth the Migration
A replacement SKU solves a naming or systems-mapping problem. It is not a way to change the product itself, repair every listing error, or move inventory between fulfillment methods.
| Identifier or action | What it represents here | What the SKU migration must preserve or verify |
|---|---|---|
| Seller SKU | The identifier for your inventory/listing record | Record the old-to-new relationship; the old identifier is not edited in place |
| ASIN | The Amazon catalog product you are offering | Match the same exact product and sellable variation, not a similar search result |
| FNSKU / Amazon barcode | An FBA inventory identifier relevant to labeling and stock reconciliation | Check the actual old and new inventory records and applicable labels |
| Replacement offer | A new seller-SKU record for the existing product | Verify condition, price, fulfillment channel, and availability |
| Deleting the old SKU | Removing the old record, not renaming it | Check stock and preserve product-data contributions first |
For the broader identifier and label requirements, use the Amazon barcode requirements guide. This migration does not require you to invent a new ASIN for an unchanged product.
Keep the old SKU when the benefit is only cosmetic. If your warehouse or ERP supports a mapping between its internal item code and Amazon’s existing seller SKU, use that mapping rather than rebuilding a working offer. Confirm that capability in your own system before relying on it.
A replacement becomes useful when an integration genuinely needs a different channel SKU or your current structure creates recurring picking and reconciliation mistakes. Write down the operational problem the new code fixes. If the only answer is that the old string looks untidy, keep it—especially while FBA units are still moving through the network.
Record the Old Offer Before Changing Anything
Create a migration record before creating or deleting offers. Start with a dated catalog export; our guide to exporting Amazon listings to Excel covers the report choices. Add the inventory and integration details the catalog file does not capture.
Keep these fields together:
- Identity: marketplace, exact ASIN, old seller SKU, proposed seller SKU, condition, fulfillment channel, and FNSKU where applicable.
- Offer settings: regular price, business pricing if used, minimum/maximum repricing limits, handling settings, and relevant shipping settings.
- Inventory: merchant-fulfilled stock allocated to Amazon; for FBA, available, reserved, inbound, unfulfillable, and stranded quantities, with shipment references.
- Outstanding activity: orders awaiting fulfillment, removals in progress, open receiving discrepancies, and returns that may reappear against the old record.
- Dependencies: ERP/WMS mappings, inventory feeds, repricer rules, advertising targets, promotions, subscriptions, and any parent-child relationships that reference the SKU.
- Ownership: who changes Amazon, who changes the stock feed, who handles labels, and who signs off the final reconciliation.
Zero available units is not the same as a finished FBA transition. Check the other inventory states and shipments rather than using the available column as permission to delete. Record what will happen to later returns and inventory adjustments even if nothing is currently sellable.
Stop the migration if you cannot reconcile the physical stock to the old record, identify which integration controls quantity, or confirm the intended ASIN. Stop a parent/child-dependent migration until those references have been mapped separately; this is not a variation-restructuring tutorial.
Preserve the old contribution data as well as the visible product page. Amazon’s inventory-file documentation, checked November 15, 2026, says deleting a SKU removes both your offer and your product-data contributions for that item. A replacement offer on the same ASIN is not a backup of everything you previously submitted.
How to Change SKU in an Amazon Listing by Fulfillment Route
The listing operation is similar across routes; the inventory operation is not. Choose the branch based on where your units actually are, including units in transit.
FBM: Move the Sellable Allocation, Not a Duplicate Quantity
For stock you fulfill yourself, use a controlled cutover:
- Pause conflicting automation. Coordinate the stock feed and repricer so they cannot recreate or reactivate the old offer during the change. Preserve the old mapping for outstanding orders and reporting.
- Create the replacement offer for the same ASIN. Enter the new seller SKU, correct condition, price, and fulfillment method. Keep its sellable quantity at zero while preparing the mapping.
- Check the saved record. Confirm the new SKU points to the intended product and condition. A successful save is only a record-creation checkpoint, not the final buyability check.
- Take the old offer’s sellable quantity to zero. Confirm the change has taken effect before allocating those same units to the new offer. A short planned gap is easier to reconcile than two offers advertising the same physical stock.
- Activate the new allocation and mapping. Send only the quantity actually available after existing orders and other-channel commitments. Resume the feed against the new Amazon SKU.
- Verify the live offer and order routing. Confirm the intended seller offer is buyable and the integration recognizes the new SKU. Keep already-placed orders tied to their original records.
If quantity reappears on the old SKU, stop and find the writer: an ERP job, a feed, or a manual update. Repeatedly zeroing the quantity without fixing its source leaves the migration unstable.
For bulk work, Amazon’s inventory-file help identifies Listing Loader as the template for adding offers to products already in the catalog, as checked November 15, 2026. Use the current template instructions and review processing results. Replacing the SKU text in a spreadsheet creates a different record; it does not rename the original one.
FBA With No Units Ever Sent Under the Old SKU
Check that no shipment has used the old SKU—not just that its current available quantity is zero. In an Amazon staff response about changing an FBA SKU, Cooper_Amazon distinguishes this case: if inventory has not been sent through the fulfillment network under that SKU, the seller may create a new offer and delete the previous offer. The reply was checked November 15, 2026.
Create the replacement against the same ASIN, verify the FBA setup, and give the prep team the correct new record and labeling instructions before the first shipment. Retire the unused old record only after confirming it has no shipment or systems dependency.
Amazon’s new-SKU barcode conversion instructions, checked November 15, 2026, show Manage All Inventory → three-dot menu → Add another condition as a route to a new offer and explicitly allow the same item condition. That page addresses switching to Amazon barcodes; follow its barcode-conversion steps only when that is also your intended change.
FBA With Stock Already Sent, Stored, or Returning
Do not treat this as the FBM quantity workflow. A manually populated replacement offer does not establish that physical FBA units have been reassigned. Keep the old SKU’s stock reconciliation separate from the replacement’s setup.
Choose a route for the existing units:
- Sell through the old stock. Keep the old offer serving those units, stop replenishing it when appropriate, and track remaining inventory states and returns before retirement.
- Retrieve and rework units when needed. Plan the removal, receiving, labeling, and replacement inbound steps before closing the old offer. The FBA removal orders guide covers that separate operation. Requesting removal is not proof that every unit has left Amazon.
- Escalate an unclear association. If the old SKU, FNSKU, shipments, or stranded record do not agree, obtain case-specific guidance from Seller Support before deleting anything.
Amazon’s Resolve stranded inventory issues page, checked November 15, 2026, instructs sellers resolving a discontinued listing to create a listing with the same ASIN and SKU as the FBA inventory. That is the important boundary: a new, differently named SKU is not a universal repair for old inventory. If stock is already stranded, follow the reason-specific recovery route; see our stranded inventory guide for the wider diagnostic framework.
Verify the Replacement and Hand Off the Old SKU
Use an acceptance card rather than a single “new listing created” checkbox. The person approving deletion should be able to trace the offer, stock, and integrations without reconstructing the migration from chat messages.
| Checkpoint | Evidence to keep | Stop condition |
|---|---|---|
| Correct product | Old/new SKU mapping with marketplace, ASIN, and condition | Wrong product, variation, or condition |
| Correct offer | Saved settings and live offer check | Wrong price, fulfillment method, or availability |
| Stock ownership | Dated inventory reconciliation and shipment/removal references | Unexplained units or stock still dependent on old SKU |
| Quantity writer | Feed configuration and successful sync result | Old SKU is automatically replenished or recreated |
| Order handling | Mapping for new orders plus access to old-order records | Orders cannot be matched to the warehouse item |
| FBA labels | Confirmed barcode choice and prep instructions | Prep team is using an unverified old label |
| Retirement | Named approver and documented disposition of remaining activity | Deletion depends only on the new offer looking active |
Check campaigns and programs separately. In its barcode-switch guidance, Amazon says targeted advertising and promotions do not automatically apply to the new SKU, and old/new inventory-planning entries are separate (checked November 15, 2026). Use that documented conversion case as a prompt to inspect your own dependencies—not as a promise that every SKU migration has identical effects.
Check FBA status in the stranded inventory view as well as Manage All Inventory. Amazon’s stranded-inventory help notes that a listing can show Active in Manage inventory while appearing stranded in the more up-to-date stranded view. A green listing status alone is therefore insufficient evidence for the stock handoff.
Keep the migration map after retirement. It connects old sales, returns, and supplier records with the replacement code. Remove the old SKU from future replenishment instructions, but retain the historical identifier in your records.
Frequently Asked Questions
When Can I Delete the Old Seller SKU?
After the replacement is verified and the old record no longer needs to support inventory, shipments, outstanding activity, or connected-system references. For FBA, reconcile more than available stock. Preserve your submitted product data before deletion, and document how later returns or adjustments will be handled. If those checks are incomplete, keep the old record and defer deletion.
Can I Keep the Same ASIN When Changing the SKU?
Yes—the replacement-offer workflow here is for the same existing catalog product. Match the exact ASIN and condition. A new seller SKU does not justify switching to a different product or assuming that SKU-level settings and FBA units have transferred.
When Should I Contact Seller Support?
Contact Support before deletion when existing FBA inventory cannot be reconciled, a SKU points to an unexpected ASIN, or a stranded record does not match the offer you intend to keep. Include the marketplace, old and proposed SKUs, ASIN, FNSKU, shipment references, inventory states, and the specific outcome you need clarified. Ask how the existing units should be handled, not simply whether a SKU can be renamed.
The practical choice: keep a working SKU when a mapping solves the problem. When replacement is necessary, change the offer record deliberately—and treat the inventory handoff as its own acceptance gate.