
Summarize with AI
Why Your Odoo Products Keep Getting Disapproved on Google Shopping (And How to Fix It)
Key takeaways:
- Most disapprovals on Odoo stores come from feed data that no longer matches the live product page.
- Each Merchant Center error traces back to a specific Odoo field, so fixes belong in Odoo, not in the exported file.
- Product variants, pricelists, and tax display settings cause errors that generic feed guides rarely cover.
- Google retired the Content API for Shopping in August 2026, so older custom Odoo connectors may now fail silently.
- Images under 500 x 500 pixels will be disapproved from January 31, 2027, which makes an image audit urgent.
Odoo Google Shopping product disapproval is rarely random. In most cases, Google compares the product data in your feed with your live product page, finds a difference, and removes the listing from Shopping ads and free listings until the two match again.
For Odoo stores, these differences appear more often because product data lives in several places at once. Prices sit in price lists, stock sits in warehouses, and variants sit under a shared template. Meanwhile, Google expects one clean, consistent record per item.
This guide maps the most common Merchant Center errors to the Odoo fields that cause them.
It also covers the 2026 changes to Google’s API and image rules, a step-by-step fix process, and a checklist to run before every sync.
How Google Merchant Center reviews your products
Google Merchant Center checks every product against two things: its product data specification and the landing page the product links to. Most cases of Odoo Google Shopping product disapproval start with this two-part check. When either check fails, the product receives an issue with one of three severity levels.
Follow these steps in order.
- Warning: The product still shows, but with limited reach. Google often uses warnings to flag rules that will soon become mandatory.
- Disapproval: The product stops serving in shopping ads and free listings until the issue is fixed.
- Account suspension: Repeated or serious Google Merchant Center policy violations, such as misrepresentation, can remove the entire catalog.
As a result, a warning today can turn into a disapproval later.
For example, Google’s 2026 product data specification update introduced warnings for images below 500 x 500 pixels in April 2026, with enforcement starting January 31, 2027.
Stores that ignore these warnings now will see a wave of disapprovals early next year.
In addition, Google crawls your Odoo product pages on its own schedule. So even a feed that was correct on upload can fall out of compliance once someone changes a price or stock level in Odoo without resyncing.
9 Google Shopping product data errors and their Odoo source
Every Google Shopping product data error points to a field, a setting, or a sync gap inside Odoo. The table below connects each common Merchant Center issue to where it starts in Odoo and how to fix it there.
| Merchant Center error | Where it starts in Odoo | Fix at the source |
|---|---|---|
| Mismatched value (price) | A website price list or discount changes the page price, while the feed still sends the base sales price. | Send the price from the same price list the website uses, and resync after every price change. |
| Mismatched value (availability) | On-hand stock drops to zero, but the feed still says in stock. | Sync availability from the forecasted or on-hand quantity on a short schedule. |
| Price incl. or excl. tax mismatch | The website shows tax-included prices, while the feed sends tax-excluded ones, or the reverse. | Match the feed to the website's tax display setting for each target country. |
| Invalid or missing GTIN | The Barcode field holds an internal code, or every variant shares one barcode. | Store a real GTIN on each variant, and set identifier_exists to no only for custom or own-brand items. |
| Missing brand | No brand field on the standard product form | Add a brand field through a custom field or module and map it to the feed |
| Product category issues | eCommerce categories follow internal logic, not Google's taxonomy. | Map each Odoo eCommerce category to a Google product category once, with product-level overrides. |
| Duplicate or broken variants | Variants of one template are sent without a shared group ID. | Send each variant as its own item, linked by an item_group_id taken from the product template. |
| Image too small or invalid | Low-resolution uploads or placeholder images on the product | Replace images below 500 x 500 pixels; Google recommends 1500 x 1500 or above. |
| Landing page unavailable | Product unpublished on the website, or pages blocked for Google's crawler | Exclude unpublished products from the feed and check robots rules for product URLs. |
Notably, the last four errors rarely appear in a one-off export. They surface as the catalog grows, which is why they often catch teams off guard.
Fixing them properly usually involves custom fields and mapping logic, which is where Odoo customization services save the most time.
Why Odoo product feed errors happen more often
Odoo is built as an ERP first, so its product model serves sales, inventory, and accounting together. That flexibility is useful for operations.
However, it means a single product can carry several valid prices and stock figures, and the feed has to pick the one Google will see on the page.
The main causes fall into four groups:
- Several sources of truth: Pricelists, multi-company setups, and multiple warehouses each produce a different correct value. A feed that reads the wrong one creates a mismatch.
- Template and variant structure: Odoo stores shared details on the product template and specific ones on each variant. Google needs every variant as a full item, so missing fields get copied or left blank.
- Multi-country selling: Stores selling across the GCC, Europe, or the US need prices in local currency with the right tax treatment for each feed. One blended feed rarely meets every market’s rules.
- Manual exports: A CSV exported on Monday is out of date by Tuesday afternoon. Consequently, the gap between Odoo and the feed grows with every price change.
The 2026 API change behind sudden Odoo Google Shopping sync errors
If your feed worked for years and then started failing, check how it connects.
According to Google’s deprecation notice, the Content API for Shopping reached its sunset date on August 18, 2026, and requests from clients without an extension began failing intermittently with HTTP 410 errors from September 1, 2026.
Many older Odoo Google Shopping integration modules and in-house scripts were built on that API.
As a result, products may stop updating while the old data slowly drifts into disapproval.
Moving these connectors to the Merchant API is a development task, and it is a good moment to review the whole Odoo ecommerce integration with Odoo development services.
Policy and account-level issues behind disapprovals
Some cases of Google Merchant Center product disapproval have nothing to do with a single product field. Instead, they come from account settings or Google Merchant Center policy violations, which can affect every product at once.
- Misrepresentation: Missing contact details, unclear pricing, or claims Google cannot verify can trigger this policy. Your Odoo website needs a visible contact page, business address, and accurate product claims.
- Returns and shipping: Merchant Center expects a return policy and shipping settings for each target country. Missing settings appear as product issues, although the fix sits in the account.
- Website verification: Google must verify and claim your website domain. A domain change, or a new site in an Odoo multi-website setup, can break this link.
- Restricted products: Supplements, alcohol, and similar categories face extra rules in each country. Therefore, review them before adding them to the feed.
Because these issues sit outside product data, fixing the feed alone will not clear them.
How to fix Google Shopping disapproved products from Odoo

The fastest way to fix Google Shopping disapproved products is to work from Google’s diagnostics back to Odoo, rather than editing the feed file directly. Follow these steps in order.
- Export the issue list: In Merchant Center, open Products, filter by issues, and download the affected items. This shows how many products each error touches.
- Sort by impact: Fix disapprovals before warnings, and start with the error affecting the most products. Usually, one root cause explains dozens of items.
- Trace each error to its Odoo field: Use the table above to find where the wrong value comes from, such as a pricelist, a barcode, or a category.
- Fix the data in Odoo: Correct the field on the product or variant itself. Otherwise, the next sync will send the same error back to Google.
- Resync and request review: Push the updated products to Merchant Center. Data errors usually clear after reprocessing, while policy issues may need a manual review request.
- Watch the next crawl: Check the products again after Google recrawls your pages. If the error returns, the feed is still reading from the wrong source.
For stores with thousands of SKUs, steps 3 and 4 take the most effort. In that case, Odoo product feed optimization works best as a one-time cleanup followed by automated rules, not as a weekly manual task.
Pre-sync checklist to prevent Google Shopping product feed issues
Most Google Shopping product feed issues can be caught before Google sees them. Run this checklist before each major sync and after any catalog-wide change such as a sale or a new product line.
- Feed prices come from the same price list and currency as the website
- Tax treatment in the feed matches the website for each target country
- Stock status updates within hours, not days, of a change in Odoo
- Every variant has its own GTIN, or identifier_exists is set correctly
- Brand is filled for every product that is not custom-made
- Each eCommerce category maps to a specific Google product category
- Variants share an item_group_id taken from their product template
- All main and additional images are at least 500 x 500 pixels
- Unpublished or archived products are excluded from the feed
- Shipping and return policies are set in Merchant Center for every country
- The connector uses the Merchant API, not the retired Content API
In practice, the last item is the one most teams have not checked.
Similarly, the image rule deserves attention now, because Google’s image size guidance confirms that undersized images will lead to disapprovals once enforcement begins.
When to bring in an Odoo developer
Some fixes are simple data entry, such as adding a brand or replacing an image. Others need changes to how Odoo stores and sends data. It usually makes sense to hire an Odoo developer when:
- Errors return after every fix: The feed is reading from the wrong field, pricelist, or warehouse.
- You sell in several countries: Each market needs its own currency, tax logic, and feed.
- Your connector predates 2026: It may still depend on the retired Content API.
- Fields are missing: Brand, GTIN per variant, or category mapping needs custom fields.
Also, if your store is still being set up, building the feed rules into your Odoo implementation from day one avoids most of these errors entirely.
Conclusion
Odoo Google Shopping product disapproval is almost always a data consistency problem. The feed says one thing, the product page says another, and Google sides with the page.
Therefore, the lasting fix is to correct each value at its source in Odoo and keep the feed synced on a short schedule.
Start with the error-to-field table, run the pre-sync checklist, and confirm your connector uses the Merchant API. Then, audit your images before Google’s January 2027 deadline arrives.
FAQs
Similar Blogs


Odoo Shopify Connector: Sync Orders, Products, and Inventory in Real Time

Odoo and TallyPrime Integration: A Practical Guide to Connected Business Operations

Is XML-RPC removed in Odoo 20? The updated JSON-2 API timeline





