Shopify’s market return controls need an agency test plan
Sima editorial · 12 November 2026 · Analysis · Release announced 10 November 2026
Imagine a clothing order with a shirt already delivered and a jacket still waiting to ship. The customer wants to send back the shirt and stop the jacket. For the agency maintaining the store, checking that a Return button appears answers only part of the question: the two items need different actions, and both requests need to reach someone who can handle them.
Shopify’s 10 November announcement introduces market-specific controls for self-serve returns and cancellations. Existing settings carry over automatically, and the new toggles sit alongside third-party returns apps in the editor. For agencies maintaining international stores, that creates a useful, bounded delivery task: prove which route each customer should encounter. Shopify’s announcement
Check the store before promising the feature
Market-specific activation requires Advanced or Plus and early access to the editor controls, indicated by an Order actions section in Customer accounts settings. Otherwise, activation is store-wide. Check the client’s admin before estimating. Setup requirements
Record the store’s plan, available controls, customer-account entry points and installed returns app. Ask the merchant to provide its approved operating policy and name the person who receives requests. The agency can then translate those decisions into settings and acceptance criteria without inventing the policy during implementation.
Keep two decisions separate: whether customers can submit requests, and which items qualify. Eligibility rules live in Settings > Policies; market-specific rules also have limited early access. A store can have market-specific activation while retaining one default policy. Record both configurations rather than assuming they change together. Return and cancellation rules
Build a small matrix with meaningful differences
Use these test cases for the hypothetical clothing store, with markets A and B. These are proposed tests, not recommended commercial policies or observed results. Give each order a unique reference and record its creation time, market, item state and applicable rules. Run settings changes in a controlled test setup; distinguish editor checks from customer journeys. Draft configuration changes take effect only after publication. Configuration scope
| Fixture | Setup | What to establish |
|---|---|---|
| Default route | Market A inherits the default; eligible delivered shirt | The customer reaches the intended request form. |
| Explicit override | Market B has Return disabled | The native return route reflects the override; the merchant’s chosen support route remains discoverable. |
| Parent change | Change the parent’s Return setting in a controlled test | A follows the change; B retains its explicit value. |
| Reset | Reset B’s override, then vary the parent | B follows the parent again. |
| Mixed order | One delivered shirt, one unfulfilled jacket; both eligible | Request the shirt’s return and the jacket’s cancellation separately; trace both requests to their owners. |
| In transit | A fulfilled shirt that has not arrived | Check return eligibility without assuming delivery is required. |
| Historical order | Comparable purchases before and after a rules change | Compare eligibility against each purchase’s recorded rules. |
The inheritance rows matter because an overridden setting stops following its parent or store default. Resetting restores inheritance. A screenshot of two matching toggles cannot tell you whether they will remain aligned after the next change. Test Return and Cancel independently: overriding one setting does not break inheritance for every setting in the market. Market inheritance
Evaluate the order’s market, not the customer’s residence. Fulfilled items can have return requests even in transit; cancellations concern unfulfilled items. Managed Markets EU orders retain request access despite disabled toggles, unless the merchant has deactivated its withdrawal feature for their own solution. Order scope and exceptions
For a Managed Markets client, add a separate EU case and record whether that feature or the merchant’s own solution handles it. Support still owns responses, return labels and return costs. The toggle matrix alone cannot establish that handover. Managed Markets responsibilities
Add cases just inside and outside the configured return window, including its start date. Changed return rules affect future purchases. Items bought with return rules disabled have no return time limit, although final-sale restrictions can still apply. Turning rules on later does not retrospectively add a deadline. A new test order cannot establish how the existing order book behaves. Rules and historical purchases
Follow the existing app all the way through
The announcement’s placement beside third-party apps is a reason to inspect coexistence, not evidence that the merchant should replace its app.
Start from the storefront’s returns link, the account navigation and an order notification. Native requests require the new customer accounts; legacy-account stores need a link to that experience. Include Shop app returns where the order email matches the customer’s verified Shop email. Account and Shop requirements
Write down where each entry point leads. If the native route and an app route are both visible, submit separate labelled test requests and inspect the receiving systems. Look for duplicate work, inconsistent instructions or a request that reaches a queue nobody monitors. Do not assume Shopify’s settings govern the app’s separate portal: establish its behaviour from the installed integration and the test result.
Compare the mobile journey too. Note the wording after submission and the next action promised. Cancellation requests leave the order unchanged until reviewed. Request handling
Hand over the exceptions with the settings
The useful deliverable is a short operating record: market, inherited or explicit settings, eligibility rules, customer entry point, receiving queue and owner. Attach an example request and the evidence for each tested outcome. Mark untested paths explicitly.
Have a support colleague follow one fixture from arrival to response using that record. If they cannot explain why two orders offer different actions, improve the handover before adding more screenshots. The change is ready when the merchant can maintain the decisions and handle the requests it creates.
Sources and scope
Based on Shopify’s linked announcement and help documentation, reviewed on 12 November 2026. The matrix is an agency testing proposal; no store tests or client outcomes are claimed.