Shopify Launch Checklist: Payments, Orders, Email and Handover
Documentation checked October 5, 2026. This guide combines official Shopify documentation with HRL planning recommendations. It does not report hands-on store, restoration or billing tests.
A store is ready when a customer can complete the intended journey and the business can handle what follows. HRL’s launch checklist makes that a reviewable decision: record the test, expected result, observed result, person responsible and any unresolved blocker.
Shopify’s launch documentation recommends test orders to check checkout, order processing, inventory, shipping and tax settings. It lists a selected subscription, store address and payment setup with test mode off among launch requirements. Those platform prerequisites are the start of business acceptance.
1. Confirm ownership and the operating budget
Make the business responsible for its store, domain and external service accounts. Verify that the person handling orders has appropriate access and that the owner can recover the account. Keep contractors’ access tied to their job rather than sharing one password.
Record the selected plan, annual or monthly commitment, required apps and the next invoices. Our Shopify pricing guide covers the subscription; the app and renewal checklist keeps other commitments visible.
2. Test the complete order journey
| Check | Expected evidence | Owner |
|---|---|---|
| Product and cart | Correct variants, prices, availability and cart totals. | Catalogue owner |
| Checkout | Expected payment outcome, delivery choices and configured charges. | Store operator |
| Order handling | Order reaches the admin and required integration once. | Fulfilment owner |
| Customer messages | Confirmation arrives with useful order details and support contact. | Customer support |
| Exceptions | Decline, cancellation and refund handling are understood. | Store operator |
| Domain and email | Public address works; existing mailboxes and replies still work. | Account owner |
Use representative items and customer locations. Test a discount if you offer one, an unavailable item if stock is tracked, and a failed-payment path. For a download or access product, verify delivery and customer access as well as payment. A successful card simulation cannot prove every external service works.
3. Respect test-mode boundaries
Shopify’s Shopify Payments testing guide says test mode captures no real payments and should not be activated on a production store. It excludes some payment methods, and simulated transactions do not appear in payouts or reports. Check the documentation for the method you actually offer.
Before test orders, disable automatic fulfilment that could ship them; do not buy shipping labels for tests. Deactivate test mode when finished so real payments can be captured. Shopify Payments testing requires a paid plan and completed setup, with regional eligibility conditions.
If another gateway is selected, use its documented testing process. A live transaction has different consequences from a simulation; confirm any processor charges and cancellation procedure before an authorized live-payment check. Preserve the result without collecting or sharing unnecessary payment details.
4. Verify domain, mail and customer-facing content
Check the public domain and HTTPS, then inspect the storefront on a phone. Review navigation, product options, cart controls and important policy links. Confirm the displayed support address and test inbound mail and replies separately from automated order notifications.
Website DNS and mailbox DNS serve different jobs. Preserve the existing mailbox records during a connection change. Our domain and email guide and email-preserving move guide explain the separation.
5. Prepare recovery and handover
Keep a dated inventory of store data, apps and configuration before the final release. Record the recovery contact and the workflow for repairing an accidental change. Use the Shopify backup and recovery guide to identify coverage gaps.
The handover should include ownership, permissions, renewal dates, support routes and the person responsible for daily orders. The business website handover checklist provides the broader account inventory.
Separate launch approval from one successful order
A passed test order is evidence for that tested journey. Launch approval also needs the intended public domain, production integrations, customer information, recovery route and accountable operator. Keep a short release decision listing passed cases, unresolved blockers and the person accepting the remaining limitations. Repeat the public journey after launch; a staging success cannot establish the production configuration.
6. Sign off, launch and check the public journey
Record unresolved issues and distinguish launch blockers from later improvements. HRL considers an unusable payment path, missing fulfilment route or lost mailbox access a reason to hold the release. Cosmetic refinements can have a separate owner and deadline.
After making the store public, check the actual public URL and customer journey again, confirm the payment configuration is live, and watch the first orders and notifications. Monitor the business workflow rather than assuming a removed password means everything is ready. This page is a checklist for readers; HRL has not launched or tested your Shopify store.
See our review methodology and affiliate disclosure. Provider links are direct. App capability, pricing and account-specific conditions must be verified for the selected service.