What ShopPath checks.

The shopper path we check

ShopPath runs browser journeys on approved public storefront URLs. URL-based setup does not require an app or plugin installation. Every storefront needs approval, and you must own it or have permission to test it.

• Discover a product and open its product page.
• Select available product options and attempt to add the product to the cart.
• Review the cart and attempt to reach the visible start of checkout.

The journey follows the storefront it encounters. A missing control, access restriction, or execution problem can stop it before all checkpoints are reached; review the result and evidence to understand why.

Desktop and mobile browser views

Desktop uses a 1440 × 900 viewport; mobile uses a 390 × 844 mobile browser view. Mobile is emulated, not a physical phone test. Neither view certifies compatibility across every browser, device, product, or geography.

Each view uses one journey. Manual tests select one view at a time on every plan. A scheduled desktop-and-mobile check uses two journeys.

Two parts of a report

• Browser journey: whether the tested path reached checkout, supported by checkpoints, screenshots, and a recording when available.
• Shopping experience analysis: a separate review of captured screenshots for issues and practical improvements.

A passed journey can still have findings worth investigating. Conversely, a bot restriction or technical execution error is not automatically a storefront defect. Review findings against the captured evidence; automated analysis does not guarantee detection of every issue.

What we do not test

Journeys stop before submitting customer details, payment, or an order. They do not test a completed purchase, charge a card, or validate payment settlement.

Automatic CAPTCHA solving is off by default. In Storefront settings, you can allow the browser provider to attempt supported challenges for that storefront. This applies to newly queued manual and scheduled tests. Unresolved challenges still stop the journey; solving is not guaranteed.

A pass means the captured path reached the visible start of checkout—not that the entire store is problem-free. A prelaunch gate or sign-in wall can make that path inaccessible to an ordinary shopper.

On demand or on a schedule

Manual tests are available within your active access and journey allowance. Eligible paid plans add daily or weekly schedules in your chosen time zone. Essential schedules use one view; Growth and above can schedule both views.

Tests enter a queue before starting. Manual and automatic tests share the allowance, and new tests pause when it is exhausted; there are no automatic overage purchases. Read the workflow and usage guide.

Unsure whether your storefront fits?

The BigCommerce app is coming soon; WooCommerce, Shopify and Magento plugins are planned. These connections are separate from the URL-based setup available by request today. Plugin availability does not determine whether a particular shopping path can be tested.

Request a storefront review. Custom, headless, and authenticated journeys need an individual fit assessment; submitting a URL does not automatically approve it or confirm that its shopping path is supported.