Identifiers — GTIN, brand, MPN
GTIN / barcode
feed attribute: gtin
If your product has a manufacturer barcode, submit it — correctly, digits only, and only once per product.
Google Merchant Center
Required where the product has a manufacturer-assigned barcode, and validated against the GS1 rules — the check digit, the length and the prefix ranges.
Meta
Carried in the catalogue as gtin and used to match your item to the same product elsewhere; incorrect values weaken matching.
What the requirement says
- If a product has a manufacturer-assigned barcode, the GTIN must be submitted. Accepted lengths are 8 digits (EAN/JAN), 12 (UPC), 13 (EAN/JAN/ISBN-13) and 14 (ITF-14).
- Google asks for valid GTINs as defined by the official GS1 validation guide. Digits only: dashes, spaces and letters are not part of a GTIN.
- An ISBN-10 is not an accepted length — convert it to ISBN-13 before submitting it.
- The same barcode cannot identify two products, so each variant needs its own correct barcode.
“The checksum digit is present and correct … The GTIN is not restricted … The GTIN is not a coupon.”
Why products lose visibility when it fails
- An item that has a barcode but submits no GTIN gets limited visibility, and a missing identifier is a common first cause of a feed-level mismatch warning.
- A GTIN that fails its checksum is treated as an incorrect identifier, which commonly causes disapproval.
- A wrong length (10 digits from an ISBN-10, or a 13-digit value that lost a leading zero) fails the accepted-length rule.
- Restricted GS1 ranges (prefixes 02, 04 and values starting with 2) and coupon ranges (98–99) are explicitly excluded by the specification.
- The same barcode on several items creates identifier conflicts: the platform cannot tell which item the history belongs to.
The checks we run on it
Straight from the audit engine, with the basis each one is judged on. “Commonly suppresses” means the failure is the kind that stops a product serving, so it is weighted more heavily in your score.
| Check | Basis | Requirement | What to do |
|---|---|---|---|
GTIN/barcode missing importantgtin_missing | required in some cases | A product with a manufacturer barcode must submit its GTIN — items with a GTIN but no value submitted can get limited visibility. | Add the barcode, or set identifier_exists to false if this product genuinely has no GTIN (custom or one-off goods). |
GTIN wrong length importantgtin_bad_length | required | GTIN values must be 8, 12, 13 or 14 digits (EAN/JAN, UPC, EAN, ITF-14). | Submit the manufacturer's barcode in full, without dashes or spaces. ISBN-10 must be converted to ISBN-13. |
GTIN fails its checksum criticalcommonly suppressesgtin_bad_checksum | required | The GTIN checksum digit must be present and correct (GS1 validation). A GTIN that fails its checksum is treated as an incorrect identifier. | Re-check the barcode against the product's packaging or the manufacturer's data. |
GTIN uses a restricted or coupon prefix minorgtin_invalid_prefix | required | GTINs must not be restricted (GS1 prefix ranges 02, 04, 2) or coupon codes (98–99). | Submit the real retail barcode for the product. |
GTIN used by more than one item importantcommonly suppressesgtin_duplicate | required | A GTIN identifies exactly one product — the same barcode on several items causes identifier conflicts and disapproval. | Each variant needs its own correct barcode; check for copy-paste between variants. |
Want to know which of your own products fail this requirement?
Audit my GTIN free →How to fix it in Shopify
- The barcode lives on the variant: Admin → Products → open the product → click the variant → Barcode.
- Bulk fix: Products → Export and fill the Variant Barcode column; re-import to write it back.
- Custom, handmade or one-off goods with no barcode: do not invent one — mark the item as having no identifiers (identifier_exists = false in your feed).
- Note for store scans: Shopify's public catalogue at /products.json does not publish the barcode field at all, so a store scan reports this check as 'not checked from this source' rather than blaming you. Paste your feed URL or upload your CSV to have GTIN checked.
How to fix it in WooCommerce
- Products → edit product → Inventory → GTIN, UPC, EAN or ISBN field.
- Bulk fix through Products → Export / Import using the GTIN, UPC, EAN, or ISBN column.
- If you use a barcode plugin with its own meta key, map that key to the gtin column in your feed plugin.
Worth knowing
- Numbers pasted from a spreadsheet lose leading zeros: a 13-digit EAN becomes 12 digits. Format the column as text before exporting.
- Shopify SKUs are not barcodes. A SKU in the gtin column fails the length and checksum rules.
How FeedGuard checks it
- We take the digits only, then check the accepted length (8, 12, 13 or 14), recompute the GS1 mod-10 check digit over the value you submitted, and test the prefix ranges Google excludes (02, 04, anything starting with 2, and the 98–99 coupon ranges).
- We also count barcodes across the whole catalogue: the same GTIN on more than one item is reported as an identifier conflict.
- A GTIN in an unreachable column (a Shopify store scan, where the public catalogue publishes no barcode) is reported as 'not checked from this source' — never as a failure.
Every failure names the field and shows the value at fault, counted over up to 250 products per scan. A requirement that does not apply to an item is left out of both sides of the score rather than counted as a pass, and a requirement our source cannot see at all is excluded from the score and listed as “not checked from this source” with the reason. Where a value can be corrected without inventing anything, the row is fixed in the corrected CSV you can download; anything we would have to make up (a real barcode, a brand, a price, a category) is listed for you to supply instead.
What each kind of scan can see
A store scan reads the public catalogue the store itself publishes (Shopify's /products.json). A pasted feed URL or an uploaded CSV is the file the shopping platform reads, so every attribute can be judged against it. This is the difference that decides whether a check can run at all.
| Attribute | Store scan (Shopify) | Your feed URL or CSV upload |
|---|---|---|
| gtin | not published — check skipped Shopify's public catalogue does not publish the barcode/GTIN field at all — the payload this audit read contains no barcode value on any variant. A missing barcode here would be our blind spot, not your data, so no GTIN check was run. | read from your file read from your file |
A store scan cannot see gtin — this check is skipped there and excluded from the score.
Shopify's public catalogue does not publish the barcode/GTIN field at all — the payload this audit read contains no barcode value on any variant. A missing barcode here would be our blind spot, not your data, so no GTIN check was run.
Paste your feed URL or upload your CSV to have it checked.
Read the engine's own rules for this requirement on the results page: every failing row links back to this guide. All 49 checks are listed on what we check.
Run the free audit on your store
Paste your store domain, paste your product feed URL, or upload a product CSV. You get a scored report of every requirement above, the products failing each one, the exact fields at fault, and a corrected CSV to download. No account, no card.
Run the free audit on your storeA store scan reads the public catalogue and skips the attributes it cannot see (listed above); a feed URL or CSV gets the full audit.
Other identifiers — gtin, brand, mpn requirements
- Brand
Required for new products: the brand shoppers recognise, not your own storefront name.
- MPN (manufacturer part number)
Required when the product has no manufacturer-assigned GTIN — a SKU is usually not a part number.
- identifier_exists
A flag that must match what you actually submit: true or false, never 'no', '0' or 'N/A'.