The catalogue that wouldn't list: what blocks a launch before it starts

A premium haircare line came into Canada with five active SKUs, a scattering of orphaned listings someone else had created, and no way to add the rest of the range. Every attempt to create a listing returned an error that looked like a formatting problem and was not.

This is the least glamorous phase of a launch and the one that decides whether there is a launch. A catalogue that will not list is a channel that does not exist, and it can sit in that state for months while everyone assumes the market is the issue.

The blockers were structural. Brand-attribute conflicts where the brand string on existing ASINs did not match the registered brand. EAN and GS1 records where the barcode prefix resolved to a different company than the one trying to list against it.

Amazon does not explain any of this. It rejects the submission. Clearing it means reconciling the GS1 record, the Brand Registry entry and the existing ASIN data until all three agree, and doing it before anyone writes a single line of listing copy.

Brand Registry enrolment first, because it is what gives you authority over the brand's ASINs and the tools to correct data someone else entered. Then variation-family architecture, because parents built wrong have to be rebuilt rather than edited. Then listings, then content.

Doing it in that order takes weeks. Doing it in any other order takes months, because every step has to be undone. The temptation is always to get listings live and fix the structure later, and the structure is what determines whether the listings can rank at all.

Once the conflicts cleared, the line went from five active SKUs to a complete catalogue across three variation families, with A+ content on every parent and a multi-page Brand Store built as the destination for brand traffic. Active catalogue up 260%.

Nothing about that is remarkable execution. It is ordinary work done in the correct sequence, which is most of what a launch is. If your Canadian catalogue has been stuck at a fraction of your US range, the reason is usually sitting in the GS1 record.