In short
- Google Merchant Center reads your feed, then checks it against the product page it can see.
- Magento price mismatches often come from special prices, catalogue price rules, VAT display, store view settings or old feed files.
- Configurable products and simple products can show different prices if the feed maps the wrong item.
- Disapprovals can also come from missing GTIN, brand, stock status or image problems.
- Webgentic for ecommerce does not edit product data, so feed work goes through Store care or the Webgentic Orchestrator.
What a Magento Google Shopping feed does
A Magento Google Shopping feed is a file that lists products for Google Merchant Center. It normally includes fields such as title, description, price, sale price, availability, link, image link, brand and GTIN.
Merchant Center uses the feed as the source of the advert data. It then checks the product page. If Google sees a different price, a different stock status, a blocked image or missing product data, it can warn you or disapprove the product.
This is why a feed can look fine in Magento but still fail in Merchant Center. The feed is only one view of the truth. Google also checks what shoppers can see on the live page.
For Magento stores, the hard part is that the price on the page may not be a simple product price. It can come from a special price, a catalogue price rule, a customer group, a store view, a tax rule, a currency setting, or the selected child product under a configurable product.
Why prices stop matching the store
Most price mismatches on a Magento shopping feed fall into a few groups.
| Cause | What happens | What to check |
|---|---|---|
| Special prices | The page shows a sale price, but the feed sends the base price. | Check price, sale_price, dates and feed mapping. |
| Catalogue price rules | The store applies a rule at display time, but the feed does not. | Check rule status, rule index, feed source and customer group. |
| VAT display | The store shows prices including VAT, but the feed sends prices excluding VAT, or the other way round. | Check tax display settings for the store view used by the feed. |
| Wrong store view | The feed uses one store view and the product page uses another. | Check currency, language, tax, URL and product status per store view. |
| Cron or indexers | The feed was meant to rebuild, but Magento did not run the job. | Check cron, indexer status and last feed file time. |
| Configurable products | Google sees the parent page, while the feed price comes from a child product, or the wrong child. | Check parent and child mapping. |
| Cached feed file | The old XML, CSV or TSV file is still being served. | Check file path, cache, CDN and server rewrites. |
Special prices are a common trap. Magento can show a special price only between set dates. If the feed generator ignores those dates, or sends the base price as price without sale_price, Google can see a mismatch.
Catalogue price rules cause the same kind of problem. A rule may make the front end cheaper than the base price. If the feed module reads raw product data instead of the indexed final price, Merchant Center can see a different figure.
VAT is another frequent cause in the UK. A store may show prices including VAT to shoppers, while the feed sends values excluding VAT. Google does not care that both are valid inside Magento. It compares the data to the landing page.
Store view and currency settings also matter. If the Google Shopping Magento feed is built from the default store view, but the advert lands on a UK store view, the product can fail even when both parts are correct in isolation.
Other feed errors that lead to disapproved products
Price is not the only reason for disapproval. Merchant Center can also reject products when required product data is missing or does not match the page.
Common issues include:
- Missing GTIN where Google expects one.
- Missing brand, or a brand that does not match the page.
- Availability set to in stock in the feed, while the page says out of stock.
- Availability set to out of stock in the feed, while the page lets shoppers buy.
- Main images that are blocked, too small, broken or not the product shown.
- Product links that redirect to the wrong store view.
- Product pages that cannot be reached by Google.
- Titles or descriptions that do not describe the product clearly.
Availability mismatches are easy to miss on Magento. Stock can come from simple products under a configurable product. A parent product may look available, while the selected child is not. Multi Source Inventory can add more places to check.
Image issues can also be boring but costly. A feed may point to an old image path. A CDN may serve a blocked image. A theme may show a different main image from the one in the feed. Google checks what it can fetch, not what the admin panel says.
A practical check from feed to store
Do not start by changing feed settings. First, prove where the mismatch begins.
Use this check:
- Pick one affected product in Merchant Center.
- Copy the exact item ID from Merchant Center.
- Find the same item in the feed file.
- Record the feed price, sale price, currency, availability, link, image link, GTIN and brand.
- Open the product page in a clean browser session.
- Check the visible price, VAT display, currency and stock message.
- Check whether the page is a configurable parent or a simple product.
- Check the Magento admin value for the parent and any child products.
- Check active special prices and dates.
- Check active catalogue price rules.
- Check indexer status.
- Check the last run time for cron and the feed job.
- Fetch the feed file from the public URL and confirm it is the same file you checked.
- Clear only the cache needed for the feed path if an old file is being served.
- Recheck the product in Merchant Center after the corrected feed is submitted.
The key point is to compare the same product in the same store view. If the feed item is a child product but the URL opens the parent page, write that down. If the feed comes from the default store view but the link opens another, write that down too.
For agencies, this is also the point where a repeatable checklist helps. Feed faults are often small. The danger is changing the whole feed setup when the problem is one store view, one stale file, or one product type mapping.
Example: a feed module in place of a paid extension
A Magento store paid every month for a feed extension.
The Webgentic Orchestrator built a feed module and its prices were checked against the store. The store owns the module and no longer needs the paid extension.
Example based on a real job, details changed.
Paid extension or owned Magento product feed module
A paid feed extension can be a good fit when it is well maintained and matches the store setup. Many stores use one because it is faster than writing a module from nothing.
The problem starts when the extension becomes a black box. If it cannot express the store price logic, or if it is hard to test, you may spend time working around it. You may also depend on the extension vendor for a fix that only affects your store.
An owned Magento product feed module can be simpler. It can be written to match the store rules exactly. It can include only the fields you need. It can be tested against known products, store views and tax settings.
This does not mean every store should replace its extension. A working extension should be left alone. But if the same feed errors keep returning, or the feed logic is tied to store specific rules, owning the module can make sense.
At Webgentic, this kind of product data and feed work is not done by Webgentic for ecommerce. The self-serve request bar can change CMS pages, CMS blocks, category text and design config on Magento. It cannot edit products, prices or stock.
Feed jobs go through Store care or the Webgentic Orchestrator. In Store care, developers run the store job list through the Orchestrator, including feeds, patches, speed, checkout and fixes. A developer checks each plan, and the store approves it. In the Orchestrator for agencies, every job follows Brief, Plan, Approve, Deliver, Prove, with risk and the way back written into the plan, and by default nothing changes until the plan is approved.
What no Magento feed fix can control
Some outcomes sit with Google. A clean feed does not force Google to approve every product. Merchant Center can still apply policy rules, crawl timing, account checks and product data requirements.
A Magento feed fix can control the data you send. It can make the price, stock, link and image match the page. It can add missing fields where the data exists. It can rebuild the file and prove what changed.
It cannot make Google accept a product that breaks policy. It cannot make Google crawl at the exact moment you want. It cannot invent GTINs where none exist. It cannot fix a landing page that hides key product data from shoppers or bots.
So the aim is not to guess what Google wants. The aim is to remove clear Magento faults first. Then any remaining Merchant Center issue is easier to read.