Online shop monitoring: cart and payment checked the way a customer would
A shop rarely goes down as a whole. More often one step breaks: the payment gateway stops responding, the cart does not calculate delivery, the order form returns an error. All that time the home page shows green. Every few minutes Uptimo walks the checkout flow in a real browser and tells you which step failed.
Failures ordinary monitoring does not see
Every situation below ends with code 200 on the home page. Monitoring that only checks the address walks past them without an alarm, while sales drop to zero.
The payment gateway does not respond
The customer reaches payment and sees a spinner. No order is created, the cart is abandoned, and in the statistics it looks like a slower day.
The cart does not calculate delivery
After a courier integration is deployed, the delivery cost field stays empty. The customer cannot go further, because the form waits for a value it will never get.
Login rejects a correct password
The session is lost after an update and the customer is sent back to the form. The shop works, but returning customers cannot reach their accounts.
The certificate expires over the weekend
The browser shows a warning about an insecure connection before anyone sees a product page.
Exactly what we check in a shop
A scenario is built from a list of steps, with no code. A typical shop path looks like this and runs every few minutes, always the same way.
On top of that come lightweight checks that cost milliseconds: HTTP and HTTPS for the shop and the admin panel, DNS, ping, TCP port and the certificate expiry of every https address. Certificates are watched in every plan, including the free one.
Works with any shop, because it clicks like a customer
You install no plugin and you give us no access to your shop's admin panel. The scenario opens your shop in a browser and walks the same path as a customer, so the engine does not matter: a hosted platform, a subscription shop or your own code. We need the address and a test account if the path requires login.
Deployments without false alarms
A shop changes during the season, and every deployment can move an element a scenario step depends on. A planned maintenance window silences alerts while the work is done, and excluding that period from SLA calculations is a separate, deliberate decision, so the report stays honest. Alerts go by e-mail, to Slack, Microsoft Teams, by SMS or webhook, with escalation and an “I am on it” acknowledgement, so one stumble does not wake the whole company.
What watching a shop costs
You pay for scenarios and frequency, because they are what occupies the browser. One shop is usually one checkout scenario, sometimes a second one for login.
Annual billing is 20% cheaper. The Solo plan (PLN 0) has no scenarios, but it watches address availability and certificate expiry, so it is a sensible first step.
What we do not do, stated plainly
- The scenario does not place a real order. It usually stops at the payment gateway and checks the text. If you want to measure the payment itself, use the provider's test mode or a product priced at 0.
- We do not bypass CAPTCHA or two-factor authentication. For monitoring you create a test account without 2FA, and the steps before the protection are monitored separately.
- We check from one location in the European Union. We do not pretend to run a network of a hundred probes; for a checkout flow, frequency and step fidelity are what matter.
- Recordings, screenshots and HAR files are kept for 14 days. The incident history stays permanently, because availability is calculated from it.
What shop owners ask
A scenario is one browser session every few minutes, which is incomparably less traffic than a single customer. To keep the data clean, use a test account and a product marked as test, and runs can be excluded from analytics by browser name.
That is when monitoring matters most. A checkout scenario runs every 5 minutes in every plan, and lightweight checks (the page, DNS, the payment API) every minute in the Team and Agency plans. An alert about a broken payment at peak sales pays for the subscription in minutes.
Every path you want to watch is a separate scenario. Three shops with one path each fit in the Team plan with room to spare. You copy one shop's configuration to the next through export and import.
Yes. Every step has its own time, so you can see that adding to the cart takes three times longer today than last week. That is usually the first sign that the database or an integration is starting to choke.
You pick the steps from a list and point at elements on the page. You can also describe the path in plain sentences; the builder runs them on your page and shows the result of every step before you save. The first checkout scenario then usually takes fifteen minutes. On a demo we build it together with you.
Check whether your cart really works
Create an account, build one scenario for your checkout flow and leave it for a day. If it finds nothing, you will know it from a measurement, not from hope.