Skip to content

Merchant Center price mismatch after a sale or price change

Trace a Merchant Center price mismatch across the selected variant, landing page, structured data, and feed using one offer ID and one timestamp.

By Crawlito · 6 min read

In short

  • Use the exact offer ID, destination URL, currency, and variant from the affected item.
  • A sale can reach the storefront, structured data, feed, and cache at different times.
  • A clean session in the target market helps reproduce the public offer shoppers receive.
On this page

When Merchant Center flags a price mismatch after a sale, take one affected offer ID and compare its submitted price with the exact variant, currency, and price a new shopper sees at the submitted link. Record the time of each observation. The goal is to identify where the price diverges between the catalog and the landing page, including the structured data inside it. Google Merchant Center’s price mismatch guidance

Reconstruct one offer before changing the feed

Download or inspect the affected item from Merchant Center. Capture its ID, country, currency, landing URL, variant, regular price, sale price, and the effective interval when applicable. Save the processing timestamp if you can see it. Compare the processed item with the source file your catalog team originally sent. A feed rule or supplemental input can change the processed value even when the spreadsheet on somebody's desktop looks correct.

Now open the submitted URL in a clean session. Keep all query parameters that select a size, pack, or color. A landing URL for a three-pack can redirect to a default one-pack when a router strips the variant selector. Both pages might use the same product name and photograph, yet represent different offers. Record what is selected before touching any controls. Also check that an item described as a bundle can actually be bought in the quantity and at the price you submit.

Build a short record of the discrepancies. A fictional example might show offer KIT-BLUE-3, three units, USD 42 in the feed, USD 42 on the visible page, and USD 16 in the first matching JSON-LD object. That is enough evidence to investigate why the page emits a single-unit offer. It does not justify changing the three-pack feed price to 16. The product variant guide covers how to keep variant identity stable across URLs.

Compare sale boundaries across four systems

SystemEvidence to retainQuestion it answers
CatalogOffer ID, amount, currency, start and end with timezoneWhat did the merchant intend to sell?
Processed product dataActive regular and sale fields, latest processing timeWhat was submitted for this item?
Public pageSelected variant and immediately visible priceWhat can a new shopper see?
Initial structured dataRelevant Offer object, SKU and price currencyWhat price did the generated page describe?

Choose a timestamp just before a scheduled sale begins, one inside the interval, and one just after it ends. A scheduled storefront promotion can start at midnight in the local store timezone while an export job treats midnight as UTC. Write out the absolute times when diagnosing the change. Check that the published amount reverts at the end of the sale too. A process tested only on launch can keep an expired sale price active in the feed.

Look at the cache lifetime of a product page and of its separate price service. A page generated yesterday might embed the old structured amount while client-side code updates the visible price after loading. Opening two tabs five seconds apart may show both screens as correct while leaving a stale initial offer in both responses. The CDN freshness guide explains how to distinguish the origin change from its public delivery.

Reproduce the offer as a first-time shopper

Use a target-market landing URL with the advertised currency. Record whether the page negotiates a new country, asks for a postal code, or silently changes selection after loading. Google's troubleshooting guidance identifies location-based price changes, incomplete variant selection, minimum quantities, and delayed dynamic prices among the causes of mismatches. A useful test reproduces the advertised configuration without an employee discount, loyalty login, or previously saved cart.

Inspect the visible price, the bytes delivered to a fresh client, and the rendered structured fields. A product page can display a crossed-out list price, current sale price, installment amount, and a “from” price in one small panel. Mark the price associated with the actual unit the shopper is able to buy. If the advertised configuration cannot be selected, fix that broken path before investigating which parser the review system might have used.

For a developer handoff, include the exact steps and the smallest relevant snippet. Record which offer in a graph matches the SKU and variant. A page with recommendations for accessories may contain other valid prices. Searching the raw HTML for the first dollar sign and treating that figure as the primary price can send the team to the wrong component. The product schema guide explains how to inspect the connection between product and offer.

Fix the first system that publishes the wrong value

If export and page both inherit the wrong amount, correct the master catalog and let its normal downstream processes regenerate them. If the catalog and visible storefront are correct but the markup reflects a default color, change the mapping that creates the relevant offer. If the public page is stale at one hostname, refresh the appropriate cached representation and confirm its next regeneration uses the correct value as well.

For an ongoing promotion, prepare a small acceptance set with a regular item, a discounted item, a different-priced variant, and a product excluded from the promotion. Inspect them once during the campaign and once when it ends. If country-specific feeds exist, include the submitted URL and currency for each affected market. Changing an international catalog rule to repair one country can introduce a new mismatch elsewhere.

When price values agree, use the next steps and review controls described in the specific Merchant Center issue. Record the time your own checks passed and the separately reported review status. A normal public price now can coexist with an older enforcement record. Preserve the pre-fix sample so that if the mismatch recurs, you can determine whether the same offer and time boundary failed again.

Investigate a mismatch that appears only after a click

A store can serve a correct product URL when opened directly but change the price after a tracking redirect. Compare the link in the processed offer with the final address after the advertising or analytics hop. Write down whether each redirect preserves the selected pack, currency, and market. A general redirect to the product handle can silently discard the option that distinguishes the submitted offer from the less expensive default.

Run the same trace with a neighboring ordinary item that has no variants. If both links go through the same redirect but only the bundle loses its selection, you have a test case for the redirect owner. Reproduce it with a fresh browser and record the first hop where the submitted selector disappears. After correction, verify that reaching the page from the original submitted link produces the same purchasable item and price as the direct, fully specified landing URL.

Frequently asked questions

Can automatic item updates replace fixing the catalog?

Treat the source of the disagreement as the repair target. An update mechanism does not correct a storefront that repeatedly selects the wrong variant.

Should the page show a sale price only after sign-in?

Test the price advertised to the audience you target and check Google's conditions for membership or discount pricing. An employee or test-account view is insufficient evidence of the public offer.

Why did only a few products fail?

Compare the failing item IDs by variant selection, promotion schedule, currency, and cache behavior. A shared template can still produce different values for different catalog records.

Check the submitted landing page

Put the exact product URL from the affected offer into the free page check. Compare its public HTML with the offer ID and timestamp in your investigation.

Filed under Platform guides. Topics: ecommerce, google, structured-data, troubleshooting