# Amazon transparency program importers: a practical guide to anti-counterfeit labeling
Amazon transparency program importers are sellers who want counterfeit units kept off their listings without hiring a law firm every quarter. Amazon runs an opt-in anti-counterfeit program under the Transparency name: enrolled brands place a unique code on every single unit, and Amazon checks those codes at its fulfillment centers before suspect products reach buyers. Units without a valid code get rejected.
That sentence hides most of the work. Getting codes printed, applied, and verified on tens of thousands of units made in China is a packaging and QC problem, not a paperwork one. The mechanics of the program are simple; the real setup is the barcode layer underneath it, the factory work of applying labels correctly, and the inspection checks that catch mistakes before a shipment sails. What follows covers the pieces Amazon transparency program importers set up before the first carton ships.
What the Amazon transparency program importers ask about actually is
The Transparency program is Amazon's unit-level anti-counterfeit tool. Brands enroll their products, and Amazon issues unique transparency codes for each unit. Those codes get printed as 2D barcodes and stuck or printed on the product packaging. When the units arrive at an Amazon fulfillment center, Amazon scans the codes. A unit that carries a valid, unduplicated code is treated as genuine. A unit without one, or with a code that was already used, is flagged and can be rejected.
Why does this exist? Counterfeit complaints are one of the fastest ways to lose a listing. When two or more sellers share a listing through commingled inventory, a counterfeit unit from any one of them damages every seller on the page. Amazon transparency program importers use the program to break that link: their units are individually identified, so fakes cannot ride along unnoticed.
Two cautions before planning around it. First, program terms and fees change, so Amazon transparency program importers should check the current enrollment requirements before committing a packaging design to the program. Second, Transparency handles the code layer, not everything else. You still need the ordinary labeling Amazon requires: an FNSKU on each unit, correct carton labels, and suffocation warnings on poly bags. Non-compliance there brings chargebacks even when every transparency code scans perfectly.
Unit barcodes: GS1, UPC, and FNSKU
Every unit you import for Amazon retail needs to be scannable at two different levels, and beginners mix them up. The retail barcode identifies the product. The FNSKU identifies your Amazon listing. Getting this layering right is where Amazon transparency program importers often stumble, because a mistake at this level makes every code you add later point at the wrong thing.
GS1-registered barcodes are the standard for retail. A UPC (or EAN outside North America) comes from a GS1 company prefix registered in your name, and it goes on the product packaging. Amazon requires the barcode to be legitimate and tied to your brand, because the barcode database is one of the places counterfeiters get caught: a UPC registered to someone else's company is a red flag.
The FNSKU is Amazon's own identifier, different from the UPC. Amazon uses it to track your inventory inside its fulfillment network. Every unit sent to FBA carries an FNSKU label, either printed directly on the packaging or applied as a sticker that covers the manufacturer's barcode so the wrong code is never scanned by mistake. Keep all three layers straight: a GS1-registered UPC on the retail packaging, an FNSKU for the Amazon listing, and a transparency code for anti-counterfeit verification.
Apply barcodes on the packaging at the factory. That sounds obvious, and it is exactly the step that fails most often. Factories that print labels in-house will sometimes reuse leftover stickers from a previous buyer's run, print at the wrong size, or place the code where a poly bag seam covers it. The placement decision belongs in your packaging brief before production starts: which code goes where, at what size, and what covers what. This is exactly where Amazon transparency program importers run into trouble, because a factory left to decide placement on its own will optimize for printing convenience, not scannability.
Getting transparency codes and labels onto packaging at the factory
Adding the code layer means changing your packaging brief, and the factory needs that brief before production, not after. A usable packaging brief covers dielines, materials (rigid box, mailer, polybag), printing specs, and inserts. Add the transparency code to it: code format, minimum print size, exact placement on the unit or carton, and which codes cover which production run. For Amazon transparency program importers, that brief is the document that makes the whole system work, so it deserves the same care as the product spec sheet.
The codes go on three ways. Printing directly on the box during the packaging run is cheapest at scale and hardest to tamper with, but it locks one code batch to one production run. Stickers applied at the factory work for smaller runs and let you split one code batch across factories, though each sticker becomes a small QC item of its own. Having labels applied by a third-party prep center works when the factory cannot print at the quality Amazon's scanners need, but it adds a handling step and its own cost.
Whichever route you choose, confirm the details before production. Send the factory a physical or digital proof of the label layout, get a sample with the actual codes printed, and scan the sample yourself with a phone before approving the run. Skipping this proof step is how importers find out about unreadable codes when the shipment is already on a boat.
Private label sellers should fold the code placement into the same step where they handle logo files and labeling compliance. The code is part of the brand's packaging system. Treating it as an afterthought produces the classic failure: a beautiful box with the code squeezed into a corner at half the minimum size.
How to add labeling to your QC checklist
Labeling checks belong on the same QC checklist as quantity, materials, dimensions, and colors, and the inspector checks them against the approved sample. Amazon transparency program importers who run pre-shipment inspections should give the inspector explicit labeling instructions, because a general "check the packaging" note does not catch barcode problems.
A workable labeling section on the checklist covers five points. Verify the UPC is the GS1-registered code for this product and scans to the right item. Verify the FNSKU matches the Amazon shipment plan and fully covers the manufacturer barcode. Verify transparency codes are present on every unit, printed at the approved size and position, and that a sample of codes scans and shows as valid. Verify suffocation warnings appear on poly bags where required. Verify carton labels match the shipment contents.
The sampling logic follows the same AQL approach as the rest of the inspection. The industry default is AQL 2.5 for consumer goods, with critical defects at AQL 0. A missing or unscannable transparency code on units bound for an enrolled listing is arguably a critical defect: it can get the whole unit rejected at the fulfillment center, which is a functional failure of the anti-counterfeit system you paid to join. Write the defect definitions into the checklist so the inspector does not have to improvise the call on-site.
Test reports matter here too. If your product category needs safety or chemical testing, validated batch-specific test reports from an accredited lab beat generic certificates every time, and retest on a cadence for repeat orders. Labeling does not replace compliance testing. It protects the listing from fakes; the test report protects you from a recall.
Costs, timing, and what to confirm with Amazon first
Joining the program costs money per code, and Amazon sets those terms, so get the current numbers from Amazon before you budget. What you can plan on your side is the factory-side cost: printing changes, sticker application labor, the proof round, and the extra minutes per carton in inspection. Amazon transparency program importers usually find these factory-side costs are the surprise line item, so build them into the landed cost per unit rather than a general overhead bucket, because per-unit costs are what decide whether the program pays for itself on your margins.
Timing needs the same honesty. The code batch has to exist before the packaging run, which means enrollment and code generation sit on the critical path of your production schedule. Importers often discover this ordering problem late: the factory is ready to print boxes, and the codes are not ready yet. Put enrollment on the calendar the day you place the order, not the day the goods ship.
Also confirm which listings and marketplaces the codes cover. A code batch is tied to the enrolled products, so a packaging redesign, a new variant, or a marketplace expansion can mean a new enrollment step. Check the current rules on Amazon's side rather than assuming the process Amazon transparency program importers followed last year still applies.
Conclusion
Amazon transparency program importers buy one thing with all this effort: units that can prove they are genuine when they arrive at the fulfillment center. The program itself is a code layer. The work is in packaging and QC: GS1-registered barcodes, correct FNSKUs, factory-applied labels at a scannable size and position, and an inspection checklist that treats labeling defects as seriously as product defects. Confirm Amazon's current enrollment terms before you start, put the code batch on the production critical path, and scan a real sample before you approve the run.
Frequently asked questions
### Do I need the transparency program if I already use FNSKU labels?
Not necessarily. FNSKU labels identify your inventory inside Amazon's network, and every FBA seller uses them. The transparency program adds a per-unit authenticity check that FNSKU does not provide. For Amazon transparency program importers, it makes sense when counterfeits are an active problem on your listings or in your category, not as a default for every product.
### Who applies the codes: the factory or a prep center?
Either works. The factory is cheaper at scale and keeps everything in one production flow, which is why most Amazon transparency program importers start there. A prep center makes sense when the factory's print quality is unreliable or when you are splitting one product across multiple factories and want consistent application.
### What happens if codes are unscannable when units arrive at Amazon?
Units can be rejected or held, which is why the proof-and-scan step before production matters. Confirm with Amazon's current policy what happens to rejected units, since the handling and any fees are set by Amazon and change over time.
### Can transparency codes replace compliance testing?
No. Codes verify authenticity; they say nothing about whether the product is safe or legal to sell. Keep your batch-specific lab test reports current, and treat labeling and compliance as two separate checklists.