Skip to content
Robnu
Amazon · Operations

Error 8572 when your ISBN came from the government

Indian publishers get ISBNs free from the Raja Rammohun Roy National Agency at isbn.gov.in. Amazon rejects them with error 8572 and asks for a GS1 certificate, which is a requirement the ISBN system does not have.

Free during early access · Forever free under 25 orders/day
Updated 8 October 2026

Error 8572 means the product ID does not match Amazon's brand records. For books it fires on valid government-issued Indian ISBNs, and Seller Support responds by asking for a current GS1 certificate. An ISBN is a type of GTIN in its own right, so that request is asking you to buy a credential the standard does not require. Escalate rather than buy.

TL;DR
  • 8572 means the product ID does not match Amazon's brand records, which for a book is usually wrong.
  • Indian ISBNs are issued free by isbn.gov.in, the Raja Rammohun Roy National Agency.
  • Seller Support asks for a valid, unexpired GS1 certificate, which the ISBN standard does not require.
  • Amazon's own reply acknowledges that an ISBN is a type of GTIN, which contradicts the request.
  • Sellers report two weeks of chats and calls without resolution, so escalate with the case ID early.

Error 8572 reports that the product ID does not match Amazon's brand records. For most categories that is a real signal, usually a GTIN registered to a different brand. For books listed with an Indian ISBN it fires on.

What the error actually means

Error 8572 reports that the product ID does not match Amazon's brand records. For most categories that is a real signal, usually a GTIN registered to a different brand. For books listed with an Indian ISBN it fires on identifiers that are correct and government-issued.

A seller with ISBN certificates for thirty books from isbn.gov.in hit it on every one, through both manual and bulk upload, and spent nearly two weeks on chats and calls without resolution. The first reply on the thread quoted the error back in Hindi, which is a reasonable indicator of who is affected.

The GS1 request is the part to push back on

In a sibling case Amazon demanded a valid and current, not expired, GS1 certificate. The seller objected that they were using government-allotted ISBNs. Amazon's entire answer was that an ISBN is actually a type of GTIN.

That reply is correct and it undermines the request. If an ISBN is a type of GTIN, then a valid ISBN is sufficient identification and a separate GS1 barcode licence is not required by the standard. Buying a GS1 licence to satisfy a support agent is spending money to work around a defect in Amazon's validation.

India is disproportionately exposed here because its national ISBN agency issues identifiers free, so Indian publishers are far more likely than US or UK ones to hold an ISBN without any GS1 relationship at all.

What to do instead

Open a case and include the ISBN certificate from isbn.gov.in, the specific error code, and the fact that the identifier is issued by the Government of India's national ISBN agency. Quote Amazon's own position that an ISBN is a type of GTIN back to them, because that is the sentence that makes the GS1 demand incoherent.

Keep the case ID and escalate on it rather than opening new cases, which resets the context each time. Sellers who ground down in this loop describe weeks of chats; the ones who move describe escalation on a single case reference.

Do not relist repeatedly while the case is open. A declined identifier can attach to the listing attempt, which is the same trap that makes GTIN exemptions so hard to retry.

Where this sits in the rest of your Amazon operation

Robnu is read-only on Amazon today: orders, returns, payouts and inventory sync so you can see and reconcile them, and it cannot accept Amazon orders or make their labels. Order processing is live for AJIO and Meesho. Related reading:

Sources & further reading

Not legal or tax advice. Amazon changes fees, windows and policies without notice, and several of the figures here changed during 2026. Check anything you plan to act on against your own Seller Central account or settlement report first.

Questions sellers ask

It reports that the product ID does not match Amazon's brand records. In most categories that points at a real mismatch, typically a GTIN registered to a different brand. For books listed with an Indian ISBN it fires on identifiers that are valid and government-issued, which is a validation defect rather than a problem with your data.

The ISBN standard does not require one. Amazon Seller Support has asked sellers for a valid, unexpired GS1 certificate while simultaneously acknowledging in the same exchange that an ISBN is a type of GTIN. Those two positions cannot both govern. Escalate with the ISBN certificate rather than buying a GS1 licence to work around the error.

From the Raja Rammohun Roy National Agency for ISBN at isbn.gov.in, which issues them free. That is why this problem is concentrated in India: Indian publishers routinely hold a valid ISBN with no GS1 relationship at all, where a US or UK publisher is more likely to have both.

Sellers report following up on chats and calls for almost two weeks without resolution before escalation. Keep one case ID and escalate on it rather than opening fresh cases, because each new case restarts the explanation. Amazon's own reply on one such thread was that the matter had been escalated to the relevant team for review.

No. A declined identifier can attach to the listing attempt, which is the same mechanism that makes a declined GTIN exemption so difficult to retry: the previous decision reappears and no new catalogue clears it. Leave the listing alone and work the case.

Keep reading

Related seller guides

More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.

SKU ID in Meesho: Meaning, Example, Variation ID and Product ID (2026)

SKU ID in Meesho means your own code for one product variation. Learn what SKU ID, variation ID, product ID and style code mean, with a seller SKU ID example.

Bulk Order Processing on Meesho: Ship Many Fast (2026)

How to process Meesho orders in bulk: bulk accept, bulk label, and bulk manifest as one workflow. The time math as volume grows, the error risk at scale, and how to keep the whole run correct.

Meesho Branded Packaging Code: Policy & Support 2026

Meesho's branded packaging policy lets eligible sellers ship in their own brand identity within the rules. Here is what the branded packaging code covers, who qualifies, and how it sits alongside mandatory BP-TP.

Meesho bulk label download: 100 orders labelled in minutes

Downloading Meesho labels one order at a time does not scale. Here is the batch dispatch workflow, bulk-select ready-to-ship orders, generate labels and invoices as one merged PDF, print, and manifest without touching each order.

Meesho Supplier Panel: a full walkthrough of every section

The Meesho Supplier Panel runs your whole business, orders, catalog, payments, returns, ads, support. A section-by-section walkthrough of what each does, where sellers get stuck, and what the panel does not do for you.

Bulk Invoice Download on Amazon: Generate GST Invoices at Scale

Downloading Amazon GST invoices one order at a time does not scale. Here is how bulk invoice generation works, why it matters for GST filing, and how Robnu handles it end to end.

Meesho orders stuck in pending: what it means and how to clear them

Blocked does not mean paused, the dispatch clock usually keeps running. The four causes, which two you can fix yourself, and what to document when you cannot.

Why AJIO rejects seller applications (and how to reapply)

The commonly reported reasons AJIO turns down seller applications, brand fit, catalog quality, documentation gaps, and how to build a reapplication that clears the bar.

build 8f2f63e4559ac31986a9c5987e1c67ab23d5a333 · 2026-10-08T08:32:25Z