Reviewed October 20, 2026
Test orders on Shopify: Bogus Gateway, test mode, and what to check
Before launch and after every major change, a store should buy from itself. How Shopify's test payment options work, what a complete test order checklist covers, and when to turn test mode off.
Your options for fake money
Shopify gives you two clean ways to test checkout without real charges. The Bogus Gateway is a built in pretend processor: activate it in place of real payments and every card number follows a script, with specific numbers producing approvals, declines, and errors on demand. Shopify Payments also offers a test mode toggle that simulates transactions inside the real payments setup, closer to production behavior without moving money.
The Bogus Gateway is the older, simpler tool and still excellent for checkout flow work, since its scripted card numbers let you rehearse failures, not just success. Test mode on your real processor is better for verifying payout and settings configuration. Know which you have enabled at any moment, because the most embarrassing launch bug in ecommerce is a live store still running pretend payments.
What a complete test order checks
A useful test order walks the whole life of an order, not just the payment screen. Place it as a customer would, from a product page, ideally on a phone: add to cart, apply a discount code, check shipping options and taxes against your expectations, and complete checkout. Then follow the confirmation email as a customer reads it, checking sender, wording, and links, since you will never see that email in your admin wanderings.
On the operations side, confirm the order lands where fulfillment expects it, inventory decrements at the right location, any automation you built fires, and analytics record the purchase. Then run the unhappy paths: a refund, a partial refund, and a decline using the scripted failure card. Problems found in rehearsal are tickets; problems found by customers are reviews.
Test after changes, not just at launch
Launch is only the first rehearsal. The standing rule: any change to theme checkout elements, discounts, shipping zones, markets, taxes, or payment settings earns at least one fresh test order, and changes to apps that touch cart or checkout earn one too. Most store breakages are change events; the test order is how you attend the event instead of hearing about it.
Keep the drill short by keeping it written: a one page checklist with the test card numbers, the addresses to use, and the expected outcomes for rates, taxes, and emails. A written drill takes fifteen minutes and gets done. An unwritten one takes an afternoon of reconstruction and quietly stops happening by the third month.
Going live cleanly
When testing ends, reverse the exact steps you took: disable the Bogus Gateway or test mode, reactivate real payments, and place one small real order if your setup allows refunds to yourself cleanly, or at minimum verify the payment settings show live status and correct bank details. Then delete or clearly archive test orders so they do not pollute your reports and inventory history.
Pin a note where your team will trip over it: the date of the last test order and what it verified. When something breaks in November, knowing the store passed a full rehearsal in October, and what that rehearsal covered, turns a panic into a diff. Testing is not a launch activity. It is the store's fire drill, and it belongs on the calendar.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Backing up a Shopify store: what to save and how often, Shopify domains and business email: setup in the right order, and Staff permissions in Shopify: roles that protect the store.
Frequently asked questions
What card numbers does the Bogus Gateway accept?
It follows a script: entering card number 1 simulates a successful transaction, 2 produces a failure, and 3 triggers an exception, with any future expiry date and any three digit code. That scripting is the point: you can rehearse declines and errors deliberately instead of only ever testing the happy path.
Will test orders mess up my reports and inventory?
They create real orders in the system, so fulfill or cancel and refund them as part of the drill, and exclude the test window when reading early reports. Inventory decrements when the test order is placed and returns when it is cancelled properly. Tidy rehearsal, like tidy anything, is part of the exercise.
Should I test on mobile or desktop?
Both, but mobile first if you must choose, since most customers will meet your checkout there. Payment wallets, address autocomplete, and shipping displays all behave differently on a phone. Run the full drill on a phone and a shorter confirmation pass on desktop after significant changes.
How do I make sure I turned test mode off?
Check the payment settings directly and confirm your real gateway shows active rather than test, then verify the storefront checkout shows normal payment fields. Add it to the written go live checklist with a name and a date beside it. The stores that launch on pretend payments are the ones that relied on memory at the busiest moment.