Amazon Transparency Program: Stop Fakes at the Unit
Transparency puts a unique code on every unit you make. Scanned at fulfilment, it separates your real stock from counterfeits before a fake ever reaches a customer. Here is how it works and when it earns its keep.
- Transparency verifies individual units with a unique code; Brand Registry protects your listing and brand rights. They are separate layers.
- The real cost is not the per-code fee. It is the labelling discipline across every unit and every production run.
- It pays off in counterfeit-hit categories. For a low-risk private label with clean listings, it is often overkill.
Counterfeits do not announce themselves. A customer buys what looks like your product, it fails, and the one-star review lands on your listing. Your brand pays for someone else’s fake. The Amazon Transparency Program exists to break that chain at the unit level, before a counterfeit ever ships as if it were yours.
What Transparency actually is
Transparency is a unit-level authentication service. Every individual unit of an enrolled product carries a unique code, usually a 2D barcode. When that unit moves through an Amazon fulfilment centre, the code is scanned and checked. A unit with a valid, unused code is genuine and ships. A unit with a missing, duplicate or invalid code gets stopped.
This is different from a batch code or an MRP sticker. It is one distinct code per physical unit. That granularity is what lets Amazon separate your real stock from a fake that copied your packaging.
How it differs from Brand Registry
People confuse the two because both live under brand protection. They solve different problems.
| Layer | What it protects | Where it acts |
|---|---|---|
| Brand Registry | Your brand rights and listing content | Listing level, the PDP and catalog |
| Transparency | Individual physical units | Unit level, at fulfilment and in the buyer’s hand |
Brand Registry is your foundation. It gives you a registered trademark on record, better control of your listing, and tools to report infringement. It does not inspect the physical unit. Transparency does. A hijacker editing your PDP is a Brand Registry matter. A counterfeit unit slipping into inventory is a Transparency matter. Serious brands run both.
Enrolment and the label workflow
The sequence is straightforward on paper.
- Hold an active Brand Registry enrolment with your trademark.
- Apply Transparency to the specific ASINs that need it. You do not have to enrol your whole catalog audit list at once.
- Provide product details and GTIN mapping so Amazon can generate codes tied to the right ASIN.
- Order or generate the Transparency codes for your production quantity.
- Apply one code to every sellable unit, either at the factory, at a prep centre, or in your own warehouse.
That fifth step is the whole game. The code has to physically reach every unit. Most brands fold it into the manufacturing or packaging line so the label is printed and applied during production. Doing it manually after the fact works for small runs, but it does not scale and it invites errors.
The cost per code, in plain terms
Amazon charges a per-code fee. It is small on a single unit, and it can change by region and over time, so treat it as a live variable and check the current terms in Seller Central. The fee itself is rarely the deciding factor. The bigger cost is operational: the labelling step, the reconciliation between codes generated and units produced, and the discipline to never ship an enrolled unit without a valid code.
Model it as cost per unit plus labour per unit, not as a one-time subscription. On a high-value item the per-code fee disappears into the margin. On a thin-margin fast mover across a large SKU count, the labour side is what you plan for.
Which brands actually need it
Transparency earns its place in categories where counterfeiting is common and the downside is real. Think supplements, beauty, electronics accessories, batteries, auto parts, and anything where a fake can be dangerous or where your brand has already been copied. If you have found counterfeit units, or your reviews carry complaints about products you know you did not make, that is your signal.
It also helps brands entering a category with known fakes, where getting ahead of the problem is cheaper than cleaning it up later. If counterfeits already dent your return rate or drag your account health through bad feedback, unit-level verification is a direct answer.
The operational load, honestly
Transparency is not a switch you flip. It is a process you run every production cycle. Codes have to be generated for each batch, applied to each unit, and reconciled so you never over-ship or under-code. A missed label means a unit that cannot pass fulfilment, which becomes stranded stock and lost sales. Coordinating this across factories, prep centres and fulfilment needs an owner and a checklist, not good intentions. This is exactly the kind of standing process our Amazon India Account Management team builds into a brand’s monthly operating rhythm so it does not slip.
When it is overkill
Not every brand needs Transparency. If you sell a private label in a low-counterfeit category, control your own supply chain end to end, and have seen no fakes, the added labelling burden buys you little. The same is true very early, when volumes are tiny and your attention is better spent on listings, Buy Box readiness and reviews. Adopt Transparency when the counterfeit risk is real, not as a reflex. Protection you do not need is just cost and friction.
Deciding in one sitting
Ask three questions. Have you seen counterfeit units of your product, or is your category known for them? Can you apply a unique code to every unit without breaking your production flow? Is the brand damage from a single fake worse than the per-unit cost of protection? Two yeses point to enrolment. Start with your most-copied ASINs, build the labelling step into production first, and expand only once the workflow runs clean.