Amerify  ·  Walkee Paws V2.0

How we recommend launching V2.0

Answering your questions on reusing ASINs, barcodes and reviews, and setting out the approach we would take.

Prepared for Lisa, Walkee Paws Prepared by Amerify July 2026

The short answer

Launch V2.0 clean, on new barcodes and a new ASIN, and do not attach it to the old listings.

There are two reasons, and the second is the one that decides it. First, the reviews you would inherit would lower your starting rating rather than raise it. Second, a new listing gets an early visibility window from Amazon that only applies to a product with no history, and reusing an old barcode or ASIN gives that up.

You can inherit the old reviews, or you can have the launch window. You cannot have both. We think the launch window is worth considerably more.

Your questions

Taking them in the order you raised them.

Can we attach V2.0 to any of the old ASINs to keep the reviews?

We would not recommend it. Amazon's process for combining listings is built for two pages showing the same product, and V2.0 is a genuinely new one. Even where it can be done, it tends to be slow, uncertain, and reversible only with difficulty.

The more practical point is that the reviews would not do what you are hoping. See the rating question below.

Do we need to use the same barcodes on the new SKUs?

No. A new product should carry its own GS1 barcode, and the fact that your V2.0 SKUs and barcodes are not yet assigned is good timing. It means we can set them up cleanly from the start rather than correcting them later.

Changing a barcode on an existing product is one of the more difficult operations on Amazon. It requires a duplicate listing, an Amazon-side merge, GS1 certificates and supporting imagery, and it often takes several attempts.

One thing worth checking separately: your current catalog uses five different barcode prefixes. Amazon removes listings whose barcode is not owned by the brand or not GS1 certified, so it is worth confirming which prefixes are licensed to Walkee Paws before the new ones are assigned.

Should we carry over only the SKUs rated 3.7 stars and above?

We modelled this, and it does not reach the rating you are aiming for.

ApproachReviews carriedResulting rating
Whole catalog2,6933.48★
Only SKUs at 3.7★ and above5143.74★
Black only, which is what V2.0 is5703.37★
Clean listing with Amazon Vineup to 30 on day onearound 4.1★ typical

Two things stand out. Nearly 70% of the 3.7-and-above group comes from a single listing, so it is effectively reusing one ASIN rather than a portfolio. And because V2.0 launches in black, matching product to product would mean inheriting your weakest colour line at 3.37★.

Industry research consistently finds the 3.5 to 4.5 range is where buyer confidence shifts most, so the gap between starting in the 3.3 to 3.7 band and starting around 4.1 is meaningful.

Is there a risk to inheriting the old reviews?

Yes, and it is worth being direct about it. The reviews carry the criticism as well as the praise. The most common theme across your current reviews is boots not staying on, which is precisely the problem V2.0 was designed to solve. Amazon tends to give prominence to detailed critical reviews, so that objection would appear near the top of the new product's page.

In other words, you would be importing the very complaint the new design resolves.

Can we simply add the old SKUs under a new V2.0 parent?

It is possible, but we would advise against it for a practical commercial reason. You plan to discount the old stock to clear it. If old and new sit in the same family, the clearance items appear as selectable options on the V2.0 page, at a lower price, competing directly with the product you are trying to establish.

Keeping them separate lets you clear old stock without it undercutting the launch.

The deciding factor

This is the point we would most want to land.

New listings receive an early visibility window that established listings do not. It applies only to an ASIN with no sales history, and a product only gets it once.

Reusing an old barcode matches the new product onto the old ASIN, which already has years of history behind it. That forfeits the window entirely.

So the choice is genuinely either or. Given that inheriting would also start you at a lower rating than launching clean, the case for a fresh listing is strong on both counts.

The approach we recommend

Sequenced so each step supports the next.

  1. New barcodes, new SKUs, new listing

    Fresh GS1 barcodes and a clean ASIN for V2.0, with the SKU naming convention agreed before anything is uploaded, as SKUs cannot be renamed later.

  2. Enrol in Amazon Vine before launch

    Vine places your product with Amazon's own reviewer programme and can put up to 30 genuine reviews on the page for day one. It requires Brand Registry, FBA inventory received, and your written approval. A clean listing qualifies, whereas one carrying inherited reviews may not.

  3. Complete the listing before it goes on sale

    Title, images, A+ content and Brand Story all finished and inventory received before the product becomes buyable, so the visibility window is not spent on an unfinished page.

  4. Launch with advertising ready to switch on

    Campaigns built in advance and activated at go-live, so early traffic and sales arrive while the window is open.

  5. Cross-promote from the existing listings

    Rather than merging them, we point them at V2.0: an A+ comparison chart showing old against new, Brand Story and Brand Store placements, and advertising on your own existing listings so current traffic finds the new product. Your old listings become a route into V2.0 rather than a liability.

  6. Build reviews steadily after launch

    Ongoing review requests through Amazon's own approved channels, so the rating grows on its own foundation.

Also available if you would like it. We run an internal launch programme covering giveaways and product seeding to build early sales momentum in the first weeks. It is optional, and we are happy to walk you through how it would work alongside the plan above.

One to confirm. In some categories Amazon can surface a "newer version available" link on an older listing. We will check whether that is available in your category and come back to you, rather than assume it.

On timing

Two things worth raising before the December date is fixed.

The category peaks in February, with December second. Demand in your niche is sharply seasonal and February is the single largest month of the year. A mid-December launch means arriving at peak season with a brand new listing, and it also means we would not want to defer review building to February, since that is when you most need the rating working for you.

Vine needs lead time. Reviewers have to order, receive, use and then write. For reviews to be on the page at launch, inventory needs to be received and Vine enrolled well ahead of the launch date. This is the constraint most likely to affect the schedule, so it is worth fixing the inventory date early.

We would also suggest sequencing the clearance of old stock separately from the V2.0 launch, so the two are not discounting against each other in the same weeks.

What we need from you