E-Commerce
Ecommerce Website Testing Checklist: 80+ Checks Before and After Launch
An online store can look finished and still lose sales: a coupon that doesn’t apply, tax charged twice in one region, an order email that never arrives. Ecommerce testing is about every path a customer and an order can take. Copy the checklist below into a spreadsheet, add an owner and a status column, and work through it before launch and after every major update.
Related service: QA and software testing
By Murtaza · October 30, 2026 · 7 min read · Updated October 30, 2026
Ecommerce website testing checklist (copy into a spreadsheet)
| Area | Check |
|---|---|
| Catalog | Product titles, prices, images and descriptions are correct |
| Catalog | Every variant (size, colour) has the right price, SKU, image and stock |
| Catalog | Out-of-stock and back-order products behave as intended |
| Catalog | Category and collection pages show the right products and counts |
| Catalog | Filters and sorting return correct results and can be cleared |
| Catalog | Pagination or infinite scroll loads all products |
| Search | Search finds products by name, SKU and common misspellings |
| Search | No-results page suggests alternatives |
| Search | Autocomplete works and is usable by keyboard |
| Product page | Add to cart works for every variant and quantity |
| Product page | Quantity limits and minimums are enforced |
| Product page | Image gallery, zoom and video work on desktop and mobile |
| Product page | Reviews, ratings and Q&A display correctly |
| Product page | Related and upsell products are relevant and in stock |
| Cart | Cart updates quantity, removes items and recalculates totals |
| Cart | Cart persists after login, logout and returning later |
| Cart | Mini-cart and cart page show the same totals |
| Cart | Shipping estimate in cart matches checkout |
| Coupons | Percentage, fixed and free-shipping coupons apply correctly |
| Coupons | Expired, used and invalid coupons show a clear error |
| Coupons | Coupon rules (minimum spend, product limits, one per customer) work |
| Coupons | Automatic discounts and coupons combine as intended |
| Checkout | Guest checkout works end to end |
| Checkout | Account checkout works, with saved addresses |
| Checkout | Required fields, validation and error messages are clear |
| Checkout | Address autocomplete works and accepts manual entry |
| Checkout | Billing can be set to the same as shipping |
| Checkout | Order review shows correct items, shipping, tax and total |
| Checkout | Terms and marketing consent checkboxes behave correctly |
| Checkout | Back button and page refresh don’t create duplicate orders |
| Payments | Each payment method completes a test order |
| Payments | Declined card shows a clear message and keeps the cart |
| Payments | 3-D Secure or SCA challenge completes and returns to the store |
| Payments | Wallets (Apple Pay, Google Pay, PayPal) work on supported devices |
| Payments | Currency and rounding are correct for every currency sold |
| Payments | Refunds and partial refunds post back to the order |
| Payments | Live keys replace test keys at launch |
| Tax | Tax is calculated correctly for each region you sell to |
| Tax | Prices shown including or excluding tax as required |
| Tax | Tax-exempt and B2B customers are handled |
| Shipping | Every shipping zone and method shows the right rates |
| Shipping | Free-shipping thresholds trigger at the right amount |
| Shipping | Addresses outside delivery zones get a clear message |
| Shipping | Local pickup and delivery slots work, if offered |
| Orders | Order confirmation page shows the order number and details |
| Orders | Stock decreases after an order and returns on cancellation |
| Orders | Orders reach fulfilment, ERP or warehouse systems |
| Orders | Order statuses update customer-facing order history |
| Emails | Order confirmation, shipping and refund emails send with correct details |
| Emails | Password reset and account emails arrive and links work |
| Emails | Emails pass SPF, DKIM and DMARC and don’t land in spam |
| Accounts | Registration, login, logout and password reset work |
| Accounts | Customers can edit addresses and view past orders |
| Accounts | Account deletion or data request process works |
| Performance | Product and category pages pass Core Web Vitals on mobile |
| Performance | Images are compressed, sized and lazy-loaded below the fold |
| Performance | Checkout stays fast under expected peak traffic (load test) |
| Performance | Third-party scripts (chat, reviews, tracking) don’t block rendering |
| Security | HTTPS everywhere with no mixed content |
| Security | Admin and staff accounts use MFA; no default passwords |
| Security | Platform, theme, plugins and apps are up to date |
| Security | Payment pages meet PCI DSS requirements for your integration type |
| Security | Forms are protected against spam and card-testing bots |
| Security | Backups run and a restore has been tested |
| Accessibility | Whole purchase journey works by keyboard alone |
| Accessibility | Images have alt text; form fields have labels |
| Accessibility | Text and buttons meet WCAG 2.2 AA contrast and target size |
| Accessibility | Errors and “Added to cart” messages are announced to screen readers |
| SEO | Unique titles and meta descriptions on product and category pages |
| SEO | Product structured data matches visible price and stock |
| SEO | XML sitemap includes products and categories; robots.txt allows them |
| SEO | Old URLs redirect (301) to new ones after a migration |
| SEO | Canonical tags handle variants and filtered URLs |
| Mobile and browsers | Full journey tested on real iOS and Android phones |
| Mobile and browsers | Chrome, Safari, Firefox and Edge render correctly |
| Mobile and browsers | Tap targets are large enough; no horizontal scrolling |
| Analytics | Product view, add to cart, begin checkout and purchase events fire once |
| Analytics | Purchase value and currency match the order |
| Analytics | Cookie consent blocks tracking until accepted where required |
| Legal | Privacy, cookies, returns and terms pages are live and linked |
| Post-launch | Uptime and checkout monitoring alerts the team |
| Post-launch | Payment failure and error rates reviewed daily for two weeks |
| Post-launch | Search Console checked for crawl and indexing errors |
| Post-launch | Customer support questions logged to find hidden bugs |
What should you test on an ecommerce website?
Test everything a customer and an order touch: finding products, the product page, cart, coupons, checkout, payments, tax, shipping, emails, accounts, and the systems orders flow into. Then test non-functional areas: speed, security, accessibility, SEO, mobile devices and analytics. The checklist above lists more than 80 specific checks.
How do you test checkout and payments?
Test checkout and payments by placing a real test order for every combination that matters: each payment method, each shipping zone, each tax region, and each coupon type. Use the payment provider’s test mode and test cards, including cards that trigger declines and 3-D Secure challenges.
Then test the failure paths: a declined card, an expired coupon, an out-of-stock item added from an old tab, and a refresh on the payment page. These are where duplicate orders and lost carts appear.
How do you test ecommerce performance?
Test ecommerce performance on real mobile devices and with lab tools such as Lighthouse, focusing on product, category and checkout templates. Check Core Web Vitals: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Before big campaigns, run a load test on checkout at expected peak traffic.
Our Core Web Vitals guide explains how to fix slow LCP, INP and CLS.
What security tests does an online store need?
An online store needs HTTPS everywhere, MFA on admin accounts, up-to-date software, protection against card-testing bots, tested backups and a payment setup that meets PCI DSS for your integration type. Stores using hosted payment pages carry less PCI scope than stores that handle card data directly.
When should you run ecommerce tests?
Run the full checklist before launch and after any major change: a new theme, a platform migration, a new payment or shipping provider. Run a shorter smoke test (search, add to cart, checkout with one payment method, order email) after every plugin, app or platform update.
- Before launch: full checklist.
- After major changes: full checklist for affected areas.
- After every update: smoke test of the purchase journey.
- Monthly: performance, accessibility spot-check, analytics accuracy.
- Before peak season: load test and payment failover check.
What should you monitor after launch?
After launch, monitor uptime, checkout completion rate, payment failure rate, error logs, page speed and Search Console every day for the first two weeks. Read customer support messages too: customers often find bugs before monitoring does. After that, move to weekly reviews with alerts for outages and payment failures.
Manual testing or automated testing?
Use both. Manual testing finds usability and visual problems and covers one-off launch checks. Automated end-to-end tests repeat the critical journeys, such as search, add to cart and checkout, after every update, so regressions are caught in minutes. Stores that update often benefit most from automation.
Frequently asked questions
What is ecommerce testing?
Ecommerce testing checks that an online store works for every customer journey and order path, including catalog, cart, checkout, payments, tax, shipping and emails, plus performance, security, accessibility and SEO.
How long does ecommerce QA take?
It depends on catalog size, payment methods, regions and integrations. A small store can be tested in a few days; complex multi-region stores take longer.
How do I test payments without real charges?
Use your payment provider’s test mode and test card numbers, including ones that simulate declines and 3-D Secure. Switch to live keys only at launch and place one small real order to confirm.
What is the difference between a launch checklist and a testing checklist?
A launch checklist covers readiness tasks such as redirects, analytics and team roles. A testing checklist verifies that each function actually works. You need both.
Should I re-test after updating plugins or apps?
Yes. Run at least a smoke test of search, add to cart, checkout and order emails after every update.
Sources
Related articles
- Shopify vs a Custom E-Commerce Website: Costs, Limits and When to Switch
Shopify or a custom-built online store? Compare fees, flexibility, SEO, integrations and total cost, plus the signs it’s time to move to custom e-commerce.
- E-Commerce Website Launch Checklist: What to Test Before You Go Live
A pre-launch e-commerce checklist covering checkout, payments, mobile usability, SEO, analytics, security and operational readiness.
- WCAG 2.2 AA Checklist in Plain English, Plus Ecommerce Product Pages
All 55 WCAG 2.2 Level A and AA success criteria in plain English, what changed from 2.1, a product page checklist for online stores, and how to test.