A price mismatch is difficult to fix if you inspect only the visible shop price. Choose one affected variant and compare its record with the exact landing page linked by the feed. A different colour or delivery country can already produce a different comparison.

Inspect one record before the whole catalogue

Record the item ID, variant, target country, currency and time. Save the landing address supplied by the feed. Open it in a fresh session and check whether the same variant is selected.

Create a small comparison table:

LocationObservation
Product data sourcePrice, currency, availability and last transfer
Visible landing pageSelected variant and displayed values
Structured dataExtracted offer and associated product variant

Google lists inconsistent product data as a possible source of problems. Its merchant listing documentation describes offer information in structured data. Valid markup alone does not guarantee a particular appearance in Google.

Trace the difference back to its source

Fictional example: a blue variant costs 49 euros on the page. Its feed still says 45 euros because an export uses an old price column. A manually overridden Merchant Center value may be replaced by the next export. The lasting task is therefore to correct the source mapping and check the next transfer.

Compare update times too. An old export and an incorrect source column are different causes and need different corrections. Keep the previous record so the change remains traceable.

Agree a specific retest

After the change, compare the same variant again. Record the values, time and remaining messages. Variant and identifier mapping is a separate part of the review.

Product data & Merchant Center cleanup covers one source, one target country, one currency and up to 20 variants. Up to ten fields and three technical fault types are agreed. Google approval is not a promised outcome.

Technical sources: Google Merchant Center: Product data specification, Google Search Central: Merchant listing structured data.