How to let customers cancel their own orders on BigCommerce

BigCommerce does not let customers cancel an order on their own — there is no native "Cancel order" button on the storefront, the confirmation page, or the customer account. Cancellation is a staff-only action in the control panel, and changing an order's status to Cancelled does not refund the payment. To offer customer self-service cancellation, you need an app layer that bounds it with a time window and an enforced refund rule.

That first paragraph is the short version. The longer version involves nearly a decade of merchants asking for this button, a subtle trap in how BigCommerce separates cancellation from refunds, and a fix that takes minutes to set up. Here's all of it.

The button merchants have requested since 2016

Search the BigCommerce community and you'll find the same question on a loop. "Can a customer cancel an order?" was asked back in 2016. "'Cancel Order' button required for customers" appeared in 2022. Developers building headless storefronts still ask how to implement order cancellation on custom Next.js frontends. The answer in every thread is identical: there is no native customer-facing cancellation. Your customer's only option is to contact you — email, chat, phone — and wait for a human to do it from the admin.

This isn't an oversight unique to small features. It's consistent with how BigCommerce treats all post-purchase changes: the order editor is built for staff, not shoppers. Address changes, variant swaps, quantity changes and cancellations all route through the control panel.

What cancelling an order actually does in BigCommerce

When a staff member opens an order and sets its status to Cancelled, two things happen — and one important thing does not:

• The status changes, which halts fulfillment workflows and (depending on your settings) notifies the customer.
• Inventory is restocked automatically, according to your store's inventory settings.
• The payment is NOT refunded. Cancellation and refund are separate actions. If you cancel an order and stop there, you've kept the customer's money. The refund is its own step — processed against the original transaction or issued as store credit.

That separation is the detail that bites new merchants. A customer who receives a "your order has been cancelled" email and then sees no refund for days will open a second, angrier ticket — or a chargeback.

The real cost of "email us to cancel"

Cancellation requests are a race against your own fulfillment speed. The customer who wants to cancel almost always wants it minutes after checkout — buyer's remorse, a duplicate order, the wrong variant, a better price found elsewhere. If that email lands in your inbox at 9pm on a Friday, the order may be picked and labeled before anyone reads it on Monday.

At that point it's no longer a cancellation. It's a return: outbound shipping you paid for nothing, return shipping someone has to cover, restocking work, and a customer who blames you for shipping something they "told you" to cancel. If they paid by card and feel ignored, a chargeback costs you the disputed amount plus a fee — for an order you would happily have cancelled.

And this is on top of an inbox already saturated with post-purchase noise: Gorgias's own data puts WISMO ("where is my order?") tickets alone at roughly 18% of support volume on average. Cancellations, address fixes and swaps stack on top of that. Every one of them is a ticket a human reads, answers and executes by hand.

How to add a customer cancel button properly

Self-service cancellation only works if it can't create chaos. Three controls make it safe:

• A time window. Allow cancellation from 15 minutes up to "until fulfillment" — when the window closes or the order ships, the button disappears automatically. No more racing the warehouse.
• An enforced refund rule. You decide once: automatic refund to the original payment method, or store credit. The system executes it consistently — no forgotten refunds, no 11pm judgment calls by a tired agent.
• Off-hours handling. A countdown that pauses outside business hours shows a Friday-night customer "Until Monday 9:15 AM" instead of a timer that expires while you sleep.

With OrderEdit.io, the "Edit order" option — including cancellation, if you enable it — appears on the order confirmation page and in the customer's account immediately after install. Inventory restocks natively, the refund follows your rule, and the request never becomes a ticket. Plans start at $39/mo with a 21-day free trial.

Half of cancellations are really edits

Here's the part most merchants miss: a large share of "cancel my order" requests aren't actually cancellations. They're a customer trying to fix something — wrong size, wrong color, wrong address, forgot an item — who sees no other way than cancelling and reordering. If cancellation is the only self-service option you offer, you'll process refunds for sales you could have kept.

That's why the cancel button belongs inside a broader self-service edit window. When the customer opens their order intending to cancel and sees they can simply swap the variant or fix the address instead, the sale survives. And when they do truly cancel, offering store credit as the refund path keeps the revenue in your store.

Write the policy down

Whatever window you choose, state it where the customer can see it: on the confirmation page ("You can cancel or edit this order for the next 60 minutes") and in your FAQ. A visible, honest cancellation policy reduces pre-purchase hesitation, sets expectations for what happens after fulfillment (a return process, not a cancellation), and gives your team a single rule to point to instead of negotiating every case.