Free
See it working on one store
$0forever
1 store
Start free- All inside checks
- Daily summary email
- Free store scans
My store runs on
StoreOnCall tries to buy from your Magento store every 15 minutes and checks it from the inside every 5: payments, cron, indexes and orders.StoreOnCall tries to buy from your BigCommerce store every 15 minutes and watches your orders and payment methods every 5, through a read-only app. When customers cannot buy, you hear it first, in plain words, with the money at risk.
Not sure which platform? Paste the address anyway: the scan finds out by itself. Prefer to start watching now? Start a free 14-day trial, no card.
Test shopper, run every 15 minutes
Example alert. Figures are illustrative.
01 / What it does
Most expensive Magento problems keep every page loading: a payment method fails, cron stops, prices go stale.On BigCommerce the servers are looked after for you, but checkout still breaks: a gateway starts declining, shipping disappears, a theme or app change stops the cart. StoreOnCall catches them, three ways.
Every 15 minutes a test shopper goes through checkout to the payment step, then stops. If customers would get stuck, it gets stuck first.
A read-only plugin reports on orders, payment methods, cron, indexes, queues and order emails, and compares orders with what is normal for that hour.
A read-only app reads your orders every 5 minutes, compares them with what is normal for that hour, and watches each payment method on its own.
Owners hear what broke and what it costs. Developers get where to look. One click to acknowledge, or it escalates.
02 / Watch it decide
Pick what goes wrong. The chart shows orders against what is normal for that hour, and the log shows what StoreOnCall does about it. Example data, not a real store.
12:00 Watching
03 / Problems we catch
Customers pick the method, the payment never completes, orders pile up in pending payment.
How we catch it: each payment method is watched on its own; when most of its recent orders are stuck or cancelled, you get an alert naming the method.
Prices, stock, search and order emails quietly stop updating, while every page still loads.
How we catch it: the plugin reports through cron every 5 minutes, so 20 minutes of silence means cron has stopped. Failed, skipped and stuck jobs are named too.
A stale page cache or a broken extension stops the cart, but the product page looks perfect.
How we catch it: the test shopper adds to cart every 15 minutes, checks twice, and the alert names the deployment just before as the likely cause.
Shoppers see old prices, or buy products you no longer have in stock.
How we catch it: every index and its backlog is checked, and price, stock and search indexes are treated as the most serious.
Customers think the order failed, then call or order again.
How we catch it: with asynchronous sending on, unsent order confirmations are counted and alerted.
Often left off after debugging; the store slows down for everyone.
How we catch it: cache status comes in with every report, and a disabled page cache is flagged as high priority.
Expired credentials or a gateway change, and orders end up Declined or Awaiting Payment.
How we catch it: each payment method is watched on its own; when most of its recent orders are declined, awaiting payment or cancelled, you get an alert naming the method.
A shipping zone or carrier setting changes, and customers in a region see no way to ship.
How we catch it: the test shopper enters a test address in your chosen country every 15 minutes and checks shipping options appear.
A script or app update stops add to cart or checkout, while the store looks fine.
How we catch it: the test shopper adds a product to a cart and opens checkout every 15 minutes, checking twice before it alerts.
A payment method is switched off or misconfigured, and checkout offers nothing to pay with.
How we catch it: the test shopper checks payment methods are offered at checkout, then deletes its cart without paying.
Something breaks that no single check sees, and orders fall well below normal.
How we catch it: orders are compared with what is normal for that hour and day, learned from your past orders on day one.
If StoreOnCall can no longer read your orders, nothing is being watched.
How we catch it: 20 minutes without a successful read raises an alert; removing the app on purpose stops quietly.
More about StoreOnCall for MagentoMore about StoreOnCall for BigCommerce
04 / How you connect
Same alerts, same dashboard, same reports on both platforms. Only the way in is different.
Magento and Adobe Commerce
A developer installs it in about 10 minutes. The setup guide walks them through it, or emails them the exact steps.
BigCommerce early access
Install it in one click from your BigCommerce control panel. No code, no developer needed.
Your store. Magento or Adobe Commerce, on your server or Adobe Cloud.Your BigCommerce store, run on BigCommerce's servers. Nothing is changed, and no customer data leaves it. Click any box.
Test shopper. Every 15 minutes it adds a product to the cart, enters a test address and checks shipping and payment options appear. It never pays, and deletes its cart. A failure is checked twice.
Read-only plugin.Read-only app. Every 5 minutes, through Magento's own cron, it sends counts and statuses: orders, payments, cron, indexes, queues, order emails and caches.Every 5 minutes StoreOnCall reads your recent orders through the app's read-only access and turns them into counts per hour and per payment method.
StoreOnCall. Every minute it compares what came in with what is normal for your store at that hour and day, learned from your last 28 days. Only problems that are confirmed and last become incidents.
The owner gets plain words and the sales at risk per hour, on email, WhatsApp, Slack or Teams. One tap to acknowledge, or it escalates.
The developer gets the failing step, recent changes and where to look, on Slack, PagerDuty, Teams, a webhook or email.
Dashboard and reports. Every store on one screen, incident timelines, and a monthly reliability report to share.
On BigCommerce instead? On Magento or Adobe Commerce instead?
05 / What is it worth?
Type your monthly online revenue. We work out what an hour, a night and a weekend of "nobody noticed" costs.
Average sales spread evenly over the month. Your busiest hours cost more. StoreOnCall's Store plan is $149 a month.
Check my store now06 / One bad night
A payment step fails after a late deployment. Times are illustrative.
07 / How it works
These are recordings of the real dashboard with a test store. Pick a step, or let it play.

08 / One alert, two readers
Every alert is written twice, so nobody has to translate at 2 a.m.
Example alert. Figures are illustrative.
Our test shopper could not pay on your store (checked twice). Customers are probably hitting the same problem right now.
About $860 of sales at risk for every hour this lasts.
What to do: try to buy something on your phone, and forward this alert to your developer. It says which step failed.
Checkout test failed at "pay": payment step returned HTTP 500 (2 of 2 tries)
Likely cause: deployment at 02:08 (static version changed)
Check: var/log/exception.log, payment module credentials,
provider status page
Recent changes: Vendor_Payment 3.4.1 to 3.5.0
Checkout test: no payment methods offered (2 of 2 tries)
Test address: Auckland, NZ. Cart deleted after the test.
Check: Settings > Payments in BigCommerce, gateway
credentials, provider status page
09 / What we check
Every check StoreOnCall runs, with the exact moment it alerts and what each person is told to do. Click one.
Sales
Sales
Sales
Background jobs
Background jobs
Background jobs
Background jobs
Prices, stock and search
Prices, stock and search
Background jobs
Background jobs
Speed
Speed
Sales
Sales
Sales
Connection
10 / Who it is for
Know your store is selling without checking it yourself. Plain-words alerts with the money at risk, and a monthly reliability report.
Start a free trialThe failing step, recent deployments and extension changes, failed cron jobs and stuck queues, in the alert.The failing checkout step, the test address used and the payment methods affected, in the alert. Every failure checked twice.
See the exact rulesEvery client store on one screen, your name on alerts and reports, bulk scans for prospects, and 25% of what referred brands pay.
For agencies11 / For agencies
12 / Pricing
Every paid plan starts with a free 14-day trial. After it, you stay on the free plan unless you choose one.
Store plan: $149 a month.
See it working on one store
$0forever
1 store
Start freeFor one store that has to keep selling
$149/month
1 store
Start 14-day trialBest for growing brands
For brands with several stores
$399/month
Up to 5 stores
Start 14-day trialFor agencies that look after many stores
$999/month
10 stores, then $79 per store
Start 14-day trialPrices in US dollars. Taxes and invoices are handled by our payment partner. Cancel any time. Compare every feature.
13 / Security
The plugin only reads, only calls out, and never sends customer data. Run bin/magento storeoncall:preview to see exactly what it would send.The app asks BigCommerce for two read-only permissions and nothing else. Orders are reduced to counts as soon as they are read. How we protect your store.
{
"orders_last_hour": 42,
"by_payment": { "card": { "paid": 31, "pending": 2 } },
"cron": { "last_run": "2 min ago", "failed": 0 },
"indexers_invalid": [],
"queues": { "async.operations.all": 0 },
"full_page_cache": "on"
}Orders: read-only
Information and settings: read-only
Everything else: no accessExample of a report. Field names simplified.
14 / Questions
Yes. You add your store and choose where alerts go in the dashboard. The plugin needs someone with access to your store's server for about 10 minutes; the setup guide can email them the exact steps with your key filled in.
Magento Open Source and Adobe Commerce 2.4, self-hosted, on managed hosting or on Adobe Commerce Cloud. BigCommerce stores are in early access, with the checkout test, order and payment checks. The free scan works on both, and tells you which platform a store runs on.
It runs in the background through Magento's cron every 5 minutes, with a handful of read-only queries. It adds nothing to the pages your customers load.
No. It reads your orders through BigCommerce\'s API from our servers; nothing is added to your storefront. The checkout test is one shopper every 15 minutes, and it deletes its cart.
No. It adds a product to the cart, enters a test address and checks that shipping and payment options appear, then stops. There is nothing to cancel or refund.
Every failure is checked twice, most problems must last a few minutes before we alert, and order drops are judged against your own store's pattern for that hour. If a firewall blocks our test, we say "could not test", never "broken". You can rate every alert, and we use those answers to tune the checks.
Yes. Cancel the plan and you drop to the free plan. You can download all your data or close the account from the dashboard, and remove the plugin with the steps in the help centre.
15 / Talk to us
Not sure it fits your store, or want a walkthrough for your agency? Message us on WhatsApp or email, and a person replies.
Chat on WhatsAppEmail hello@storeoncall.com
WhatsApp +91 91806 04521, Monday to Friday, 10 am to 6 pm India time. Email any time.
The free scan takes a few minutes and needs no sign-up.