Online Store Launch Checklist: 60 Checks Before Go-Live

In this article10 sections
An online store launch checklist is the list of things your team confirms before customers can buy: products are correct, every payment method works, delivery costs are right, search engines can find the site, legal pages are in place, the store is secure and you can measure what happens next. Most launch-day problems are small things nobody checked, such as a test payment mode left switched on or a missing redirect. The 60 checks below are grouped into nine areas, so different people can take ownership of each one.
Key takeaways
- Give every area of the checklist a named owner and a deadline before launch day.
- Place real orders with every payment method and delivery option, then refund them.
- If you are replacing an old store, map and test every important old URL with a redirect.
- Launch early in the week, at a quiet time, with your developer available.
- Keep watching orders, errors and search data closely for the first two weeks.
How to use this online store launch checklist
Copy the checks into a shared spreadsheet with four columns: the check, the owner, the status and notes. Start working through it at least two weeks before launch, not the day before. Some fixes, such as correcting product data or waiting for a payment provider to approve your account, take time.
Test on the staging copy of your store first, then repeat the most important checks on the live site immediately after launch. A store that worked perfectly on staging can still fail on the live server because of a missed setting, such as an email service or a payment key.
If you are still at the planning stage, our ecommerce website requirements checklist helps you define what the store must do before the build starts.
Products and content (checks 1–9)
- Every product has a clear name, price, description and at least one good photo.
- Variants such as size and colour show the right photo, price and stock.
- Prices are correct, including sale prices, tax display and currency.
- Stock levels match what you actually have, or sync correctly from your stock system.
- Out-of-stock products behave as intended: hidden, shown as unavailable or available to back-order.
- Categories contain the right products, in a sensible default order.
- Product weights and dimensions are filled in where delivery costs depend on them.
- Placeholder text, test products and sample images have all been removed.
- Spelling and brand names have been checked on the home page, category pages and best sellers.
Checkout, payments and delivery (checks 10–20)
- A full order has been placed with every payment method, using real cards or accounts where possible.
- Payment gateways are in live mode, not test or sandbox mode.
- Successful payments create orders with the correct status in the admin.
- Failed and cancelled payments show a helpful message and do not create paid orders.
- Refunds work from the admin and reach the customer's payment method.
- Guest checkout works, as well as checkout for signed-in customers.
- Discount codes, gift cards and automatic promotions apply correctly and cannot be stacked by mistake.
- Delivery costs are correct for each zone, weight band and order value.
- Free delivery thresholds work exactly at the threshold, not just above it.
- Taxes are calculated correctly for each country or region you sell to.
- Order confirmation, dispatch and refund emails arrive, look right on a phone and do not land in spam.
Shoppers who meet problems at checkout often never come back, so this section deserves the most testing time. Our guide on how to reduce cart abandonment explains which checkout details matter most to buyers.
Design, mobile and accessibility (checks 21–27)
- The store has been tested on real phones, both iPhone and Android, not just a resized desktop browser.
- Menus, filters and galleries work with touch on small screens.
- Buttons and links are large enough to tap easily.
- Pop-ups and banners do not cover products or block the page on mobile.
- Every image has descriptive alt text, and decorative images are marked as such.
- The whole checkout can be completed using only a keyboard.
- Text has enough contrast against its background to be read easily.
SEO and redirects (checks 28–36)
- Search engines are not blocked: the robots.txt file allows crawling and no live page carries a stray "noindex" tag from staging.
- Every page has a unique title and meta description.
- URLs are short, readable and final.
- An XML sitemap is generated, lists only pages you want indexed and is submitted in Google Search Console.
- Canonical tags point to the main version of each page.
- Product structured data includes price and availability, and passes Google's Rich Results Test.
- If you are replacing an old store, every important old URL redirects permanently to its new equivalent.
- Redirects have been tested from a list of the old store's top pages, not just spot-checked.
- Internal links point to final URLs, not redirects or staging addresses.
Redirects are the most common reason stores lose search traffic after a launch. Our e-commerce SEO guide explains why they matter so much.
Legal pages and trust (checks 37–43)
- Terms and conditions, privacy policy and cookie policy are published and linked from the footer.
- The returns and refunds policy is clear and linked from product pages and checkout.
- Delivery information, including costs and times, is published.
- Company name, address and contact details are shown where local law requires them.
- The cookie banner works and respects the visitor's choice before non-essential cookies load.
- Marketing consent boxes are not pre-ticked.
- Customer service contact options are visible, and someone is ready to answer them.
Your returns policy is also a sales tool. Our guide to writing an ecommerce returns policy shows how to make it clear and reassuring.
Security and performance (checks 44–51)
- HTTPS works on every page, and the certificate renews automatically.
- Every admin account uses a strong, unique password and two-factor authentication.
- Test and developer accounts that are no longer needed have been removed.
- The platform, theme and extensions are fully up to date with security patches.
- Automatic backups are running, stored off the server, and a restore has been tested.
- Uptime monitoring and error alerts are set up and send to someone who will act.
- Key pages load quickly on a mobile connection, and caching is switched on.
- The store has been load-tested if you expect a launch campaign or high traffic.
For a deeper review, work through our ecommerce security checklist before launch day.
Analytics, tracking and integrations (checks 52–56)
- Analytics records page views, add-to-cart, checkout steps and purchases with the correct revenue.
- Advertising and conversion tags fire only after consent where required.
- Orders flow correctly into your accounting, ERP or warehouse system.
- Stock and price updates flow back from those systems into the store.
- Email marketing sign-ups reach your email platform with the right consent.
Launch day and the first two weeks (checks 57–60)
- A launch time is agreed, ideally early in the week at a quiet hour, with the developer, host and key staff available.
- A rollback plan exists: who decides, and how the old site or a maintenance page can be restored quickly.
- Immediately after launch, a real order is placed on the live store and checked end to end.
- For the next two weeks, someone checks orders, error logs, payment failures, Search Console and customer messages every day.
What to watch after launch
The first days tell you a lot. Look at conversion rate by device, checkout drop-off by step, payment failures, 404 errors and the questions customers ask your team. A sudden rise in "where is my order?" emails, for example, may point to a missing dispatch email. Keep a short list of issues and fix them in order of how many customers they affect.
| Area | Checks | Suggested owner |
|---|---|---|
| Products and content | 1–9 | Merchandising or product team |
| Checkout, payments and delivery | 10–20 | Operations and finance |
| Design, mobile and accessibility | 21–27 | Design or agency |
| SEO and redirects | 28–36 | Marketing or SEO specialist |
| Legal pages and trust | 37–43 | Owner or legal adviser |
| Security and performance | 44–51 | Developer and host |
| Analytics and integrations | 52–56 | Marketing and developer |
| Launch day and after | 57–60 | Project lead |
The surprises we see most often
Some problems turn up at launch so often that they deserve a special mention. Check these twice:
- Staging settings copied to live. A "noindex" tag, a test payment key or a password-protected page carried over from staging can quietly block sales or search traffic.
- Emails from the wrong address. Order emails sent from an unauthenticated domain often land in spam, so customers think their order failed.
- Delivery rules with gaps. A missing postcode range or country can leave some customers with no delivery option at all.
- Old links in marketing. Emails, social profiles and adverts still point to old URLs that now return errors.
- Nobody watching the inbox. Launch campaigns bring questions, and slow answers on day one cost sales and goodwill.
Each of these takes minutes to check and can take days to notice once the store is live.
Frequently asked questions
How long before launch should we start the checklist?
At least two weeks for a new store, and longer for a migration from an old platform. Some items, such as payment account approval, redirect mapping and product data clean-up, cannot be rushed.
Should we launch on a Friday?
It is better not to. Launch early in the week, when your developer, host and payment provider support are all available to fix anything unexpected.
Do we need to place real orders?
Yes. Test mode does not prove that live payment keys, bank settlement and emails work. Place a small real order with each payment method, check it end to end, then refund it.
What if we find a problem on launch day?
Decide in advance who can call a rollback and what the threshold is. Small issues can be fixed live. If customers cannot pay or orders are not recorded, switch to a maintenance page or the old site until it is fixed.
Planning a launch or migration? Talk to our team about a pre-launch review, or see how we handle store migrations without losing orders or rankings.
Want an expert to look at your store?
Tell us what you are working on. A senior e-commerce consultant will reply within one working day with honest, practical advice. No obligation and no sales script.
- Reply within one working day
- Advice even if we are not the right fit
- Your details are never shared