Catch broken checkouts before customers do.
Tracefox replays the checkout flows you set up for each store, on a schedule. When one fails, you get an alert that names the step, with a screenshot of every step before it.
Built for agencies looking after many client stores. Works the same for one store.
Free plan: one test, 10 runs a month by hand, no card. Scheduled runs start on Starter, and every paid plan starts with a 7-day trial.
Scheduled daily run, mobile viewport, confirmed by a re-run
The test could not get to shipping: the “Continue to shipping” button was on the page but never became visible.
Technical detail
Step 5: Could not find the element to click. “Continue to shipping”: 1 match but none visible (hidden duplicate, collapsed section, or display:none).
- Open product page (passed)2.1s
- Select size 50 ml (passed)0.6s
- Add to cart (passed)0.9s
- Apply code WELCOME10 (passed)1.4s
- Continue to shipping (failed)timed out
Every client store, one screen
Add a test for each flow that matters on each client store. The tests page shows which passed, which failed, which you paused, and how much of the month's run allowance is left.
- One workspace for all your stores, with teammates and shared alert settings.
- A usage forecast before you turn on a schedule, and a clear notice if runs stop.
- A report for each client store: what was checked, which checks failed, when a later check passed, and any gaps in scheduled checks. On paid plans, with your branding on Pro and Business.
Sample client report Sample failed run How agencies use Tracefox
Know which step failed, and why
A test checks what its steps check. These are failures a well-built test finds, and what the run report shows you.
Add to cart stops working after a theme update
Step: Click “Add to cart”
Report: “1 match but none visible”, plus the page as the test saw it
A discount code no longer applies
Step: Apply the code, then check the order summary shows the discount
Report: The text it expected and didn’t find, with the summary on screen
Shipping can’t continue for one country
Step: Select the country, then click Continue
Report: Which step stopped, and a screenshot of any error on the form
The payment form doesn’t appear
Step: Wait for the payment section to show
Report: The wait timing out at that step, before anything is paid
A product page errors or redirects
Step: Open the page and check the product title is there
Report: The address it landed on and what the page displayed
Set up a store in three moves
Create the test
Generate it from the store URL, record it with the Chrome extension on Pro and Business, or add steps by hand. Choose desktop, mobile or tablet for it.
Run it once
A manual run proves the steps work. You get a screenshot of each one, so you can fix a step before anything is scheduled.
Schedule it
Weekly, daily or hourly, as your plan allows. Failures go to your email, and to Slack on Pro and Business.
Want help with your first store?
Email us the store URL and the flow you want covered, for example add to cart through to shipping. We'll reply by email and help you set up and check that first test. A person answers, usually within one business day.
When you'll hear about it
A failure is found on the next scheduled run, so the schedule decides how long it can go unnoticed.
| Schedule | From | Found within |
|---|---|---|
| Weekly | Starter | up to 7 days |
| Daily | Pro | up to 24 hours |
| Hourly | Business | up to about an hour |
Add the run itself and, usually, one confirming re-run before the alert: a few minutes. Runs come from a monthly allowance shared by the workspace; one hourly test uses up to 744 runs a month.
What it doesn't do
- It runs Chromium only. Mobile and tablet are emulated screens, not real iPhones or Safari, so check Apple Pay and Safari on a device.
- It stops before payment unless you build a test that completes a zero-total order with a 100%-off code.
- It checks the flows and steps you set up. A page or step that isn't in a test isn't checked.
- Pixel monitoring tells you when a script appears, disappears or changes. It doesn't verify that the right event fires with the right data.
- Consent checks are technical observations, not legal advice.
Also included: script and pixel checks
Tracefox scans each site you add for tracking scripts, pixels and cookies, and tells you when one is added, removed or changed. So a theme update that drops the Meta Pixel shows up in a scan, not weeks later in your ad reporting.
One site on Free, up to 50 on Business. Scans run monthly to daily depending on plan.
What a broken checkout could cost
Put in your own numbers. The model shows its working, and its result is sales at risk, not a promise.
Estimated sales exposed per year
- Without scheduled checks
- $16,800
- With daily checks
- $8,400
Modeled exposure avoided: $8,400 a year. Pro costs $990 a year on annual billing ($99 monthly).
How this is calculated
- Sales per hour: 120 orders × $70 ÷ 24 = $350
- Exposed per hour: $350 × 100% = $350
- Without checks: 2 failures × 24 hours × $350 = $16,800
- With daily checks: a failure is found on average 12 hours after it starts (half the time between runs).
Assumes a failure is equally likely to start at any time between runs. Run time, the confirming re-run and alert delivery (usually minutes) are left out, and so is time to fix, which is the same either way.
These are sales at risk, not profit or guaranteed recovered revenue: some customers come back and buy later.
Plans
Start free with one test and 10 runs a month. Paid plans add schedules and start with a 7-day trial.
Free forever, no card needed
Try Tracefox risk-free.
- 1 Checkout test, 10 manual runs a month
- Chromium, desktop viewport
- Email alerts on test failure
- Bonus: 1 website monitored monthly
- 7-day history
7-day trial, then billed monthly
For freelancers and small ecommerce stores.
- 20 Checkout tests, weekly runs
- 120 test runs per month, shared across the workspace
- Chromium, desktop viewport
- Email alerts on test failure
- PDF reports
- Bonus: 5 websites monitored weekly
- 30-day history
7-day trial, then billed monthly
For growing ecommerce stores and agencies.
- 20 Checkout tests, daily runs
- 750 test runs per month, shared across the workspace
- Choose desktop, mobile, or tablet per test
- Chrome extension recorder
- Step screenshots and run video
- Slack + email alerts on failure
- White-label PDF reports
- Bonus: 15 websites monitored daily
- 60-day history
Video is off for runs that enter a sensitive value or fill a password field.
7-day trial, then billed monthly
For high-volume ecommerce and large agencies.
- Up to 30 checkout tests, hourly cadence available
- 3,000 test runs per month, shared across the workspace
- One hourly test uses up to 744 runs a month, so about 4 can run hourly; see the usage forecast
- Choose desktop, mobile, or tablet per test
- Chrome extension recorder
- Step screenshots and run video
- Slack + webhook + email alerts
- White-label PDF reports
- Bonus: 50 websites monitored daily
- 90-day history
- Priority support
Video is off for runs that enter a sensitive value or fill a password field.
Questions
How does a checkout test work?
A test is a list of steps on one store: open a product, add it to the cart, apply a code, fill the shipping form, check that the order summary shows what it should. You create it from a store URL, record it with the Chrome extension (Pro and Business), or add steps by hand, and pick one viewport for it: desktop, mobile or tablet. Tracefox runs it in Chromium on your schedule and keeps a screenshot of every step.
Will tests place real orders?
Not unless you build one that does. Most tests stop before payment, and reaching the payment step doesn't prove a payment would go through. If you want to check the last step too, use a discount that brings the whole total to zero, including shipping and tax; that order is real, shows up in your store, and can change inventory and send emails. Tracefox never asks for real card numbers. Test data you enter (name, address, email) is stored with the test so it can fill in forms, so use made-up details.
How quickly will I hear about a failure?
It depends on the schedule. A failure is found on the next run: up to a week later on a weekly schedule, up to a day on daily, up to an hour on hourly. Scheduled failures are usually re-run once to rule out a blip, then you get an email, and a Slack message on Pro and Business.
Does it test Safari or real iPhones?
No. Every run uses Chromium. Mobile and tablet tests emulate the screen size and touch input, which catches layout and flow problems, but not Safari-only bugs. Check Apple Pay and Safari on a real device.
Which platforms does it work with?
Recorded or hand-built tests work on most checkouts that work in Chromium: Shopify, WooCommerce, BigCommerce, Magento, and custom or headless storefronts. Generating a test from a store URL works for Shopify, WooCommerce and BigCommerce. Nothing is installed on the store.
How is it different from Ghost Inspector or Checkly?
Ghost Inspector also records tests without code, and Checkly runs Playwright scripts you write. Both can run far more often, and Ghost Inspector covers more browsers, which suits QA and engineering teams. Tracefox is narrower: it is built around checkout flows across client stores, with client reports, one shared run allowance per workspace, a usage forecast before you turn a schedule on, and script and pixel checks included.
Can I try it free?
Yes. The Free plan includes one test that you can run by hand 10 times a month, with no card. Scheduled runs start on Starter ($29 a month, weekly checks), and every paid plan starts with a 7-day trial (card required at checkout). Annual billing costs the same as ten months.
Guides and free tools
For diagnosing a checkout that has already stopped converting.
- Shopify checkout not working?A step-by-step diagnosis, most common causes first.
- Reduce cart abandonmentCheckout bugs that look like abandonment, and how to find them.
- Shopify checkout, explainedCheckout Extensibility, customization and testing.
- Shopify abandoned cartRecovery emails versus fixing what breaks.
- Cart abandonment statisticsSourced figures by industry, device and cause.
- Free toolsCookie scanner, script audit, website grader and more.
Schedule your first checkout.
One test and 10 runs a month free, no card. Paid plans start with a 7-day trial.