Customer accounts / Improvement

Self-serve returns now
support "order cancellations"

Self-serve, which previously only handled return requests, now lets customers request order cancellations on their own. Cancellation rules can be configured per market alongside return rules, and they support the EU's "14-day right of withdrawal."

On this page
  1. What's actually changing (understand in 30 seconds)
  2. How it works: the flow for a customer requesting a cancellation
  3. How returns and cancellations relate
  4. How per-market rules work
  5. Supporting the EU Right to Withdraw
  6. Key setup steps (3 steps)
  7. 5 points developers should know
  8. 3 use cases you can put to work
  9. A one-line summary for your pitch

1What's actually changing

Until now, self-serve only allowed customers to request returns.
From now on, customers can request order cancellations themselves and merchants can configure cancellation rules alongside return rules.

Before: returns only

The only thing customers could request themselves through self-serve was a return.

Now: returns + cancellations

In addition to returns, customers can now request cancellations. Cancellation rules can be configured alongside return rules.

2How it works: the flow for a customer requesting a cancellation

Customer Self-serve Cancellation request From the order page request it themselves Runs alongside return requests Rule evaluation Per-market cancellation rules Evaluated against Default + overrides Processed according to rules
The buyer's entry point is self-service in Customer accounts. It's easiest to think of it as cancellation requests being added to the same flow as return requests.
* The detailed behavior of approval and refund processing after a request is not described.

3Relationship between Returns and Cancellations

ItemReturnsCancellations
Buyer action Already supported Request via self-service Added now Request via self-service
Rule configuration Set return rules Alongside return rules,setcancellation rules
Per market Supported Configurable per market Supported Configurable per market
Policy structure A default policy for the entire store. Override rules can be added for individual markets.

4How per-market rules work

Default policy (storewide) Return rules + cancellation rules Applied to the entire store If nothing is added, shared across all markets Override Market A (EU) Override the right-to-withdraw rules Market B Override with custom rules Market C Default (no override)
The key point is the "build on a default policy, override only the markets that need it" structure. Even when you add rules for a specific market,other markets are unaffected..

5Supporting the EU Right to Withdraw

EU

14-day withdrawal policy

Merchants selling in the EU can offer a "withdrawal policy." The period runs from the time of the order until 14 days after the last item is delivered .

Extend so it doesn't end on a weekend or holiday

You can extend the return window so it doesn't end on a weekend or holiday .

This withdrawal policy can be set without affecting the rules in other regions for the EU market only (market-specific rule override). It's the mechanism that supports compliance with the EU "right to withdraw" regulation.

6Setup essentials (3 steps)

1

Set the default policy

Prepare the default return + cancellation rules that apply across the entire store.

2

Override per market

Add market-specific rules (such as the right to withdraw) for individual markets like the EU.

3

Set up the point of contact

Extend the return window so it doesn't fall on weekends or holidays as needed.

The exact settings path and screen names in the admin are not describedin this article. For details, check the official "self-serve cancellations" help (link at the end of the article).

75 points engineers should know

Self

1. Cancellations are now self-serve too

A "cancellation request" has been added to self-serve in Customer accounts. It can be handled through the same buyer flow as returns, reducing inquiry-driven cancellation handling.

2. Managed alongside return rules

Cancellation rules are designed to be configured alongside return rules. Returns and cancellations are treated as separate concepts but run within the same rule framework.

3. Markets as a first-class concept

Both returns and cancellations can be configured per market. A two-layer structure of default policy + market override expresses regional differences.

14d

4. Express the EU right of withdrawal as a rule

Override the "order through 14 days after the last delivery" withdrawal window for the EU market only. Since it doesn't affect other regions, you can satisfy regulatory requirements while maintaining global operations.

5. Extend the window end date to avoid weekends and holidays

Being able to extend the return window so it doesn't end on a weekend or holiday is useful for CS operations and closing-process design. Note that details on Admin API / Webhook handling and approval flows are not documented in this article — meaning you should validate in a sandbox before automating.

8Three use cases you can apply to your business

EU
USE CASE 1

Automating "right-of-withdrawal compliance" for cross-border stores selling into the EU

Challenge
You sell into the EU and handle the 14-day right to withdraw after an order via manual emails or a custom implementation, which gets mixed up with other regions' policies and creates risk.
Solution
Override the "order through 14 days after the last delivery" withdrawal policy for the EU market only, and offer buyers a self-service cancellation request.
Impact
Turn regulatory compliance into a rule and eliminate person-dependent operations. It doesn't affect other markets, so it coexists with global policy operations.
Technical note
Expressed as two layers: a default policy plus market overrides. The internal behavior of approvals and refunds isn't documented in the article, so prior validation is recommended.
USE CASE 2

Shifting CS "cancellation inquiry" workload to self-service

Challenge
"Actually, I'd like to cancel" inquiries pile up in chat and email, and CS handles them one by one, causing backlogs during busy seasons.
Solution
Set up cancellation rules and switch to a flow where buyers can request cancellations themselves from their customer account.
Impact
Make routine cancellation handling buyer self-service so CS can focus staffed support on exception cases. It also shortens first-response wait times.
Technical note
Because it rides the same self-service flow as return requests, it's easy to integrate with existing return operations.
USE CASE 3

Eliminating "weekend/holiday endings" of the return window to level out closing tasks

Challenge
Deadlines for accepting returns and cancellations fall on weekends or holidays, so requests pile up on closing days or teams get confused handling them on days off.
Solution
Use the setting that extends the return window so it doesn't end on a weekend or holiday, shifting deadlines onto business days.
Impact
Consolidate closing, restocking, and refund operations onto business days to level out the workload. It also avoids the customer frustration of "the deadline closed on a holiday."
Technical note
Combined with per-market rules, it's easier to accommodate differences in regional holiday calendars (the specific calendar-integration spec isn't documented in the article).

9A one-line summary you can use in a pitch

"Self-service now supports order cancellationsin addition to returns.
Cancellation rules can be set alongside return rulesper market, and
The EU's 14-day right of withdrawalcan be made into a rule without affecting other regions."