Return-policy handoff notes should connect the customer-facing promise to the operational rules used for real orders. Record who owns the policy, which terms apply, how requests are evaluated, and how staff test the workflow. Do not assume a platform template settles legal obligations; the business owner should obtain jurisdiction-specific advice when needed.
Identify the policy and its owner
Record the current published policy URL, effective date, approving owner, support contact, return location, and the markets or sales channels in scope. Save an approved copy or version reference so staff can determine which terms applied when an older order was placed. List the next review date and events that trigger an early review, such as a new market, carrier, product class, or fulfillment partner.
Separate written terms from platform rules
Document both the customer-facing policy and the store's configured return rules. Shopify notes that a generated written policy does not automatically include configured return rules, and that rule changes apply to future orders rather than previous orders. Compare the two deliberately: return window, when the window starts, shipping charges, restocking fees, final-sale items, cancellation terms, and market-specific variations.
Define eligibility and exceptions
List which products may be returned, which are final sale, condition requirements, proof-of-purchase rules, damaged or incorrect-item handling, exchanges, gifts, and any hygiene or perishable exclusions. State who may approve an exception and what evidence is required. Avoid vague phrases such as reasonable condition unless the notes give staff an observable test.
Map the request workflow
Write the path from customer request to authorization, label or shipping instructions, receipt, inspection, disposition, refund or exchange, and closure. Name the owner and expected evidence at each step. If self-serve returns are enabled, document what customers see and which requests still need manual review. Shopify distinguishes fulfilled-item returns from unfulfilled-order cancellations, so staff should not use those terms interchangeably.
Explain refunds and inventory effects
Document who may issue a full or partial refund, how shipping and fees are handled, whether returned units are restocked, and how payment timing is communicated. Shopify permits refunds without first creating a return but states that a return cannot be created after that refund is issued. The handoff should therefore tell staff when a return record is required before a refund and how to avoid losing return-reason data.
Prepare customer messages
Keep approved templates for acknowledgment, approval, denial with a cited policy reason, shipping instructions, receipt, refund confirmation, and escalation. Templates should leave room for order-specific facts and should never claim a refund has been completed until the store and payment record show it. Record the supported reply channel and the owner of unanswered cases.
Test representative orders
Use test or approved low-risk orders covering an eligible item, final-sale item, partial return, late request, exchange, damaged item, and cancellation before fulfillment. Verify the customer view, staff decision, fee calculation, inventory result, status, notification, and audit trail. Do not change the live policy merely to make a test pass; record the mismatch for the owner.
Close the handoff
Record the outgoing and incoming owners, open disputes, temporary exceptions, unresolved platform limitations, and next audit date. The handoff is complete when the new owner can match the written promise to the configured rules, process each test case, and trace the resulting inventory and refund records.
Sources
- Setting up return and cancellation rules — Shopify Help Center
- Refunding orders — Shopify Help Center