Returns & reassurance

Reassurance is useful when it resolves a specific purchase risk. It becomes clutter when it adds badges, promises, or policy language without answering the question a shopper is actually carrying.

This module starts with returns because the decision is concrete. A first-time buyer needs to know the return window and who pays return shipping. The full policy can remain one tap away, but those two facts should not require a search through the footer.

Put the answer where the decision happens

Read Answer the return question on the product page before adding a generic reassurance strip or copying policy text into several templates. The lesson keeps the policy in one Shopify source of truth, places a short verified statement near the buy box, and uses product-level data only when the terms genuinely differ.

The implementation route depends on the active theme. Use a suitable product-information block when one exists. Assign a small theme edit when it does not. Use a metafield only for a real product-level difference, not as a substitute for one consistent policy.

Module diagnostic

Open a product page on a phone while logged out. Without using search or the footer, find:

1. how long the shopper has to return the item;
2. who pays return shipping; and
3. where the full terms live.

If any answer is missing, buried, or inconsistent with the policy, record the exact failure rather than adding a broad trust message.

Assignment

Write the two-fact line from the store's verified terms, choose its implementation route, and ask up to three unfamiliar people to find both facts without help.