Getting started
CheckoutBeat does one thing: it walks your online store's buy path with a real browser and tells you when a step breaks. Product page, add to cart, cart, checkout page. It stops before payment. Every 60 minutes on Starter, every 30 minutes on Growth and Agency.
Try it without an account
Paste your store's address into the box on the home page and press Check my store free. A browser opens one of your products, adds it to the cart, opens the cart and opens the checkout page, then shows you each step with its timing and, if something failed, the error and a screenshot. Three free checks per hour per visitor.
Sign in
- Open the sign-in page and enter your email address.
- Click the magic link in the email you receive. There is no password to remember.
- You land on the dashboard.
Add a store
On the dashboard, enter your store URL and press Add store. Shopify and WooCommerce stores are recognised from the home page and the first purchasable product is used; you can name a specific product page instead. Monitoring needs a plan: Starter watches 1 store, Growth 5, Agency 20, with up to 3 buy paths (products) per store.
The first check runs in the next schedule slot. From then on the store card shows its status, the time of the last check, the share of checks that passed in the last 30 days and a 48-block timeline (one block per schedule slot: green passed, amber passed up to the cart, red failed, grey no check).
What a check looks at
| Step | Passes when | Fails when |
|---|---|---|
| Product page | The page answers 2xx | 4xx/5xx, no response within 20 seconds |
| Add to cart | The add-to-cart button exists and the store accepts the add | Button missing, product sold out, the store rejects the add |
| Cart | The cart holds the item | The cart is empty after adding, the cart page errors |
| Checkout page | The checkout page loads | 4xx/5xx, timeout. A bot challenge stops the check at the cart and says so. |
Every check also records your store URL's HTTP status and time to first byte, the days left on its SSL certificate, and a fingerprint of the theme's stylesheet and script names, so a changed theme is noticed and emailed.
When something fails
One failed check is noted on the timeline. The same step failing on two consecutive checks opens an incident: you get an email (and a Slack message or a text if you set them up) with the step, the error, when it first failed and a screenshot. When a check passes again the incident closes and you get one more message with how long it was broken. See Alerts.
Where to go next
- Checks: the details of each step, bot protection, what counts as an on-demand check.
- Alerts: email, Slack, SMS and the daily digest.
- Billing: plans, limits, upgrading and cancelling.
- API keys and Agent access: running checks and reading results from code and from AI agents.
- Refunds: 14 days, no questions asked.
Support: the assistant on the account page answers from these pages; a person reads everything it cannot answer.