Amazon Transparency Codes: Counterfeit Prevention Guide

Define the enrolled product scope

Record the exact products, identifiers, packaging versions, manufacturing locations and marketplaces included in the program. Confirm the current enrollment and code requirements shown in the brand account before printing or releasing inventory.

A code plan must account for existing non-coded inventory, bundles, replacement packaging and regional product versions.

Control code generation and application

Test scans at the point of packaging and again before release. Keep failed-code and reprint records so a later incident can be distinguished from unauthorized duplication.

• Authorized personnel and systems that can obtain codes
• One-to-one application and duplicate-prevention checks
• Print quality, placement and scan verification
• Batch, date, facility and purchase-order traceability
• Scrap, rework, returns and unused-code handling

Investigate code incidents in context

When a unit fails verification, preserve the code, product, packaging, seller, order and distribution records. A missing code may reflect old inventory or a packaging error; a duplicated or invalid code may require a different investigation.

Do not assume Transparency resolves catalog edits, copied images or every unauthorized offer. Maintain separate monitoring and evidence routes for those issues.

Use incident data to close supply gaps

Track failures by seller, distributor, batch and location. Review partners with repeat anomalies and update release, audit or contractual controls based on verified findings.