Q4 2026: Peak storage starts 1 Oct. Peak fulfillment 15 Oct–14 Jan. Recalculate break-even ACOS before you raise bids. Operator calendar · Calculators

Services · Convertir

Catalog & Variations

You cannot harvest a child that is not indexed.

Best fit: catalogs with messy parent-child trees or ASINs that keep falling out of search

Index We do not advertise a child Amazon will not show
Tree Variations stop stealing the hero’s rank
Watch Stranded and suppressed do not wait for a QBR

Split vendors miss this because it sits between “SEO” and “ops.” Ads buy traffic. The catalog decides whether Amazon will show the page. Parent-child errors, stranded inventory, and empty backend terms are why launches stall with “the campaign is fine.”

I fix the tree on the ASINs that pay the rent — not a forensic rebuild of every forgotten SKU. Suppressions get a case or a listing edit the same week we find them.

Backend search terms are a listing job. They belong here because they are how you index without stuffing the title. I will not pack them with competitor brands.

Who this is for

Sellers whose PPC “does not work” until you notice the ASIN is suppressed, the parent is a junk drawer, or the backend is empty.

Who it is not for

A 10,000-SKU catalog rebuild as a one-week project.

How the work actually runs

01

Hero pass

Indexed? Buy Box? Stranded? On the right parent? Backend filled?

02

Fix the tree

Wrong children off the hero. New launches onto the right parent.

03

Clear blockages

Suppressed listings get an edit or a case the same week.

04

Keep watch

Catalog defects go in the log next to bids. Same desk.

What is in the workstream

  • Parent-child variation audit on heroes
  • Stranded and suppressed ASIN watch
  • Indexing check before we buy traffic
  • Backend search terms (no competitor-brand stuffing)
  • Buy Box and listing-quality flags that kill ads
  • Case notes when Amazon owes a catalog fix
  • Launch SKUs added to the right parent
  • Catalog line in the weekly log

Week one

I check hero ASINs: indexed, Buy Box, stranded, variation membership, backend terms. Anything we would have advertised into a wall gets named before week-one spend.

Every week after

Suppressed and stranded watch, variation mistakes that steal rank, backend term hygiene on ASINs we are about to spend on.

FAQ

Will you rebuild my entire catalog?

I work the ASINs we advertise and the parents they sit on. A 10,000-SKU archaeology project is a different job — I will say so on the review.

Is this listing SEO?

Listing SEO is title, bullets, and A9 copy. Catalog work is whether Amazon will show the page at all. They pair. They are not the same ticket.

Do you handle UPC / GTIN issues?

I can see them and open the case. I do not buy barcodes or file brand-owner disputes as a legal service.

Vendor Central?

Catalog trees on Seller Central live here. 1P PO shortages, ASN, and chargebacks are the Vendor Central shortages workstream — a different console.

This workstream on the free review

You do not need to hire it to find out if it belongs on the account. Send the public store link. I tell you whether this lever is leaking, whether I am the person to run it, and what week one would be.

01

The leaks I can see from the public listing

Title, bullets, A+, reviews, brand defense, and obvious ad-real-estate problems. Storefront URL only — no Seller Central login until we agree to work.

02

Whether this desk is a fit

If I cannot show the leaks, I decline. You are not added to a roster. A “no” is a complete answer, not a follow-up sequence.

03

What week one would be

Harvest, defense, listing pass, or “not yet.” Named in writing — not a 40-slide deck and a 12-month PDF.

Request a free review

Capacity is limited because I work the accounts myself. The review is how we decide if this workstream belongs on yours.

Request a free review

Related workstreams

Pedir una revisión