Brand Registry, MAP & resellers
Transparency is Amazon's unit-level serialization program. You put a unique Transparency code on every unit you make, Amazon scans that code before the unit ships to a customer, and any unit without a valid code is blocked. Enrollment runs through Brand Registry, the codes are ordered from Amazon and cost a small amount per unit, and once an ASIN is enrolled every seller of that ASIN has to comply.
For a brand selling wholesale, this is the most useful program in the whole brand-protection stack, and for a reason that has little to do with counterfeits. Every code you order is attached to a specific production run and, once you record where the cases went, to a specific customer. When units surface on Amazon from an account you never sold to, the code tells you whose shipment they came out of.
How the program works step by step
The mechanics are simple enough to hold in your head.
You enroll a brand in Transparency through your Brand Registry account and select which ASINs to cover. You order codes, either as printed labels shipped to you or your co-packer, or as a data file if your printer can apply them inline. Every code is unique to one unit. The codes go on the unit, not the case, and they have to be visible on the outside of the unit packaging.
From the date the ASIN goes live in the program, Amazon scans the code on every unit before it leaves a fulfillment center, and every unit sent into FBA by any seller. Units with no code, a duplicate code or an invalid code are stopped. Customers can scan the code in the Amazon app to see product information you provide, which is the customer-facing half of the program.
The part that matters commercially is the reporting. Amazon shows you where codes were scanned and lets you look up individual codes. You know which run a code belongs to. If you also keep a record of which run went into which shipment, you know the customer.
What Transparency proves and what it does not
It proves a unit is one you made and released. It does not prove the unit is being sold by someone you authorized.
That distinction is the whole game for a wholesale brand. A distributor who buys 600 genuine units and resells them to an Amazon seller is passing on units with perfectly valid codes. Transparency will not block those units, because they are not counterfeit. What Transparency does is answer the question you otherwise cannot answer: which of your customers did those units come from.
That answer is leverage. Not a takedown, leverage. You go back to the distributor with the run number and the codes, point at the clause in the agreement about the channels they are permitted to sell into, and have a real conversation. Without serialization that conversation is your suspicion against their denial, and it goes nowhere.
The other thing Transparency does not do is set prices or restrict who may list. Pricing lives in your policy and your contracts, which is the subject of minimum advertised price on Amazon. Listing restrictions come from a different set of mechanisms covered in Amazon brand gating.
What it costs, and how to think about the cost
There is a per-code charge, and it falls as volume rises. The other costs are the real ones: applying the label.
If a co-packer applies the label by hand, you are paying for labor on every unit. If your printer can print the code inline on the packaging run, the marginal cost is close to nothing but the setup takes a production cycle to arrange. The cheapest moment to solve this is when you are already redesigning packaging for wholesale, because you are opening the artwork files anyway to add a case-pack label, a retail-ready barcode and the case markings a distributor's warehouse expects.
Work the arithmetic on your own numbers. A brand making 12,000 units a year of a $28 product is paying a code charge measured in low hundreds of dollars annually, plus whatever the application step costs. Set that against one contested featured offer. A rogue offer sitting $6 under your price for a month on a listing doing 400 units costs more than the program does in a year, and that is before the time you spend on it.
Where it fits against Project Zero and Registry
The three programs stack rather than compete.
Brand Registry is the foundation and the prerequisite. Everything here requires it, and Amazon Brand Registry covers what the base layer gives you.
Project Zero adds automated counterfeit scanning and the ability to remove infringing listings yourself, without filing a complaint and waiting. It is invitation-based and performance-based, and its own serialization component is essentially Transparency.
Transparency is the physical layer. Registry and Project Zero operate on listings; Transparency operates on units. That is why it behaves differently. A listing-level tool tells you about an offer. A unit-level tool tells you about a shipment, and shipments are what you actually sold.
If you can only run one, run Transparency. The listing tools help when someone is faking your product. Serialization helps with the far more common case, which is your own product moving through a channel you did not intend.
Setting it up before the first wholesale order
The sequence matters, because retrofitting serialization onto inventory already in distributors' warehouses is close to impossible. Units without codes are grandfathered awkwardly, and a mixed pool of coded and uncoded stock undermines the whole signal.
A workable order looks like this. Enroll the brand and the ASINs while you are still the only seller. Get codes onto the next production run, not the current one, so the packaging change happens once. Record, in something as plain as a spreadsheet, which code range went into which purchase order. Put a clause in the reseller terms that says the customer will not divert units to online marketplaces and will identify the source of any units found there. Then start shipping cases.
The record-keeping step is the one brands skip and regret. Amazon tells you a code was scanned. It does not tell you who you sold that code to. That mapping is yours to keep, and it takes five minutes per purchase order.
What happens when you find diverted units
Here is the sequence that works, in order of escalation.
Buy a unit from the offer. You need the physical unit, not a screenshot. Scan the code, look it up, identify the run. Match the run against your shipment records and you have a customer name.
Contact that customer with the specifics. Most of the time you will be told a sub-distributor or a retail account sold it on. That is often true. Ask them to identify the buyer and to stop supplying them, and hold them to the identification clause you wrote in.
If the customer will not or cannot help, the decision is commercial: keep selling to them with different terms, or stop. Cutting off a paying account is uncomfortable, and it is also the only sanction that is genuinely yours to apply. Amazon will not do it for you. The full playbook, including what to do when the source is a liquidation lot rather than a live account, is in unauthorized sellers on Amazon.
Before any of that, it helps to know which distributors and retailers are the right fit in the first place, since most diversion comes from accounts that were never a good match for the product. Paste your listing into WholesalePilot and the preview shows who plausibly stocks products like yours, which is a better starting list than whoever happened to email you.
Questions sellers ask about Transparency
Do I have to enroll every ASIN? No, enrollment is per ASIN. Brands commonly start with the one or two listings that attract the most unwanted offers and extend from there.
What happens to units already in FBA without codes? Amazon handles the transition per ASIN and gives you a window, but plan for a period where old stock sells through while coded stock arrives. Do not enroll an ASIN the week before a big inbound shipment.
Can other sellers still list on my enrolled ASIN? Yes. They can list, and their units have to pass the code check like yours. A seller with genuine coded units will pass. A seller with units that carry no code will not be able to ship them through FBA.
Does the customer see anything different? They can scan the code in the Amazon app and see the information you loaded against it, such as the manufacturing details or ingredient notes you choose to publish.
Does this work outside Amazon? The codes are physically on your units wherever they go, so a retail partner or your own team can verify a unit anywhere. The automated blocking, though, happens inside Amazon's fulfillment network.