GS1 GEPIR Lookup: How to Check Your Barcodes Before Amazon Does

Amazon runs a GS1 GEPIR lookup — now called Verified by GS1 — automatically when you create a product listing. If the company name on your GS1 account doesn’t match your brand name exactly, Amazon fires error 5461 and your listing doesn’t go live. The check takes two minutes and it’s free. Most sellers only find out about it after they’ve already hit the error.

What Amazon actually checks when you list a product

When you enter a GTIN during listing creation, Amazon queries GS1’s database in the background. It cross-references three things:

• Whether the GTIN exists in GS1’s records at all. If it doesn’t resolve to any company, it’s invalid — no support ticket will fix that.
• Who owns the company prefix. The License field in GS1’s database shows which GS1 Member Organisation issued the prefix and to which company name. That company name is what Amazon sees.
• Whether your brand name matches the GS1 licensee name. If your Brand Registry enrollment says “Acme Products LLC” but your GS1 account was registered as “Acme LLC,” that one word is enough to trigger a mismatch.

This is exactly why reseller barcodes from grey-market vendors consistently fail Brand Registry checks: the GS1 prefix belongs to the reseller’s company, not yours. Amazon sees a different owner and blocks the listing. The barcode may scan correctly and look like a legitimate GTIN — but in GS1’s database, it’s licensed to someone else. Amazon finds that in under a second.

March 2026 made this more consequential, not less. Amazon eliminated commingled inventory for Brand Registry sellers and started using manufacturer GTINs printed on packaging as the primary tracking identifier. Your GTIN record needs to be accurate, not just present.

Why GS1 database mismatches happen

The most common cause is a name mismatch that looks trivial: the legal entity name on your GS1 account (“Acme Holdings Inc.”) doesn’t match the DBA you registered in Brand Registry (“Acme”). A missing “LLC.” An extra comma. A different capitalisation of a company name. Amazon’s automated check is string-level — it doesn’t account for obvious variations.

A second common cause: your GS1 product record is empty. GS1 lets you register a company prefix without filling in individual product details. You get a GTIN but never go back to populate the product name and description fields. Amazon’s automated validation is more likely to flag a GTIN with no associated product data.

The third cause is one that trips up sellers doing their own research: outdated tutorial links. GS1 rebranded and replaced GEPIR (Global Electronic Party Information Register) with a new service called Verified by GS1 at the end of 2023. Most forum posts, YouTube videos, and seller guides still reference gepir.gs1.org — which now redirects — or describe the old interface. Sellers following those instructions may check the wrong place, misread the results, or not realise the lookup even exists under a different name.

Understanding what GS1 Digital Link is and how identifiers are structured helps here: the company prefix is the root of your entire product identity in GS1’s ecosystem, and a corrupted or misregistered prefix affects every GTIN that branches off it.

What a clean GS1 record looks like

When you run a Verified by GS1 lookup on a properly registered GTIN, you’ll see:

• License: the GTIN resolves and points to a valid GS1 company prefix
• Licensee name: the company name that owns the prefix — this should match your Amazon Brand Registry brand name character for character
• Status: Active
• Product details: at minimum a product name populated; ideally a description and product image URL as well

If the licensee name belongs to someone else, no amount of appeal to Amazon will fix it — the data lives in GS1’s system, not Amazon’s. If the GTIN returns no result at all, it either wasn’t registered through a legitimate GS1 Member Organisation or the prefix is no longer active.

A blank product record isn’t automatically a listing rejection, but it’s an unnecessary risk. Filling in the product name and description in your GS1 account takes two minutes and removes one more reason for Amazon’s automated check to pause.

How to run the check — step by step

1. Go to gs1.org/services/verified-by-gs1. This is the current official lookup, the direct replacement for GEPIR. No account is required for a basic lookup.

2. Enter your GTIN as a 14-digit number. GTINs are always 14 digits in Verified by GS1. If you have a 12-digit UPC or 13-digit EAN, pad with leading zeros on the left.

3. Read the License field. The licensee name shown here is what Amazon will see. Compare it character by character with your Amazon Brand Registry name.

4. Check product details. If the product name field is empty, log into your GS1 account (gs1us.org if you’re registered in the US, or your local GS1 Member Organisation) and populate it before listing.

5. If you see “GTIN not found” or the licensee name is not your company, stop. A support ticket to Amazon will not fix a GS1 record that doesn’t belong to you. Register the GTIN correctly through GS1 first.

Run this check on every GTIN before your first listing, and again before any bulk ASIN creation. Catching a mismatch at this stage is far less expensive than clearing listing suppression after the fact.

There’s a longer-term reason to get this right too. Sunrise 2027 is 201 days away — on January 1, 2027, all retail point-of-sale globally must be able to read GS1 Digital Link 2D codes. The GTIN embedded in those QR codes is the same GTIN that Amazon validates today. A clean, accurate GS1 record now is the foundation for both.