Audit the purchase journey, not just the theme

A Shopify UX audit should follow a shopper from finding a product to receiving an order confirmation. Use these 25 checks with real products, realistic delivery addresses, and the payment methods your store supports. Theme, plan, and checkout customizations can affect what you can change.

Finding products: checks 1 to 5

  1. Navigation language. Ask a new shopper where they would find a product. Category names should match how customers describe the items.
  2. Search results. Try a specific product, a broad category, and a common misspelling. Check that the result helps the shopper recover from an unsuccessful query.
  3. Filters. Verify that relevant attributes can be combined and cleared, and that selected filters remain visible.
  4. Collection cards. Make the product name, price, key variant information, and image understandable without opening every item.
  5. Empty states. Check out-of-stock collections and combinations of filters with no results. Offer a useful way back.

Understanding products: checks 6 to 10

  1. Image usefulness. Show scale, details, and relevant angles using authentic product imagery. Check zoom and image loading on mobile.
  2. Variant selection. Make the selected size or color explicit, and update price, availability, and image consistently.
  3. Product information. Answer the questions that influence purchase, such as dimensions, materials, compatibility, or care.
  4. Delivery expectations. Explain available delivery estimates and what information is needed for a more precise estimate.
  5. Returns and conditions. Make relevant conditions easy to find before purchase and keep the summary consistent with the actual policy.

Basket and checkout: checks 11 to 15

  1. Add-to-cart feedback. Confirm which variant and quantity were added, with an obvious next action.
  2. Basket editing. Change quantity, remove an item, and return to shopping. Check totals and stock feedback after each action.
  3. Total-cost clarity. Surface known charges and explain which taxes or shipping costs still depend on the address.
  4. Account requirement. Verify the configured account experience and make the available purchase route understandable.
  5. Discount interaction. Test an expired code and an ineligible basket. Explain the outcome without losing entered information.

Payment and recovery: checks 16 to 20

  1. Address entry. Try realistic local addresses, long names, optional fields, and mobile autocomplete.
  2. Payment options. Confirm that the displayed options work for the regions and currencies you serve.
  3. Validation feedback. Check that errors identify the field and explain the correction, with usable keyboard focus.
  4. Failure recovery. In an appropriate test environment, test a declined payment and an interrupted attempt. The customer should understand whether an order exists.
  5. Confirmation. Check the order reference, purchased items, next steps, and consistency between the confirmation page and notification.

Quality and measurement: checks 21 to 25

  1. Mobile usability. Complete the journey on a small screen. Look for obstructive overlays, cramped controls, and sticky elements covering important content.
  2. Accessibility. Check keyboard use, visible focus, labels, contrast, image alternatives, and announcements for meaningful status changes.
  3. Performance. Inspect large media, unnecessary app scripts, and layout shifts. Test representative pages rather than only the homepage.
  4. Localization. Verify language, direction, currency formatting, and regional addresses using actual content where those markets are supported.
  5. Analytics quality. Check the definitions and consent behavior of product-view, add-to-cart, checkout, and purchase events. Avoid counting repeated purchase events as separate orders.

Turn observations into prioritized work

Record each issue with the page, affected task, reproduction steps, observed consequence, and supporting evidence. Separate a confirmed usability problem from a hypothesis. Prioritize issues that block a purchase or misrepresent an order before cosmetic inconsistencies.

Assign an owner and a verification step to each fix. Some improvements belong in theme code, others in product content, app configuration, or operations. Check current platform capabilities before proposing a checkout change.

Further reading