All guides

How to Send Transparency Codes to Resellers and Partners

By Todd Welch, founder of T-Code Manager. Published October 15, 2026.

If you own a Transparency-enrolled brand and sell through resellers, distributors or sales partners, those partners need codes from you. The codes belong to your brand. Amazon issues them for your enrolled products, and your partners can't order them on their own.

At a lot of brands, the process is an email. A reseller asks for 500 codes, someone finds the file, copies out 500 rows and sends them over. It works until two partners get the same codes, or a reseller says they never got a batch you know you sent.

This guide is for the brand side: a simple way to send codes to resellers and partners and keep a record of every one.

Why resellers need codes from you

As of October 2026, Amazon's Transparency page says that once your products are protected, a valid Transparency code must accompany every unit listed or shipped in Amazon's Transparency-supported stores. Fully protected products can't be listed without valid codes that match the enrolled product. Amazon's Australian page puts it more plainly: all sellers have to provide the brand's unique codes before units can be listed or shipped.

That includes your resellers. Without valid codes from you, they can't list or ship your enrolled products on Amazon. Their stalled order is your stalled sale.

Resellers usually get codes one of three ways: units arrive already labeled, the brand sends code files or the brand authorizes API access. The guide for 3PLs and prep centers covers those from the receiving side. If you can label units before they leave you, that's the simplest option. When partners need the codes themselves, the process below keeps it under control.

Check Amazon's guidance first

Amazon's public Transparency pages don't spell out rules for sharing codes with resellers or distributors. Before you set up a process, check the guidance in your Transparency account or ask Transparency support how codes should be shared with partners, and whether units should be labeled before they ship to them.

What goes wrong when codes go out by email

  • The same codes go to two people. Someone copies rows out of the master file and doesn't mark them sent. Next week a second reseller gets the same rows. Each code is meant for one unit, and now two units carry it.
  • No record of who got what. A reseller has a problem with codes on a shipment months later. Which batch did they get, and when? The answer is buried in someone's sent folder, if it's anywhere.
  • Slow turnaround. Requests wait until the one person who knows where the file lives gets to them. Meanwhile the reseller's stock sits unlabeled.
  • Codes sitting in inboxes. Every email with a code file is another copy of codes you paid for, in a mailbox you don't control. Once it's forwarded, you've lost track of who has them.
  • Wrong product. A reseller asks for codes for one variation and gets the file for another. Amazon keeps a record of the product every code was generated for, so those codes are wrong for the units they end up on.

A simple process for sending codes

1. Give it one owner

One person, with a backup, handles every reseller request. When three people can send codes, nobody knows the real count.

2. Take requests in one format

Every request needs the same details: reseller name, ASIN, SKU, quantity and a reference like a purchase order number. Use a short form or a fixed email template, and send incomplete requests back. Checking the ASIN and SKU against each other catches the wrong-variation mistake before it happens.

3. Issue exact counts

Send the number of codes the reseller needs for the units on that order, not a round number to be safe. Extra codes sitting with a partner are codes you paid for and can't account for. If they need more later, they ask again.

4. Take codes out of stock before you send

Mark codes as issued the moment you pull them for a reseller, before the email goes out. If you send first and update later, someone will eventually forget, and the next request gets the same codes.

5. Record who received which codes and when

For every batch, log the reseller, the product, the quantity, the codes themselves, the reference, the date and who sent it. Amazon's codes are non-sequential, so a first and last code doesn't describe a batch. Keep the actual list, and keep a copy of the file you sent.

6. Confirm receipt

Ask the reseller to reply with the count they received and the product it's for. It takes them a minute and settles the "we never got it" question before it starts.

7. Reconcile

Once a month, check that codes received from Amazon equal codes you used yourself, plus codes issued to resellers, plus codes still available, plus codes void. Keep the reseller number separate so you can see how many codes each partner has taken. Here's how to reconcile Transparency codes.

Reseller requests come out of the same stock as your own labeling, so count them when you decide how many codes to order and when.

Put the ground rules in writing

Agree on these with each reseller before you send the first file:

  1. Codes are only for the product they were issued for.
  2. Each code goes on one unit.
  3. Codes don't get passed to anyone else without your OK.
  4. Unused codes get reported back, not used on another product.
  5. Who to ask for more, and how much notice you need.

How software helps

Email and a spreadsheet can work for one or two resellers who order a few times a year. Once requests come in every week, or more than one person handles them, software covers the steps people forget:

  • Codes are marked used the moment they go out, so the same codes can't be handed out twice.
  • Every product has a current count, so you know what you can promise a partner.
  • Every batch is logged with who, when, which product and which reference.
  • Alerts warn you before a product runs low, instead of a reseller's request telling you.

If you're not sure you're there yet, read spreadsheet vs software for Transparency codes.

Where T-Code Manager fits

T-Code Manager tracks your codes per product. The dashboard shows how many codes each product has left, and you can set a threshold per product to get an email before it runs dry.

If you label units before they ship to a reseller, your team scans the product, enters a quantity and prints. Codes are marked used as soon as the label file is created, and every print job is logged with who ran it, when, the product and the shipment or order reference you enter.

If a reseller needs the codes themselves, the dispensing flow hands you an exact number of unused codes, marks them used on the spot and logs them with the order ID you enter. You can copy them one per line or comma separated. The dispense screen strips the "AZ:" prefix by default for pasting into ShipStation. Turn that option off before you copy codes for a reseller, so they get the codes exactly as Amazon issued them.

You still send the codes and collect the reseller's confirmation yourself. What T-Code Manager takes off your plate is the count and the record. Every plan includes unlimited users, and plans start at $29 a month.

Start a free 14-day trial. No credit card required. Or compare plans and pricing.

Manage your Transparency codes without spreadsheets.

Start Free Trial

14-day free trial. No credit card required.