Know your checkout still works, before a customer tells you it doesn't.
Tracefox records your checkout flow once and replays it on a schedule, hourly, daily, or weekly, in a real browser. When a theme update, a plugin change, or a payment-gateway config flip breaks a step, the next scheduled run fails and shows you which step broke. No code. No staging environment. Works on most ecommerce platforms.
Free plan: 1 test, 10 manual runs a month · No credit card required
Checkouts break silently, not loudly.
Real outages, servers down, error pages, are rare and everyone notices. The expensive breakages are the quiet ones: a button that no longer adds to cart, a shipping step that only fails on mobile, a coupon field that swallows the code. These don't trigger uptime alerts. They just bleed revenue until a customer emails support.
Theme & app updates
Shopify theme push. WooCommerce plugin auto-update. BigCommerce app install. Any of these can break a checkout step without throwing an error anywhere.
Hours or days to detect
Without automated replay, you learn about breakage when conversion drops in analytics, often hours or days later, or when a customer emails. By then the revenue is gone.
Device-specific failures
Checkout works on your desktop but a third-party mobile script is blocking the submit button on phones. You'd only find out if you happened to test on mobile. Tracefox can run that test on a mobile viewport so the mobile-only break is visible (emulated in Chromium; issues that only happen in Safari or on real devices aren't covered).
Set it up once. Replay on a schedule.
Setup is a one-time job per flow. After that, Tracefox runs unattended until you change the flow.
Install the extension
The Tracefox Chrome extension (Pro and Business) captures clicks, typing, dropdown choices, checkboxes, scrolling and page changes as you walk through your checkout manually.
Click through checkout
Add to cart, fill in shipping info, and reach the payment step, where recording stops. The extension saves the steps as a reusable test.
Pick a schedule
Hourly on Business, daily on Pro, weekly on Starter. Pro and above unlock the mobile and tablet viewports, so you can save a second test of the same flow on a different device size.
Get alerts on failure
Email on every plan, Slack on Pro and Business, webhooks on Business. After a confirming re-run, Tracefox sends the failed step, a screenshot, and a link to the run and its video.
If a shopper can complete it in a browser, you can usually test it.
Tracefox uses real headless Chromium. There's no platform-specific integration, no API that needs to exist, no custom SDK. If the checkout loads in a browser, it's usually testable. Steps inside iframes, such as card fields, and hover, drag or file upload steps aren't recorded.
Shopify
Theme updates, Shopify Plus checkout extensions, app installs, payment gateways.
WooCommerce
Plugin updates, WordPress core changes, cache invalidation, payment gateway plugins.
BigCommerce
Embedded checkout, custom checkouts, Stencil theme changes, app conflicts.
Magento / Adobe Commerce
Module updates, composer updates, checkout extension conflicts.
Plus Squarespace Commerce, custom Next.js / headless storefronts, and any other browser-based checkout.
You don't just hear "it broke." You see exactly how.
Many testing tools tell you a test failed. Tracefox tells you which step failed, what the page looked like when it failed, and what the browser recorded leading up to it.
- Video of the full run , on Pro and Business, watch the failure happen (not for runs that use a sensitive value)
- Step-level screenshots , a screenshot after each step, so you can pinpoint where it went wrong
- Error message , the step that failed and why the browser couldn't complete it
- Link to the run , open the screenshots and video from the alert and pass them to a developer or client
On Pro and Business, a video of each run (except runs that type a password or other sensitive value).
Desktop, or mobile or tablet on Pro and Business, chosen per saved test.
A screenshot after each step, in sequence.
The failing step and its error message.
What a passing test proves, and what it doesn't
A pass means every step you configured worked in Chromium, on the test's viewport, at that moment: the product page, cart, discount and shipping steps, up to the payment step. These checks do not verify payment authorization. A test configured to complete a zero-total order can additionally verify order creation and confirmation.
A failure means a configured step couldn't be completed. It doesn't by itself show that customers were affected, and pages or steps outside the test aren't checked.
Common questions
What is automated checkout testing?
Automated checkout testing is when a tool replays a full checkout flow, add to cart, enter shipping, reach the payment step, on a schedule, in a real browser, without a human clicking through it. If a step fails, you get an alert once a re-run confirms it. It's how you can find out your checkout is broken before customers tell you.
How is this different from uptime monitoring?
Uptime tools tell you if the homepage loads. Checkout testing tells you whether a customer can get through your checkout to the payment step. Proving that a payment is authorised and an order created needs a separate sandbox or zero-total test, because routine monitoring stops before payment. Many outages that kill revenue aren't site-down events, they're silent regressions: a payment gateway app update, a theme change, a Shopify app conflict. Uptime checks miss all of these. A replayed checkout catches them in the next scheduled run, on the steps the test covers.
Do I need to write code to set this up?
No. On Pro and Business you install the Chrome extension and click through your checkout once (add to cart → checkout → payment page); the extension records each step and stops at payment. On any plan you can also generate a test from a Shopify, WooCommerce or BigCommerce store URL, or add steps by hand. Tracefox replays the test on its infrastructure, weekly, daily, or hourly depending on your plan, with no code involved.
Will it place real orders every time it runs?
No. Tests stop before payment: the extension stops recording at the payment step, and test data never includes card details. A test only completes an order if you deliberately build it to place a zero-total order (for example a 100% discount plus free shipping), and that creates a real order you then cancel. A typical setup runs against the live store without placing orders.
How often should checkout tests run?
Depends on volume. For a store taking orders every hour, run the most important flow hourly (Business plan), so a break is flagged within about an hour. One hourly test uses about 720 runs a month of the shared allowance. For smaller stores or staging environments, daily or weekly is typically fine. The key is running them unattended, on a schedule, not just after deploys.
What platforms does this work with?
Most browser-based checkouts: Shopify, WooCommerce, BigCommerce, Magento, Squarespace Commerce, custom Next.js / headless storefronts. Generating a test from a store URL works for Shopify, WooCommerce and BigCommerce; recorded or hand-built tests work on other storefronts. The recorder captures steps on the main page, not inside iframes such as card fields, and doesn't record hover, drag or file upload steps.
What happens when a test fails?
When a scheduled test fails quickly, Tracefox re-runs it once to rule out a blip; that re-run doesn't use another run from your allowance. If it fails again, you get an email alert (plus Slack on Pro and Business, webhooks on Business) with the step that broke, the error message and a link to the run, which shows a screenshot of every step and, on Pro and Business, a video (not for runs that use a sensitive value). From there you can share the evidence with your developer or client. When the test passes again, you get a recovery email.
Stop finding broken checkouts in arrears.
Start with one free checkout test with manual runs. No credit card.