Return policy markup for stores with product exceptions
Map your standard return policy and product exceptions to MerchantReturnPolicy markup, then check country, return window, and the policy shoppers can read.
By Crawlito · 5 min read
In short
- A store can describe its standard return policy under Organization.
- A product-specific return policy can be associated with its Offer when a genuine exception applies.
- A finite return window needs the correct number of days and the market where it applies.
On this page
If your store has a standard return window and a few final-sale products, describe the general policy under the store's Organization and handle real exceptions at the product offer level. Start with what a shopper can read and actually do. If the public policy, checkout wording, and structured fields describe different terms, resolve those differences before adding more markup. Google’s merchant return policy documentation
Turn the written policy into a table of decisions
Open the return policy as a new shopper in each market you plan to describe. Write down who can return a product, the country the terms apply to, how the return window starts, which items are excluded, the return method, and any fee. If customer service cannot answer an ambiguity from the current wording, identify the policy owner. A developer cannot infer a binding customer promise from the name of a checkbox in a CMS.
Imagine a fictional stationery store that accepts unopened notebooks for 30 days after delivery in one market, but excludes custom engraved covers. Note which catalog field makes an item engraved. If a product can be ordered plain or engraved, an offer selected on the page may determine the policy. A rule attached indiscriminately to the parent product could describe the engraved purchase incorrectly. The product variant guide helps identify how the selected offer is exposed.
Keep the customer-facing policy URL with each row. If one global page switches text based on a saved region, record how an anonymous visitor can locate the correct market terms. A policy selector that works only for returning customers makes the information awkward to share. Giving customers a stable path to the right terms also gives your team a reliable address for acceptance testing.
Put the ordinary rule in the right entity
Google supports hasMerchantReturnPolicy on Organization for standard store policy and documents different fields for product-level policies. Use the documented properties supported at each level. The following fragment illustrates a fictional merchant's finite window and the market it applies to. Add only terms your store actually offers. The maintained details page should explain the policy in language a buyer can understand.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Stationery",
"url": "https://example.com/",
"hasMerchantReturnPolicy": {
"@type": "MerchantReturnPolicy",
"applicableCountry": "GB",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30,
"merchantReturnLink": "https://example.com/returns/gb"
}
}Check the unit carefully. merchantReturnDays is a number of days measured from delivery in Google's documentation. If your business has a more complicated condition, express it accurately in the human policy and review which supported fields can represent it faithfully. A promise to “contact us within 30 days” may need further interpretation from the person who applies the policy. The organization markup guide shows how to locate the store's existing entity.
Trace exceptions through a real purchase option
Take one standard item and one exceptional item. Read their visible product text, selected offer, cart summary, and returns page together. For an engraved item, ask whether the exception applies before personalization, after approval, or only once manufacturing has begun. If the terms only change at a later step, a blanket final-sale declaration on the unconfigured product page can mislead someone buying the plain version.
Google supports a product-level policy attached to the relevant offer and explains the precedence when organization and product policies both exist. Keep exceptional data close to the catalog attribute that causes the exception. A separate list of handwritten URL exceptions can get out of date as soon as someone changes a handle, duplicates a product, or adds a new finish. Give the merchandiser a way to preview the resulting customer-facing wording when editing that attribute. Google’s merchant listing offer guidance
| Sample item | What to compare |
|---|---|
| Ordinary notebook | General policy page, organization markup, product wording |
| Engraved cover | Exact selected offer, visible exception, applicable terms |
| Same product sold abroad | Destination market, local policy URL, country in the data |
| Product with no explicit exception | The standard rule still applies after the template update |
Verify what the published templates actually contain
Fetch the policy and sample product pages without your merchant login. Check the canonical host, the visible terms, and the JSON-LD after a normal deployment. Search every graph for return policy entries. A theme can output the current policy while an extension supplies a second entry with an old number of days. A validator may accept the shape of each entry individually while the two give opposing instructions about the same sale.
Use Google's Rich Results Test for the supported markup and inspect the product and organization data it recognizes. A general schema validator can also help locate an unexpected entity. If a tool does not display a particular optional field, inspect the actual response and check the current feature documentation. Record which of these observations you made. The JSON-LD troubleshooting guide is useful for malformed blocks and duplicate entities.
Repeat the tests after a policy revision. Include an order date or product state where old terms may still apply so that a change for new shoppers does not rewrite the historical terms promised to prior customers. Search presentation is a separate question from contract administration. What you can test on the public site is that a prospective buyer sees one understandable answer for their market and purchase option.
Work through a purchase that crosses two markets
Imagine a buyer living in one country who orders from the storefront serving a neighboring market and has the goods delivered there. A policy author might have used “country” to mean the shop's headquarters, the dispatch warehouse, the customer's residence, or the market where the offer is sold. Check the definition of each field in Google's guidance. For the applicable country, identify the country the policy covers, including where the sale and return apply. Do not assume it is the place where the merchant registered its company.
Trace one representative order with the support team using fictional details. Ask which written instructions they would provide, where the customer would send the item, how long they have after delivery, and whether the standard label is prepaid. Compare those answers with the product's public policy and the generated structured fields. If the return destination country differs from the market where the policy applies, record both meanings explicitly in the internal mapping.
Now switch the shop's country selector and repeat the same test. Watch for a page that changes its visible terms while the machine-readable policy stays cached from the first market. Also check the policy link copied from the second view in an anonymous browser. A shopper who shares the terms with somebody else should still be able to identify which market's policy they are reading.
Frequently asked questions
Do all products need a copy of the standard store policy?
Google documents a general policy at the organization level. Represent specific exceptions on eligible offers when those terms genuinely differ.
Is an unlimited window represented by a very large number?
Use the documented policy category that corresponds to the real terms. A made-up number creates a finite promise that the store may never have intended.
Can a policy be correct in JSON and wrong for customers?
Yes. A syntactically valid block can describe the wrong country, item, or fee. Check it against the visible policy and real purchasing conditions.
Check an exception page
Run the free page check on a public product with a real exception, and compare its readable content and structured data with the policy used by your support team.
Filed under Structure and schema. Topics: ecommerce, structured-data, google