AI shopping assistants are reusing remembered product facts — even after they change

A pattern showing up in merchant reports through September 2026 is that AI shopping assistants are reusing product facts they captured in earlier conversations. When a buyer returns to plan a purchase days later, the assistant often opens with what it already "knows" about the product — a price, a shipping window, a warranty length — rather than re-reading the page.

The practical consequence is that your product page is no longer just competing for citations in the moment. It is also competing to be the version of the fact that gets remembered.

Assistants with conversation history or saved preferences carry forward facts from prior sessions. That is a feature for the buyer: less repetition, faster shortlists. But the underlying fact is stored as it existed when it was captured. If your price, availability, or returns window changed after that capture, the assistant may present a stale fact with the same confidence as a fresh one.

There are two triggers. First, seasonal catalog changes — a size being discontinued, a price moving back up after a promotion — now produce support tickets where the buyer quotes the assistant rather than the page. Second, and more subtly, merchants who publish precise facts are finding those facts are the ones that stick, for better and worse. A vague page is rarely remembered at all; a specific page is remembered and then may be quoted after it has changed.

The response is not to write less precisely. It is to make your published state unambiguous and your changes legible:

• State facts with their validity, not just their value. "Free shipping on orders over $50 through 30 September" is more useful and less dangerous than "free shipping over $50" if the threshold changes.
• Avoid facts that depend on a moving context without saying so. A price that varies by region read as a flat price becomes a wrong fact when remembered elsewhere.
• Keep the canonical fact on the page. Assistants fall back to the page when they re-check. A page that states the current value clearly is the correction mechanism you control.
• Do not state the same fact two ways across pages. When a remembered fact conflicts with a fetched one, resolution is messier, and consistency across your own pages gives the assistant only one version to hold.

This is the reason we recommend treating your published facts as a governed surface rather than page copy. A Visora scan surfaces where the same fact is stated inconsistently across your catalog — the classic source of a remembered fact that later contradicts your page. Running it after a price, stock, or policy change tells you which pages now disagree with each other, so the version an assistant remembers has a single correct source to fall back to. The [audit page](/audit) explains what the consistency check reports.