Van Born Labs / Guides / Marketing & Ads
How to Fix Google Merchant Center Feed Errors
A practical pass through the GTIN, price, title and availability problems that get products disapproved — and a hard rule: never invent a GTIN.
By Arkadiusz Van Born. Updated 2026-11-18 (America/Phoenix).
A Google Merchant Center disapproval is usually not a mystery, even when the email feels like one. Most rejected or demoted products fail on a short list of mechanical problems: a price that is not in the form 19.99 USD, a GTIN that is the wrong length or has a bad check digit, a title in ALL CAPS with “FREE SHIPPING!!!”, an availability value the feed specification does not recognise, or a Shopify export that turned a barcode into scientific notation.
You can fix these by hand. For a catalogue of 30 products you should. For a catalogue of 3,000, you want a repeatable, conservative process that will not invent data Google can later treat as misrepresentation. This guide is that process.
Start with the system of record, not the error email
Download the feed you actually submit — or export it from Shopify, WooCommerce or your PIM — and work on that file. Do not patch products one at a time in the Merchant Center UI if the next scheduled upload will overwrite your patches.
Keep three artefacts every time you do a pass:
- The original file, untouched.
- A working copy you will edit.
- A change log (a third sheet is enough) with the product id, the field, the before value, the after value, and why.
If you cannot explain a change in one sentence, do not make it. That rule alone prevents a lot of damage.
Van Born Labs
Try it live
Paste a public CSV, TSV or Google XML product feed. The demo checks the first 15 products and does not return a fixed file.
The errors that appear over and over
Required attributes
Google Shopping still expects the basics on every item: id, title, description, link, image_link, price, availability, and a brand or identifier, plus condition in many cases. If any of those are empty, fix the source catalogue first. A fixer tool cannot invent a product name you do not have.
link and image_link should be absolute https URLs, with no spaces. A common export bug is a space in a file name, or an http:// image URL that your site long ago redirected. Encoding the space and upgrading the scheme are safe. Inventing an image you do not host is not.
Price format and currency
The standard form is a number and an ISO currency, such as 19.99 USD or 12.50 EUR. Frequent problems:
- A bare
19.9with no currency. - A currency symbol in the wrong place, or a European decimal comma (
1.299,99) left unnormalised in a US feed. - A zero or negative price, which should be flagged, not silently flipped to
0.01. - A
sale_pricethat is higher than or equal toprice. If the sale is not actually lower, drop the sale price and log it. Do not invent a discount.
When you reformat a price, keep the value. Turning 19.9 into 19.90 USD is a format fix. Turning it into 29.99 USD is a different product.
GTINs: the hard rule
GTINs (UPC, EAN, JAN, ISBN-style identifiers) are 8, 12, 13 or 14 digits and include a check digit. If the check digit does not match the rest of the number, the GTIN is wrong.
Safe GTIN work looks like this:
- Strip spaces, hyphens and a leading apostrophe that Excel added to “keep the zeros”.
- Restore leading zeros only when the check digit proves the restored number. Spreadsheet damage such as
8.6E+11is recoverable sometimes, and only then. - Leave the field empty if you cannot prove the code.
Never generate a GTIN. Do not copy a competitor’s barcode. Do not use a “GTIN generator.” Do not pad a SKU with extra zeros until it looks long enough. A missing GTIN can be a warning or a policy issue, depending on the product and the country. A fake GTIN is worse: it is a data-quality problem that can look like misrepresentation.
If you are not the brand and you do not have a real manufacturer code, it is honest to submit without a GTIN and use the identifier-exists flags correctly, rather than to mint a number.
Titles and descriptions
Merchant Center is unimpressed by shouting. Typical title issues:
- ALL CAPS.
- Promo stuffing: “FREE SHIPPING”, “SALE”, “!!!”.
- Titles far longer than the recommended length (commonly 150 characters is the line you should not cross).
- The same word repeated as a keyword list.
Safe fixes: sentence case, strip promotional phrases, truncate at a word boundary. Unsafe fixes: rewriting the title into something the product is not, or stuffing a different brand name.
Descriptions should be readable text. HTML left in from a Shopify or WooCommerce export can be stripped. Do not replace a thin description with marketing copy you invented if the original product data is empty — go back to the catalogue.
Availability and condition
Normalise obvious variants to the values the spec allows: in_stock, out_of_stock, preorder, backorder. “In Stock”, “yes”, “InStock” and similar can be mapped with a short dictionary. Do not map “unknown” to in_stock just to get the item approved.
Condition should be a recognised value (new, refurbished, used). Guessing “new” for a product you actually sell as used is a policy problem, not a formatting problem.
Apparel attributes and variants
Clothing and footwear often need color, size, gender or age_group, and variants need a stable item_group_id. Two important cautions:
- Do not flag a pair of bed sheets or a cosmetic as apparel just because the export has a Color column.
- When a Shopify Handle can honestly group variants, filling
item_group_idfrom it is reasonable. Do not invent a group that mixes different products.
Duplicates, encoding, and ragged CSV
Duplicate id values should be resolved, not hidden. If you append -2 and -3 to colliding ids, log it, and make sure those ids stay stable the next time you export.
Open the file in a way that does not destroy leading zeros or special characters. A Windows-1252 export pasted into a UTF-8 pipeline is a classic source of “mystery” title errors.
A checklist you can run in order
- Freeze the original file.
- Check that every row has the required attributes.
- Normalise prices and currencies; flag zero or negative prices for a human.
- Normalise availability and condition with a dictionary, not with guesses.
- Repair GTINs only when the check digit proves the repair; otherwise leave them blank and list them for the merchandiser.
- Clean titles and strip HTML in descriptions, without rewriting facts.
- Fix
httpimage links and spaces in URLs. - Fill
item_group_idonly where the source already has a variant grouping. - Scan for duplicate ids and ragged rows.
- Upload to a test feed or a small Merchant Center feed first, not straight to the production feed on a Friday afternoon.
If you work in Shopify or WooCommerce, export from the same stock path you will use in production. A hand-edited CSV that does not match the next app export will only buy you a week.
When a validator is worth it
On a small catalogue the checklist is enough. On a large one, or on a weekly regression check, you want something that applies the same conservative rules every time and writes the change log for you.
That is what Merchant Feed Doctor is for. It takes a Shopify export, a WooCommerce export, or a native Google CSV/TSV, reports each issue with a code and a severity, and applies only safe, deterministic fixes. It will reformat a price, sentence-case a shouting title, strip promo phrases, normalise availability, and restore a GTIN only when the check digit proves it. It will not invent a GTIN. You get a ready-to-upload TSV, a scored HTML report, and the change log.
You can run it as an Apify actor ($0.01 per product checked plus $0.25 per run, billed to your own Apify account; skipped rows such as Shopify drafts, gift cards and WooCommerce parent rows are not charged) or call the same engine as a RapidAPI listing if you want it inside an app or a workflow.
Use a validator the way you would use a spellchecker: it should catch mechanical mistakes and leave merchandising decisions to you. If a tool offers to “generate missing barcodes,” do not use that feature.
After you upload
Re-download or review the Merchant Center diagnostics after the new feed is processed, not only the “upload accepted” message. An accepted file can still have item-level disapprovals.
When a product is still disapproved, read the policy name. Some remaining issues are not feed syntax: misrepresentation, official-merchandise rules, or adult-content labelling will not be fixed by a tidier CSV. Those need a human and, sometimes, a change to how you sell the product.
Then schedule the same check. Most feed problems come back the next time someone adds a product in ALL CAPS or Excel reopens the GTIN column as a number. A weekly run against the latest export is less heroic than a quarterly panic.
Independent note: Merchant Feed Doctor is software I make at Van Born Labs. It is not affiliated with, endorsed by or sponsored by Google, Shopify or WooCommerce. Safe fixes only, and never a made-up GTIN.
Questions
How do I fix Google Merchant Center GTIN errors?
Repair formatting only when the check digit proves the restored number. Never generate or invent a GTIN, and do not copy a competitor’s barcode. A missing GTIN is better than a fake one.
What is the correct price format in a Google Shopping feed?
A number plus an ISO currency, such as 19.99 USD. Do not leave a bare 19.9, and do not invent a sale price that is not actually lower than the regular price.
Can I auto-fix a Shopify or WooCommerce export?
Yes, with conservative rules: reformat prices, clean shouting titles, normalise availability, and restore GTINs only when the check digit proves them. Review the change log before you upload to your production feed.
What is Merchant Feed Doctor?
A Google Merchant Center feed validator and auto-fixer by Van Born Labs. It takes Shopify, WooCommerce or CSV/TSV, applies only safe fixes, and returns a ready-to-upload TSV plus an HTML report. It never invents GTINs.
Tools mentioned
Related guides
Canonical URL: https://arkadiuszvanborn.com/labs/guides/how-to-fix-google-merchant-center-feed-errors. Support: arkadiuszvanborn@gmail.com.