A new FBA seller SKU can preserve the product's ASIN while requiring separate operating setup. Product reviews remaining visible do not prove that inventory planning, advertising, subscriptions, or bundles followed the new SKU.
This guide is for an authorized operator with an actual affected SKU and store. The US policy instructions were checked November 4, 2026. Confirm the current notification and product-specific eligibility in your account before changing an offer or sending stock.
Identify the actual barcode requirement
Read the FBA Barcode Choice and Labeling FAQ against your role and product. It distinguishes qualifying Brand Representatives, resellers, and products without an eligible manufacturer barcode. Brand enrollment alone does not establish that every product is properly linked or eligible.
Keep the ASIN, old seller SKU, barcode type, marketplace, brand role, and affected shipment dates in one change record. A GTIN, ASIN, seller SKU, and fulfillment label serve different purposes; do not substitute a made-up identifier to complete a form.
Amazon's manufacturer-barcode criteria require the applicable product and brand relationship. Where your actual SKU remains ambiguous, obtain a supported account-specific answer or hold the new shipment.
Separate old stock from new shipments
The documented policy distinguishes new shipments from qualifying inventory already stored or in transit before March 31, 2026. Do not interpret a general barcode announcement as an instruction to relabel or remove every older unit.
Build an inventory bridge before conversion:
| Record | What to capture |
|---|---|
| Old SKU available stock | Actual quantity and location/state |
| Old SKU inbound stock | Shipment reference and receipt status |
| New SKU planned units | Units not already counted elsewhere |
| Returns or unsaleable units | Separate condition and next action |
| Uncertain balance | Exact variance to investigate |
For a hypothetical case, 30 units remain under the old SKU while 50 new units are planned for the new SKU. The bridge contains 80 distinct existing or planned units, not 130 records produced by counting the same planned 50-unit shipment in both a purchasing sheet and an inbound view. Keep the 30 existing units and 50 planned units in their separate states; planned stock is not available stock.
Use the supported single-SKU route when required
Amazon's new-SKU barcode instructions describe Inventory → Manage All Inventory, finding the affected entry, and choosing Add another condition. Enter a new seller SKU and complete the required offer fields; the documented route can use the same item condition where appropriate.
In the supported conversion flow, choose Amazon barcode and complete required dangerous-goods or other information before finishing the FBA listing steps. Preserve the actual result and generated identifiers. A saved form is not proof that the offer is correctly buyable or the stock is received.
If your account exposes a different route, compare the current instructions rather than improvising a destructive shortcut. Keep the original valid operation available where supported while the new path is unresolved.
Fund and verify the labeling process
Print and apply the labels required for the actual units through your own qualified process, supplier, or prep provider. Scan-check that the readable identifier matches the intended SKU and that packaging does not obscure the required label.
Amazon's US prep policy states that FBA prep and item-labeling services ended for new US shipments from January 1, 2026. A historical fee table on that page does not make the former service an available fallback.
Budget unit handling, labels, labor, freight, and any transition review. Do not promise an automatic fee saving merely because the barcode route changed.
Rebuild the dependencies that do not automatically follow
The supported SKU-switch guidance identifies separate effects on recommendations, planning entries, targeted advertising, promotions, subscriptions, bundles, and other stores. Review what your business actually uses, rather than blindly creating every possible feature.
For each dependency, record old identifier, intended new identifier, owner, verification evidence, and any unresolved gap. Use a focused list:
- Confirm actual offer price, business pricing, and relevant discounts.
- Check each affected campaign or promotion against the intended new SKU.
- Inspect the supported subscription transfer or setup route if applicable.
- Review any virtual bundle that should include the new SKU.
- Reconcile old/new inventory planning entries and stranded units.
- Check each desired store separately.
These are different operating checks. A campaign editor accepting the SKU is not evidence that the same targeting or performance will continue.
Keep ASIN and seller-profile evidence in the correct place
Product ratings and reviews belong to the product/ASIN relationship described in the FAQ, while seller-profile feedback is another measure. Keep those separate from the new SKU's operational setup.
A hypothetical operator sees the same product reviews and concludes the transition is complete. A later check shows that a subscription and a campaign still reference only the old SKU. The review continuity answered one question while the operating dependencies remained unresolved.
Do not use historical performance to guarantee future visibility or demand. The new offer still needs actual buyability, stock, fulfillment, and customer evidence.
Accept continuity before closing anything
Compare actual stock states and offer status after the change. Confirm the specific campaign, pricing, subscription, and bundle decisions that matter. Preserve errors and the recovery action rather than hiding them in a final “complete” label.
Do not place removal orders or close old stock merely to make a checklist look tidy. Those actions have cost and operational consequences and need their own justified plan. If the transition remains uncertain, hold the affected new shipment or obtain qualified assistance.
Carry the final record into the inventory operating review and settlement reconciliation. Another operator should be able to identify the physical units, active offers, and continuing obligations without assuming that one shared ASIN transferred every dependency.

