Amazon Transparency Program: The FBA Brand Owner's Prep Guide (2026)

The Amazon Transparency Program is not a listing protection tool. It is a unit-level authentication system, and that distinction changes almost every step of your prep workflow the moment you enroll an ASIN. This guide covers what actually changes operationally - from the moment you download a code batch to the moment a consumer scans the label at their door - and explains the failure modes that most prep guides skip entirely.

What Transparency Does at the Unit Level

Standard Brand Registry enforcement works at the listing level: you flag a bad actor, Amazon investigates, and a listing may be removed. A counterfeit unit already inside a fulfillment center, or already in transit to a buyer, is not stopped by that process.

Transparency operates differently. Each enrolled unit receives a unique 26-character alphanumeric serialized 2D barcode that exists nowhere else in the world. Amazon scans that code at FC intake during receiving - before the unit ever enters available inventory. A unit with a missing, invalid, or already-consumed code is quarantined as a potential counterfeit before it reaches a shelf.

The three-layer architecture is what makes this effective:

• Portal to batch file: You order serialized codes in downloadable batches from the Transparency portal; each code is globally distinct and single-use.
• FC intake scan: Amazon scans every Transparency code at receiving; once scanned, the code is consumed and cannot be reused on another unit.
• Consumer verification: After delivery, buyers scan the 2D barcode with the Amazon Shopping app or the standalone Transparency app; a green check confirms authenticity and surfaces batch-level product details the brand loaded during enrollment.

That chain cannot be faked by reprinting someone else's code. The serialized structure means a duplicate or re-used code fails immediately at intake, which is something a listing takedown cannot achieve once a counterfeit unit is already in the supply chain.

Enrollment Prerequisites in the Correct Order

Three conditions must all be true simultaneously before Amazon will accept a Transparency application: active Amazon Brand Registry enrollment, a registered trademark (not a pending application), and a valid GTIN - either a UPC or EAN - assigned to every ASIN you plan to enroll. Having two of the three will stall the application.

The step sellers most often miss is GTIN assignment at the ASIN level. Brand Registry membership does not mean every ASIN in your catalog carries a valid GTIN. Generic or bundled listings created without a barcode, listings built under a brand exception, and ASINs set up as catalog matches can all lack a GTIN even when the brand account itself is registered. Before you submit the application, audit each ASIN you intend to enroll:

• Confirm the GTIN appears in Seller Central under Manage Inventory for that specific ASIN
• Verify the trademark registration matches the brand name on the ASIN exactly as Brand Registry has it on file
• Check that Brand Registry enrollment is active, not pending re-verification

Transparency launched in 2017 and now covers the US, Canada, Germany, France, Italy, Spain, the UK, India, Japan, and Australia. If you sell across multiple markets, every enrolled ASIN requires codes in every market where the product is sold - not just your primary marketplace.

Per-Code Cost Structure

There is no enrollment fee and no subscription. You pay only for the codes you order, and pricing is volume-tiered - the per-code rate drops as your total annual code volume rises. Amazon uses a tiered structure based on annual code volume, with rates varying by marketplace. Check the Transparency portal for current rates in your marketplace, since fees can vary by country and are reviewed periodically.

The budget decision that matters before enrolling a high-volume ASIN is whether your order cadence lets you reach a lower tier. If you manufacture in runs that put you near a tier boundary, consolidating two production runs into one code order can reduce your per-unit cost meaningfully. Factor the code cost against your current COGS on each ASIN, then separately account for the prep labor added by the labeling step. For most mid-volume private label sellers, code cost is small relative to the FC intake protection it provides. The calculation changes for high-velocity, low-margin consumables where even small per-unit additions matter.

The Label Layouts

Amazon offers multiple official Transparency label layout types - at least four standard options have been defined since the program launched, and additional variants have been introduced since. Check the Transparency portal for the current full list before setting up label templates. The four most commonly referenced layouts are described below, and choosing the right one is a prep center efficiency decision, not just a compliance checkbox.

Layout	Contains	FNSKU labeling	Best for
Layout 1	Transparency 2D code only	Separate step required	Manufacturer pre-application at factory
Layout 2	Transparency 2D code + brand logo	Separate step required	Brand presentation on retail packaging
Layout 3	Transparency 2D code + GTIN barcode (UPC/EAN)	Separate step required	Combining Transparency code and product GTIN on one label
Layout 4	Transparency 2D code + FNSKU or GTIN + optional logo and condition	Included in same label	Prep center single-pass labeling

Layout 4 is the right choice for most prep center workflows because it merges both identifiers onto one physical label. Instead of running units through two separate labeling passes - one for FNSKU, one for Transparency - a prep center using Layout 4 applies a single label that satisfies both requirements. Tools like FNSKU Studio support combined label files that print both codes in one pass, which cuts handling time and eliminates the alignment risk that comes with applying two separate labels close together on the same surface.

One rule applies regardless of layout: the FNSKU label must never cover the Transparency code. Both must remain independently scannable. This is one of the rare cases in Amazon prep where two barcodes deliberately coexist on the same unit without one overprinting the other.

Three Points of Code Application

Factory application looks attractive because it removes a step from the prep workflow. The risk is that damaged or unscannable codes arriving at the prep center cannot be fixed by applying a spare code from the same batch - a replacement batch must be ordered from the Transparency portal for exactly the count of damaged units before relabeling can happen. Factory application also means trusting a manufacturer's printing equipment and QC process to meet Amazon's scan durability standards.

In-house application by the seller works at low volumes but breaks down when shipment prep is time-sensitive and the seller lacks commercial label printing equipment and reconciliation processes.

Prep center application is the most auditable option for most FBA sellers. A professional prep center logs each code against the unit it was applied to, maintains batch records that allow post-shipment tracing, and operates the thermal transfer printers Amazon recommends - not inkjet - for scan durability through warehouse handling and carrier transit. The prep center workflow is also where cross-ASIN mismatches are easiest to catch, because a well-run operation sequences code files to specific ASINs and flags any quantity or file mismatch before labeling begins.

The Prep Center Workflow Step by Step

This is the operational sequence that turns a downloaded code batch into a compliant, labeled, shippable unit. Skipping the reconciliation step at the end is how batches get lost and FC rejections become invisible until intake.

1. Download the code batch file from the Transparency portal for the specific ASIN and unit quantity matching this shipment. Code files are ASIN-specific - do not mix files from different ASINs in the same download session.
2. Verify the code count against the unit count for this prep run before printing begins. A file mismatch caught here is free to fix; one caught at FC intake is not.
3. Load the file into label printing software and configure the template for the correct layout. Confirm the print profile is thermal transfer.
4. Print a test label and scan it with both a 2D barcode scanner and the Transparency app before committing the full batch. This catches printer calibration problems, ribbon wear, and label stock issues early.
5. Label each unit sequentially, applying one unique code per unit. No code is reused. Place the label per the placement requirements updated in April 2026.
6. Scan each labeled unit's Transparency code and log it against a unit identifier - carton number or lot reference - in the batch reconciliation record. This record is what lets you trace any FC intake rejection back to a specific print run.
7. Complete standard prep steps (poly bagging, bubble wrap, bundling) after Transparency labeling, not before. Applying a label to a poly bag surface over the product rather than directly to the product is a common placement error.
8. Cross-reference the reconciliation record against the shipment manifest before the shipment closes. Total codes used must equal total units shipped for that ASIN.

When Factory-Applied Codes Arrive Damaged

Factory pre-application failures arrive silently. A shipment lands at your prep center and looks fine from the outside, but some percentage of Transparency codes on individual units are scratched, smeared, or otherwise unscannable. Run this checklist at receiving for every inbound shipment of factory-labeled enrolled ASINs:

• Scan a sample of Transparency codes with a 2D barcode scanner at receiving - do not rely on visual inspection alone
• Test both the barcode scanner read and the Transparency app read, since they use different decoding paths
• Flag any code that reads as invalid, already consumed, or belonging to a different ASIN
• Count all damaged or unscannable codes and record the exact quantity before taking any action
• Do not apply spare codes from the existing batch to replace damaged ones - a replacement code batch for the exact damaged count must be ordered from the Transparency portal

Once you have the count, log into the Transparency portal, open the enrollment for that ASIN, and order a replacement batch for exactly the quantity of damaged units. Replacement codes are fresh and unconsumed. Only after the replacement batch downloads and prints to spec should relabeling proceed. If your shipment window is tight, order replacement codes the moment damaged units are identified - do not wait for the full receiving count to finalize. A partial relabel can ship while you wait for the remainder.

FC Intake and the Quarantine Outcome

Most FBA sellers are familiar with inbound defect fees: a missing FNSKU, a prep defect, a label that does not scan. These generate a fee and the unit typically enters inventory. Transparency failures are categorically different.

Amazon scans every Transparency code at FC intake. A unit with a missing, invalid, or already-consumed code is quarantined as a potential counterfeit - not processed as a defect and passed through. It does not enter available inventory. The seller does not pay a defect fee and move on. Instead, the quarantined unit must go through a removal order, be shipped back to origin at the seller's cost, be relabeled with a freshly ordered valid code, and then be fully re-inducted through a new inbound shipment. The all-in cost per rejected unit - removal fee, return freight, replacement code, re-inbound freight, and prep labor - typically exceeds the original per-code price by a factor of ten or more.

One quarantined unit costs more than a hundred correctly applied codes. The economics of Transparency compliance are not about the per-code fee - they are about preventing the quarantine outcome entirely.

Two specific misapplication errors cause most rejections. First, consumed codes: a code that was applied to a different unit at an earlier point in the supply chain has already been scanned and consumed, so applying it to a new unit produces a failure even though the label looks valid. Second, cross-ASIN codes: a valid, unconsumed code from the wrong ASIN's batch reads as authentic but does not match the ASIN traveling with it, triggering quarantine even though the code itself is active.

Extending Transparency to FBM and Multi-Channel

For Fulfillment by Merchant and Seller Fulfilled Prime orders, the requirement does not disappear because the unit never passes through an Amazon FC. Sellers must enter each unit's unique Transparency code into Seller Central - or via the Transparency API - before generating the shipping label for that order. No valid code entry means no label, so the order cannot ship. There is no workaround for this step.

The consumer-facing layer works the same way for FBM as for FBA: after delivery, the buyer scans the 2D barcode with the Amazon Shopping app or Transparency app. A green check confirms authenticity and surfaces the batch-level product details the brand loaded during enrollment.

Transparency enrollment also gives enrolled brands access to Amazon Project Zero, a separate brand protection tool that lets brands remove counterfeit listings through a self-service mechanism. However, Transparency enrollment is not a prerequisite for Project Zero - Project Zero requires active Brand Registry enrollment and a demonstrated track record of accurate counterfeit reports, and brands can apply for Project Zero without enrolling in Transparency. The two programs are complementary: Transparency adds unit-level serialization while Project Zero adds a self-service removal workflow, and using both together provides a stronger protection posture than either does alone.

Frequently Asked Questions

Can I enroll only some of my ASINs in Transparency and leave others unenrolled?

Yes, enrollment is at the ASIN level, not the account or brand level. You can enroll high-counterfeit-risk or high-velocity ASINs while leaving others unenrolled. Each enrolled ASIN requires codes for every unit shipped to every marketplace where it is sold, so factor that scope into the decision for each ASIN individually.

What happens if my prep center runs out of codes mid-shipment?

You must order additional codes from the Transparency portal before labeling can resume - you cannot use codes from a different ASIN's batch as a substitute, and unlabeled units cannot be sent to the FC. To avoid this, order a buffer quantity modestly above your expected unit count each time you place a code batch order, particularly for ASINs with variable unit yields from production.

Does Layout 4 replace the FNSKU label entirely, or is a separate FNSKU label still required?

Layout 4 includes the FNSKU (or GTIN) barcode on the same physical label as the Transparency 2D code, so a separate FNSKU label is not required. Both barcodes are printed side by side on the single label and remain independently scannable, satisfying both requirements in one prep step.

If a consumer scans a Transparency code and gets a failed result, what are the consequences for the seller?

A failed consumer scan - indicating the code is invalid, consumed, or not registered to that product - signals the unit may be counterfeit or was relabeled incorrectly. Amazon can see these scan results, and a pattern of failed consumer scans linked to your account can trigger an investigation separate from the FC intake quarantine process. This is another reason that batch reconciliation records matter: they let you identify and explain any anomalous scan results if an investigation occurs.

How does the April 2026 label format update affect sellers whose packaging was designed before that date?

Any packaging that incorporated a Transparency label placement into the printed design before April 30, 2026 may not meet the updated placement or format specifications. Review your packaging design files against the current requirements in the Transparency portal before your next production run, and update supplier SOPs accordingly. Prep centers applying labels to existing packaging stock should also verify that label placement complies with the updated requirements - not assume previous templates are still valid.

Is a bundle treated as one enrolled unit or does each item in the bundle need its own Transparency code?

A multi-pack or bundle is treated as a single enrolled unit. One Transparency code is applied to the bundle as a whole, not one per item inside it. The GTIN assigned to the bundle ASIN is what must be in place before that ASIN can be enrolled, and codes are ordered at the bundle unit count - not at the individual component count.