Most launch disasters are not dramatic. They are a discount code that does not apply, a shipping rate that never appears for one country, an order confirmation email that goes to spam, a tracking pixel that was never installed. Small things, each of which quietly costs orders from the first hour the store is live.
Quality assurance before launch is how you catch them while they are cheap to fix. A checklist is not bureaucracy; it is the accumulated memory of every way a launch has gone wrong before. Here is the shape of the one we run, end to end, on every store.
01 · Mindset
A launch is a system.
The temptation before launch is to click around, see that the homepage looks nice, and call it done. But a store is a chain of dependent systems—catalog, cart, checkout, fulfilment, email, analytics, SEO—and a chain fails at its weakest link. QA means testing each link deliberately, not admiring the whole.
Work from a written list so nothing rides on memory, and test on real devices and a real network, not just a desktop on office wifi. The bugs that survive to launch are almost always the ones that only show up on a mid-range phone.
You are not checking whether it looks finished. You are checking whether it works when a stranger uses it.
02 · Transactions
Buy something real.
The single most important test is a complete, real purchase. Place a live order end to end and watch what happens—then refund it. This one exercise validates more than any amount of clicking around.
- Add to cart, apply a discount code, reach checkout, pay, and confirm the order is created.
- Verify shipping rates appear for every region you sell to, including the edge-case countries.
- Confirm taxes and duties calculate correctly and match what you promised on the page.
- Check the order confirmation email actually arrives, in the inbox, looking right.
If your store relies on custom checkout logic—discounts, delivery or payment rules—test each rule against the carts it is meant to affect. A rule that works on the happy path can quietly misfire on a mixed cart.
03 · Content
Content and links.
Placeholder text and dead links are the fingerprints of a rushed launch, and customers read them as carelessness. Sweep the whole store for the leftovers: "lorem ipsum," sample product copy, an unfinished about page, a policy that still references the previous business name.
Crawl for broken internal and external links, confirm every image has meaningful alt text, and check that navigation, footer and collection links all lead somewhere real. The password page comes off only after everything else passes—and confirm no staging or test products are still visible.
Read the store on a phone as a first-time visitor would, not as the person who built it. Familiarity hides the awkward heading that wraps onto three lines, the form field that is fiddly under a thumb, the collection image that is subtly the wrong crop. The team that built the store has stopped seeing these; borrow a fresh pair of eyes and let them click around before a paying customer is the one who finds them.
04 · SEO
SEO and redirects.
If this is a replatform, redirects are the highest-stakes item on the list. Every URL that existed on the old store and had traffic or links must point to its new home, or you lose rankings the search engines spent years granting you. Build the redirect map before launch, not after the traffic drops.
Then check the fundamentals: unique titles and meta descriptions on key templates, a working sitemap, sensible robots rules, canonical tags, and that you did not accidentally leave the whole store set to "discourage search engines." These are quick to verify and painful to miss.
05 · Tracking
Tracking and analytics.
A store that launches with broken tracking is flying blind on its most important days. Confirm analytics is installed once—not zero times, not three times—and that key events fire: page views, add to cart, begin checkout, purchase. A purchase event that never fires means every ad platform is optimizing on nothing.
This is exactly where our PixelProbe tool earns its place: it x-rays which pixels are actually firing, flags duplicates and confirms conversions are being recorded. Pair it with DeadCode Scanner to strip any leftover snippets from apps or themes used during the build, so you launch clean.
06 · Gate
The final gate.
The last step is a shared go/no-go review. Walk the checklist with the client, confirm every item passed or has a documented exception, and only then remove the password page. Assign an owner for the first hour after launch to watch orders, errors and analytics land for real—because the truest test is the first genuine customer.
Quick check
Are you actually ready to launch?
- A real order was placed, confirmed by email, then refunded.
- Shipping, taxes and any custom checkout rules verified per region.
- No placeholder text, dead links or stray test products remain.
- Old URLs redirect; titles, sitemap and robots are correct.
- Analytics loads once and the purchase event actually fires.
Boring launches are good launches.
The best launch is the one nobody remembers because nothing broke. That calm is not luck—it is a checklist run properly, by people who have seen the ways a store can fail and refuse to find out the hard way again. Test the whole chain, buy something real, and open the doors only when every light is green.