Shopify price mismatch in Google Merchant Center: find what is wrong
The store looks right, but Google sees another price. Trace one product offer from its data source to checkout before changing your catalogue. In Merchant Center this usually appears as “Mismatched value (page crawl) [price]”.

01Reconcile one offer before changing a price
Do not make the store imitate an old Google price. Establish which price the business actually intends to sell, then reconcile the same variant, market, currency, quantity and time across the feed and buying journey. Those five dimensions belong at the top of the investigation.
Copy the affected item and reported values from Merchant Center. Preserve its issue timestamp: a mismatch discovered during yesterday's sale may no longer reproduce now. Google's mismatched-price guidance[1] identifies source timing, sale dates, initial HTML and structured-data disagreements as possible causes. The error alone does not tell you which system is wrong.
This workflow is for publicly purchasable, one-time offers. Loyalty programs, subscriptions, regional inventory and bundles require their applicable specifications too. Do not republish a conditional member price as an unconditional offer just because its number matches the screenshot.
What the evidence does and does not prove
| Observation | What it establishes | What it does not establish |
|---|---|---|
| Merchant Center reports "Mismatched value (page crawl) [price]" | Google saw a different price on the landing page than in your data, at that time | Which system is wrong, or that it is still wrong now |
| The page shows the right price in your browser | The rendered price for your session and market | What the initial HTML or structured data said when Google crawled |
| Automatic item updates are enabled | Google may reconcile some values from your site | That every offer is consistent, or that the page is the right source |
| Google says recrawl happens over hours or days | Fixes are not instant | A deadline, or that an account-level restriction will lift |
02Which amounts should agree—and which should not?
| Amount | Interpretation | Common mistaken repair |
|---|---|---|
| Current selling price | Amount for the submitted variant under the advertised purchasing conditions. | Replacing it with the product family's lowest variant price. |
| Shopify compare-at price | Reference amount used to display a sale, not the current charge. | Submitting the crossed-out amount as what the customer pays. |
| Active sale price | The effective advertised selling amount during the stated sale window. | Leaving a past sale active in one system after the store has returned to regular pricing. |
| Per-unit or bulk amount | Distinguish a unit comparison from the minimum purchasable quantity. | Advertising one unit's amount when the buyer must purchase a pack. |
| Cart or checkout total | Separate merchandise from quantity, discounts and explicitly identified shipping/tax components. | Comparing a multi-line cart total with one feed item's merchandise amount. |
Shopify's sale-price instructions[2] distinguish Price from Compare-at price. Google also treats sale_price[3] as a selling amount, while sale annotations have separate conditions and are not guaranteed. A missing strike-through badge is not proof of an incorrect charge.
Google's checkout requirements[4] should govern the purchasing-path check. Do not use this troubleshooting article as tax advice. Country-specific tax display, shipping and membership rules need their own review; a legitimate separate charge is not a reason to conceal the actual total.
03Build a dated offer record
Use a private window and the exact submitted link. Before changing any selectors, write down what it opens. Record the Merchant Center item ID, Shopify variant identifier or SKU, target country, currency, minimum purchasable quantity, sale window and source update time.
- Merchant Center: preserve the reported submitted and found values, current item state and data source.
- Shopify: inspect that variant's intended price and the applicable market catalog or adjustment—not only the base-currency product summary.
- Initial document: in browser Network, inspect the main HTML response and the relevant Product/Offer values.
- Rendered page: record selected options, visible amount, currency and any conditions after scripts run.
- Cart and checkout: verify the same item and minimum quantity, separating charges. Stop before a paid order.
Repeat with one unaffected variant at another price. This control catches a patch that forces every destination to select one option. Do not save customer details, session cookies or payment data in the evidence record.
04If the feed is stale, repair its owner
If Shopify, the page and checkout agree but Merchant Center has an earlier amount, identify the source that supplied that item. An installed Google & YouTube channel does not establish that it owns every listing; inspect the item's actual source and any supplemental changes.
Save the intended value and source-processing timestamp, correct the owning source, and verify the next received value. If the amount reverts, compare the reversion time with source updates before making another manual change. Do not reinstall the channel or delete the catalog as a first diagnostic action.
Automatic item updates[5] can reconcile some discrepancies from website information, but Google says they do not replace regular source updates. An enabled setting is not proof that all offers are consistent, and it does not make an incorrect page authoritative. Distinguish these consistency updates from a business decision to run automated discounts.
05If the page is wrong, identify the producing component
If the destination chooses another size or color, preserve the redirect chain and selected variant before investigating prices. Both prices may be valid for different products. Repair the submitted destination or selection behavior so the first visit reaches the advertised item.
If the visible offer is right but the initial document is stale, identify the theme or application that outputs the conflicting value. Test the exact URL with Google's Rich Results Test[6], then inspect the offer values—not just whether the markup parses. Several product objects can describe legitimate different entities; do not indiscriminately delete every object except the first.
Give the responsible developer a copy of the offending output and expected variant/price pair. Require a theme backup and a reversible correction to the existing producer. Adding a second hard-coded price block may hide today's issue while breaking the next price change. The variant structured-data guide covers that entity relationship in more detail.
06If only one country fails, trace the market price
Start with the submitted country's buying path, not the currency remembered in your own browser. Shopify local pricing[7] can involve conversion, adjustments, rounding and fixed prices. Its exchange-rate guidance[8] states that international fixed prices take precedence over a manual conversion rate. Calculating base price × exchange rate is therefore not sufficient for every item.
Write down the applicable market configuration and the actual returned currency. Check whether a redirect or persisted country selection switches the visitor elsewhere. Then follow the intended delivery country's checkout path. Shopify documents checkout restrictions[9] that can change currency based on shipping destination; testing another country's delivery address is not a like-for-like comparison.
If Google displays a converted local amount, first establish whether its currency-conversion feature applies. Google's landing-page requirements[10] describe that scenario. Do not overwrite the store's base price to imitate a conversion display you have not reconciled.
07Test a sale at both boundaries
A promotion needs a start-state and end-state check, not only a screenshot while the offer is active. Record the sale's timezone, the source's effective window and the store's actual price changes. Keep the regular price, sale price and current effective price in separate fields.
Hypothetical worked record: an ordinary public offer is USD 60; an unconditional sale is USD 48 until the stated end time. After that time the page and cart return to USD 60, but the submitted sale remains USD 48. The first discrepancy is the effective sale state. Reopening the sale on the storefront merely to match stale data would change the business's intended promotion.
The acceptance test is not “all numbers equal 48.” It is “the active buying amount and submitted effective offer agree at this point in the schedule.” Check before, during and after the next promotion. Do not use this example for coupon-only, paid-member or subscription prices without their separate requirements.
For minimum quantities, Google's price-inconsistency guidance[11] requires the minimum purchasable amount. If a customer must buy three units, a per-unit label is not enough to establish the advertised purchasing price. Resolve the quantity identity before diagnosing a threefold price difference as a feed bug.
08Prove the correction survives the next update
Retest the affected item and control after the repair and after the next relevant source update. If the repair touched a theme producer, repeat a normal authorized price-change test in a test environment; do not alter live catalog prices merely for this article's exercise.
Record source receipt, page consistency, Merchant Center issue state and any account-level review separately. Google's mismatched-price guidance describes recrawling over subsequent hours or days; it is not a guaranteed deadline. A broader account restriction can remain after one item is corrected.
Send support the exact item, submitted and final URLs, five-checkpoint record, market, sale times, source history and most recent relevant change. If you cannot reproduce the reported value, say so and retain the original timestamp. Avoid simultaneous feed, theme and market changes that make the cause untraceable.
If the page cannot be reached at all, use the landing-page access workflow first. Requesting organic indexing does not resolve a Merchant Center price restriction.
09Copy this offer reconciliation record and fill in the brackets
Offer reconciliation record
Merchant Center item: [ID] Shopify variant/SKU: [ID] Country: [xx] Currency: [xxx] Min. quantity: [n] Reported: submitted [amount] vs found [amount] at [timestamp] Data source: [Google & YouTube / app / file] 1 Merchant Center now: [amount] 2 Shopify intended price for this market: [amount] 3 Initial HTML / structured data: [amount] 4 Rendered page after scripts: [amount] 5 Cart/checkout merchandise line: [amount] Control variant (different price): [ID] → [all five amounts] Sale window: [start–end, timezone] regular [amount] / sale [amount] / effective now [amount] First disagreeing checkpoint: [n] → owner [name/system] Repair: [one change] Rechecked after next source update on [date]: [pass/fail]
10Review scope
Reviewed October 8, 2026 using the linked Google and Shopify primary references. The offer record and USD example are editorial troubleshooting aids, not customer results. Actual source mappings and permissions differ by store. This article does not guarantee approval, a sale badge, rankings or a review deadline.
For a wider audit, use the technical checklist. If the evidence spans multiple owners, ask ShopXN to review the collected record; passwords and private customer details are not needed in an initial inquiry.

Answer the customer while the price is being checked
A shopper who sees two amounts needs a clear next step while you reconcile the offer. Ask for the product link, chosen options, delivery country and the two amounts with their currencies. A redacted screenshot can help; do not request a payment-card number or an unredacted checkout image.
Initial reply when the difference is unexplained:
Hi [first name], thank you for flagging the price difference for [product]. Please send the product link, the size or option selected, your delivery country, and the two amounts with their currencies. If you send a screenshot, please hide your contact and payment details. We will compare the same item and market and update you by [staffed date, time and timezone]. If you prefer, please wait for our check before placing the order.
Give a response time your team can meet. This is a commitment to investigate, not a promise that Google will refresh a listing by that time. Google's product data overview explains that product information can come from structured data, Merchant Center feeds or both. Keep the customer reply focused on the buying information while the technical team checks those sources.
Use a resolution reply only after the five-checkpoint check
Different variants confirmed: use only after verifying both selected variants and their current prices.
Hi [first name], we checked the two amounts. [Amount and currency A] applies to [variant A]; the [variant B] you selected is [amount and currency B]. Here is the direct link for [requested variant]: [verified link]. Please check the selected option before paying. If you saw the lower amount attached specifically to this same variant, send that view and we will review it.
Different market prices confirmed: Shopify documents local pricing, including market-specific adjustments. First check the store's actual configuration and the destination-specific price. Do not dismiss a discrepancy merely because the currencies differ.
Hi [first name], the [amount and currency A] you saw was for [market A]. For delivery to [country], we checked [exact variant] in [market B], where the merchandise price is [amount and currency B]. Please use [verified country-specific link or country-selector instructions]. [State verified shipping or tax information separately.] If the price changes unexpectedly after selecting that destination, please pause and contact us so we can check the same buying path.
Existing order or alleged overcharge: use your private support route. Do not convert a public listing investigation into an automatic refund decision.
Hi [first name], we will review the amount charged for [product] against the confirmed order. Please contact us through [verified private support route] with [minimum order reference required by your process]. We will check the item, quantity, currency, discounts and separate charges, and explain any available resolution by [staffed date, time and timezone]. Please do not send card details.
Choose the owner before offering a remedy
| Finding | Owner and action | Customer commitment |
|---|---|---|
| Current store and cart agree; external listing differs | Feed owner records the exact item and source update. | Explain the verified current offer; give the next support update time. |
| Variant or country selection changes unexpectedly | Store developer investigates the submitted link and selection. | Offer a verified path only if one exists; otherwise continue the check. |
| Checkout contradicts the same product and market | Authorized store staff reviews the buying path before asking the shopper to proceed. | Acknowledge the unresolved discrepancy. |
| Paid order disputed or customer requests a refund | Payments or returns staff verifies the case and decides the remedy. | Confirm the review process; state a refund amount or timing only when approved. |
Close the support case with the confirmed variant, market, amounts, explanation and any authorized remedy. Keep the Merchant Center issue open in the technical record until its own status changes. A satisfied customer and a cleared listing issue are separate outcomes.

11Questions
How do I fix 'Mismatched value (page crawl) [price]' on Shopify?
Find the first checkpoint where the price disagrees for the same variant, market and quantity, and fix the system that owns it. Don't change the store price to match an old Google value.
How long does Merchant Center take to recheck a price?
Google describes recrawling over hours or days. There is no guaranteed deadline.
Does the compare-at price cause mismatches?
It can if it is submitted as the selling price. Compare-at is the crossed-out reference, not what the customer pays.
Sources and what still needs a direct check
Support workflow sources checked November 4, 2026: Shopify local pricing, Google product data documentation and Google mismatched-price guidance. Fill in the verified variant, market and amount before sending a price explanation.
- Google Help, Mismatched-price guidance. Checked November 4, 2026.
- Shopify Help Center, Sale-price instructions. Checked October 8, 2026.
- Google Help, Sale_price. Checked October 8, 2026.
- Google Help, Checkout requirements. Checked October 8, 2026.
- Google Help, Automatic item updates. Checked October 8, 2026.
- Google Search tools, Rich Results Test. Checked October 8, 2026.
- Shopify Help Center, Local pricing. Checked October 8, 2026.
- Shopify Help Center, Exchange-rate guidance. Checked October 8, 2026.
- Shopify Help Center, Checkout restrictions. Checked October 8, 2026.
- Google Help, Landing-page requirements. Checked October 8, 2026.
- Google Help, Price-inconsistency guidance. Checked October 8, 2026.
Still to check yourself
- Which data source actually owns each affected item in Merchant Center.
- Your market price rules: fixed prices, rounding and adjustments per country.
- Tax, shipping and membership display rules for each target country.