What is a return policy for an online store?
A return policy is the public document in which a store explains the conditions under which it accepts returns: the deadline, the condition of the product, how it is sent back, who pays return shipping, which products are excluded and what refund the customer gets.
Key takeaways
- It is a page for people, but Google, Merchant Center and shopping agents read the deadline, the cost and the return method from it.
- Merchant Center requires that the page can be read without signing in and that it says the same thing as what you set in its dashboard.
- In the ChatGPT feed, the policy URL does not replace the field that says whether returns are accepted.
- The same deadline has to appear identically on the page, in Merchant Center and in the feed.
Two things go by similar names and are not the same. The return policy is the page your store writes with its conditions. And MerchantReturnPolicy is that policy written in structured data for a search engine. This entry is about the first one, and it matters twice over: your customers read it before buying, and more and more machines read it on their behalf to say, next to your product, whether it can be returned, within how many days and who pays.
What it includes
What your store decides. The policy is yours, and these are the decisions it has to put in writing:
- The deadline, in days.
- The condition in which you accept the product.
- How it is returned: by mail, in store or at a pickup point.
- Who pays for the way back, and whether that changes when the product arrives defective.
- What the customer gets: the money, an exchange or store credit.
- The exceptions, product by product or by category.
- The countries where it applies.
What search engines and agents read
Google. Its search can show the return policy next to your products and in knowledge panels from your markup, and it also accepts it configured in Google Merchant Center or in Search Console; if you have it in both places, the configuration wins over the markup.[1]Google Search Central. Merchant return policy (MerchantReturnPolicy) structured data Which properties it uses is covered in the MerchantReturnPolicy entry.
Merchant Center. Google says return information can help the performance of your products and that it appears in your ads, your free listings and Gmail. In exchange it asks for four things: the URL of the policy on your site, that the page can be read without signing in, registering or giving personal data, that it says the same in Merchant Center and across the whole site (the footer, the returns page, the notices) and that the policy does not stop at defective products but also covers the customer who simply changes their mind.[2]Google Merchant Center Help. Set up your return policies for Shopping ads and free listings
ChatGPT. The product feed specification that OpenAI accepts has three optional fields for this, product by product: accepts_returns (whether returns are accepted), return_deadline_in_days (the number of days) and return_policy (the URL of the policy). The specification warns that the policy URL does not fill in or replace the field that says whether returns are accepted: if you only send the link, that answer stays unspecified.[3]OpenAI. Products (product feed specification) The entry on the product feed for ChatGPT explains the rest of the file.
In a store
Fictitious example. An invented clothing store publishes this policy, and this is how it translates into what each machine reads:
| What the page says | What it decides | In the OpenAI feed |
|---|---|---|
| "You have 30 calendar days from receiving your order" | The deadline | accepts_returns: true, return_deadline_in_days: 30 |
| "Send it back by mail with the label we sent you" | The method | No field of its own: it goes on the page |
| "You pay for return shipping, unless it arrives defective" | Who pays | No field of its own: it goes on the page |
| "Garments embroidered with initials cannot be returned" | An exception (customized product) | accepts_returns: false on those garments |
All of the above, at /returns |
The source | return_policy with that URL |
Look at the two rows without a field. What does not fit in a field only reaches a machine if the page says it clearly, and it only reaches a customer if the page can be read without an account.[3]OpenAI. Products (product feed specification)[2]Google Merchant Center Help. Set up your return policies for Shopping ads and free listings The same 30-day deadline has to appear identically on the page, in Merchant Center and in the feed.
What people often get wrong
Believing that linking the policy is enough. In the ChatGPT feed, the policy URL does not fill in or replace the field that says whether returns are accepted: if you send only the link, that answer stays unspecified.[3]OpenAI. Products (product feed specification) And in Merchant Center the page has to be readable without signing in.[2]Google Merchant Center Help. Set up your return policies for Shopping ads and free listings
How to check it
- Read your policy from start to finish: the deadline, the condition of the product, how it is returned, who pays for the way back, the countries and the exceptions with their reason.
- Open it in a private window, signed out. If it asks for an account or personal data, Merchant Center will not accept it.[2]Google Merchant Center Help. Set up your return policies for Shopping ads and free listings
- Look for the deadline everywhere: the page, the footer, the site notices, the Merchant Center settings and the Search Console settings. It has to be the same number.[2]Google Merchant Center Help. Set up your return policies for Shopping ads and free listings
- If you send a feed to ChatGPT, check the three returns fields and not just the link.[3]OpenAI. Products (product feed specification)
- Check where Google reads your policy from. If you have it configured in Merchant Center or in Search Console, what your markup says moves to the background.[1]Google Search Central. Merchant return policy (MerchantReturnPolicy) structured data
Related concept: MerchantReturnPolicy
The return policy is the document, with its fine print. MerchantReturnPolicy is its summary in closed values, the country, the type of window, the days, the method or who pays, that a search engine can compare across stores. The order is always the same: first you decide and publish the policy, and then the markup copies exactly what it says. Which properties Google asks for, where it is declared and which source wins over which is in the MerchantReturnPolicy entry.
To go further, the catalog and entities reading path orders the rest of the terms, and the OfferShippingDetails entry covers the other half of what a customer looks at before paying: shipping.
Synonyms
- English
- return policy, returns policy
- Español
- condiciones de devolución, política de cambios y devoluciones
Sources
- [1] Google Search Central. Merchant return policy (MerchantReturnPolicy) structured data. Accessed . ↑ ↑
- [2] Google Merchant Center Help. Set up your return policies for Shopping ads and free listings. Accessed . ↑ ↑ ↑ ↑ ↑
- [3] OpenAI. Products (product feed specification). Accessed . ↑ ↑ ↑ ↑
Change history
- First English version.
- No country-specific law: the term is general.
This definition is published under CC BY 4.0. Reuse this definition freely, crediting Clione with a link to this page.
Related terms
MerchantReturnPolicy
What MerchantReturnPolicy is, which properties Google asks for, where it goes (organization or offer), what overrides what and how to check it in your store.
OfferShippingDetails
What OfferShippingDetails is, what Google asks for to show shipping cost and delivery time, when to use it versus a store-wide policy and how to check it.
Google Merchant Center
What Google Merchant Center is, how your product data gets there, where Google shows it and how to check that the feed and the product page match.
ChatGPT product feed
What the ChatGPT product feed is, which fields OpenAI requires, how to send it by SFTP or API, which markets it covers today and how to validate it.
B2B ecommerce
What B2B ecommerce is, what sets it apart from a B2C store (per-customer pricing, minimum orders, login access) and what Google and AI agents see of it.
Price and availability signals
What price and availability signals are, where each copy lives (product page, markup and feeds), how Google compares them and what happens when they differ.
Make your catalog easy for bots to read
Clione fills every product page with what bots read best: the JSON-LD graph with its structured data, the meta description and the FAQs. You review and press Push; then we check your live store so it all stays published.