Review representative products and states
Choose a small product set that exposes the storefront's important differences: a long title, multiple variants, an unavailable option, a promotion, and an item with special delivery information. Check listing cards, search, product detail, cart quantities, and empty-cart behavior. Use realistic test data rather than relying on the shortest product name and a single default variant.
Compare displayed information across the journey. Prices, discounts, selected variants, availability, and delivery expectations should remain understandable as the shopper moves between pages. Keep regional and account conditions in the report when they affect the result. A screenshot should support the claim; describe the interaction when the problem happens only after a selection or refresh.
Test purchase behavior safely
Use your platform's supported test-order or sandbox process for payment checks. Shopify, for example, documents test orders for checking checkout and store settings. Confirm that test mode and fulfillment behavior are appropriate before running a transaction. Keep real payment details, customer records, and private order information out of screenshots and recordings.
Checkout may run on another domain or within a restricted platform surface where arbitrary scripts are unavailable. Do not assume that installing a storefront widget gives it access to checkout, payment-provider frames, or every order screen. Review those steps with the platform's own tools and record findings through an appropriate route when on-page capture is unavailable.
The review workflow
Choose safe review coverage
List representative products, variants, regions, devices, and journey states. Use a staging store or controlled test data and confirm where the platform permits the widget script.
Report the exact storefront state
Pin the affected control and name the product, selected variant, quantity, and actions taken. Describe the expected cart or page result without exposing customer or payment information.
Verify across the journey
Retest the product page, cart, and supported checkout path. Check that the resulting order or cart state matches the display, using the store platform's safe testing process.
DEFINE DONE
Acceptance checklist
- The selected product variant and quantity match what appears in the cart.
- Pricing, promotion, and delivery messages remain consistent through the reviewed journey.
- Unavailable and invalid states explain what the shopper can do next.
- Payment and order checks use approved test procedures and safe data.
ILLUSTRATIVE EXAMPLE
A size selection lost when returning to a product
Fictional example: a clothing storefront reviewer selects a medium shirt, opens the size guide, and returns to the product. The button still looks ready, but the selection has reset.
THE FEEDBACK
Select medium, open and close the size guide, then add to cart. Expected: one medium shirt. Actual: the cart contains the default size, although the page did not clearly show the reset.
The developer fixes the selection state. The reviewer repeats the sequence with several sizes and checks the cart on the agreed mobile and desktop layouts.
Fit and plan limits
There is no guarantee of widget access inside a hosted checkout or third-party payment frame. Use only installation locations your platform supports, and review protected payment steps separately when necessary.
Screen recording and external integrations require paid plans. The widget is hidden on production hosts unless production visibility is enabled; decide deliberately whether a live storefront should expose review controls. Feedback capture is not a conversion experiment or payment-security audit.
Common questions
Will the widget work in every checkout?
Only where the platform permits installation and the page configuration supports it. Hosted checkouts, cross-origin payment frames, and restricted surfaces may need separate review tools.
Should we use real customer orders for testing?
Prefer safe test data and the platform's supported sandbox or test-order procedure. Avoid putting real payment details or private customer information in review evidence.
Further reading
- Shopify's test-order guidance
Platform-specific guidance for safely checking checkout and order settings; use your own platform's equivalent procedure.