A checkout that completes is not a checkout that works. After a theme or app change, the test is whether the order in your admin holds everything the storefront collected.
After a theme edit or a new app on a live store, place a real order through the storefront, the way a customer would. Then open it in your Shopify admin and check it holds everything the shopper entered. Then cancel and refund it.
Do it twice: once through the normal cart, and once through the Buy it now button. They are different routes and they break differently.
Save Shopify's simulated payment options for stores that are not taking orders yet. On a live store they get in the way of real customers, for reasons covered below.
Shopify describes a test order as a way to check that your checkout and your settings for order processing, inventory, shipping, email notifications and taxes are all correct. It recommends placing one during setup and whenever you change payment settings.
A theme or app change deserves the same check, for a reason that is easy to miss. The storefront collects information before checkout ever sees it: order notes, gift messages, personalisation fields. A theme edit can break any of those without the checkout looking wrong at all.
So a test order passes only when all of these are true:
A checkout that completes but loses the gift message is a failed test, not a passed one.
Shopify documents three ways to place a test order. They are not interchangeable, and the difference matters most on a store that is already selling.
| Method | How it works | On a live store |
|---|---|---|
| Real order, then cancel and refund | A normal order through your real payment provider, cancelled and refunded straight away | The safe default. Shopify notes your payment processor may charge a fee |
| Test payment gateway | A simulated gateway. You must switch off your credit card provider before you can turn it on | Risky. While it is on, real customers cannot pay by card, and every order placed is a test order |
| Shopify Payments test mode | Uses Shopify's test card numbers instead of real cards | Shopify says not to turn it on for a store in production. Real cards are refused and some local payment methods disappear from checkout |
Both simulated options change what real customers can do at checkout while they are switched on. If you must use one on a live store, do it in your quietest hour, keep the window short, and switch it off the moment you are done.
If you do use the Test payment gateway, Shopify's test details are simple. Enter Test payment gateway as the name on the card, then use card number 1 for an approved payment, 2 for a declined one and 3 for a gateway failure. The order total has to be more than the equivalent of $1. Test orders never show up in your payouts or reports.
Shopify Payments test mode also does not cover everything. Shopify lists POS card readers, Shop Pay Installments and PayPal Wallet as payments it cannot test.
Try it on one of your own procedures.
Record a process once, AI writes the structured SOP. 3 free SOPs, no credit card.
One happy-path order hides the most common theme breakage. Run two separate orders.
The cart route. Start with an empty cart. Type something distinctive into every personalisation or gift message field, such as TEST-GIFT-001, so you can find it later. Add to cart, go to the cart, then check out. If shoppers can check out from both a cart drawer and a full cart page, test each one separately, and repeat on a phone.
The Buy it now route. Empty the cart again and use the Buy it now or express checkout button on a product page. This route skips the cart entirely.
Shopify states that accelerated checkout buttons don't support cart attributes. A gift message field that lives on the cart page is never seen by a shopper who buys straight from the product page. Test it, and if the field matters, put it where both routes will meet it.
One rule for anything you could not test: if a payment method or route is unavailable in your test, write it down as untested. Not as passed.
Open the order in your admin and work down this list.
If you fulfil through ShipBob: how to confirm a test order was routed to the warehouse you expected.
Use the same test order to confirm GA4 recorded the purchase once, with the right value.
How the abandoned checkout flow is set up, so you can confirm a completed test order did not trigger it.
Keep one short log for every run. Write down the date, who ran it, the device, which routes were tested, which were not, the theme version, and the test order number. The theme version and order number are the first two things a theme developer or app support team will ask for when a field stops saving.
Then the clean-up that usually gets forgotten:
Cancelling and refunding the test order the same way you would a real one, including writing the outcome back.
A checkout QA routine goes out of date faster than most procedures, because Shopify keeps changing the checkout underneath it.
The clearest recent example is Shopify Scripts. Shopify's own help centre states that as of 30 June 2026, Shopify Scripts has been deprecated, and any Scripts still published on a store have been deactivated and no longer work. A QA step written to check discount or shipping logic built with Scripts now tests something that no longer runs.
Three habits keep the routine honest:
How a procedure quietly stops matching the screens it describes, and the signals that give it away.
This is where ReccordSOP fits. Record your next test order run once, and it becomes a step-by-step SOP with a screenshot of every step and the clicked button highlighted. Record it again after Shopify changes something, and ReccordSOP compares the two runs and shows which steps changed, instead of overwriting the old version. What it will not do is place the test order or check your admin for you. Someone still has to run it.
Start with your next theme change. Run both routes, log the order numbers, and record the run while you do it. That recording is the procedure for every theme change after it.
On a live store, the safest way is a real order through your storefront using your normal payment provider, which you then cancel and refund straight away. Your processor may charge a fee. Shopify also offers its Test payment gateway and Shopify Payments test mode, but both change what real customers can do at checkout while they are on, so they suit stores that are not taking orders yet.
Shopify says not to turn on Shopify Payments test mode for a store in production. While it is on, real cards are refused and some local payment methods are not available at checkout. The Test payment gateway requires switching off your card provider first, so real customers cannot pay by card while it is active.
With the Test payment gateway, enter Test payment gateway as the name on the card, then card number 1 for an approved payment, 2 for a declined payment, or 3 for a gateway failure. Use any three-digit CVV and any future expiry date. Shopify Payments test mode uses its own list of test card numbers.
No. Test the normal cart route and the Buy it now route as separate orders, because Shopify's accelerated checkout buttons don't support cart attributes. A field on the cart page is never seen by someone buying straight from the product page. If shoppers can use both a cart drawer and a cart page, test those separately too, and repeat on a phone.
Orders placed through Shopify's Test payment gateway or Shopify Payments test mode don't appear in your payouts or reports. A real order that you cancel and refund is a real order, so handle it through your normal refund process and keep it out of fulfilment.
3 free SOPs to start. No credit card required. See if drift detection keeps your docs honest.
Start for freeI built ReccordSOP after watching too many DTC ops teams lose months to undocumented workflows. These SOPs are battle-tested with Shopify operators running $1M to $50M brands.
Last reviewed October 7, 2026
A refund starts in your helpdesk and ends in your store. The seam between them is where refund procedures quietly break.
Most SOPs are wrong within 90 days of publishing. Here's how to detect it before it costs you a customer.
A shipping rate nobody has touched in months can still start charging the wrong amount. The rate did not change. Something it reads from did.
We use essential cookies for sign-in and a small amount of analytics to improve the product. Privacy policy.