

An old AI shopping price can turn interest into doubt. Find the record behind the mismatch, correct the offer and keep the next promotion consistent.

Your promotion ended yesterday. The product is back to $99. This morning, a customer sends a screenshot from an independent shopping assistant showing $79. “Why does the price go up when I click?”
To the customer, your store just changed the deal. Your team needs to find where that $79 is still being published. Before changing anything, check that the two prices describe the same offer. Then trace the source and fix it.
You can update your own pages and feeds directly. For third-party listings or a stale AI result, submit a correction and check later whether the displayed price has changed. The useful question is who controls the price at each step.
Follow the merchant link in the result. Match the product, variant, seller, country and currency to your store. Then check the terms: a member discount, subscription, pack size, tax or shipping charge can explain the difference.
Take the $79 screenshot. If members can still buy that exact item for $79, make the condition clear wherever the price appears. If the sale has ended for everyone, you have an old price to track down.
Save the screenshot, prompt, time and destination link. That gives your team a specific offer to investigate. Keep those details together as you follow the price through the next steps.
Your store admin may show $99 while a feed still carries $79. A review site may quote last month’s sale. These are separate records, and they do not update together.
Start with the source attached to the displayed price. Does it lead to your store, a retailer or an old comparison article? Find the amount on that page and check its conditions. Inspect text answers and product cards separately: they may show different sources or sellers.
Follow the relevant path through the product page and structured data, submitted feed, or third-party content. An AI result may also reflect an earlier version or older model knowledge. A visible citation is a lead to investigate; it does not reveal every step that produced the answer.
Use the customer’s screenshot to choose the first check:
| What the customer sees | Possible source | What to verify | What to do |
|---|---|---|---|
| An ended sale price still appears. | An active sale field, an outdated feed, or an old promotion page. | Compare the variant’s regular price, sale price, dates, and time zone on the page and in channel data. | Correct the sale data and submit the update. Refresh your old promotion pages. |
| The price changes when a size, quantity, or purchase option is selected. | A default variant, a different pack size, or a subscription offer. | Match the selected option and destination URL to the item in your channel data. | Correct the variant or link. Show the price and conditions for that option. |
| The page looks correct, but channel diagnostics report a different price. | Page markup or submitted data that disagrees with the visible page. | Compare the reported item with the price in the page’s HTML and structured data. | Ask your developer or feed provider to fix the conflicting output. Validate it and resubmit. |
| The number belongs to another region or has unclear conditions. | A regional page, member offer, or price with different tax treatment. | Check the country, currency, tax treatment, and discount conditions. | State the conditions clearly. Correct any wrong regional data. |
| The cited review or comparison page quotes an old price. | Outdated third-party content. | Find the old price on the cited page. Save the URL. | Send the publisher the correction and your current terms. Report the inaccurate platform result. |
| Your checked sources are correct, but the result still shows the old amount. | A delayed update, an unidentified source, or an error in the generated answer. | Repeat the original question in a new session. Save the result and visible sources. | Report the result and recheck it. Leave correct source data in place. |
For Google’s shopping channel, Merchant Center’s price-mismatch guidance covers submitted product data, landing pages and structured markup. Use the affected channel’s diagnostics to narrow the investigation to the record or output that needs correcting.
A product page can already be correct while an older offer remains in circulation. A feed export is one place the update can stop.
For a shopping channel receiving your product feed, the investigation can look like this:
The old amount points to the feed handoff. Rewriting the product page would leave the failed export untouched.
If the old amount instead appears on a review page, the publisher owns that correction. Use the source you find to choose the fix. The next step is to confirm that the correction reached the places the customer encounters.

Check the supplied record and the customer-facing result separately. A saved edit shows that the source changed; the receiving channel still needs to process it.
If the source and channel are current but the AI result remains stale, report the item, screenshot and current URL through the platform’s supported process. There is no universal refresh deadline. Schedule a follow-up check instead of repeatedly editing correct data.
Keep the original screenshot, the correction and the updated result together. A report submitted to the platform is a step in the process. The goal is a price the customer can actually buy at.
Most teams know who launches a promotion. Decide who owns its end while the campaign is being planned: the expiry time, return to the regular price and updates to each channel.
Send the source system and feed provider the start, end and time zone together. Check the receiving system’s time-zone rules rather than assuming its default matches the store.
If an agency operates the feed, name the person who checks delivery and the person who repairs a failed job. A completed store update should trigger a check of the records distributed beyond it.
Group repeated errors by promotion rule, feed or template. Fixing the shared cause can prevent the same mismatch from resurfacing across several products.
A customer who follows a recommendation has a reason to consider your product. A price that changes without explanation can interrupt that decision and make the whole offer harder to trust.
Consistent pricing lets the customer judge the real deal. Clear conditions explain what they are paying for. Together with useful information about product fit, they help the customer continue with the offer they chose.
AON connects merchant offers with relevant buying requests inside AI products. Highly structured commercial information helps applications understand and compare the offer; matching connects it to the request, and attribution links qualifying outcomes to the referral.
For a merchant, the value is a route to customers whose needs the business can serve. Current prices and clear terms help those customers continue from recommendation to purchase with confidence.
The repair is complete when the customer can act on the offer they were shown. That is the standard worth carrying into the next campaign.
Telling ChatGPT a price is wrong does not reliably correct the underlying source or other shoppers’ answers. Save the specific answer and identify the variant, market and purchase conditions involved. Correct the responsible page, feed or promotion record, then use the platform’s supported reporting process. Recheck the displayed result separately; feedback on one conversation is not evidence that the source was updated.
Updating product schema does not automatically correct a shopping feed supplied by another system. Check the exact variant and market in the visible page, markup, checkout and submitted feed, then correct the responsible source. For offers distributed through AON, update the source supplying those offers as part of that process. This is separate from an independent AI platform refreshing its own shopping display.
There is no single refresh time across AI shopping platforms. First check whether the receiving channel has accepted your updated data. Then repeat the original query and inspect the displayed price. Keep the submission time and screenshots together. If a platform provides a review status or support process, use that to follow up on a result that stays wrong.
Contact the publisher with the exact page, old amount, and a link to your current offer. Ask them to update the price or clearly mark the promotion as expired. If you control a merchant profile on that site, update it too. Report the inaccurate AI result while you wait. The publisher controls its page, and the AI platform controls when its display changes.
Check the exact variant, market and purchase conditions against your page, checkout, structured data and submitted feed. A different pack size, regional offer or subscription condition can explain an apparent mismatch. Then search for the product name with the wrong amount to investigate old promotions or third-party pages. Save the original answer; a source the assistant names later is not proof that it supplied the price.
Start with customer-reported errors, products in current campaigns, and items whose promotions recently ended. These give you a focused first batch. Group confirmed mismatches by feed, template, or promotion rule so you can fix a shared cause. Check a few affected items after the change, then review other products using the same setup.
Try live offer search without an account or API key. Start building today — go live when you are ready.