Two of the most common questions a shopper asks an AI assistant have nothing to do with the product itself. "Does it ship to me?" and "Can I return it if it doesn't fit?" These are the questions that decide whether someone clicks buy, and they are exactly the questions that unstructured policy data fails to answer. A shopper on your site will hunt through the footer for a returns link. An assistant will not. It works from the policy data it can read, and if that data is thin, it either drops you or hedges.
This is the part of AI readiness that has nothing to do with schema on a product page and everything to do with the operational data behind the sale. It is also one of the easiest places to win, because most stores have never thought of their shipping and returns policies as machine-readable signals.
Shipping eligibility is a hard filter, not a preference
When an assistant searches the catalog, it separates soft context from hard filters. Price ranges, availability, and shipping eligibility are filters: a product that fails one is removed from the results before ranking even happens. So when a shopper says "ships to Canada," and your shipping data does not show coverage for Canada, you are not ranked lower. You are gone from that shopper's results entirely.
That makes shipping configuration a discovery issue, not just a fulfillment one. If you serve a market, your shipping profiles need to cover it and your rates need to be configured for it, or an assistant will treat you as unable to ship there. This is the same filter-versus-context distinction that runs through the whole catalog, which we explain in the Shopify Global Catalog guide. Shipping is the place it most often costs stores a sale they never knew they were in the running for.
A few practical checks:
- Confirm your shipping profiles cover every market you actually serve, not just your home country.
- Make sure rates exist for those markets. A market with no rate can read as no coverage.
- If you ship internationally, verify the configuration end to end, because a gap here silently removes you from every cross-border query.
Return terms are a trust and ranking signal
Where shipping is a filter, returns lean more toward trust and ranking. When several stores sell the same product, an assistant clusters the offers and surfaces one, the way a buy box works. The levers include price, shipping, availability, and the richness of your data, and return terms increasingly sit inside that data. A free, generous, clearly stated return window is the kind of post-purchase reassurance that makes an assistant comfortable recommending you over a store whose policy it cannot read.
The catch is the same as everywhere else in agentic shopping: the assistant only knows what your data says. A thirty-day free-returns policy that lives only in a footer page nobody linked, or worse, inside a downloadable PDF, may never be read. The terms need to exist as text an agent can parse: the window length, who pays return shipping, any restocking fee, and the exclusions. This sits alongside the other trust signals AI assistants check before recommending a store, and policy clarity is one of the cheapest to fix.
Where to put the policy so it gets read
There are three layers worth covering, and they reinforce each other.
Your Shopify policy fields and a crawlable policy page. Use the built-in shipping and returns policy fields and keep a clean, crawlable policy page. Plain text that a crawler can read beats an image of a policy or a PDF download every time.
Structured data and on-page text near the product. Where it applies, expose shipping and returns terms in structured form, and state the headline terms in readable text close to the buying decision rather than three clicks away. Compliance and policy disclosures that agents are expected to surface should sit near the product, not in a footer. If you are new to structured data, start with the structured data for Shopify guide.
Your agents.md or llms.txt summary. A short, accurate summary of your shipping coverage and return terms in your agents.md or llms.txt gives assistants a clean place to read the policy without parsing the whole site. This is the file AgentReady publishes and keeps current, and policy clarity is one of the highest-leverage things to put in it.
A short checklist
When we audit policy readiness on a store, this is the pass:
- Confirm shipping profiles and rates cover every market you serve.
- State return terms (window, who pays, fees, exclusions) as readable text, not an image or PDF.
- Keep the policy pages crawlable, not gated behind a download.
- Surface compliance and policy disclosures near the product, not only in the footer.
- Summarize shipping coverage and return terms in your agents.md or llms.txt.
- Re-check after any change to markets, carriers, or terms, since stale policy data misleads both shoppers and agents.
See how your policy data reads to an assistant
You cannot fix what you cannot see, and no assistant emails you to say it dropped you from a market or skipped you because it could not find your return terms. The way to find those gaps is to look at your store the way an agent does.
Our free Shopify AI-readiness checker grades the shipping coverage, policy text, and trust signals that decide whether an assistant can confidently recommend you, and hands back the specific gaps ranked by impact. Returns and shipping clarity is unglamorous work, but it is the work that answers the two questions every shopper asks before they buy.
Browse every guide in the Shopify Catalog and AI and agentic commerce topics.

Comments
Every comment here comes from a verified email. Write yours, confirm from your inbox, and it's live.
Loading comments…