A practical Shopify returns workflow checklist
Use this checklist to connect policy, account setup, review and fulfilment. Work through it before opening a new request channel and whenever a policy or return tool changes.
Pre-launch information. Public availability and final plan access are subject to Shopify review.
Before customers start a request
□ Publish the return window and specify whether it starts at purchase, fulfilment or delivery. □ List eligible items, condition requirements, exclusions and exception owners. □ Explain return postage, refund timing and how an exchange is handled. □ Choose one customer entry point and link to it from order, help and policy pages. □ Confirm the store's Shopify Customer Accounts experience and required app extension setup.
Make the written policy match the configured settings. If the return tool supports a maximum window, choose a value within its supported range and verify the customer-facing wording. Give Me Another's current settings support a 1–60 day window; this does not choose a policy for the merchant.
At the customer entry point
□ Test that a signed-in customer can start from an order they are entitled to see. □ Check that the extension works on desktop and mobile. □ Show customers only request choices that match the store, plan and item rules. □ Explain that submitting a request is not the same as approval or a refund. □ Provide a support route for an inaccessible order or an unusual case.
Use an eligible test order and an ineligible example. In the current Give Me Another flow, the customer account authenticates the request and the app checks customer ownership of the order. Do not use a public order-number form as a substitute for account verification.
During eligibility checks
□ Verify payment, fulfilment and prior return state. □ Confirm the item and quantity are still returnable. □ Apply the return window using the date defined in the policy. □ Check product exclusions and any documented exception. □ For a same-product exchange, confirm the requested variant is available for sale and has stock. □ For a different-product request, confirm plan entitlement and merchant configuration.
Record the reason an option is unavailable. This gives staff something specific to explain and helps identify configuration errors. In Give Me Another's current plan map, different-product requests require Growth or Scale and merchant enablement; same-product exchange choices depend on the order, catalogue and inventory.
At merchant review
□ Assign new requests and review the oldest first. □ Confirm the requested outcome, reason, original line and order context. □ Ask for missing details before deciding. □ Use manual review for exceptions, uncertain eligibility and high-risk cases. □ If conditional approval is enabled, document the exact reasons and order-age rules. □ Record the decision and who made it.
A conditional rule should be narrow enough that staff understand why it applied. Give Me Another currently defines conditional approval for eligible requests on Growth and Scale, with merchant configuration. Do not describe this as automatic approval of all returns or exchanges.
After approval or decline
□ Tell the customer the decision and the next action they need to take. □ Recheck inventory and price before an exchange is processed. □ Arrange return instructions or postage under the store's policy. □ Complete refund, order, payment and fulfilment actions in the appropriate Shopify workflow. □ Send a clear update when the replacement is actually arranged or the refund is processed. □ Close the request only when the agreed operational work is complete.
A request or approval does not itself issue a refund, create a label, reserve inventory or fulfil a replacement. Keep those steps visible in the merchant process so that customers are not told an outcome has completed before the team has taken the relevant Shopify action.
After launch and after policy changes
□ Review first-response time, request volume and repeat contacts. □ Sample approvals and declines for consistent policy application. □ Check exchange reasons for sizing, colour or product-content issues. □ Confirm request allowances and current plan configuration before promotion. □ Re-test boundary dates, unavailable variants and inaccessible orders after changes. □ Update the policy, help content, account experience and staff notes together.
Keep a dated QA note with the test store, account type, example order state and expected result. Use customer data only where the team has an appropriate operational purpose, and avoid keeping unnecessary information in informal spreadsheets or support notes.
Explore the Give Me Another merchant review workflow and its current eligibility checks.
Questions merchants ask
What is the first step in a Shopify returns workflow?
Publish a policy that defines the return window, eligible items, postage, refund handling and customer entry point.
Who should handle exceptions?
Assign a named role or team and record the reason, so policy exceptions remain consistent and reviewable.
When is a request complete?
After the merchant decision and any required Shopify refund, return or fulfilment work are complete and the customer has been updated.