>_ E-commerce QA Checklist

Short answer

An E-commerce QA Checklist is a list of checks for an online store or e-commerce product before launch, release, or changes to the product catalog, cart, checkout, payment, shipping, orders, promo codes, email notifications, and integrations.

This checklist helps make sure that a user can find a product, open the product page, add the product to the cart, apply a discount, choose a shipping method, pay for the order, receive a confirmation email, and that the team can see the order in the admin panel or order management system.

E-commerce QA is especially important because even a small issue can directly affect revenue: an incorrect price, broken checkout, wrong tax calculation, failed payment flow, lost order, incorrect inventory, or a confirmation email that never arrives.

The main idea is: e-commerce QA should check the full purchase journey end-to-end - from viewing a product to successful order creation, payment, notification, and internal order processing.

This guide can also be used as an e-commerce website testing checklist, online store QA checklist, or checkout testing checklist for stores, marketplaces, and checkout-heavy web products.

When to use an E-commerce QA Checklist

Use this checklist before launching or releasing an e-commerce website, marketplace, online store, checkout flow, or any functionality related to purchases.

For example:

• a new online store is launching;
• a new checkout flow is launching;
• the cart is being updated;
• a new payment method is added;
• prices, discounts, or promo codes are changing;
• a new shipping method is added;
• tax logic is changing;
• the product catalog is being updated;
• product search or filters are added;
• the product detail page is changing;
• the mobile version is being updated;
• the order confirmation flow is changing;
• emails or notifications are added;
• inventory logic is changing;
• returns, cancellations, or refund flow is added;
• the order admin panel is updated;
• integrations are changing: payment provider, CRM, ERP, warehouse, delivery service, analytics.

For a small change, you can use a shorter e-commerce smoke checklist. For a store launch, major release, or checkout change, it is better to go through the full checklist.

Quick E-commerce QA Checklist

If you need a minimal e-commerce smoke test, check that:

• homepage and catalog open correctly;
• product listing page works;
• product detail page opens;
• product price is displayed correctly;
• product can be added to the cart;
• cart shows the correct amount;
• checkout opens;
• shipping and billing fields work;
• promo code is applied correctly, if available;
• payment is successful in test mode;
• failed payment is handled clearly;
• order is created in the system;
• confirmation page is displayed;
• confirmation email is delivered;
• inventory is updated, if expected;
• order is visible in the admin panel;
• analytics event is sent, if tracking is important;
• mobile checkout works at least in the basic scenario;
• there are no critical console errors or failed API requests.

This is not full e-commerce QA. It is a minimal check that helps quickly confirm whether the main purchase flow works.

Track this checklist in qa::checklist

You can use this guide as a manual e-commerce QA checklist, or track it in qa::checklist as a QA project. Split checks by catalog, cart, checkout, payment, orders, inventory, mobile, and integrations, then export the completed result to CSV.

Full E-commerce QA Checklist

1. Preparation before testing

Before starting e-commerce QA, it is important to understand what exactly is included in the testing scope. An online store may look like a single website, but it usually contains many connected parts: catalog, search, cart, checkout, payment, shipping, orders, emails, inventory, admin panel, and external integrations.

Check that:

• it is clear which pages are included in the check;
• it is clear which user flows are critical;
• there is a staging or test environment;
• the latest version has been deployed;
• test products are available;
• products in different statuses are available: in stock, out of stock, low stock, sale, hidden;
• products with variants are available: size, color, bundle, subscription;
• test users are available;
• guest checkout is available, if supported;
• test payment methods are available;
• access to a test email inbox is available;
• access to the admin panel or order management system is available;
• supported shipping regions are clear;
• taxes, currencies, and discounts that need to be checked are clear;
• integrations included in scope are known.

If the scope is not defined in advance, e-commerce QA can quickly turn into a random review of pages. It is better to define the critical path first: product -> cart -> checkout -> payment -> order confirmation -> admin/order processing.

2. Homepage and navigation check

Homepage and navigation help the user reach products, categories, promotions, and checkout. If navigation is broken, the user may never reach the purchase flow.

Check that:

• homepage opens without errors;
• main banners and hero sections are displayed correctly;
• CTA buttons lead to the correct pages;
• main menu works;
• category links open the correct categories;
• logo leads to the homepage;
• cart icon opens the cart;
• account icon opens login or account page;
• footer links work;
• links to shipping, returns, contact, privacy, and terms open correctly;
• there are no links to staging, localhost, or old URLs;
• important pages do not return 404;
• the user can quickly get to the catalog or search.

The main question for this part is: can the user quickly get from the homepage to products and start shopping?

3. Product catalog and category pages check

Product listing pages and category pages are where the user chooses a product. Here, it is important to check not only the layout but also the correctness of product data.

Check that:

• category page opens;
• products are displayed;
• product cards look correct;
• product image is displayed;
• product name is displayed;
• price is displayed correctly;
• sale price and original price are displayed correctly;
• out-of-stock product is displayed correctly;
• product badge is displayed if needed: sale, new, bestseller, out of stock;
• pagination or infinite scroll works;
• product count in the category is correct;
• link to product detail page works;
• empty category state is clear;
• sorting does not break the product list;
• category description is displayed, if available;
• there are no placeholder images or test products in production.

If the catalog is large, you do not need to check every product. But you should check different product types: a regular product, a discounted product, an out-of-stock product, a product with variants, and a product with a long name.

4. Search, filters, and sorting check

Search, filters, and sorting have a strong impact on conversion. The user should be able to find the right product quickly and not get lost in the results.

Check that:

• search field works;
• search finds a product by exact name;
• search finds a product by partial name;
• search handles different letter cases;
• search handles typos, if this is expected;
• empty search results are displayed clearly;
• filters are applied correctly;
• multiple filters can be selected;
• filters can be reset;
• selected filters are visible to the user;
• price filter works;
• category filter works;
• size, color, brand, or other attributes work;
• sorting by price works;
• sorting by popularity, newest, or rating works, if available;
• URL updates correctly if filters should be saved in the URL;
• search and filters do not return products that should be hidden.

It is especially important to check combinations: search + filter, filter + sorting, multiple filters at once, resetting filters, and empty results.

5. Product detail page check

The product detail page is one of the most important pages of an e-commerce website. This is where the user makes the purchase decision.

Check that:

• product page opens;
• product name is displayed correctly;
• product images load;
• image gallery works;
• zoom or carousel works, if available;
• price is displayed correctly;
• discount is displayed correctly;
• stock status is displayed correctly;
• product description is up to date;
• product specifications are displayed;
• size, color, or other variants can be selected;
• unavailable variants cannot be purchased;
• quantity selector works;
• add to cart button works;
• buy now button works, if available;
• wishlist button works, if available;
• reviews are displayed, if available;
• related products are displayed correctly;
• shipping or return information is available;
• product page does not show test content.

The main question is: can the user understand what the product is, choose the right variant, and add it to the cart?

6. Product variants check

If products have variants, such as size, color, material, bundle, or subscription plan, they should be tested separately. Variants often break price, inventory, and add to cart logic.

Check that:

• the user can select a variant;
• price changes when selecting a variant, if expected;
• image changes when selecting a color or style, if expected;
• SKU changes correctly;
• stock status changes correctly;
• unavailable variant cannot be added to the cart;
• pre-order variant is displayed correctly, if available;
• selected variant is saved in the cart;
• variant is displayed in the order summary;
• variant is displayed in the confirmation email;
• variant is displayed in the admin panel;
• the user cannot accidentally buy a different variant.

For example, if the user selected size M and color Black, this exact variant should appear in the cart, order, email, and admin panel.

7. Cart check

The cart is a key step before checkout. The user should see the correct products, prices, quantities, discounts, and total amount.

Check that:

• product is added to the cart;
• cart icon updates the product count;
• cart page or cart drawer opens;
• product name is displayed correctly;
• selected variant is displayed correctly;
• product image is displayed;
• price is displayed correctly;
• quantity can be changed;
• product can be removed from the cart;
• subtotal updates after quantity changes;
• discount is displayed correctly, if applied;
• shipping or tax preview is displayed, if expected;
• empty cart state is clear;
• cart is saved after page refresh;
• cart is saved after login, if expected;
• cart does not duplicate products without a reason;
• out-of-stock product in the cart is handled correctly.

Also check the scenario where the user adds several products, changes quantity, removes one product, and then continues to checkout.

8. Checkout flow check

Checkout is the most critical area of e-commerce QA. If checkout does not work, the store cannot sell.

Check that:

• checkout page opens;
• guest checkout works, if supported;
• logged-in checkout works;
• shipping address fields work;
• billing address fields work;
• required fields are actually required;
• optional fields can be left empty;
• email, phone, postal code, and address are validated correctly;
• country, state, city, and postal code are connected correctly, if this logic exists;
• shipping method can be selected;
• payment method can be selected;
• order summary is displayed;
• subtotal, shipping, taxes, discounts, and total are calculated correctly;
• the user can go back to the cart;
• the user can change order details;
• checkout does not lose data after an error;
• checkout does not create an order before the expected step, if this matters;
• checkout does not break after page refresh;
• checkout does not allow order placement without required data.

The main question is: can the user complete checkout from beginning to end without help from the team?

9. Guest checkout and account checkout check

In e-commerce, there are often several purchase paths: guest checkout, checkout after login, checkout after registration, and checkout from a saved cart. Each path should be checked separately if it is supported.

Check that:

• guest user can place an order;
• logged-in user can place an order;
• new user can create an account during checkout;
• existing user can log in during checkout;
• cart is saved after login;
• address book works, if available;
• saved payment method works, if available;
• order appears in account order history;
• guest order can be found by email or order number, if expected;
• user cannot see someone else's orders;
• private account pages are not available without login.

If checkout works only for logged-in users, make sure a guest user sees a clear path to login or signup instead of a broken state.

10. Pricing, taxes, and currency check

Pricing logic is one of the riskiest parts of e-commerce. A mistake in price, tax, or currency can lead to financial loss and user distrust.

Check that:

• base price is displayed correctly;
• sale price is displayed correctly;
• original price and discount are displayed correctly;
• subtotal is calculated correctly;
• tax is calculated correctly;
• shipping cost is added correctly;
• total amount is calculated correctly;
• currency is displayed correctly;
• currency conversion works, if used;
• rounding works correctly;
• price on the product page matches the cart;
• price in the cart matches checkout;
• total in checkout matches confirmation page;
• total in confirmation email matches the order;
• total in the admin panel matches the user-facing order.

If the store supports different countries, regions, VAT, tax exemptions, or multi-currency, make sure to check several regional scenarios.

11. Discounts, promo codes, and gift cards check

Discount logic often contains edge cases: a promo code may apply to the wrong products, work after expiration, conflict with sale price, or calculate the total incorrectly.

Check that:

• valid promo code is applied;
• invalid promo code shows a clear error;
• expired promo code is not applied;
• promo code with limits applies only under the correct conditions;
• discount is applied to the correct products;
• discount is not applied to excluded products;
• percentage discount is calculated correctly;
• fixed amount discount is calculated correctly;
• free shipping promo works, if available;
• promo code can be removed;
• total is recalculated after promo code removal;
• multiple discounts work according to product rules;
• gift card is applied, if supported;
• gift card balance updates after the order;
• refund with gift card is handled correctly, if included in scope.

Make sure to check promo code behavior in the cart, checkout, confirmation page, email, and admin panel. The amount should match everywhere.

12. Shipping and delivery check

Shipping logic depends on country, address, weight, product type, warehouse, carrier, and delivery rules. Issues here can block an order or show an incorrect shipping cost.

Check that:

• shipping address is accepted;
• unsupported address shows a clear error;
• shipping methods are displayed;
• shipping cost is calculated correctly;
• free shipping works, if available;
• delivery estimate is displayed correctly;
• pickup option works, if available;
• shipping method is saved in the order;
• shipping information is displayed in the confirmation email;
• shipping information is displayed in the admin panel;
• shipping changes update the total;
• digital product does not require shipping address, if expected;
• physical product requires shipping address;
• restricted products cannot be shipped to unsupported regions.

If the store ships to different countries or regions, check at least one supported and one unsupported region.

13. Payment flow check

Payment is a critical area of e-commerce. It is important to check not only successful payment but also errors.

Check that:

• payment method is displayed;
• test card or test payment method works;
• successful payment creates an order;
• failed payment shows a clear error;
• declined payment does not create a successful order;
• payment status is saved correctly;
• user does not receive successful order confirmation after failed payment;
• user can retry payment after an error, if expected;
• 3DS or additional verification works, if used;
• wallet payments work, if available;
• PayPal, Apple Pay, Google Pay, or other methods work, if supported;
• payment amount matches order total;
• payment provider receives the correct data;
• webhook from payment provider is processed correctly;
• duplicate payment is not created after double click or refresh.

For a smoke test, one successful payment is usually enough. For full e-commerce QA, successful, failed, declined, and interrupted payment scenarios should be tested.

14. Order confirmation check

After payment or order placement, the user should receive a clear confirmation. The correct order should also appear inside the system.

Check that:

• confirmation page opens;
• order number is displayed;
• order summary is correct;
• products and variants are displayed correctly;
• quantity is displayed correctly;
• subtotal, shipping, tax, discount, and total are displayed correctly;
• shipping address is displayed correctly;
• billing address is displayed correctly, if used;
• payment status is displayed correctly;
• user understands that the order was created successfully;
• user receives instructions, if needed;
• confirmation page is not available to another user;
• refreshing the confirmation page does not create a duplicate order;
• order appears in the admin panel;
• order appears in account order history if the user is logged in.

Order confirmation should match checkout, email, admin panel, and payment provider. If amounts or products do not match, this is a critical bug.

15. Emails and notifications check

E-commerce depends heavily on email notifications. The user should receive order confirmation, and the team should receive the necessary internal notifications.

Check that:

• order confirmation email is delivered;
• payment confirmation email is delivered, if it is separate;
• shipping confirmation email is delivered, if included in scope;
• cancellation email is delivered, if there is a cancellation flow;
• refund email is delivered, if there is a refund flow;
• password reset email works, if accounts exist;
• email contains the correct order number;
• email contains the correct products and variants;
• email contains the correct amounts;
• email contains shipping address;
• links in the email work;
• email does not contain staging links;
• email does not contain test copy;
• internal notification about a new order is delivered to the team, if needed;
• emails are not sent multiple times without a reason.

It is especially important to check that the email matches the real order. The user will often use this email as the purchase confirmation.

16. Inventory and stock logic check

Inventory bugs can lead to selling products that are not available or blocking products that can actually be purchased.

Check that:

• in-stock product can be purchased;
• out-of-stock product cannot be purchased;
• low-stock product is displayed correctly, if this status exists;
• stock decreases after a successful order;
• stock does not decrease after failed payment if no order is created;
• stock is restored after cancellation, if expected;
• stock is restored after refund, if expected;
• unavailable variant cannot be added to the cart;
• stock status is consistent on product page, category page, cart, and checkout;
• user sees a clear message if the product becomes unavailable during checkout;
• admin panel shows the correct stock;
• backorder or pre-order logic works, if supported.

Also check this scenario: the product was available, the user added it to the cart, but by the time they reached checkout it became out of stock. This is a common and important edge case.

17. Order management and admin panel check

E-commerce QA does not end on the user side. The team should be able to see and process the order inside the system.

Check that:

• new order appears in the admin panel;
• order number matches the user-facing confirmation;
• customer information is displayed;
• shipping address is displayed;
• billing address is displayed;
• products and variants are displayed;
• quantity is displayed;
• discount is displayed;
• tax and shipping are displayed;
• total amount is displayed correctly;
• payment status is correct;
• fulfillment status is correct;
• admin can change order status, if expected;
• admin can cancel an order, if expected;
• admin can add a tracking number, if expected;
• admin actions do not break the user-facing order status.

If the order is visible to the user but does not appear in the admin panel or order management system, the team may not fulfill the order. For e-commerce, this is a critical defect.

18. Cancellation, returns, and refunds check

Not every e-commerce release includes returns or refunds, but if this logic exists, it should be tested separately.

Check that:

• user can cancel an order if cancellation is allowed;
• cancellation is unavailable after a certain status, if expected;
• admin can cancel an order;
• cancellation updates order status;
• cancellation email is sent;
• refund can be created;
• partial refund works, if supported;
• full refund works;
• refunded amount is calculated correctly;
• refund status is displayed correctly;
• inventory is updated after refund or return, if expected;
• user sees a clear return status;
• admin sees refund or return request;
• payment provider receives correct refund information.

Refund logic is often complex because it connects payment, inventory, order status, emails, and accounting. It should not be checked only through the UI.

19. User account and order history check

If the store has accounts, users should be able to see their orders, addresses, settings, and purchase history.

Check that:

• user can sign up;
• user can log in;
• user can log out;
• password reset works;
• account page opens;
• order history is displayed;
• new order appears in order history;
• order details open;
• user cannot see someone else's orders;
• saved addresses work;
• user can edit address, if expected;
• saved payment methods work, if used;
• wishlist works, if available;
• cart is saved after login, if expected;
• account pages are unavailable without login.

For e-commerce, privacy is especially important: a user should not see someone else's orders, addresses, emails, or payment-related data.

20. Integrations check

E-commerce usually depends on external systems. Even if the frontend works, the order may not reach the payment provider, warehouse, CRM, ERP, delivery service, or analytics.

Check that:

• payment provider receives the payment request;
• payment webhook is processed;
• CRM receives customer or order data;
• ERP receives order data, if used;
• warehouse or fulfillment system receives the order;
• delivery service receives shipping information;
• email provider sends emails;
• tax service returns correct taxes, if used;
• inventory system is updated;
• analytics receives purchase event;
• external API errors are handled clearly;
• failed integration does not create a silent failure;
• logs or admin panel show the problem if integration failed.

Integrations should be tested end-to-end: not only "the order was created in the interface," but also "all external systems received the correct data."

21. Mobile e-commerce flow check

E-commerce often receives a lot of traffic from phones. Mobile checkout should be not only visually acceptable but also usable and reliable.

Check that:

• homepage opens on mobile;
• category page is readable;
• filters are available on mobile;
• product page is displayed correctly;
• images do not break the layout;
• add to cart button is visible;
• cart opens;
• checkout can be completed on a phone;
• fields are easy to fill out;
• keyboard does not cover important fields;
• payment method can be selected;
• CTA buttons are not covered by sticky elements;
• modal or drawer fits on the screen;
• there is no unexpected horizontal scrolling;
• order confirmation is displayed correctly.

For e-commerce mobile QA, checkout is especially important. If the user can browse products but cannot complete the purchase comfortably, the mobile experience is effectively broken.

22. Browser compatibility check

Even if checkout works in one browser, it may break in another because of payment widgets, scripts, layout, or validation.

Check that:

• main pages work in supported browsers;
• product page works in Chrome, Safari, Firefox, and Edge, if they are supported;
• checkout works in main browsers;
• payment widget is displayed correctly;
• forms can be submitted;
• images and icons load;
• fonts are displayed correctly;
• there are no browser-specific layout bugs;
• mobile Safari works;
• mobile Chrome works;
• there are no critical console errors.

For e-commerce, Safari and mobile Safari are especially important to test because checkout, payment buttons, sticky elements, and forms often have issues there.

23. UI, content, and trust elements check

In e-commerce, the user makes a decision not only based on functionality but also on trust. Errors in copy, images, prices, or policy information can reduce conversion.

Check that:

• product images are high-quality and up to date;
• product descriptions do not contain placeholder text;
• product specifications are correct;
• price labels are clear;
• sale labels are not misleading;
• shipping information is available;
• return policy is available;
• payment security message is displayed, if needed;
• trust badges are displayed correctly, if used;
• reviews look correct, if available;
• shipping or returns FAQ is available;
• contact information is up to date;
• legal links work;
• there are no internal team comments;
• there is no test content in production.

For e-commerce, content is part of QA. An incorrect product description, wrong price, or outdated return policy can be just as critical as a broken button.

24. Security and access basics check

E-commerce works with personal data, addresses, orders, and payment-related information. A full security audit is a separate task, but basic access checks are always needed.

Check that:

• the website works over HTTPS;
• there are no mixed content warnings;
• checkout works over a secure connection;
• private account pages are unavailable without login;
• user cannot open someone else's order by direct URL;
• admin panel is closed to regular users;
• debug messages are not visible in production;
• secret keys are not visible in HTML, console, or network responses;
• payment-related data is not exposed unnecessarily;
• personal data is not available to other users;
• roles and permissions work;
• test users and test data are not publicly visible;
• spam or abuse protection works for forms, if needed.

Pay special attention to order details, account pages, admin pages, uploaded files, and API responses.

25. Analytics and conversion tracking check

For e-commerce, analytics is not a nice-to-have. It is how the team understands sales, conversion, and funnel problems.

Check that:

• page view is sent;
• product view event is sent;
• add to cart event is sent;
• begin checkout event is sent;
• purchase event is sent;
• purchase event contains the correct amount;
• purchase event contains the correct currency;
• purchase event contains order ID;
• purchase event is not duplicated after refresh;
• promo code or discount is passed, if needed;
• cart and checkout events are sent in the correct order;
• UTM parameters are not lost;
• analytics property is correct;
• ad pixels work, if included in scope;
• cookie consent does not unexpectedly break tracking.

It is especially important to check the purchase event. If it does not work or is duplicated, the team may misread sales and ad performance.

26. SEO check for e-commerce pages

If the store relies on organic traffic, product and category pages should be available to search engines and have basic SEO settings in place.

Check that:

• product pages have unique title tags;
• category pages have unique title tags;
• meta descriptions are filled for important pages;
• each page has one main H1;
• canonical URL is configured correctly;
• product pages that should be indexed are not blocked with noindex;
• out-of-stock products are handled according to the product's SEO logic;
• robots.txt does not block important pages;
• sitemap contains important product and category pages;
• internal links point to current pages;
• there are no links to staging or old domains;
• product structured data is added, if used;
• price and availability in structured data match the page, if included;
• images have alt text where it matters;
• Open Graph / social previews are configured for important pages.

This SEO section does not replace an SEO audit. But before launching an e-commerce website, it is important to make sure technical settings do not block indexing of important pages.

27. Performance check

E-commerce performance directly affects conversion. A slow product page or checkout can cost sales.

Check that:

• homepage loads fast enough;
• category pages load acceptably;
• product page does not load too slowly;
• checkout works without long delays;
• images are optimized;
• product gallery does not block page loading;
• third-party scripts do not slow down the critical flow;
• payment widget does not cause a long delay;
• lazy loading works where needed;
• pages do not jump during loading;
• mobile performance is acceptable;
• loading states are clear;
• the user does not click repeatedly because of unclear delay.

Pay special attention to performance on mobile, product pages, cart, and checkout.

28. Production smoke check after release

After releasing e-commerce changes, run a short production check. Some issues appear only in production because of payment settings, domain, analytics, email delivery, inventory sync, or feature flags.

Check that:

• production domain opens;
• homepage and catalog are available;
• product page opens;
• cart works;
• checkout opens;
• test or agreed production payment flow works;
• order is created;
• confirmation email is delivered;
• order appears in the admin panel;
• payment status is correct;
• inventory is updated, if expected;
• analytics receives purchase or checkout events;
• there are no links to staging;
• there is no test content;
• feature flags are configured correctly;
• logs and monitoring do not show a sudden increase in errors.

A production smoke check should be short and safe. Its goal is to make sure real users can purchase after the release.

Common mistakes

1. Checking only the product page and forgetting checkout

The product page may look perfect, but if cart, checkout, or payment do not work, the e-commerce flow is broken. The main purchase scenario should always be tested end-to-end.

2. Not verifying amounts

Subtotal, discount, shipping, tax, and total should match across product page, cart, checkout, confirmation page, email, admin panel, and payment provider. Even a small difference can be critical.

3. Testing only successful payment

Successful payment is important, but it is not enough. At minimum, failed payment, declined payment, interrupted flow, and absence of duplicate orders should also be checked.

4. Forgetting guest checkout

If guest checkout is supported, it should be tested separately. It may behave differently from checkout for a logged-in user.

5. Not checking inventory

If stock logic does not work, the store can sell unavailable products or block products that are actually available. Inventory should be checked on the product page, cart, checkout, and admin panel.

6. Not checking emails

A user may successfully pay for an order but never receive a confirmation email. For e-commerce, this is a serious issue because email is often the main purchase confirmation.

7. Ignoring mobile checkout

A mobile user may reach the product page but get stuck at checkout because of small fields, a covered button, broken payment widget, or inconvenient form.

8. Not checking admin/order management

If the order is visible to the user but does not reach the admin panel, warehouse, CRM, or fulfillment system, the team may not process the purchase.

9. Not checking discounts and edge cases

Promo codes, gift cards, sale prices, free shipping, taxes, and multi-currency often create complex edge cases. They should not be checked with only one happy path.

10. Not running a production smoke check

Staging may work, but production can fail because of payment configuration, email sender, analytics property, feature flags, domain settings, or integrations.

FAQ

What is an E-commerce QA Checklist?

An E-commerce QA Checklist is a list of checks for an online store or e-commerce product. It helps test catalog, product pages, cart, checkout, payments, shipping, taxes, discounts, emails, orders, inventory, admin panel, integrations, analytics, and production readiness.

The main goal is to make sure the user can complete the full purchase journey and the team can correctly receive and process the order.

What should be checked in e-commerce QA?

At minimum, check:

• product catalog;
• product detail page;
• product variants;
• cart;
• checkout;
• pricing and total;
• promo codes or discounts;
• shipping;
• payment;
• order confirmation;
• emails;
• inventory;
• admin panel;
• mobile checkout;
• analytics;
• production smoke check.

If the product is complex, also check returns, refunds, subscriptions, gift cards, multi-currency, taxes, integrations, and role-based access.

How is e-commerce QA different from regular website QA?

Website QA usually checks pages, links, forms, mobile, SEO, analytics, and production readiness.

E-commerce QA goes deeper because it includes purchasing and order processing: product data, cart, checkout, payment, tax, shipping, promo codes, inventory, confirmation emails, order management, refunds, and integrations.

In simple terms: website QA answers "does the website work?", while e-commerce QA answers "can the user buy, pay, receive confirmation, and can the team process the order?"

How do you test checkout?

Checkout should be tested end-to-end:

• open checkout;
• fill in shipping and billing information;
• choose shipping method;
• check subtotal, tax, shipping, discount, and total;
• choose payment method;
• complete successful payment;
• check confirmation page;
• check confirmation email;
• check order in the admin panel;
• check payment status;
• check inventory update, if expected.

Also test errors: invalid address, invalid card, declined payment, required fields, page refresh, double submit, and out-of-stock during checkout.

Should failed payment be tested?

Yes. Failed payment is a required scenario for e-commerce QA, especially if the store accepts online payments.

Check that failed or declined payment does not create a successful order, does not send the wrong confirmation email, does not reduce stock without a reason, and shows the user a clear error.

How do you test promo codes?

Promo codes should be tested not only for application but also for rules.

Check that:

• valid code is applied;
• invalid code shows an error;
• expired code does not work;
• discount is calculated correctly;
• code applies only to the right products;
• excluded products do not receive the discount;
• total is updated;
• promo code is displayed in checkout, email, and admin panel;
• promo code can be removed;
• multiple discounts work according to product rules.

What should be checked in mobile e-commerce QA?

For mobile e-commerce QA, check:

• product listing;
• product detail page;
• product variants;
• add to cart;
• cart;
• checkout;
• forms;
• payment method;
• order confirmation;
• mobile menu;
• sticky CTA;
• no horizontal scroll;
• readability of products, prices, and order summary.

The main goal is to make sure the user can not only browse products but also complete the purchase from a phone.

Should the admin panel be checked?

Yes. E-commerce QA should include the admin panel or order management system if the team uses it to process orders.

Check that the order appears, customer data is correct, products and variants are correct, the amount matches, payment status is correct, fulfillment status is clear, and the team can process the order.

What is an e-commerce smoke test?

An e-commerce smoke test is a short check of the main purchase flow. It usually includes:

• product page opens;
• product can be added to the cart;
• checkout opens;
• payment works in test mode;
• order is created;
• confirmation email is delivered;
• order is visible in the admin panel;
• there are no critical errors.

A smoke test does not replace full QA, but it helps quickly confirm whether the store works at a basic level.

How do you know an e-commerce release is ready?

An e-commerce release can be considered ready when:

• product pages work;
• cart works;
• checkout works end-to-end;
• pricing, discounts, shipping, tax, and total are calculated correctly;
• payment works;
• failed payment is handled correctly;
• order is created;
• confirmation email is delivered;
• inventory is updated correctly;
• order is visible in the admin panel;
• mobile checkout works;
• analytics collects key events;
• there are no blocker or critical bugs;
• production smoke check has passed.

Create an e-commerce QA checklist

Use this e-commerce QA checklist as a starting point for your next online store launch, checkout release, or marketplace update. In qa::checklist, you can organize checks by catalog, cart, checkout, payment, inventory, admin, and integrations, then export the completed checklist to CSV.