How to investigate price mismatch in Merchant Center

A price mismatch involves your feed, landing page or checkout. A static file checker cannot establish a mismatch without reading and interpreting the live offer.

Reviewed October 4, 2026 · Independent guidance · Manual/live investigation; not a performed scan check

What does this issue mean?

Google expects the submitted offer price and currency to match what shoppers can purchase. A mismatch can be caused by a stale feed, a selected variant with a different amount, a sale schedule, tax presentation or a page that changes by location. The feed may be perfectly parseable while the live page disagrees.

Why this happens

Dynamic themes can initially render a parent minimum price before showing the selected variation. Discounts may be visible only after an interaction or restricted to members. Currency-switching and region-specific pages can also show different amounts to crawlers and shoppers. Diagnose the exact offer URL rather than comparing an unrelated product listing card.

How to diagnose and fix it

Record the submitted product ID, link, base price, sale price and currency from the current feed snapshot.
Open that exact public offer URL without a logged-in or member discount and select the submitted variant.
Compare visible price, structured data and checkout, including any target-country tax presentation and minimum quantity.
Correct the inconsistent source, feed schedule or page rendering, then resubmit and review Merchant Center diagnostics after processing.

Before and after example

The examples are illustrative. Replace them with verified information for your own offer; copying an example identifier, amount or URL would introduce incorrect data.

Before

Feed: 19.99 USD
Public selected variant: 24.99 USD

After review

Feed: 24.99 USD
Public selected variant: 24.99 USD

Feed Doctor does not implement live price comparison in this MVP. It can validate submitted formats and provide an affected-record audit, but it must not label a format pass as a price-match pass.

Shopify fix

Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies price. If a separate feed app generates your export, inspect its mapping instead of assuming the channel settings control that file. Change verified source data, save it, and obtain a fresh export.

Compare one affected variant and one previously correct offer before making a bulk change. Do not change stable IDs just to improve a report score. If the issue involves identifiers, verify whether the connector reads barcode, brand or manufacturer reference data. If it concerns a live page or shipping account setting, a feed-column edit alone may not resolve it.

WooCommerce fix

Open the relevant product or variation and inspect the attribute consumed by your Google feed integration. Google for WooCommerce can map product attributes into feed attributes; third-party feed generators may use different mappings. Check both the stored value and the exported result, especially when parent attributes are inherited by variations.

Update the source value or mapping deliberately and regenerate the feed. Keep product identity, currency and variant relationships consistent. Avoid editing only a downloaded snapshot if a scheduled exporter will replace that change. For an account or website issue, repair the effective configuration and public offer as well as reviewing the file.

Verify the repair before submitting

Keep the original feed as a backup and compare the same affected product IDs in the regenerated file. Confirm that the expected product count remains unchanged and that no unrelated fields disappeared. If you applied a bulk rule, inspect offers outside the original affected set as a control; an overly broad mapping can fix one problem while creating another.

Run a new static scan, then separately check live product information and your Merchant Center diagnostics. File format validation cannot determine every policy, account, image or website condition. Processing and recrawling take place in Google’s systems, so a corrected file is not an immediate promise of approval. Use the actual updated diagnostics to decide whether additional investigation is required.

Scan your feed for this issue

Check all parsed products in an XML, CSV or TSV feed. Preview the score and issue samples free; unlock affected-product details and downloadable reports with a one-time payment. Live page checks described above are not performed by this scanner.

Check My Feed

Frequently asked questions

Does this finding always mean my product is disapproved?

Feed Doctor does not implement live price comparison in this MVP. It can validate submitted formats and provide an affected-record audit, but it must not label a format pass as a price-match pass.

Can Feed Doctor fix price automatically?

This MVP does not run the live or account-level checks needed to establish this issue. It supplies static feed diagnostics and this manual investigation workflow.

Should I fix the exported file or my store?

Correct the source product or feed integration whenever possible. A downloaded file edit may be overwritten by the next scheduled export. Keep a backup and compare the exact affected IDs in a fresh feed snapshot.

Do I need to connect Google to scan a feed?

No. Feed Doctor accepts a Google-format XML, CSV or TSV file, or a public HTTPS feed URL. It checks the feed without accessing your Merchant Center account. Reports are private to your browser and expire after 7 days.

Related feed issues

Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.