How to Do a Test Order on Shopify: Complete Step-by-Step Guide for 2026 August

Knowing how to do a test order on Shopify is one of the first skills every store owner and developer must master before going live. A test order lets you verify that your checkout flow, payment processing, order confirmation emails, shipping rules, and discount codes all work exactly as expected — without charging a real credit card or affecting your actual revenue data.

Shopify provides a built-in Bogus Gateway specifically for this purpose, and understanding how to use it correctly can save you from costly mistakes at launch. Keeping an eye on shopify stock trends is useful context when timing a store launch, but nothing replaces hands-on checkout testing before you flip the switch.

Before running a test order, you should have a clear understanding of what you are trying to verify. Most merchants want to confirm that the correct price is charged, that taxes and shipping are calculated properly, that inventory decrements after a purchase, and that the post-purchase email sequence fires. Developers working through the Shopify Partner dashboard have additional testing tools available, including test credit card numbers that simulate specific failure scenarios such as declined cards, insufficient funds, and gateway errors. These scenarios are critical to test so your customers never encounter an unhandled error state during a live purchase.

Shopify's Bogus Gateway is enabled through the Settings section of your admin dashboard. Navigate to Settings, then Payments, and scroll to the section labeled "Third-party providers." From there you can search for and enable the Bogus Gateway. Once it is active, you will need to place your store into test mode so that no real transactions are processed. This is a temporary configuration — you will switch back to your production payment provider once testing is complete. The process takes under two minutes, and the gateway accepts a specific set of fake card numbers that trigger different outcomes.

Understanding Shopify fees is important context when testing because your test orders should reflect the real transaction costs your business will incur. Shopify charges a transaction fee on every order processed through a third-party payment gateway unless you use Shopify Payments. These fees range from 0.5% to 2% depending on your plan tier.

During test mode with the Bogus Gateway, no fees are charged, but you should run at least one live test with a real card after you switch to production to confirm that fees are being calculated correctly in your reporting dashboard. Many merchants are surprised to discover that test order data sometimes populates analytics reports and must be manually archived.

The test order workflow also covers digital products, subscription items, and products with multiple variants. If your store sells a T-shirt in five sizes and three colors, you should test at least one variant from each size group to confirm inventory tracking works independently per SKU. Subscription apps installed from the Shopify app store often have their own sandbox modes that must be enabled separately from the Bogus Gateway. Always check the documentation for each installed app before assuming that the core Shopify test mode covers all app-specific behaviors — this is a common source of errors during pre-launch QA.

After you complete your test order, Shopify will show the order in your admin under Orders. You should review every detail: the line items, the shipping address, the applied discount codes, the tax breakdown, and the payment status. Test orders in Bogus Gateway mode will show a payment status of "Authorized" or "Paid" depending on which test card number you used. You can also test partial refunds and full refunds through test orders to make sure your refund workflow is configured correctly. Many merchants discover that their refund email templates contain broken links or outdated branding only during this phase.

Once you are satisfied that every scenario has been tested, go back to Settings, then Payments, and disable the Bogus Gateway. Re-enable your production payment provider, and make sure test mode is turned off. Run one final live transaction with a real card — even a $1.00 test purchase — to confirm end-to-end production behavior. Then immediately issue a refund on that transaction. This final check ensures your live payment credentials are working correctly before your first real customer reaches checkout, and it confirms that your refund process functions in a production environment.

The Bogus Gateway is Shopify's official sandbox tool, but understanding exactly how the test card inputs work makes your QA process far more effective. When you type the number "1" into the card number field during a Bogus Gateway checkout, Shopify simulates a fully authorized and captured payment. The order will appear in your admin with a "Paid" status, inventory will decrement, and all fulfillment automations will trigger exactly as they would for a real order. This is the scenario you want to run first because it tests your entire happy-path flow from cart to confirmation email.

Typing "2" in the card number field simulates a payment decline. This is critically important to test because your storefront must handle declined payments gracefully. The customer should see a clear error message, their cart should remain intact, and no order record should be created in your admin.

If your theme or any installed app interferes with this error state — for example, partially creating an order or failing to restore cart items — you need to fix that before launch. Declined card handling is one of the most common sources of customer complaints in new Shopify stores and is worth testing across multiple product types.

The number "3" triggers a gateway exception, which is different from a simple decline. An exception represents a technical error between Shopify and the payment provider — for example, a timeout or a malformed request. Your error page should communicate that the issue was on the system's end, not the customer's fault, and should invite them to try again or contact shopify support if the problem persists. Many merchants skip this scenario entirely during testing, which leads to poorly worded error pages that confuse customers and increase abandoned cart rates during legitimate system hiccups.

Beyond the three core Bogus Gateway scenarios, Shopify Partners and developers working in development stores have access to test credit card numbers provided by Shopify's payment partners. These include Visa, Mastercard, and American Express test numbers that simulate specific behaviors like 3D Secure authentication challenges, AVS mismatches, and card network-specific decline codes. If you are building a custom checkout experience or integrating a headless storefront using Shopify's Storefront API, you will want to use these extended test credentials to verify your custom payment flow handles all edge cases properly.

One area that many merchants overlook during test order setup is the email notification system. Every Shopify order triggers a cascade of email notifications: order confirmation to the customer, new order notification to the store owner, and potentially fulfillment and shipping confirmation emails if you have those automations configured. During a test order, all of these emails will fire to whichever addresses are configured in your notification settings. It is good practice to temporarily set your customer notification email to a test inbox you control so you can review the exact formatting and content that your customers will receive.

Shopify's test mode also interacts with installed apps from the Shopify app store, but not always in the way you expect. Apps that add upsells, post-purchase flows, or loyalty point accruals at checkout may behave differently in test mode depending on how the app developer implemented their sandbox detection. Always check each app's documentation for test mode compatibility.

Some apps require you to separately enable a sandbox or staging mode within the app's own settings panel. Testing with apps active is essential because apps frequently modify the checkout experience in ways that can break your core order flow if they are not properly configured for your specific product catalog and shipping zones.

After your test orders are complete, Shopify gives you the option to archive or delete test order records. It is strongly recommended to archive rather than delete them, as deleted orders cannot be recovered and may create gaps in your order numbering sequence that can confuse accounting and fulfillment teams.

Some merchants prefer to use a dedicated development store — available for free through the Shopify Partner program — to run all pre-launch testing so that no test data ever enters their production store's order history. This approach also makes it easier to do repeated end-to-end testing when you push major updates to your theme or checkout flow.

Troubleshooting failed test orders is a skill that separates confident Shopify merchants from those who launch with lingering anxiety about their checkout. The most common issue encountered during test order setup is forgetting to enable test mode after activating the Bogus Gateway.

If you enable the gateway but do not check the test mode box, Shopify will attempt to process your test card numbers through a real payment flow, which will fail immediately because "1", "2", and "3" are not valid card numbers on any real network. Always confirm that both steps — gateway activation and test mode toggle — are completed before attempting a test purchase.

Another frequent troubleshooting scenario involves tax and shipping rates not appearing at checkout during a test order. This usually happens when a merchant has set up shipping zones but has not assigned rates to those zones, or when the customer's test address falls outside all configured shipping zones.

Shopify will not charge shipping if no rate matches the destination, but this can also cause the checkout to stall if your store is configured to require a shipping method selection before payment. Testing with multiple shipping addresses — including international addresses if you ship globally — is essential for catching these zone configuration gaps.

Discount codes are another area where test orders frequently reveal problems that would embarrass a store at launch. A discount code that works in isolation may fail when combined with a subscription product, a bundle, or a product tagged as excluded from promotions.

During your test order phase, run each discount code in multiple scenarios: alone, combined with other discounts if stacking is enabled, with products that have minimum purchase requirements, and with products that are explicitly excluded from promotions. Shopify's discount system has numerous edge cases, and discovering them during testing rather than after a social media promotion goes viral is critically important for your brand reputation.

Inventory management issues are among the trickiest to catch during test orders because they depend on your inventory tracking settings. If a product is set to continue selling when out of stock, a test order will complete even if inventory drops to zero or below, which may not match your intended behavior.

Conversely, if a product is set to stop selling when out of stock and you only have one unit available, a second test order attempt will fail at checkout. Testing both scenarios deliberately — with inventory tracking on and off, and with stock levels at zero and above — ensures your storefront behaves correctly across all inventory states your business will realistically encounter.

Email notification troubleshooting during test orders deserves special attention because email deliverability is complex and often overlooked during pre-launch QA. Shopify sends all order emails from a shared sending infrastructure, but your store's From name, Reply-to address, and email content can all affect whether emails land in inbox or spam.

During your test order phase, place test orders with email addresses on multiple providers — Gmail, Outlook, Yahoo, and your own business domain — and check both the inbox and spam folders for each. If any notifications land in spam, you may need to configure custom email domain authentication through Shopify's email settings or a third-party email service provider.

App conflicts are a sophisticated troubleshooting category that requires methodical isolation to diagnose. If your test order fails in an unexpected way and you have multiple apps installed, temporarily disable all apps except the core Shopify checkout and rerun the test. If the order succeeds, re-enable apps one at a time and repeat the test after each activation until you identify which app is causing the conflict.

Most reputable apps in the Shopify ecosystem are well-tested, but conflicts can arise from apps competing for the same checkout event hooks or modifying the same DOM elements on the checkout page. The Shopify app store reviews and support forums are useful resources for identifying known conflicts between popular apps.

Webhook configuration is an advanced area that test orders help validate for merchants using custom integrations. If your store sends order data to an external ERP, warehouse management system, or custom fulfillment provider via webhooks, test orders will trigger those webhooks in test mode, allowing you to verify that your external system receives and correctly processes the payload.

Check your webhook delivery logs in the Shopify admin under Settings > Notifications to confirm that all configured webhooks are delivering successfully and returning 200 status codes. Failed webhook deliveries during live operations can cause orders to be missed entirely by your fulfillment system, so catching these failures during testing is genuinely critical for operational continuity.

Advanced testing strategies go well beyond the standard Bogus Gateway workflow and are essential for merchants running high-volume stores, subscription businesses, or complex B2B operations. One of the most valuable advanced techniques is load testing your checkout flow before a major marketing campaign or product launch. Shopify's infrastructure is designed to handle high traffic spikes, but your installed apps, custom theme code, and third-party integrations may not be equally robust. Tools like Shopify's built-in analytics and external performance monitoring services can help you identify bottlenecks before your launch traffic reveals them to real customers at the worst possible moment.

Multi-currency testing is another advanced scenario that many international Shopify merchants skip. If your store uses Shopify Markets or a third-party currency converter to display prices in local currencies, you need to verify that test orders reflect the correct converted price at checkout, that taxes are calculated in the appropriate currency, and that your payment provider correctly settles the transaction in the chosen currency. Currency rounding differences and exchange rate fluctuations can cause small discrepancies between displayed and charged amounts that, while legal, may generate customer complaints if they are not disclosed clearly at checkout.

B2B merchants on Shopify Plus should test their wholesale pricing, customer-specific discount tiers, and net payment terms during the test order phase. Shopify Plus offers dedicated B2B features including company accounts, payment terms like Net 30 and Net 60, and quantity-based pricing rules that behave differently from standard consumer checkout flows.

Each of these features requires separate testing with accounts that have the appropriate B2B customer tags assigned. The shopify fees structure also differs for Plus merchants, with a fixed monthly rate replacing the percentage-based transaction fees that apply to lower-tier plans, so confirming that your fee reporting reflects the Plus structure is part of a thorough test order review.

Subscription testing is a specialized category that requires working with your chosen subscription app's own test environment in addition to the standard Shopify Bogus Gateway. Apps like Recharge, Bold Subscriptions, and Shopify's native Subscriptions feature each have their own test card credentials and sandbox modes.

A subscription test order should verify not only the initial checkout but also the recurring billing cycle, the customer-facing subscription management portal, pause and cancellation flows, and the skip-a-delivery feature if your store offers it. Failed recurring charges are one of the leading causes of subscriber churn in subscription businesses, so testing these scenarios thoroughly is directly tied to your revenue retention.

Gift card testing is an area that catches many merchants by surprise. If your store sells digital gift cards, you need to verify that the gift card code is delivered to the recipient's email immediately after purchase, that the code can be applied successfully at checkout, and that partial redemptions correctly reduce the remaining balance on the card.

Test orders for gift card products behave differently from standard product orders in Shopify's system — gift card inventory is not tracked in the same way as physical products, and the fulfillment flow is automated rather than requiring manual fulfillment steps. Always run a complete gift card purchase and redemption cycle during your pre-launch testing.

Headless Shopify implementations using the Storefront API or Hydrogen framework require a fundamentally different testing approach compared to standard Shopify Online Store themes. In a headless setup, your frontend is completely decoupled from Shopify's backend, which means that the standard Bogus Gateway test mode must be enabled in your Shopify admin while your custom frontend handles the payment UI rendering and API calls independently.

Test orders placed through a headless checkout use the same Bogus Gateway card inputs as standard checkout, but you must separately verify that your custom frontend correctly handles all API responses including success confirmations, decline messages, and error states that Shopify's API returns as JSON rather than HTML redirects.

Returning customer testing rounds out a comprehensive pre-launch QA strategy. Create a test customer account, complete one test order, then log back into that account and verify that the order history is displayed correctly, that reorder functionality works, and that saved payment methods — if your store uses Shopify's customer-saved payment feature — are stored and retrieved properly.

Loyalty program apps, referral apps, and customer review platforms often trigger post-purchase emails and in-app prompts that activate after an account's first or subsequent orders, so testing these flows with a returning customer account ensures that your post-purchase marketing automation fires at the correct cadence for each customer segment.

Building a repeatable test order protocol is one of the highest-value investments a Shopify merchant or developer can make. Rather than running ad hoc tests before each launch or major update, creating a documented QA checklist that your team follows consistently ensures that no scenario is accidentally skipped under time pressure.

A well-designed test protocol covers the happy path, every failure scenario, edge cases for your specific product catalog, and post-order workflows including fulfillment, shipping notifications, and returns. Store this protocol in a shared document that your team can update as your store evolves and as new apps are added to your tech stack.

The relationship between testing rigor and Shopify costs is straightforward: merchants who invest time in thorough pre-launch testing spend significantly less on customer service, refunds, and reputation management after launch. A single viral social media post about a broken checkout can cost a small Shopify store thousands of dollars in lost sales and brand damage — damage that a 30-minute test order session would have prevented entirely. When you factor in the time value of customer service emails, refund processing, and churn from frustrated first-time buyers, the ROI of comprehensive checkout testing is essentially infinite relative to its cost.

Shopify updates in October 2025 introduced several changes to the checkout experience that affected how test orders behave for stores using checkout extensions. If you built custom checkout extensions before October 2025, it is worth re-running your full test order protocol to confirm that these extensions still render correctly and that all checkout customizations survive the platform update intact. Shopify regularly releases updates to its checkout infrastructure, and staying current with Shopify updates means re-validating your test order results after each significant platform change rather than assuming that a passing test from six months ago still reflects current behavior.

The Shopify careers ecosystem includes a growing number of roles specifically focused on quality assurance, checkout optimization, and merchant success — reflecting how critically important reliable checkout experiences are to the platform's overall health. If you are pursuing a career in Shopify development or ecommerce operations, mastering the test order process and being able to articulate a comprehensive QA strategy is a differentiating skill that employers and clients consistently value. Merchants who hire developers specifically mention checkout reliability and pre-launch testing competence as top hiring criteria in Shopify freelance communities.

Shopify Partners who work with multiple merchant clients benefit enormously from standardizing their test order workflows across all client accounts. Creating a shared test order template — including which card numbers to use, which scenarios to cover, which apps require separate sandbox configuration, and which post-order checks to perform — allows partner agencies to deliver consistent quality across their entire client portfolio.

The Shopify partner ecosystem also provides access to a partner academy and certification program that covers testing best practices, making formal certification a valuable credential for agencies competing for enterprise merchant clients who have high standards for pre-launch quality assurance.

Finally, documenting your test order results creates an auditable record that can be invaluable for troubleshooting future issues. When a customer reports a checkout problem after launch, having detailed records of your pre-launch test results helps you quickly determine whether the issue was pre-existing or was introduced by a recent change.

Version your test records alongside your theme and app version history so you can trace the source of any regression to a specific update. This disciplined approach to QA documentation is a hallmark of professional Shopify development and will serve you well whether you are managing a single boutique store or a portfolio of enterprise Shopify Plus merchants generating millions of dollars in annual revenue through the platform.

Staying informed about platform changes through Shopify's official changelog, partner forums, and developer documentation ensures your test order protocols remain accurate over time. The Shopify ecosystem evolves rapidly, with major feature releases typically announced at the annual Shopify Editions event and smaller updates rolled out continuously throughout the year. Bookmarking Shopify's developer changelog and subscribing to the Shopify partner newsletter are two practical habits that keep you ahead of changes that could affect your testing procedures and ensure your checkout experience remains reliable for every customer who discovers your store.