The four post-purchase support requests, and what each one costs you
Pull a week of post-purchase tickets and sort them. Almost all of them are one of four sentences.
"I put in the wrong address." "Can I change it to a medium." "Can you make it two." "Can I cancel." The variety in the queue is mostly in the phrasing, and that matters because four request types is a small enough set to design around.
The four, and which ones a customer can safely handle
| Request | Share of the queue | Self-servable | The complication |
|---|---|---|---|
| Change shipping address | Usually the largest | Yes | Taxes recalculate, shipping rates do not |
| Change size or variant | Large in apparel | Only at equal price | A price change means collecting or refunding money |
| Change quantity | Moderate | Yes, downward | Upward is a new charge |
| Cancel the order | Steady | Yes, before fulfilment | Partial fulfilment blocks it |
The pattern is that anything which does not move money is straightforward to hand over, and anything which does is a different problem wearing the same clothes.
Address changes are the cleanest win and usually the biggest bucket. No money moves, the customer knows the correct answer better than your agent does, and the failure mode of not fixing it is a redelivery or a lost parcel. One caveat worth building for: changing an address recalculates taxes for the new destination but does not recalculate shipping rates, so a change across a rate boundary quietly leaves you shipping at the old price.
Variant swaps at the same price are equally safe. A medium for a small is an inventory movement, not a financial one.
Variant swaps at a different price are the awkward one. Now you are collecting more money or refunding some, mid-flow, from a customer who has already checked out. Shopify's own guidance notes that accelerated checkouts such as Apple Pay are unavailable for collecting payment after an edit, so the smooth path your customer used originally is not there for the top-up.
Cancellations are self-servable right up until something ships. After partial fulfilment they stop being a cancellation and become a return, which is a different workflow with different economics.
Cost them yourself, and do not use a benchmark
There is a well-circulated figure for what an ecommerce support ticket costs. It traces back to one study, republished by a chain of aggregators, none of which is a primary source. I am not going to put it in an article that other people will cite.
Your own number is both defensible and more useful, and it takes an afternoon.
Take one month of post-purchase tickets and tag them into the four buckets
Time ten of each, end to end
Multiply by your loaded hourly cost
Add the downstream cost of the ones that failed
Step four is the one that changes the answer. Handling an address-change ticket might take four minutes. Not handling it in time costs a parcel.
What self-serve actually removes
Be precise about this, because the category oversells it.
A self-serve editing tool removes the handling time on the three money-neutral requests, and only within the window before fulfilment ingests the order. It does not remove:
- Requests that arrive after the window closed. Those still land on an agent, and they are the hardest ones.
- Variant swaps that change the price, unless you have decided in advance how payment gets collected.
- Cancellations after partial fulfilment, which are returns.
- The fifth category, whatever yours turns out to be.
So the honest expectation is a large reduction in the biggest bucket, a partial reduction in two more, and no change to the difficult tail. That is still a substantial change to a queue where address changes dominate, and it is not the same as the tickets going away.
Order Editing handles the money-neutral three inside the fulfilment window, and it is free. What decides whether it helps is not the tool but the window, which is set by when your fulfilment provider pulls the order rather than by Shopify.
The honest part
The four-bucket taxonomy is drawn from what these tools are built to handle and from what merchants describe, not from a published study of ticket composition. Your mix will differ by category. Furniture skews to cancellations and delivery scheduling; apparel skews hard to size changes; anything with a long lead time skews to "where is it", which is a fifth bucket and a different problem covered in what WISMO is and how to reduce it.
I have also deliberately not given you a cost per ticket. That is less satisfying than a number and it is the correct call: a figure I cannot source properly would end up quoted back at me, and this whole library depends on that not happening.
And self-serve editing has a cost of its own that the ticket saving has to clear. You are delaying fulfilment for every order to create the window, which is worth it at fifteen minutes and questionable at two hours.
Frequently asked questions
What are the most common post-purchase support requests?
Four dominate almost every Shopify queue: change the shipping address, change the size or variant, change the quantity, and cancel the order. Address changes are usually the largest bucket, and in apparel size changes rival them. Everything else tends to be a small tail worth measuring separately.
Which order changes can customers safely make themselves?
The ones that do not move money: address changes, same-price variant swaps, and quantity reductions, all before fulfilment. A variant swap that changes the price requires collecting or refunding payment mid-flow, and Shopify notes accelerated checkouts like Apple Pay are unavailable for post-edit payment collection, so that one usually stays with an agent.
How much does a post-purchase support ticket cost?
Work out your own rather than using a benchmark. The circulated ecommerce figures trace back through aggregators to a single study and are not a primary source. Time ten tickets of each type end to end, multiply by your loaded hourly cost, then add the downstream cost of the ones that failed, which is where the real money sits.
Will self-serve editing eliminate these tickets?
It removes handling time on the money-neutral requests inside the fulfilment window, which is usually the largest share. It does not remove requests arriving after the window closes, price-changing variant swaps, or cancellations after partial fulfilment, which are returns. Expect a large reduction in the biggest bucket rather than an empty queue.
The exercise to run this week: tag one month of post-purchase tickets into the four buckets and count them. If address changes are your largest and most arrive within an hour of checkout, a short fulfilment hold with customer-side editing will take most of that bucket off the queue. If they arrive on day three, the window is not your problem and no editing tool will help.