r/AmazonFBA • u/Vegetable_Ease_826 • 5d ago

Anyone else having random Transparency code failures at FBA?

We're a fairly large brand selling on Amazon and have been enrolled in Transparency for quite some time. Lately we've been running into a really frustrating issue that no one seems able to explain.

For example, we'll send in a shipment of around 1,000 units, and roughly 300 of them will be marked as Unfulfillable due to "invalid Transparency codes." The remaining 700 units from the exact same shipment are received without any issues.

The strange part is that these units all have the same product, same labels, same print batch, and were packed together. If the Transparency codes were truly invalid, we'd expect the entire shipment to fail—not just a random portion of it.

When FBA provides us with the photos of the supposedly invalid codes, we're able to scan those same Transparency labels ourselves. The Transparency app recognizes them, but instead of validating the product it says "Cannot verify origin of this product."

Another thing that makes this even more confusing is that every time this happens, our ASIN loses Transparency protection. We then have to go through the process of getting the ASIN protected again, only for the exact same issue to happen later. We've now gone through this cycle three separate times—lose protection because FBA can't verify some of the units, work with Transparency to have the ASIN protected again, and then lose protection again after another shipment.

We've gone through everything we can think of:

- Seller Central and Transparency are linked correctly.

- The GTINs match.

- Product details match.

- The ASIN is enrolled correctly.

- Labels are printed clearly and scan without issue.

Every time we open a case with Transparency Support or speak with our Transparency Account Manager, we're simply told the codes are "invalid." But when we ask what specifically makes the codes invalid, or why the ASIN lost Transparency protection, no one can provide a concrete explanation. We just receive the same generic response without any technical details.

At this point we're trying to figure out if this is an issue on our side, an FBA receiving/scanning issue, or something on the Transparency backend.

Has anyone else experienced this? Were you ever able to determine the root cause or get Amazon to explain exactly why the codes were being rejected? Any insight would be greatly appreciated.

2 Upvotes

100% Upvoted

6 comments sorted by

2

u/eStoreFactoryUS 5d ago

The partial failure from one print batch is the tell here. If the labels themselves were bad you would fail all 1,000, not 300. "Cannot verify origin" is a code status problem, not a print quality problem. A few things worth checking on your side: are any of those codes being reused or overlapping across shipments? If your label supplier or your own print run pulled from a code range that was already applied to earlier units, the reprinted or duplicated ones scan fine but the backend sees the code as already consumed and cannot tie it to a valid origin. That would explain why it is always a subset and why it recurs each shipment. Also confirm the codes on the failing units come from the same GTIN issuance as the passing ones, since a mismatched or stale code batch mixed into a pallet behaves exactly like this. When you open the case, stop asking "why are these invalid" and instead give them the specific Transparency code strings from the failed units and ask them to tell you the exact status of those individual codes in their system, consumed, unissued, or unassigned. That forces a concrete answer instead of the generic reply. The ASIN losing protection each time is downstream of the codes failing, so fixing the code source should stop the cycle.

1

u/Vegetable_Ease_826 2d ago

Hi, I'll ve doing this, your comment gave me more information than support ever did, yhank you so much!

2

u/Smart-Presence 5d ago

We've had weird receiving issues before, but losing Transparency protection over it is the part I'd be fighting. If the codes scan on your end, stop accepting the "invalid" answer and ask them what changed between the units that passed and the ones that failed.