MerchantReturnEnumeration
MerchantReturnEnumeration is a schema.org Enumeration for the category of a merchant's product-return policy. It is the value of MerchantReturnPolicy.returnPolicyCategory (and of the returnPolicyCategory on MerchantReturnPolicySeasonalOverride).
It has 4 members:
MerchantReturnFiniteReturnWindow: returns accepted within a specific window (typically 14, 30, 60, or 90 days). The most common category.MerchantReturnUnlimitedWindow: returns accepted with no time limit (lifetime-return retailers).MerchantReturnNotPermitted: returns not accepted (final sale).MerchantReturnUnspecified: the merchant has not stated a policy (a fallback; use the specific values whenever possible).
Full example of schema.org/MerchantReturnEnumeration json-ld markup
The markup is verified as valid with Rich Results Test from Google.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MerchantReturnPolicy",
"applicableCountry": "US",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30,
"returnMethod": "https://schema.org/ReturnByMail",
"returnFees": "https://schema.org/FreeReturn"
}
</script>Working with FiniteReturnWindow
Pair MerchantReturnFiniteReturnWindow with merchantReturnDays on the same MerchantReturnPolicy to specify the length. Google's product rich result requires both fields together to show a structured return-window chip.
Minimal valid version
The smallest markup that still produces a valid MerchantReturnEnumeration entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MerchantReturnPolicy",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30
}
</script>Google rich results this unlocks
MerchantReturnEnumeration is a structural type. It does not produce a rich result on its own.
Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). MerchantReturnEnumeration becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.
Common MerchantReturnEnumeration mistakes
Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.
- 01
FiniteReturnWindow without merchantReturnDays
WrongreturnPolicyCategory = FiniteReturnWindow with no daysRightAlways pair with merchantReturnDaysGoogle's return rich result requires both; without days, the chip does not render.
- 02
Using MerchantReturnUnspecified as a default
WrongMerchantReturnUnspecified on a site with a real policyRightState the actual categoryUnspecified is a fallback for genuine ambiguity; using it when you know the policy wastes the rich-result slot.
Schema properties in this example
About the example data
Xoo Code Shop's 30-day standard return policy for apparel.
Comments
Loading comments...