Why are my products disapproved in Google Merchant Center?

This distinction comes first. An incorrect price on individual products calls for a different investigation from an account-level restriction. Record the message, time, affected item identifiers, target country and marketing method. A product can have different status information for different uses.

A representative sample makes the assessment more useful. Are only variants affected, only offers for Switzerland, or almost every item from one export? That gives us a working hypothesis. Resubmitting everything without understanding the cause may obscure the problem rather than solve it.

Google compares submitted product information with the landing page. Price differences can lead to disapproval. Its price mismatch guidance identifies causes including updates arriving at different times and conflicting structured information.

We would open an affected product in the exact variant and compare it with the submitted record. Does the currency match? Has a sale price already started in the store while the export still contains the old price? Does the destination address select the advertised version? The relevant offer is the publicly visible one, not a price shown only to a logged-in trade customer.

For German and Swiss offers, the target market, currency and landing page need to agree. An identical product name does not establish identical terms. This matters particularly when the ERP, store and export update at different times.

• Message: the exact disapproval wording and timestamp, rather than just a red indicator.
• Record: item identifier, variant, data source and last transmission time.
• Landing page: the submitted URL, redirects and accessibility without signing in.
• Offer: a direct comparison of price, currency, availability and relevant sale periods.
• Technology: rendered product information, export module, cache and connected systems.
• Verification: the corrected record, reprocessing and subsequent product status.

This assessment framework is not a replacement for Google’s full product specification. It helps the merchant, agency and ERP team investigate the same fault. Passwords and complete customer records do not belong in an unprotected email attachment for this purpose.

In PrestaShop, we follow the information from its source through price rules and variants to the storefront and export. If stock is managed in the ERP, an incorrect availability value should ideally be corrected there or in the transfer. Otherwise, a manual Merchant Center change may be overwritten by the next import.

Consider a hypothetical merchant who discounts one variant on Friday evening. The store displays the new price immediately, but the feed runs the following morning. We would coordinate updates and the promotion period, then test that transition again. This is a testing scenario, not a claimed customer case study.

PrestaShop is a useful foundation for such requirements because individual data flows and rules can be adapted. Clear responsibilities are essential. Another feed module will not automatically resolve an ERP mapping error. We discuss those dependencies in our PrestaShop ERP integration article.

First, we check that the corrected information appears in both the submitted record and the landing page. Then we inspect processing and current status in Merchant Center. A local correction is not confirmation that Google has already reviewed it again.

Google describes automatic product information updates as support for certain discrepancies. Regular data submissions remain necessary. We would treat this feature as a supplement, not a substitute for a reliable export. Account-level issues also require attention to the relevant policy message; fixing a price alone may not be sufficient.

Merchant Center approval does not guarantee a mention in an AI answer. The immediate benefit is consistent offers and the removal of specific barriers to Google product listings. The same maintenance prevents storefront content and machine-readable information from giving contradictory answers.

Our article on structured product data covers the foundations. This article focuses on practical Merchant Center troubleshooting. At sjmedia, we can connect Google Ads and Shopping management with technical PrestaShop work. A clearly described issue and affected items are enough to start defining a focused assessment, before deciding on larger store changes.