Shopify Payments Test Mode Has a Turn-Off Step Almost No Guide Mentions
Shopify Payments test mode lets you run practice orders with fake card numbers before you go live, and Shopify's own instructions cover turning it on in about four lines. What they don't cover — and neither does almost anything else ranking for it — is what happens to the orders you create while it's on, whether the apps already connected to your store treated them as real, and how to actually clean up before launch day.
Shopify Payments test mode lets you place practice orders with fake card numbers before your store takes real ones, and you turn it on from Settings > Payments > Manage > Test mode. What almost nothing written about it — including Shopify's own instructions — covers is the second half of the job: what happens to the orders you create while it's on, whether the apps already wired into your store treated them as real, and how to actually turn it back off before launch day without leaving a mess behind.
Turning it on
From your Shopify admin, go to Settings > Payments. In the Shopify Payments section, click Manage, find the Test mode section, and select Enable test mode, then save. This only appears once Shopify Payments is set up and approved as a gateway on your store — it's a state of that specific gateway, not a store-wide setting you can flip before Payments exists.
One thing worth knowing before you flip it: test mode blocks every customer from placing a real order while it's active, store-wide, not just yours. That's fine on a brand-new store nobody has found yet. It is not something to switch on for a quick five-minute check against a store that's already taking live orders — more on the alternative for that case below.
The test cards, and what they actually simulate
With test mode on, checkout stops accepting real card numbers and only accepts Shopify's published test values. The two worth memorizing: 4242 4242 4242 4242 completes a successful Visa charge, and 4000 0000 0000 0002 triggers a declined-card message, which is the fastest way to see exactly what a customer sees when a payment fails. Shopify publishes a fuller table — covering Mastercard, Amex, and specific decline reasons like insufficient funds or an expired card — in the same Test mode section of the admin, and it's worth pulling up live rather than copying from a third-party list, since the exact set can change. Any expiry date in the future and any three-digit CVV works with these numbers; nothing about the rest of the checkout form needs to be fake.
What activating it doesn't warn you about
Here's the part every guide ranking for this, including Shopify's own, skips: an order placed in test mode is a real Order object in your store, not a sandboxed copy that lives somewhere separate. Shopify's Admin API documents a boolean test field directly on the order resource — the field exists precisely because the order is otherwise indistinguishable from a real one to anything reading it. Nothing in Shopify's documentation says webhook delivery or app notifications are suppressed for test orders; the test flag is there so your code, or the app's code, can choose to filter it out. Most integrations were never written with that check in mind.
In practice that means a test order can trigger the same things a real one does: an abandoned-cart or post-purchase email flow firing to whatever fake address you typed in, a review-request app scheduling a follow-up, a Shopify Flow automation tagging a customer or notifying a Slack channel, or a server-side conversion event landing in an ad platform if you've got Conversions API-style tracking wired up rather than browser-only pixels. None of it is dangerous, but a "12 new orders today" Slack ping from your fulfillment app during a two-hour testing session is a bad surprise if you weren't expecting it, and a marketing automation that emails a nonexistent customer is a wasted send at best and a bounce-rate problem at worst if you're testing against a real inbox repeatedly.
Before you start a test run on a store that already has apps connected — not a brand-new build — check each app's settings for a "skip test orders" or "ignore test mode" toggle. Some do have one; it's just rarely on by default, because the app vendor can't assume every merchant wants it. If an app doesn't offer the option, the honest workaround is to keep the test session short and deliberate: place the specific orders you need to verify a flow, then move straight to cleanup rather than leaving test mode on to poke around for an afternoon.
Turning it off, and what happens to the orders you made
Deactivating is the same screen as activating: Settings > Payments > Manage > Test mode, then toggle it off and save. What doesn't happen automatically is any cleanup. The orders you created stay exactly where they are, marked with a "Test order" tag in the Orders list, and turning test mode off doesn't touch them.
Two things about those leftover orders are worth knowing before launch:
- They generally don't count toward your own Analytics and financial reports. Shopify's reporting is built to exclude test orders from sales totals, which is the right default — but "generally excluded from reports" is not the same as "invisible everywhere." They still sit in your Orders list, and anything outside Shopify's own reporting (an app's dashboard, a spreadsheet export, a manual count) may not apply the same filter.
- There's no native bulk-delete. An order with no real transaction attached — which test orders qualify for — can be permanently deleted from its order page under More actions, but that's a one-at-a-time action in Shopify's own admin. A handful of test orders is a five-minute cleanup. Thirty is not, which is a real argument for testing with a short, specific list of scenarios rather than clicking through checkout repeatedly "just to see."
A cleanup checklist before you actually go live
- Filter the Orders list for test orders and decide, deliberately, whether to delete or archive each one rather than leaving them mixed into the list your team will look at on day one.
- Check any connected marketing or automation app for messages it sent during the test session — a scheduled review request or an abandoned-checkout email to a fake address is easy to miss until a customer support inbox gets a bounce notice.
- If you run server-side ad conversion tracking (Meta's Conversions API, a similar setup for Google or Microsoft), check whether the test session sent events into a live ad account — this is the one item on this list that can quietly cost money, since it can skew a campaign's reported conversion rate mid-flight.
- Confirm test mode is actually off before announcing a launch date. This isn't optional cleanup — while it's on, real customers cannot check out at all, so a forgotten toggle is a launch-blocking bug, not a cosmetic one.
- Run one final check with a real card after switching off — a small purchase you refund immediately — rather than trusting the admin's toggle state alone. It's the only way to confirm the switch actually took from a customer's point of view, not just Shopify's.
When to use Bogus Gateway instead
Everything above assumes Shopify Payments is already set up as a gateway on your store. If it isn't — you're using a different processor, haven't been approved yet, or haven't decided — there's a separate option built for exactly that gap: the Bogus Gateway. Add it from Settings > Payments > Additional payment methods > Add payment method. It simulates checkout without needing Shopify Payments or any live processor connected at all, which makes it the right tool for testing a theme's checkout flow or an app integration before a payment provider decision is locked in. Its test card numbers are different from the Shopify Payments table above — don't mix the two lists, since a card that triggers a specific decline in one won't do the same thing in the other.
Who should skip this entirely
If your store is already live and taking real orders, don't switch on Shopify Payments test mode for a quick spot-check — it stops every customer from checking out, store-wide, for as long as it's on. For a live store, use a real card on a small purchase you refund afterward, or create a draft order from the admin (Orders > Create order) to test fulfillment and notification flows without touching the live checkout at all. Test mode is a pre-launch tool, not a maintenance one.
Most of what goes wrong with this feature isn't Shopify getting it wrong — it's that the setup half of the task is well documented and the cleanup half isn't, so stores launch with stray test orders, a marketing app that fired on a fake customer, or test mode quietly still switched on. If you're mid-relaunch and want someone to run the checkout, apps, and tracking checks before you flip live rather than after, that's the kind of pre-launch QA work we take on directly — get in touch and we'll tell you plainly what your specific setup still needs checked.
If the reason you're testing payments at all is that you're not sure Shopify Payments is the right processor for your store, we've covered the fee math and the countries where you don't get a choice before you build a test plan around a gateway you might not end up using. And if you've already gone live and your payout balance isn't behaving the way this article's test orders did, that's usually a verification hold rather than anything to do with test mode — worth ruling out before you assume the two are related.