From your first test to useful evidence.

Start without a plugin

URL-based setup is available by request today. You do not need to install a plugin or know which platform powers your store.

1. Request a free trial with your business email and storefront URL. Choose Storefront URL — no plugin required as the setup method.
2. We review the shopping path and your ownership or authority to test it. The request does not create an account or charge, and submitting a URL does not guarantee approval.
3. After approval, follow the secure invitation email to set your password and sign in to ShopPath. Check the approved storefront and your allowance before the first test.

The BigCommerce app is coming soon. WooCommerce, Shopify and Magento plugins are planned; they are not required for URL-based access and are not yet generally available.

Check that you are ready

• Storefronts: the store is approved and active. For a connected BigCommerce store, check the connection too; its name and URL are managed through BigCommerce.
• Usage & plans: your trial or subscription has active access and journeys remaining.
• The storefront: products and the cart are accessible to an ordinary shopper, without relying on your store-admin session.

Only test storefronts you own or are authorized to test. A pending store cannot run journeys. If you already have BigCommerce app installation access, follow the BigCommerce installation guide for that separate setup path.

Run a shopper test

1. Choose Run Shopper Test and select an approved storefront.
2. Choose desktop or mobile. Review Browser locale and the optional Postal code, then submit the test.
3. Follow the queued or running status in Shopper Tests. Queued means the journey is waiting to start; you do not need to submit it again.
4. Open the journey to review its result and evidence. If cancellation is available on an active journey, request it there.

One manual test uses one selected view and one journey. Both views are available on every plan; to check desktop and mobile manually, submit one test for each view. Mobile is an emulated browser view, not a physical-device certification.

An explicit new retry is another journey and uses the same allowance as a new test. Internal technical retries do not create extra customer journeys. Do not repeatedly retry a CAPTCHA or access restriction; investigate the block first.

Read the result, then inspect the evidence

The browser journey result describes whether the tested path reached the visible start of checkout. The shopping experience analysis separately reviews captured screenshots for findings and practical improvements. A passed journey can still have findings.

• Start with context: confirm the storefront, browser view, test time, and result.
• Inspect the path: review checkpoints, screenshots, and the browser recording when available. Match a finding to the evidence before changing your store.
• Distinguish the cause: a storefront problem, a bot restriction, and a technical execution failure are not interchangeable. Missing evidence is not proof that the store is broken.
• Track follow-up: use Issues for recurring findings. Manually closing an issue records your decision; it does not mean a later test verified a fix.

Journeys stop before submitting customer details, payment, or an order. Results cover the captured path, not every product or device. ShopPath does not guarantee detection of every issue. Review coverage and limitations.

Choose how tests handle CAPTCHAs

Open Storefronts, expand Storefront settings on the relevant store, and use Automatically solve CAPTCHAs. It is off by default. Turn it on and save to let the browser provider try supported challenges.

The saved choice is shared by your workspace and applies to tests queued afterward, including scheduled tests. Already queued or running tests and their automatic attempts keep their original setting. A new retry you request uses the current storefront setting. An unresolved challenge still stops the test; enabling this option does not guarantee completion or change storefront approval requirements.

Set up automatic tests

Eligible paid plans support daily or weekly schedules. Open Schedules, choose the approved storefront, and review the schedule settings: frequency, day where applicable, local time, time zone, and browser view. Enable and save the schedule, then check its next run.

Essential schedules use one view. Growth and above can schedule desktop and mobile together; that check uses two journeys. Manual and automatic tests share the same allowance. Plan for both when reviewing remaining journeys.

You can pause a schedule without deleting its saved settings. New tests pause when access is inactive or the allowance is exhausted; ShopPath does not automatically buy overages. A schedule does not bypass approval, connection, or storefront access restrictions.

Understand your allowance and billing dates

Usage & plans separates your subscription from the capacity available to this workspace. Check the current plan, access status, journeys used and remaining, allowance dates, and any workspace-specific limits.

• Trial: seven journeys during seven days. It ends on the displayed date and does not renew or automatically become a paid subscription.
• Stripe monthly billing: the journey allowance follows the subscription's monthly billing period, not a separate first-of-the-month reset.
• Stripe annual billing: payment renews yearly, but the included journey allowance renews monthly from the subscription anchor. The next payment and allowance reset can be different dates.
• Additional credits or custom capacity: these are shown separately and do not rename your subscription. Check credit expiry and the actual dates shown; unused additional credits do not automatically renew or roll over.

Use the billing controls offered to your workspace. Review the charge and effective date before confirming a change. Stripe-managed upgrades can take effect immediately with a prorated charge; downgrades and annual-to-monthly changes take effect at the next renewal. Do not assume a plan change resets usage or that uninstalling an integration cancels billing. Read billing and cancellation terms.

Share a report carefully

Growth and Scale include shareable reports. When sharing is available for the journey, choose Share report, select an expiry, review the access warning, and confirm before creating the link.

Copy the complete link before leaving the dialog; its access key cannot be displayed again. Anyone with that link can view the report and its screenshots and video without signing in. Screenshots and video are not redacted. Account details, debug logs, and other reports stay private.

Shared reports are marked not to be indexed and are not listed in sitemaps, but that does not make the link recipient-restricted. Send it only to intended recipients. Use Revoke in the sharing dialog to stop new access; it cannot recall downloaded copies. The link also ends when the report's workspace availability period ends, even if you selected a later expiry.

Get help without sharing credentials

Open Help & support and create a ticket with the closest topic, a specific subject, and a plain-text message. Include the journey ID, expected behavior, visible error, and approximate time with its time zone. Attachments and live chat are not available.

“Waiting for support” means the ticket is in the support queue. A support reply changes it to “Waiting for you”; your reply returns it to the queue. You can close a resolved ticket and reopen it to continue.

The original requester receives email notifications for support updates. Read and reply in ShopPath; email replies are not added to tickets. If you cannot sign in, email support@getshoppath.com. Never include passwords, API keys, OAuth codes, tokens, or payment card details.