Features · Protect revenue
Know when orders stop, before the day’s takings tell you.
Operanse learns how many orders and payments this store normally takes at each hour of the week, and tells you when that changes: orders thinning out, payments failing, paid orders stuck, or a store that can no longer sell.
On every plan, Watch (free) includedWatch: a store that can no longer take an order. Monitor: orders and payments against the store’s own normal, priced.
≈ $1 240 shortfall, priced from this store's own takings
- observed
- 2 orders, 14:00–15:00
- usual
- 11–17 for a Tuesday at 14:00
estimate ≈ $1,240 shortfall over 3 hours, priced from this store’s own takings
A checkout can break while every page still loads
A gateway update goes out at lunchtime. The shop, the cart and the checkout page all load; the uptime check stays green. Customers press Place order and nothing happens. The first sign is usually an evening sales report that looks thin, or a customer email.
- Fewer orders than usual for the hour, with no error page anywhere.
- Payments failing at one gateway while another is fine.
- Orders paid at the gateway that never move out of pending.
What you can see
Orders against this store’s own normal
Orders are compared with the same hour on previous weeks, so a quiet Sunday night is not an alarm and a quiet Tuesday afternoon is. A slowdown and a full stop are both reported, with the store’s usual range beside what was observed.
Payment failures by gateway
Completed, failed and refunded payments are counted for each gateway. The failure rate is judged on first attempts; retries are counted apart, so a retry run after a bad hour does not look like a second bad hour.
For Stripe’s own reason codes, see Stripe payment monitoring.
| gateway | completed | failed (first attempts) | retries | status |
|---|---|---|---|---|
| Stripe | 3 | 7 | 2 | failing |
| PayPal | 5 | 0 | 0 | normal |
Paid, and never moved
An order carrying a gateway transaction that is still pending after 15 minutes means the money arrived and the store did not finish the order. These are counted with their total, which is often the first sign of a broken payment webhook.
An incident with what it is costing
Each incident is priced from the store’s own hourly sales, as an estimate, or says which figure is missing to price it.
- observed
- 9 orders with a Stripe transaction, pending more than 15 minutes
- usual
- none for Thursday 09:00–10:00
- payments
- 2 completed in the last hour, against a usual 11–17
estimate $1,180 taken at the gateway and not fulfilled
The figure is an estimate from this store’s own hourly sales, labelled as one. When there is not yet enough history to price an incident, it says which figure is missing and when it will exist, rather than guess.
Coverage and limits
What it covers
- Orders that stop or slow. Orders arriving below their usual rate for this hour, or stopped altogether, with the revenue it is costing.Monitor
- Payment failures by gateway. Completed, failed and refunded payments for each gateway. A failure rate counts first attempts; retries are counted apart.Monitor
- Paid, and never moved. Orders that were paid for and are still pending after 15 minutes, with their total.Monitor
- A store that can no longer take an order. The last payment method switched off, the checkout, cart or shop page unpublished, or every product out of stock.All plans
- What it is costing. Each incident priced from the store’s own hourly sales, or a plain statement of which figure is missing to price it.Monitor
- Can it still sell? On every plan, including Watch: the number of payment methods enabled, the checkout, cart and shop pages published, and products in stock.
Limits
- It does not place test orders. A checkout that fails in the browser is seen when orders stop arriving, typically within about 30 minutes.
- Revenue figures are estimates from the store’s own history, and say so. Until there is enough history, the incident says which figure is missing instead.
- Learned comparisons start once the store has 48 hours of history; a weekly pattern takes about two weeks.
- It never retries a payment or changes an order. It is read-only.
Stripe reason codes · Outage cost calculator (free) · How incidents are priced
Start using it
- Install the plugin from wordpress.org. It is read-only: it cannot change the site.
- Pair the site with the token from your dashboard. Setup, step by step
- Readings start at once. Judgements against the store’s own normal start once it has 48 hours behind it.
All plans On every plan, Watch (free) included. Watch: a store that can no longer take an order. Monitor: orders and payments against the store’s own normal, priced. Compare plans
Questions
Will I get an alert for every declined card?
No. Ordinary declines are counted. An alert comes when the failure rate is unusual for this store at this hour, or when the store can no longer take an order.
What does the free plan cover?
Watch checks whether the store can still take an order: a payment method enabled, the checkout, cart and shop pages published, and products in stock. Learned order and payment comparisons and revenue estimates are on Monitor and Insight.
Which gateways does it count?
Payments are counted per gateway from WooCommerce’s own orders, whichever gateway took them. Stripe’s reason codes need the official WooCommerce Stripe Payment Gateway plugin.
How is the cost worked out?
From the store’s own takings for that hour of the week, compared with what came in. It is labelled as an estimate, and renewals due in the window are included without counting retries twice.