Shopify launch checklist
By Adrian Diaz
Prepare the catalogue
Review product titles, descriptions, images, prices, variants, and inventory. Check that products appear in the intended collections and that unavailable variants are presented clearly. Test search and collection filters using the language a customer would use. For apparel, review size information and make sure customers can distinguish the options before adding an item to the cart.
Check the storefront
Navigate the store on a phone and desktop. Review the homepage, collection pages, product pages, cart, and contact information. Test links, menus, product images, and any app-powered controls. Remove temporary copy and test data from customer-facing areas. Ask someone unfamiliar with the catalogue to find and choose a product without assistance.
Test checkout and fulfilment
Use the payment provider’s supported test procedure to run representative orders. Review shipping rates, delivery regions, taxes, discounts, and order notifications for your situation. Confirm that the order reaches the people and systems responsible for fulfilment. Cancel or clean up test orders according to your operational procedure and check that real payment settings are restored before launch.
Review policies and access
Make contact, delivery, returns, and privacy information easy to find and review it with the appropriate business or legal adviser. Check staff accounts and app permissions, removing access that is no longer needed. Confirm ownership of the domain, billing, and recovery methods. Keep a record of who is responsible for ongoing store administration.
Measure the right actions
Confirm analytics is connected to the intended property and that visits and key commerce events appear in the relevant reports. Use a test journey and allow for normal reporting delays. Avoid counting your own test orders as real business results. Document the events and reports the team will use after launch so everyone understands what is being measured.
Launch and follow up
Check the live domain, remove launch restrictions when ready, and repeat the most important journey on the public store. Monitor orders, error reports, customer enquiries, and inventory during the first days. Assign an owner for each issue and verify fixes on the live site. Save the final theme and document any changes made during launch.
Plan for the first orders
Before launch, agree who will watch for new orders and who can resolve payment, shipping, or inventory problems. Make sure the support team can find order details and knows how customers will receive updates. Check that business contact information reaches a monitored inbox and that the person responsible knows how to respond.
Once the store is public, repeat a small set of checks on the live domain. Find a product, select a variant, review the cart, and check the delivery information. Use the payment provider’s approved testing process rather than placing unplanned real orders. Record any issue and its owner, and confirm the resolution in the same customer journey.
Walk through a sample order
Choose a product that represents a typical order and another that has variants, such as size or color. Find each through the collection navigation and search. Confirm the description, images, prices, availability, and variant selection are understandable before adding the item to the cart. Review the cart on a phone and verify that quantities and selected options remain visible.
Proceed through checkout using the payment provider’s supported test method. Test the delivery regions and rates that are relevant to the business, including an address that should not qualify if that is part of the configuration. Apply a valid discount and check how the store handles an invalid one. Confirm the resulting order appears in the system used for fulfilment and that notifications reach the intended recipients.
Follow the business’s process for cancelling or cleaning up test orders and restoring live settings. Document what was tested, who checked it, and any remaining issue. Repeat the most important checks after the domain is live, because a working staging experience alone does not establish that the public customer journey is ready.
After the first week
Review issues reported by customers and staff alongside the orders and fulfilment records. Look for repeated questions about sizes, delivery, discounts, or product availability. An individual question is not proof of a widespread problem, but repeated friction is a useful reason to inspect the relevant page or workflow.
Confirm that backups or theme copies and access records are kept according to the store’s operating process. Document which apps are in use and who owns their billing and settings. Schedule a follow-up review after the launch changes have settled, and retest any fix on the live store.
Put the guidance into practice
Start with the page or workflow that matters most to the people using the site. Write down the current behavior, the change you intend to make, and the person responsible for reviewing it. If the site has a staging environment, test the change there before applying it publicly. Keep a record of the previous configuration and make sure the team knows how to restore it if the change causes a problem.
After the change, repeat the original task with realistic content. Check it on a small screen and with a keyboard, and include any form, payment, or integration that the change could affect. Record the date, result, and any follow-up. Share the outcome with the site owner in terms of what visitors can now do and what remains uncertain. Revisit the check when the underlying content, theme, or connected tools change.
Explore related services.