How should you write returns and warranty terms so AI shopping answers can cite them?

Return policies and warranty terms are among the most-cited sections of a product page in AI shopping answers, and among the least-optimized. Merchants spend their effort on titles, images, and price, then write the return policy once, paste it into a page template, and never look at it again. That asymmetry is easy to exploit.

Here is the practical version: an AI assistant can only quote a policy that is stated as a specific, self-contained sentence. If your returns information exists only as a link to a policy page, or as a wall of legal prose, the assistant will describe your policy generically — or describe your category's norms instead of your actual terms.

## Why policies get pulled into AI answers at all

Shopping questions are rarely just about the product. Buyers ask:

• "Which of these can I return if the size is wrong?"
• "Does this brand cover shipping damage?"
• "What is the warranty on this?"
• "Is there a restocking fee?"

These are constraint questions. When an assistant assembles an answer, it needs a citable sentence for each constraint. A page that states the constraint clearly gets quoted; a page that points at a policy page is a weaker source than a competitor that states the same term inline.

The retrieval step is the reason. A system fetching chunks at query time has a limited budget. A sentence that answers the question directly is a high-value chunk. A policy page URL is a pointer, not an answer, and pointers rarely survive into synthesized text.

## The five policy facts worth stating inline

Most of the value comes from five facts. State each one as a plain sentence inside the product page, near the price or the buy box:

1. Return window — the number of days, and the trigger event ("30 days from delivery," not "30 days"). 2. Who pays return shipping — you, the buyer, or split by reason. This is the fact buyers actually care about and the one most often missing. 3. Condition requirements — unused, original packaging, tags attached. Be specific about what disqualifies. 4. Restocking or handling fees — state the amount or state clearly that there is none. "No restocking fee" is a quotable sentence; silence is not. 5. Warranty and damage coverage — duration, what it covers, and who to contact.

A useful test: read your own policy section and ask whether a stranger could answer the four buyer questions above using only sentences that appear on this page. If they would have to click somewhere else, an assistant likely will not click either.

## The wording mistakes that make policies uncitable

• Linking instead of stating. "See our returns policy" contains zero extractable facts.
• Legal hedging with no number. "Returns are accepted at our discretion within a reasonable period" gives the assistant nothing to commit to.
• Template mismatch. A localized storefront showing the English default policy, or a policy that contradicts what the buy box says, produces conflicting chunks. Assistants resolve conflicts by hedging or by preferring the more confident source.
• Conditional prose with no branch structure. If returns differ by region or by product type, a single paragraph of exceptions reads as ambiguity. Use a short list per case.
• Stale dates. A policy referring to a season that has passed reads as outdated and gets discounted.

## A worked example

Weak version, common on cross-border storefronts:

> We want you to be happy with your purchase. Please contact us within a reasonable time if there is an issue and we will do our best to help.

Strong version, same policy, stated as facts:

> Returns: 30 days from delivery. Unused items in original packaging with tags attached. > Return shipping: We cover return shipping for defective or wrong items. Buyer covers return shipping for change of mind. > Fees: No restocking fee. > Warranty: 12-month manufacturer warranty covering defects in materials and workmanship. Contact support with your order number.

The second version is shorter and it contains six extractable facts. It gives an assistant something to cite, and it gives a buyer something to decide on.

## How this fits the rest of your pages

Policy text is one of several "decision-fact" blocks that assistants treat as hard commitments, alongside price, availability, and delivery windows. The pattern is the same each time: a fact that exists only as an implication is invisible; a fact stated as a sentence is citable.

If you want to see which of these blocks are missing or inconsistent across your catalog rather than on one lucky page, that is exactly the structural scan Visora runs — it reports missing and conflicting decision facts at catalog scale so you can fix them in batches instead of page by page. Start with a free scan at [/audit](/audit), and read [/faq](/faq) for what the scan does and does not measure.

## Common questions

Both, but the product page needs at least the five facts above as sentences. The policy page can hold the full legal text; the product page holds the answerable version.

Avoid copy-pasting prose that contradicts per-product terms. Stating the same global facts consistently across pages is fine and helps; it is inconsistency, not repetition, that breaks citation confidence.

You can, and it converts poorly. Assistants increasingly check policy claims against order and fulfillment data, and buyers compare the answer to the checkout terms. State the real terms clearly; clarity is the advantage, not generosity you do not honor.

Ask two or three assistants the same return question before and after the edit, and record the answers verbatim. Then confirm on the page that the fact you meant to state is actually the fact a reader would extract.