What is Shopify storefront QA?
Shopify storefront QA is a repeatable check of the public shopping journey before launch or client handoff. It verifies that the product a shopper selects is the product added to the cart, totals remain consistent, configured discounts behave as expected and checkout can begin without submitting payment.
The goal is not to produce a generic score. The goal is to answer a practical delivery question: can the client review a clear record of what passed, what needs attention and what was outside the tested scope?
1. Prepare a controlled test
Choose representative products instead of clicking random pages. Include a simple product, a product with multiple options, a discounted product and any high-risk bundle or subscription experience. Record the storefront domain, exact product URL, test date, browser width and expected promotion before starting.
Use a clean cart unless cart persistence is part of the test. If the store contains customer-specific pricing, localization, markets or app-generated widgets, record that context so another tester can reproduce the same result.
2. Test product pages and variants
Confirm the visible title, price, availability message, product media and add-to-cart action describe the same purchasable item. For products with variants, note the option selected at page load, then choose a genuinely different available option. Do not count clicking the already-selected option as a variant test.
- Select each important color, size or bundle option and confirm the selected state is visible.
- Check whether variant-specific price, compare-at price, media, SKU and availability update when applicable.
- Add the alternate option to the cart and verify the cart line item names the chosen variant.
- Review unavailable combinations and sold-out states so shoppers cannot add an invalid option.
This follows the same customer-facing concerns highlighted in Shopify's official theme testing checklist, including variant selectors and dynamic variant information.
3. Verify add-to-cart and cart state
After adding the product, compare the cart with the selection made on the product page. The product name, variant, quantity and price should remain aligned. Increase and decrease quantity, remove the item and inspect the empty-cart state. If the theme uses both a cart drawer and a cart page, test the transition between them.
Cart restoration matters during QA because testing should not silently destroy a user's original cart. Record whether the initial cart was empty, preserved or restored. CartProof can restore the original cart state after a supported audit, but the final report should describe the customer-facing outcome rather than internal endpoint details.
4. Compare discounts with an expected result
A discount check needs an explicit expectation. Record the code and expected percentage or amount before applying it. Then compare the observed subtotal, discount line and final cart total. A code being accepted is not enough if the resulting amount is wrong.
Automatic discounts, bundles, subscriptions and market-specific pricing can change the calculation path. When the result cannot be confirmed safely, label it as a warning with a recommended manual review instead of reporting a false pass.
5. Check checkout handoff without payment
Confirm that the cart's checkout action reaches the expected Shopify checkout path and carries the intended line items forward. Stop before payment submission. If the project requires a completed transaction, use an approved Shopify test-order method as a separate test with the merchant's permission.
CartProof verifies checkout handoff without submitting payment. This boundary keeps a routine storefront audit from creating an order or charging a card.
6. Turn observations into handoff evidence
Use pass, warning and fail consistently. A pass means the expected behavior was observed. A warning means the result needs human review or the evidence is incomplete. A fail means the observed result did not match the stated requirement.
Issue: Selected variant state did not visibly change.
Expected: The selected state, image or price should update for the alternate option.
Observed: No visible change was detected after selecting a different available variant.
Recommended action: Review theme variant bindings before client sign-off.
Finish with one decision: Ready for handoff, Ready with warnings, or Fixes required before handoff. That conclusion makes the report usable by a project manager or client who was not present during testing.
What CartProof automates and what stays manual
CartProof is a Chrome side-panel extension for repeatable public storefront checks. It detects supported Shopify pages, runs user-triggered product and cart checks, records results and exports client-ready evidence. Public storefront checks do not require Shopify admin access.
Final visual review, copy accuracy, analytics, accessibility, legal content, business-specific acceptance criteria and completed payment testing remain manual responsibilities. Treat automated findings as evidence for a review, not as a guarantee that every storefront issue has been found.
Shopify QA questions
Do you need Shopify admin access to test a storefront?
Many public product, variant, cart and checkout handoff checks can be completed without admin access. Configuration, analytics, inventory rules and approved payment tests may still require merchant access.
Should storefront QA complete a real order?
No. Verify product, cart and checkout handoff first, then use Shopify's approved test-order process separately when payment completion is in scope.
What evidence should the report include?
Include the tested URL and scope, expected and observed behavior, status, screenshot evidence where useful, recommended action and the final handoff decision.