My checkout just broke and orders stopped coming in, is this a Shopify outage or something I did?
When checkout suddenly stops converting, the first job is figuring out whose outage it is, yours, Shopify's, or your payment processor's, and the second is cleaning up any duplicate orders it left behind.
What's going on
"My checkout just died and I'm watching orders disappear in real time, is this Shopify or is it me?" That's the panic behind this problem: a store that was doing steady sales suddenly sees checkout errors, an abandoned-cart spike, or customers emailing screenshots of a broken payment page. Merchants report this same scramble in the Shopify Community whenever there's a platform hiccup, and the honest answer is that it can be either side. Shopify's checkout, payments, and storefront services are generally reliable, but they do have occasional regional or partial incidents, and separately, your own theme customizations, a recently installed checkout extension, or your payment gateway's own upstream issue can produce symptoms that look identical from the merchant's side.
The stakes are real: every minute of broken checkout is lost revenue, and a botched recovery, such as panicking and manually re-processing orders or telling customers the wrong thing, can create duplicate charges or duplicate order records that take hours to untangle afterward. The core challenge merchants describe is twofold: quickly figuring out whose problem it is, so you're not debugging your own theme during a Shopify-wide incident or vice versa, and avoiding a pile of duplicate orders from customers who understandably hit 'place order' several times when the first attempts appeared to fail.
Why it happens
Checkout is the most infrastructure-heavy part of any Shopify store: it touches Shopify's own servers, your theme's checkout customizations or checkout extensions, your payment gateway or processor, and sometimes third-party apps that hook into the cart or checkout flow. An outage can originate at any one of these layers, and the merchant-facing symptom, 'checkout is broken,' looks identical regardless of the cause.
Duplicate orders happen because checkout failures are rarely clean. A customer's payment can succeed on the processor's end while order creation stalls or times out on Shopify's end, or the reverse, and a frustrated customer resubmitting the form multiple times compounds the problem. Shopify's checkout has safeguards against charging the same submission twice, but it can't fully prevent a customer from creating several separate order attempts when they don't know whether the first one worked.
5 ways to fix it
Check Shopify's status page before touching anything in your store
Shopify publishes a public status page listing active and recent incidents across checkout, payments, storefront, and admin, usually with timestamps and resolution notes. If Shopify is already reporting a checkout or payments incident, the right move is patience and customer communication, not troubleshooting your own theme or apps. If the status page shows everything normal, the problem is more likely coming from your theme's checkout customizations, a recently installed checkout extension, or your payment gateway, and that's where you should look next.
Post a visible, honest status message for customers right away
During any checkout disruption, a simple on-site banner or announcement telling customers you're aware of the issue and working on it cuts down on repeated checkout attempts and support tickets. For most stores this messaging isn't automatic, so you'll need to add it yourself through your theme or a banner app, and repeat it over email or social if the outage runs long.
Don't manually re-trigger orders, and check for duplicates only after things are stable
When checkout is unreliable, customers often click 'place order' several times in a row, which can leave you with multiple order records for a single purchase attempt. A single successful payment generally shouldn't be charged twice, but partial failures, where payment goes through but order creation lags or fails, are a common source of the duplicate-order complaints that show up after an outage. Once checkout is working again, review your Orders list for the outage window, sort or filter by customer and timestamp, and look for near-duplicate orders (same customer, same total, minutes apart). Cancel and refund the extras yourself; Shopify does not automatically merge or dedupe orders for you.
Escalate to Shopify Support with specifics if your store looks affected but the status page is clear
If Shopify's status page shows nothing wrong but you're still seeing failed checkouts, contact Shopify Support (or your dedicated support channel if you're on a higher-tier plan) with exact timestamps, affected order or draft order IDs, and which payment method or gateway was involved. Some payment-processor-side problems, such as an issue with a specific card network or regional payment method, originate upstream of Shopify and won't necessarily appear on Shopify's own status page, so support may need to confirm and investigate separately.
Set up your own monitoring so you're not relying on customer complaints to notice
Consider a lightweight external uptime monitor that periodically loads your storefront and cart page and alerts you the moment something breaks, rather than waiting for a visible drop in order volume or angry emails to tell you. Pairing that with a habit of quickly scanning recent orders for same-customer, same-amount duplicates after any incident will shorten how long cleanup takes the next time this happens.
Bottom line
A break in the cart-to-checkout path is almost always either a genuine Shopify or payment-processor incident, which the status page will usually confirm, or a theme- or app-level checkout customization gone wrong. The fix is diagnosis and clear customer communication, not a hidden setting. If duplicate-order cleanup after outages becomes a recurring headache, a narrow, purpose-built monitoring tool can save the manual audit work, but it's not a substitute for knowing where the outage actually started.
Browse the rest of the problem library, run a free storefront scan to catch issues like this automatically, or email us and we'll work out a custom solution for it.