The price may be right. The selected variant may not be.
When a submitted item and its landing page disagree, changing the feed price alone may miss the cause. First establish which variant each system is describing.
The same item, two storiesIllustrative example
Cotton crew tee
Navy / Medium
SKU · TEE-NV-M
Submitted feed
Variant
Navy / M
Price
$38.00
Availability
In stock
Landing page opens
Variant
Charcoal / S
Price
$34.00
Availability
In stock
!
Check the variant URL. The feed link may be opening the default option.
Synthetic catalog. A demonstration of our diagnostic approach.
Follow one item all the way through.
In this synthetic example, a navy medium tee costs $38. The feed contains that price, but its product URL opens the default charcoal small tee at $34.
The first thing to investigate is the URL and the variant selection behavior. Replacing $38 with $34 would describe the wrong variant and leave the underlying inconsistency in place.
A root-cause hypothesis becomes a confirmed finding only after checking the actual URL, redirect behavior and selected product option.
Four places to inspect
1. Submitted item and link
Start with the exact item ID, submitted price and destination URL in the current data source. Check whether the URL includes the intended variant selection and whether redirects preserve it.
2. Visible landing-page state
Open that link in a fresh session. Record the selected color and size, displayed price, currency and stock state. A previously selected option or location can hide a problem during a casual browser check.
3. Sale and update timing
Compare the active promotion with the submitted regular and sale price. Record when the feed was generated and when the store changed. A stale export and a mapping error require different fixes.
4. Page data and theme behavior
If the visible selection is correct, inspect the product data the page publishes and how the theme updates it when an option changes. Changes to the theme or feed integration may need your developer or app provider.
Keep the evidence together. A useful issue record includes the item ID, full submitted URL, observation time, expected variant and actual page state. A screenshot without those details is difficult to reproduce.
What we can take off your list
The $299 diagnostic checks up to 2,500 variant rows and manually reviews 20 product URLs. We identify reproducible mismatches, distinguish confirmed evidence from hypotheses and propose a repair scope.
We do not promise approval or treat every Merchant Center issue as a feed error. Account-level, policy and business information issues may require a different specialist.
Reference: Google’s product data specification. Requirements depend on product, destination and market; we check the applicable requirements during a diagnostic.
Compare one exact variant in one market during the same session. Record both the source row and Merchant Center’s current processed values, rather than assuming your latest export is already the version Google holds.
Fill this record for each sampled item
Checkpoint
Record
What a difference suggests
Identity
Item ID, country, size, color and observation time
Different variants are not a valid price comparison
Processed feed
Current price, currency, sale price and active sale period
A stale or transformed value needs source investigation
Landing URL
Full link, final URL, selected option and visible price
A redirect or default selection may change the item
Structured data
The matching Product/Offer identifier, price and currency
Theme or app output may differ from the visible option
Cart and checkout
Same item and product price; delivery/tax recorded separately
Currency or pricing logic may change the result
Download the plain-text evidence worksheet — no email or account required. It contains one clearly fictional worked example and a blank item record. Do not put customer information or passwords in it.
Use the result to choose a repair
If the wrong size opens, investigate link selection before replacing a valid price. If the right size opens but the processed feed is older than the current sale, investigate update timing. If page and cart disagree, isolate the pricing rule before changing catalog data. Keep each explanation provisional until you can reproduce it.
For the applicable requirements, see Google’s price attribute guidance. Recheck the affected item after an agreed change and separately record Merchant Center’s processing and issue status.