Deleting an ASIN/SKU (and starting clean).

Sometimes a listing is too broken to fix in place. The wrong category at creation locked the wrong attribute schema and Amazon refuses to re-categorise. The wrong GTIN at attach pulled in the wrong canonical product family and the parent-child structure grew the wrong way. A persistent hijack polluted the review base with reviews of an unrelated counterfeit product. A failed launch left the ASIN sitting at a 3.2-star rating with 40 negative reviews that cannot be diluted by any reasonable volume of new reviews. In these cases, deleting and recreating is a real option — but it has real trade-offs, a 60–90 day waiting period that punishes impatience, and an SKU-vs-ASIN distinction Amazon enforces strictly.

SKU vs ASIN — Amazon's distinction

The first thing to internalise: SKUs and ASINs are different things, owned by different parties, with very different deletion semantics.

• SKU. Your own internal identifier for an offer. You created it; you can delete it freely. Closing or deleting a SKU just stops your offer — Amazon does not care, because the ASIN-level catalogue record is unaffected. Other sellers can still offer the ASIN. Deleting a SKU does not delete the underlying ASIN.
• ASIN. Amazon's catalogue-level identifier for a product. Amazon owns it. You can request ASIN deletion, but the request is honoured only when no seller has had inventory against the ASIN within the recent past, no reviews exist, and you are the legitimate brand owner or GTIN registrant. ASIN deletion requests on listings with sales history are routinely refused.

The practical implication: most "delete and recreate" decisions in real catalogues are SKU deletions paired with a new SKU on a new ASIN — leaving the old broken ASIN orphaned in Amazon's catalogue rather than truly deleted. The old ASIN may still be findable by direct URL for months or years, but with no inventory and no live offer.

When delete-and-recreate is the right move

• Wrong primary browse category that Amazon refuses to change (covered in Episode 08's one-shot pattern).
• Wrong GTIN locked the wrong attribute schema — the ASIN can't be edited into the correct attribute fields because Amazon's catalogue layer expects a different shape.
• Hijacked or polluted reviews from a counterfeit period or from variation-family contamination, where the review base is so misaligned that it actively misrepresents the current product.
• Parent-child structure grew the wrong way — variation theme picked incorrectly at creation, can't be restructured in place, and the family's review-aggregation behaviour is hurting the strongest children.
• Failed launch with persistent 3.0–3.5 star rating on a SKU that has since been materially improved (formula reformulated, hardware revision, packaging upgrade). The underlying product is now better, but the existing reviews anchor the rating below the buyability threshold and no realistic volume of new reviews will recover it within 12 months.
• Brand transition or rebrand where the old ASIN's brand name no longer matches the trademark on the new packaging.
• Suppressed ASIN that cannot be re-validated after multiple Seller Support escalations — sometimes the cleanest path is to restart on a fresh ASIN.

When delete-and-recreate is the wrong move

• The listing converts acceptably and the rating is above 4.0. Fix the specific issue in place; the cost of starting over outweighs the marginal lift.
• You don't own the brand. Resellers cannot meaningfully recreate an ASIN they don't have catalogue-control over.
• The listing has strong ad-campaign history. Sponsored Products algorithms use historical performance to set bid recommendations; a fresh ASIN starts with no signal and ad efficiency drops measurably for the first 30–60 days.
• You're in a peak season. Never recreate during Q4, Prime Day, or category-specific peaks — the catalogue propagation, ad-history reset, and review-cold-start combine to nuke peak-season revenue.

The 60–90 day rule

When you do delete and recreate, give the old ASIN at least 60–90 days to fall out of Amazon's catalogue caches, search indexes, and recommendation pipelines before you publish the new ASIN with the same GTIN. Recreate too quickly and Amazon's catalogue dedup layer may detect the GTIN match against the still-warm old ASIN and either merge the new submission back into the old one (you wanted to start fresh; you got the old listing back) or reject the new submission as a duplicate. The 60–90 day window is observed behaviour rather than published policy, but it is consistent across categories and worth respecting.

The operational sequence:

1. Day 0: close all SKUs against the old ASIN. Allow current FBA inventory to drain (sell-through, return, or remove).
2. Day 1–60: the old ASIN sits dormant. Sponsored ad campaigns referencing the ASIN stop firing. Organic rank decays.
3. Day 60–90: wait. Resist the temptation to recreate early.
4. Day 90+: create the new ASIN with the corrected category, GTIN handling, parent-child structure, or whatever the original failure was.
5. Day 90 onward: ad campaigns, Vine enrolment, Brand Registry assignment, and review-velocity rebuilding all start from zero on the new ASIN.

What you lose

• All reviews and ratings. The new ASIN starts at zero reviews. This is the largest loss — depending on category, 90+ days of Vine plus Request-a-Review work are needed to rebuild a baseline.
• All organic rank and BSR history. The ranking algorithm has no historical signal on the new ASIN. Expect 60–120 days to rebuild organic ranking comparable to the old listing.
• All review-velocity signals to the ranking model. A fresh ASIN is a cold-start problem.
• All inbound links, sponsored-ad performance history, and Amazon-internal recommendation signals that pointed to the old ASIN.
• The Buy Box history on attached listings — every offer on the new ASIN starts from scratch in the Buy Box auction.

What you keep

• Brand-level history with Amazon — your seller-health metrics, account standing, Brand Registry enrolment, and ad-account history are all account-level rather than ASIN-level.
• The right to use the same GTIN on the new ASIN (the original failure aside — if the GTIN itself was the problem, you need a new one).
• The cleanly structured listing you couldn't get otherwise. The right category, the correct attribute schema, the variation family you should have built the first time, the brand-name match with your current trademark.
• All A+ Content and Brand Store assets — A+ documents are reusable across ASINs, so the work invested in A+ on the old ASIN can re-attach to the new one immediately.
• The lessons from the first launch — keyword research, photography, copy work. None of that has to be redone.

The bridge strategy — running both ASINs in parallel

For SKUs with material existing revenue, a fully serial delete-and-recreate kills 60–90 days of sales. The alternative for some scenarios: launch the new ASIN as a fresh SKU while the old one is still live, gradually shift advertising and external traffic to the new ASIN over 30–60 days, then close the old SKU once the new one is established. This avoids the dead period but only works when the old and new ASINs are distinct products in Amazon's eyes (different GTIN, different sufficient attribute differences) rather than literally the same SKU in a new wrapper. Walking this line requires care to avoid triggering Amazon's duplicate-listing detection.

The recreation checklist

• Browse category re-picked using the Episode 08 method, with three competitor breadcrumbs validating the choice.
• GTIN handling confirmed (Episode 05 if exempt, new GS1 code if the old GTIN was the root cause).
• Brand Registry attachment ready — the new ASIN inherits Brand Registry the moment it goes live if the brand and category are covered.
• Photography, copy, A+ Content, and video assets all ready to deploy on day one — there is no excuse for shipping a thin listing on a recreated ASIN.
• Vine enrolment queued for the new ASIN immediately on launch.
• Advertising plan in place to seed the cold-start (30–60 days of higher-than-normal ad spend to bridge the missing organic signal).
• Documentation: keep an internal record of the old ASIN, the reason for the delete-recreate, and the date the new ASIN went live — useful for Amazon Support cases and for your own future audits.

Seller vs Vendor — the recreate flow differs

Sellers self-service the SKU close and new SKU creation as described. Vendors do not — Vendor ASIN deletions and recreations run through the NIS workflow and require Vendor Manager involvement, with longer turnarounds (often weeks rather than days). Vendor recreates are also less common because the Vendor relationship gives Amazon Retail more latitude to clean up broken ASINs in-place through catalogue-team work, without a full delete.

What to take into the next episode

The recovery path closed, the next episode steps from single-marketplace operations into multi-marketplace work — translation workflows, per-marketplace Style Guide differences, the Build International Listings tool, and the silent-overwrite trap that catches most cross-marketplace teams at least once.