A feed price is useful only when it represents the product a buyer can actually choose. Compare the feed, landing page and checkout before sending more traffic to the offer.
Choose an exact buying configuration
Specify the product, option and quantity. A starting price for a range cannot be compared fairly with the price of its most expensive variant. Keep currency and the treatment of delivery explicit.
Use a normal product, a sale item and a variant product as separate cases. One matching simple item does not prove the difficult paths.
Record where the values originate
Identify the source for each displayed amount and how often it updates. If the feed is generated from a different export than the storefront, write down the timing difference.
Google's Merchant Center specification includes price and availability requirements. Confirm the current rules for the destination and the actual landing-page behaviour rather than assuming a technically accepted file is sufficient. Product data specification
Test a change through the whole path
In a controlled environment, change an allowed test value and observe the feed and page. Record when each reflects it. Do not advertise a sale ending at a precise time if the update routine cannot support that promise.
Include an unavailable product. A low price on an item that cannot be bought can waste customer attention even when the feed field is formatted correctly.
Investigate differences before compensating
Do not manually change one surface solely to make a screenshot match. Find whether the discrepancy comes from variant selection, stale data, a discount rule or a different cost definition.
Keep the correction at the appropriate source. Otherwise the next export may restore the inconsistency.
Make reconciliation repeatable
Use a short sample after pricing-policy changes and before important campaigns. Retain the tested item references, time and outcome. Give one person responsibility for following up on failures.
This guide does not promise a native feed integration or real-time synchronisation. Use the pricing and platform hub to define the offer first, then verify every representation of it.
Illustrative case to check
A sale ends at midnight, but a manual feed is not refreshed until the next afternoon. A buyer may see the earlier offer before arriving at the new price. Identify the actual update gap and change the publishing routine or offer timing. Do not claim real-time consistency when the process depends on a later manual upload.
Examples are illustrative. Confirm current features, charges and suitability before making a business decision.
Explore this topic → · Find an oBizee setup guide · Ask about your store