If your Google Merchant Center account is throwing Invalid value [gtin] or Incorrect identifier [gtin] and products are sitting disapproved three weeks out from Click Frenzy, the cause is almost always one of four things: a barcode with a broken check digit, a number that Excel mangled on import, a resold barcode that GS1 has registered to somebody else, or your own-brand product that never had a GTIN and shouldn't be claiming one. Shopify now checks barcodes against the GS1 registry at the moment you type them, which means you can find and fix most of this inside the admin instead of waiting for Google's crawler to tell you. Do it in the first week of November. Google's review queue runs slower in peak, and a product that gets approved on 22 December is a product that missed Christmas.
What Google is actually complaining about
Shopify has one field for this: Barcode (ISBN, UPC, GTIN, etc.), which sits on each variant, under Inventory, on the product page. The Google & YouTube sales channel maps that field straight to Google's gtin attribute. There is no transformation, no cleanup, no padding. Whatever string is in that box is what Google receives.
So the error messages split into two groups. Invalid value means the number itself is malformed: wrong length, failed check digit, letters or spaces in it, or a value in a range Google reserves. Incorrect identifier means the number is structurally fine but Google doesn't believe it belongs to you, usually because the GS1 prefix is licensed to a different company than the brand you've submitted.
Missing barcodes behave differently. An empty GTIN on a resale product you didn't manufacture typically triggers a warning and depressed performance rather than an outright block, but Google will disapprove it outright once it recognises the brand as one that assigns GTINs. That distinction matters because the fix is different for each.
The GS1 check Shopify added, and why it lands at an awkward time
From late October, Shopify validates what you paste into the barcode field against the GS1 registry rather than just storing it. Enter a legitimate GTIN and it can pull back the registered product details for you. Enter a number with a bad check digit, or one that GS1 has no record of, and you find out immediately.
The timing is the whole point. Merchants who have been quietly carrying bad barcodes for two years are seeing them surface for the first time in the exact fortnight when Shopping traffic is at its heaviest. Two weeks later and those SKUs sit disapproved through Black Friday, Cyber Monday and the Australia Post parcel cutoffs. Finding the problem in the admin in early November is a Tuesday afternoon of work. Finding it in Merchant Center on 10 December is a lost month.
Check the maths yourself before you blame the feed
A GTIN-13 is twelve digits plus a check digit, and the check digit is arithmetic you can verify by hand. Take the first twelve digits, multiply alternate positions by 1 and 3 starting with 1 from the left, add them up, then subtract the total from the next multiple of ten.
Using a made-up number on an Australian prefix, 931234567890:
- 9×1 + 3×3 + 1×1 + 2×3 + 3×1 + 4×3 + 5×1 + 6×3 + 7×1 + 8×3 + 9×1 + 0×3
- = 9 + 9 + 1 + 6 + 3 + 12 + 5 + 18 + 7 + 24 + 9 + 0 = 103
- 103 mod 10 = 3, so the check digit is 10 − 3 = 7
The full GTIN is 9312345678907. If your supplier's spreadsheet gave you 9312345678905, Google rejects it and it is not Google's fault. We have had suppliers send us whole price lists where the last digit had been retyped by hand at some point and never checked again.
The other classic is Excel. Open a CSV of barcodes in Excel, let it treat the column as a number, and a 13-digit GTIN becomes 9.31235E+12, or a UPC-12 loses its leading zero and arrives at Shopify as eleven digits. Both import cleanly. Both get disapproved. Format the column as Text before you touch anything, or build the import out of Google Sheets with the column locked to plain text.
Own-brand products that genuinely have no GTIN
This is the case Australian merchants get wrong most often, because so much of the local D2C market is own-label: candles, skincare, activewear, pet food, coffee. You made the product. Nobody ever assigned it a GS1 number. You have two legitimate options and one illegitimate one.
The illegitimate one is inventing a number, or borrowing a similar product's barcode, or reusing your SKU in the barcode field. Shopify's GS1 check now catches most of this at entry, and Google catches the rest.
Option one: buy a proper GS1 licence and assign real GTINs. Worth it if you sell wholesale, if a retailer has asked for barcodes, or if you plan to list on marketplaces that require them.
Option two, and the right call for a lot of small catalogues: declare that no identifier exists. In Google's schema this is the identifier_exists attribute set to no. In the Google & YouTube channel the lever is a product-level metafield, historically mm-google-shopping.custom_product, set to TRUE; if you run your feed through a third-party app like Simprosys or DataFeedWatch you can map identifier_exists directly and in bulk, which is faster when you have a few hundred SKUs to flip. Send your brand and, if you have one, an MPN alongside it. Google then stops expecting a GTIN for that item and the warning disappears.
Do not use this as a blanket switch across the catalogue. If you stock other people's brands and declare that no identifier exists, Google will eventually match the product to its own catalogue, see that a GTIN does exist, and disapprove you for a misdeclaration. We have cleaned up two or three accounts where someone set the metafield at the collection level to silence warnings and created a much worse problem a month later.
Where resold barcodes come unstuck
Search for cheap barcodes and you'll find sites selling "lifetime" numbers for a few dollars each. These are almost always slices of a GS1 prefix that was licensed to a company in the 1990s and subdivided afterwards. The numbers are structurally valid. The check digit passes. And the registry still shows the prefix belonging to someone else entirely.
Google resolves brand ownership against GS1 data. When the brand on your feed is your brand and the prefix belongs to an unrelated business, you get Incorrect identifier, and no amount of resubmitting fixes it. Now that Shopify runs the same lookup, you'll see the mismatch in the admin as well.
GS1 Australia is the only source that solves this properly. It's an annual licence rather than a one-off purchase, and for a single-brand store with a modest SKU count the smallest allocation usually covers you. If the cost doesn't stack up against your Shopping revenue, declare no identifier and move on. That's a legitimate answer, not a workaround.
EAN or UPC: does it matter which one goes in the Shopify barcode field?
Not really. Both are GTINs. A UPC is a GTIN-12 and came out of the North American system; an EAN is a GTIN-13 and is what you'll get from Australian and European suppliers. Google accepts 8, 12, 13 and 14-digit GTINs, so a UPC from US-sourced stock works fine as-is. You don't need to pad it with a leading zero, though doing so produces a valid GTIN-13 for the same product if you prefer consistency across the catalogue.
What you must not put in that field: ISBN prefixes on non-book products, internal store codes in the 02 and 2 ranges (those are reserved for variable-weight retail items and Google rejects them), coupon codes in the 99 range, or your own SKU. Keep the SKU in the SKU field where it belongs.
One GTIN per variant, not one per product
Apparel and anything sized is where this falls over. A GTIN identifies a specific sellable unit, so a tee in S, M and L is three GTINs. Copy the same barcode across all three variants and Google will either collapse them or flag an identifier mismatch, and you'll see a chunk of your catalogue go dark for no obvious reason.
The quickest way to audit this is the product CSV export. Pull the Handle, Option1 Value and Variant Barcode columns, sort by barcode, and look for any value appearing more than once. If you have more than a couple of thousand variants, it's worth having a developer script the check and the re-upload rather than doing it by hand; we put a developer on jobs like this for a day or two and it comes back clean.
Fixing Google Shopping feed errors before the Australian peak
A rough timeline that works for a November to December trading period:
- Now: export the full product CSV, run the barcode column through a check-digit validation, and separate the list into three buckets: broken numbers, missing numbers on resale brands, missing numbers on own-brand items.
- Same week: chase suppliers for correct GTINs on the resale bucket. This is the slow part, because it depends on someone else answering an email.
- Before Click Frenzy: set the no-identifier declaration on the own-brand bucket and re-sync the feed. Allow three business days for review, longer in peak.
- While you're in there: confirm your prices include GST. Australian feeds are submitted tax-inclusive, and a price mismatch between feed and landing page is the second most common reason we see items disapproved at this time of year. If you run a separate price for Afterpay or Zip messaging, make sure the feed is reading the actual product price and not a display variable.
- Mid-December: nothing. If you are editing feed attributes a week out from the Australia Post cutoffs, you've already lost the window.
Put a number on what disapprovals cost you. If Shopping sends 2,000 sessions in a typical November week, converts at 1.8% and your AOV is $95, that's 36 orders and roughly $3,400 a week. Lose 20% of the catalogue to identifier errors for three weeks and you're down around $2,000 of revenue, before you count the Performance Max learning you've thrown away by starving the campaign of inventory mid-flight. Your numbers will differ. Run them anyway, because that figure is what decides whether a GS1 licence is worth the money.
Quick answers
Where do I add a GTIN in Shopify? Product page, scroll to Inventory, the field labelled Barcode (ISBN, UPC, GTIN, etc.). It's per variant. For bulk edits, use the Shopify bulk editor or a product CSV import with the Variant Barcode column.
Can I sell on Google Shopping without GTINs at all? Yes, for products you manufacture. Submit brand and MPN, declare that no identifier exists, and expect slightly weaker matching into comparison surfaces. For products you resell, no: you need the manufacturer's GTIN or the listing will be throttled and eventually disapproved.
Will Shopify's GS1 check break my existing products? It doesn't retroactively delete anything. It flags problems when you edit or add a barcode. Old bad values sit there until you touch them, which is why an export-and-audit beats waiting for the admin to tell you.
Do I need GS1 Australia specifically, or will any GS1 office do? Any GS1 member organisation issues globally valid numbers, but licensing through the office in the country where your business is registered keeps the registry record consistent with the brand on your feed, which is exactly what Google is checking.
If you'd rather not spend a week in CSVs during your busiest trading month, send us your store and your Merchant Center diagnostics and we'll tell you which bucket each disapproval falls into. Our free audit covers feed health, and the team that works with Australian stores has done this cleanup often enough to know where the supplier data usually breaks.


