01 / Start with the ordinary path
Give customers the answer they came for.
Begin with the most common return journey. Put the core rule near the top, then break it into the questions a customer will actually ask. Avoid making someone translate internal terms such as “authorization,” “RMA,” or “restocking” before they know what to do.
Make the standard rule scannable
- What products or order types are covered
- The return window and the event that starts it
- The condition, packaging, and proof of purchase you need
- Who pays for return shipping, if that varies by case
- What happens after the item arrives back
Use the exact values your brand has chosen. If the window is measured from delivery, say “from delivery,” not only “within the return period.” If the refund begins after inspection, say so. Precision is kinder than a broad promise that leaves the customer to guess what counts.
02 / Treat exceptions as a first-class path
“It depends” is not an explanation.
Exceptions are where policies become difficult to trust. They may cover sale items, personalized products, hygiene-sensitive goods, damaged deliveries, exchanges, or a request outside the ordinary window. Only include the exceptions that apply to your business, and give each one a clear label.
Name the situation
“Personalized items” is easier to find than a paragraph that implies it.
State the change
Explain whether the item is excluded, eligible for an exchange, or reviewed individually.
Give the next step
Tell the customer what to send, where to send it, or when to contact your team.
- Name the exception plainly instead of hiding it in a long paragraph.
- Explain what changes from the ordinary path.
- Tell the customer what information or action is needed next.
- Say who will review the case and how the customer will hear back.
If a decision is genuinely case-by-case, describe the review rather than promising an outcome. A useful exception path can say what your team needs to assess, while keeping the final decision with the person responsible for it.
03 / Write for action
Turn policy language into a small decision guide.
A clear policy is not just accurate; it helps a customer choose the right next step. Put the answer before the background, use short labels, and separate what the customer does from what your team does.
| Customer needs to know | Write it as |
|---|---|
| Whether the rule applies | “This applies to…” |
| What to prepare | “Before you start, have…” |
| What happens next | “After we receive it, we…” |
| Where the rule changes | “If this is your situation…” |
Then check the places where customers make decisions: product pages, order emails, the account area, and the first reply from support. A policy that is clear in one place but vague in another still creates a confusing experience.
04 / Before you publish
Read it as someone who has never seen your process.
Ask a teammate who did not write the policy to find the answer to these prompts:
- “I received the wrong item. What should I do?”
- “My situation is not listed. What information should I send?”
- “When will I know what happens next?”
If they have to search across several sections or infer an exception, rewrite the path. The goal is not to remove every edge case. It is to make the rule, the exception, and the next human step visible.