A product can have the correct price in the commerce admin and still show a different price to an ad visitor. A feed may be delayed, a sale may have expired in one system, or the destination may select a more expensive variant.
Treat the mismatch as a data-path investigation before trying to compensate with bids. The task is to identify where the price diverges and which system owns the correction. A campaign change cannot repair an inconsistent purchase experience.
Define the exact offer being compared
Start with the product ID, variant ID, target market, currency, quantity, and relevant offer conditions. Record the time of the observation. A parent product's “from” price is not necessarily the price of the variant advertised.
Check whether the offer is a standard price, sale price, member price, bundle, subscription, or regional offer. These cases can have different platform requirements. Do not flatten them into one universal rule about what belongs in the price field.
Google Merchant Center's price specification documents amount and currency consistency, variant presentation, and country- or product-specific handling. Consult the sections that apply to the actual offer rather than borrowing a tax or membership rule from another market.
Build a price trace with timestamps
Capture the value at each stage.
| Stage | Evidence |
|---|---|
| Commerce source | Variant price, sale state, market and last update |
| Export or API payload | Submitted fields, item ID and submission time |
| Processed platform product | Current interpreted price, status and diagnostics |
| Landing page | Visible selected-variant price and currency |
| Structured data | Offer values associated with that variant |
| Cart and checkout | Actual purchasable item and resulting price components |
This trace separates an export problem from a processing delay or a website problem. Keep screenshots and sanitized values sufficient to reproduce the discrepancy. Avoid copying private customer records into the audit.
If the values changed during the investigation, preserve both observations. An intermittent mismatch can disappear on refresh while the underlying update sequence remains broken.
Inspect variant selection and redirects
Open the exact ad destination, including relevant variant parameters. Follow redirects and confirm the final selected product. A redirect to the parent URL can discard the selected size or color and display a default price.
Test a fresh session and a representative mobile viewport. Do not rely on a logged-in admin browser that remembers the desired variant or customer pricing. Record conditions that affect presentation, such as a selected market or membership status.
Use the variant destination checklist when the feed value is correct but the shopper sees a different item. Fixing the URL or selection behavior may resolve the mismatch without changing the product's actual price.
Check promotion timing and field precedence
Compare the ordinary price, sale price, effective period, discount code, and automatic cart discount. The price a buyer can actually obtain should match the offer representation appropriate to the platform and market.
Google's sale-price documentation explains how the sale price relates to the regular price and the displayed purchase path. Inspect whether an expired sale value remains in the feed or whether a current sale never reached the processed product.
Look at the system order: commerce update, feed export, website cache, structured-data render, and platform processing. If the site updates first and the export arrives hours later, the problem may be synchronization rather than a mistyped number.
Inspect checkout separately from the product page
Add the advertised variant and quantity to the cart using an authorized test process. Confirm that the item remains the same and that the price does not unexpectedly change. Inspect shipping, mandatory charges, and market-specific tax treatment under the applicable requirements.
Merchant Center's checkout guidance addresses price consistency and disclosure of additional charges. A page that displays the expected price is not sufficient if checkout changes the offer in a way that conflicts with those requirements.
Avoid completing a real order unless the test process authorizes it. The audit needs evidence of the purchase path, not accidental revenue, fulfillment, or refund work.
Repair the authoritative source
If the commerce record is wrong, correct it there. If a transformation applies an old discount, repair the mapping. If structured data uses the lowest variant price while the page selects another offer, coordinate the page and schema implementation.
Do not rely on a manual downstream override without documenting how future source updates will interact with it. Otherwise the next sync can recreate the mismatch or overwrite a correct repair.
For a large catalog, prioritize affected products by active exposure and commercial importance while sampling different offer types. One fixed item does not prove that every currency, variant, or sale configuration uses the same path.
Verify recovery and prevent recurrence
Read the corrected source, submitted payload, processed product, and customer path again. Track unresolved platform processing separately from completed website repairs. Do not promise an immediate eligibility recovery after a feed submission.
Add a focused check around price changes and promotions. Compare representative high-exposure products at the moments when discrepancies are most likely: sale start, sale end, market change, or catalog integration release.
The final audit should identify the cause, repaired system, affected scope, and remaining uncertainty. Once offer consistency is established, the buyer can assess delivery and performance on a sounder basis. Bid changes should respond to those business results, not conceal a broken price path.