How should sellers replace an Amazon seller SKU?
Treat the change as a migration, not a rename. Freeze the old SKU’s product identity, ASIN, condition, fulfillment channel, inventory, open orders, and downstream references. Create the new SKU only after the target mapping is approved, then cut over inventory and integrations in a controlled sequence.
Amazon’s current inventory-file guidance says every product needs a unique SKU, every new SKU creates a new catalog record, and an existing SKU cannot be changed. Uploading new data for an existing SKU updates that record; it does not rename the identifier.
Build an old-to-new SKU map
- Record marketplace, old SKU, proposed new SKU, ASIN, condition, fulfillment channel, product identity, and business reason.
- List active quantity, FBA inventory, reserved units, inbound shipments, open FBM orders, returns, removal orders, and reimbursements tied to the old SKU.
- Map repricing, inventory feeds, order routing, advertising, reporting, accounting, warehouse labels, and support procedures that reference the SKU.
- Preserve source listings, reports, pricing, images, attributes, and variation relationships before creating the replacement.
- Choose an owner, cutover time, verification window, rollback conditions, and final disposition for the old offer.
- Reject any new SKU that points to a different product, condition, pack, variation child, or fulfillment assumption.
Cut over without duplicate live offers
Create and verify the new SKU against the intended ASIN and condition with zero or tightly controlled quantity. Confirm product data, price, fulfillment settings, shipping template, and downstream mapping before making it sellable. Then stop new quantity updates to the old SKU and reconcile orders already attached to it.
When the new workflow is proven, set the old offer quantity to zero or close it according to the intended outcome. Delete only after retention, inventory, orders, and dependency checks are complete. Amazon warns that deletion removes the SKU and seller-account listing information; closing retains the SKU and listing data.
Use a seller SKU migration checklist
- The old and new SKUs map to the same verified product, ASIN, condition, and intended offer.
- Inventory, inbound, reserved, order, return, removal, reimbursement, and label dependencies are reconciled.
- Feeds, apps, repricers, ads, accounting, warehouse, and reporting systems use the approved new mapping.
- The new SKU is verified with controlled quantity before the old offer is disabled.
- Open orders remain fulfilled and traceable under the SKU on which they were placed.
- Closing, zero quantity, deletion, retention, and rollback decisions are separately approved.
Scope and exceptions
SKU behavior, reuse timing, inventory transfer options, FBA relabeling, catalog contribution, and history visibility can differ by marketplace, fulfillment channel, listing state, and current Amazon workflow. A new SKU does not automatically move FBA units, open orders, advertising references, or external-system history.
Review Amazon’s current [SKU guidance](https://sellercentral.amazon.com/help/hub/reference/external/581?locale=en), [close and delete guidance](https://sellercentral.amazon.com/help/hub/reference/external/G551?locale=en-US), and live inventory status before cutover. Do not use deletion as a shortcut for product-identity or catalog-policy changes.
Related Amazon seller guides
- [Close or delete listings without leaving live offers](https://amazonmargincalculator.cloud/blog/amazon-close-delete-listing-safety-control)
- [Prevent wrong-item complaints with a condition and SKU audit](https://amazonmargincalculator.cloud/blog/amazon-product-condition-sku-audit)
- [Reconcile inventory reports before updating stock](https://amazonmargincalculator.cloud/blog/amazon-inventory-report-reconciliation-control)