How do you currently handle it when a customer wants to change an order after checkout?
Things like changing the size or variant, adding another item, fixing the shipping address, or changing the quantity.
Do you let customers make the change themselves, have your support team handle it, or just cancel and place a new order?
Curious what other store owners and operators are doing here, especially stores with a decent order volume.
We use a short edit window, then lock the order once fulfillment starts.
Put the cutoff in the confirmation email and use one support tag for change requests so they get handled first.
This is a really sensible workflow, especially the hard cutoff once fulfillment starts.
How do you handle the short edit window in practice? Is it a fixed time like 30 minutes, or does it depend on how quickly the order moves to fulfillment?
Also like the idea of tagging these requests separately so they get picked up before the order gets packed.
Hi there @MayraApps
For more significant sums, I tend to recommend splitting the changes into what can be safely modified and what will necessitate a new order. Changes in address and number of items can be processed immediately in many cases prior to processing shipment, but changes in variety or product availability and prices should be confirmed. If the order is already being fulfilled, canceling and reordering is usually cleaner. Having a solid cutoff window and documenting the process also helps to ensure your fulfilment stays consistent and errors stay minimal.
@SealSubs-Roan This is a good distinction. I especially like separating the “safe” changes from ones that can affect price or inventory.
The cutoff is probably the biggest piece too. Once an order moves into fulfillment, trying to edit it can create more problems than just canceling and reordering.
Do you have a fixed cutoff time, or does it depend on how quickly each order moves into fulfillment?
The cleanest policy is based on whether the requested change alters the commercial agreement.
Low-risk corrections such as a phone number or minor address typo can follow a documented support checklist. Changes to product, quantity, price, discount, shipping method, tax, or destination should trigger a new review because they can affect authorization, fraud checks, inventory, and fulfillment.
I’d give support three explicit outcomes: “edit allowed,” “manager approval,” and “cancel/recreate.” That is much safer than letting each agent improvise.
@AppAvio I like the three-outcome approach. It gives support a clear path instead of making every request a judgement call.
I’d probably add one more check: whether the order has already entered fulfillment. A change that is fine at 10 minutes after checkout can be a completely different situation once picking or shipping has started.
Having that status as part of the checklist could prevent a lot of avoidable fulfillment issues.
We tagged change requests for a couple of months just to see what they actually were, and it was overwhelmingly two things.
Address validation took care of most of the first group. The second turned out to be our variant selector letting people add to cart without ever actively confirming what they’d chosen, so they’d find out from the confirmation email.
If you haven’t counted yours yet, I’d start there before building the process. It’ll probably show if it’s more a support problem or workflow-related.