QA an Ecommerce Redesign Before Launch

A redesign can pass a visual review while still losing orders or search paths. Quality assurance should replay the work customers and staff perform, using representative products and documented expected results. Do the highest-risk tests before the launch window, then repeat a short smoke test after deployment.

Build a risk-weighted sample

Select a simple product, a variant-heavy product, an out-of-stock item and a special-delivery item. Test category navigation, search, filters, image gallery, price, stock and cart. Include phone and desktop where the layout changes. Record pass, fail, owner and retest date rather than a vague “looks good.”

Prove the order and event path

Run successful and failed payment scenarios. Confirm the buyer sees the right total and status, staff see one correct order, and analytics records one purchase with the right value and currency. Test a cancellation or refund route where the store supports it. Never use a live customer’s personal data in a public checklist.

Protect existing discovery

Export old priority URLs and test their destination after migration. Check redirects, canonical output, sitemap entries, internal links and the first indexed pages. Keep a rollback owner and criteria for delaying launch. Megvi’s Fyonka case documents the scale of a 1,500-SKU, 6,000-variation migration; it is a reminder that a sample catalog test must cover complexity.

Worked decision example

Illustrative failed QA row: the variant page loads and adds to cart, but an old product URL redirects to the homepage instead of the correct successor. Mark the URL test failed, map it to the relevant product, deploy the redirect and retest both desktop and mobile before launch approval.

Practical review checklist

• Did representative products pass browsing and checkout?
• Do purchase events match real test orders?
• Do priority old URLs reach relevant destinations?

Where to go next

ecommerce website service · Fyonka case · handover checklist