How the Amazon Catalogue Works: ASINs, Contributions and Who Controls a Listing

The word listing suggests something a seller owns, like a classified advertisement. On Amazon a listing is a page in a catalogue, one page per product, and every seller who offers the product contributes to it. The title a seller wrote can be replaced by another seller's, or by Amazon's own systems, and the seller who wrote it finds out when the page changes. Most catalogue confusion, and most of the support cases about it, comes from that one fact.

This is how the catalogue works: what an ASIN is, how a page is built from contributions, why a new offer lands on an existing page, how the brand owner comes to control the page, and what to do when it is wrong.

On Amazon a listing is not a seller's own page. Each product has one page, identified by one ASIN, and every seller of the product sells on it. A new offer is matched to the existing page by its product identifier, the GTIN or UPC on the barcode, and a second page for the same product is a duplicate that Amazon merges or removes.

What the page shows is built from contributions. Every seller can submit a title, bullets, images and other attributes, Amazon keeps them all, and for each attribute it shows the one it trusts most: a brand owner's over a reseller's, data matching the manufacturer's over data that does not, and its own systems' where a field is empty or disputed. That is why a title can change without anyone at the brand touching it.

Brand Registry is how a brand controls the page. Enrolled, with the selling account as owner or authorised representative, the brand's contributions take priority, it can report listings that misrepresent the product, and it can limit who sells on its ASINs.

When the page is wrong, compare the live page with the account's own contributions to find the attribute in dispute. A brand owner confirms the Brand Registry role and submits the value again; a reseller files a case with the manufacturer's data; and nobody deletes and recreates the offer, which changes nothing on the page and resets the seller's history on it.

Checked monthly, attribute by attribute, the catalogue stops surprising anyone: every difference between the live page and the account's contributions has a contributor, and finding it is the first step to fixing it.

Amazon's catalogue rule is that each product has exactly one page, identified by an ASIN, and every seller of that product sells on that page. A seller creating a listing for a product that already exists is not creating a page; the catalogue matches the product identifier, the GTIN or UPC on the barcode, to the existing ASIN and adds the seller's offer to it. Creating a second page for the same product is a duplicate listing, which Amazon merges or removes, and the seller who created it loses the work. The adding keywords article assumes the page is yours to edit; this article is about when it is not.

The identifier is what makes the match, which is why a product without one, or with one that belongs to something else, causes trouble: a wrong GTIN attaches a seller's offer to somebody else's product page, and the customer receives the wrong thing.

A product sold in several sizes or colours is not one ASIN but a family of them, and the family has its own rules.

The parent is not for sale. A family has a parent ASIN that groups it and a child ASIN for each version a customer can buy. The parent carries the shared page; the children carry the price, the stock and the attributes that make each version different.

The variation theme. Each category allows certain ways of varying: size, colour, size and colour together, count, flavour and others. The theme decides how the choices appear on the page, and a family can only vary in the ways its category allows.

Reviews are shared. Customer reviews are shown across the family, which is why a family is valuable and why sellers are tempted to abuse it. Grouping products that are not genuinely versions of one another, to borrow another product's reviews, breaks Amazon's variation policy and is a common reason for a family to be split by Amazon.

Changing a family. Adding a child, removing one or regrouping a family is done through the listing tools or a file for the brand's own products, and through Seller Support or the brand's support team where the family was built by somebody else. A brand owner's request carries the most weight, for the same reason its contributions do.

Check each family's children after any catalogue change. An orphaned child, sitting on a page of its own, loses the family's reviews and is easy to miss.

Every seller on an ASIN can submit values for its attributes: the title, the bullets, the description, the images, the brand, the dimensions. Amazon stores all of them as contributions and shows, for each attribute, the one it trusts most. Trust is decided by rules rather than by who was first: a brand owner's contribution outranks a reseller's; a contribution that matches the manufacturer's data outranks one that does not; a contribution flagged by customers loses; and Amazon's own systems, which fill attributes from the manufacturer or from images, can outrank everybody where a field is empty or contested.

That is why a title changes under a seller. Another seller contributed a different title, or Amazon's systems did, and the contribution won. The seller's own contribution is still stored; it is simply not the one shown. A seller who edits the title back is contributing again, and if nothing has changed in the trust order, the edit loses again, silently.

Brand Registry is the mechanism. A brand enrolled in Brand Registry, with the selling account listed as its owner or an authorised representative, has its contributions to its own products' pages given the highest trust. In practice the brand owner's title, bullets, images and A+ content hold, and a reseller's contributions do not displace them. The brand owner can also report a listing that misrepresents the product, and can restrict who may sell on its ASINs at all.

For a brand that is not enrolled, every seller on its pages is an equal contributor and the page is whatever the trust rules produce that week. That is the most common reason a manufacturer's own listing carries a reseller's photograph of the product in its packaging. The enrolment is the work of our Brand Registry service for the brands we run, and what a reseller may do on a brand's page at all is the subject of the reselling article.

Not every change to a page comes from another seller. Amazon contributes to its catalogue too, and in 2026 its own changes became much more common.

Corrections from Amazon's data. Amazon updates attributes it believes are wrong, from customer feedback, from returns and from its own measurements. A product's weight or dimensions in the catalogue can change after Amazon measures it, which also changes the fees it is charged.

Title rewrites. Since 27 July 2026, titles outside media are limited to 75 characters, and Amazon has said titles still over the limit are replaced with recommendations its own tools write, gradually. A seller who did not shorten a title will find Amazon's version on the page.

The brand owner's window. Amazon's announcement gives brand owners 14 days to review, modify and approve those recommendations before they take effect, in the Review Listing Changes section of Seller Central. Somebody has to read that queue; fourteen days passes quickly when nobody does.

What to do about it. Read the account's listing changes weekly, accept what is right, correct what is not with evidence, and write the 75 character titles before Amazon does. The detail on the title change is in Amazon's 75 character title limit and Item Highlights.

First find out whose contribution is showing. The listing's attributes in Seller Central show what the account contributed; the live page shows what won; the difference is the contested attribute. For a brand owner, the fix is to confirm the Brand Registry role on the account and submit the correct value again, which then holds. For a reseller on a brand's page, the fix is a case to Seller Support with evidence, the manufacturer's own data or images, because a reseller cannot outrank the brand and Amazon's systems by contributing harder.

For an attribute Amazon's own systems changed, the case is the same, and it is the slowest kind. The Seller Support cases article is how to write it so it is read. What never works is deleting the offer and recreating it, which changes nothing about the page and resets the seller's history on it.

One product, one ASIN is the rule, and duplicates are how it breaks: two pages for the same product, each with part of the reviews, the rank and the offers.

How duplicates appear. A seller lists the product with a different barcode, or none, and creates a new page instead of joining the existing one. A brand relaunches with new packaging and a new barcode for a product that has not changed. A supplier feed creates its own page alongside the brand's.

Why they cost. Reviews, sales history and rank are split between the pages, so neither ranks as well as one would. Customers comparing offers see fewer of them on each page. And creating a duplicate page knowingly is against Amazon's policies, which puts the account that made it at risk.

Getting them merged. The brand owner, through its brand support, or a seller through Seller Support, can ask for the duplicate pages to be merged, giving every ASIN involved and the evidence that they are the same product: matching packaging, identical specifications, the same manufacturer part number. Merges take time and are not guaranteed, so the case has to be clear.

Preventing them. Search the catalogue by barcode and brand before creating any page, keep one barcode per product across every change of packaging that does not change the product, and check new supplier listings against the existing catalogue before they go live.

The catalogue is built the way it is so that a customer searching for a product finds one page with every offer on it, and the rules that frustrate sellers are the rules that make that true. A seller who works with it registers the brand, uses the right identifiers, contributes complete and accurate data, and reads the live page rather than the edit form. A seller who works against it creates duplicates, fights the trust order by re-editing, and files cases that ask Amazon to prefer a contribution over its rules.

For the brands we run, the catalogue is checked monthly: the live page against the account's contributions, attribute by attribute, and any difference traced to its contributor. It is dull work and it is the difference between a page a brand controls and a page it visits.