Is your checkout working right now? Find out in a few minutes, free, no sign-up.Scan my store

My store runs on

Checkout broke at 2:10 a.m.
You knew by 2:15.

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.

to see problems as money at risk.

No sign-up. Our test shopper never places an order or logs in.

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.

  1. Test shopper tries to buy
  2. Fails twice at payment
  3. Owner and developer alerted
  4. Acknowledged and fixed
example-store.com02:14

Test shopper, run every 15 minutes

  1. Open a product page
  2. Add to cart
  3. Shipping options appear
  4. Reach the payment step

Example alert. Figures are illustrative.

Every 15 mina test purchase, stopping before payment
Every 5 mininside checks from a read-only pluginorders read through a read-only app
13 checks4 checkseach explained in plain words
No customer dataever leaves your store

01 / What it does

Uptime tools ask "is the site up?" StoreOnCall asks "can people buy?"

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.

Tries to buy

Every 15 minutes a test shopper goes through checkout to the payment step, then stops. If customers would get stuck, it gets stuck first.

Watches the inside

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.

Tells the right person

Owners hear what broke and what it costs. Developers get where to look. One click to acknowledge, or it escalates.

02 / Watch it decide

See StoreOnCall think, minute by minute

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.

Normal for this hour Orders Half of normal Alert sent

12:00 Watching

    03 / Problems we catch

    Real Magento problems, and how StoreOnCall catches each oneReal BigCommerce problems, and how StoreOnCall catches each one

    A payment module breaks after an update

    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.

    Cron stops after a server change

    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.

    Add to cart fails after a deployment

    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.

    Indexes fall out of date

    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.

    Order emails stop going out

    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.

    The full page cache is switched off

    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.

    A payment gateway starts declining

    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.

    Shipping disappears at checkout

    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 theme or app change breaks the cart

    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.

    No way to pay at checkout

    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.

    Orders quietly drop

    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.

    The app loses access

    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.

    04 / How you connect

    A read-only plugin, installed by your developer in 10 minutesA read-only app, installed in one click

    Same alerts, same dashboard, same reports on both platforms. Only the way in is different.

    Magento and Adobe Commerce

    A read-only plugin

    A developer installs it in about 10 minutes. The setup guide walks them through it, or emails them the exact steps.

    • Test shopper every 15 minutes
    • Orders against normal, payment methods
    • Cron, indexes, queues, caches and order emails
    • Deployments and extension changes named as likely causes
    How it works on Magento

    BigCommerce early access

    A read-only app

    Install it in one click from your BigCommerce control panel. No code, no developer needed.

    • Test shopper every 15 minutes
    • Orders against normal, payment methods
    • BigCommerce runs the servers for you, so there is less that can quietly break
    • Same alerts, reports, API and agency features
    How it works on BigCommerce
    Your store Test shopper PluginApp StoreOnCall Owner Developer Reports visits like a customer counts every 5 minorders every 5 min

    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?

    What does a broken checkout cost you?

    Type your monthly online revenue. We work out what an hour, a night and a weekend of "nobody noticed" costs.

    One hour$139
    One night, found in the morning (8 hours)$1,111
    A weekend, found on Monday (60 hours)$8,333

    Average sales spread evenly over the month. Your busiest hours cost more. StoreOnCall's Store plan is $149 a month.

    Check my store now

    06 / One bad night

    The same problem, two very different mornings

    A payment step fails after a late deployment. Times are illustrative.

    Without StoreOnCall

    1. A deployment breaks the payment step. Every page still loads.
    2. The uptime monitor checks the home page: all green.
    3. A customer emails: "I could not pay."
    4. The developer finds the cause and rolls back.
    5. More than 8 hours of lost orders.

    With StoreOnCall

    1. A deployment breaks the payment step.
    2. The test shopper fails at payment, checks again, fails again.
    3. Owner and on-call developer are alerted, with the deployment named as the likely cause.
    4. One click to acknowledge. The developer rolls back.
    5. Minutes of lost orders, not a morning.

    07 / How it works

    Set up in an afternoon. Then forget about it.

    These are recordings of the real dashboard with a test store. Pick a step, or let it play.

    Adding a store in the dashboard (test store)

    08 / One alert, two readers

    Plain words for the owner. The detail for the developer.

    Every alert is written twice, so nobody has to translate at 2 a.m.

    Example alert. Figures are illustrative.

    Critical Customers cannot complete checkout

    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
    AcknowledgeOpen incident

    09 / What we check

    Everything between a shopper and an order

    Every check StoreOnCall runs, with the exact moment it alerts and what each person is told to do. Click one.

    Sales

    Checkout test

    What it watches
    Every 15 minutes a test shopper adds a product to the cart, enters a test address and checks that shipping and payment options appear. It never places an order.
    Why it matters
    If the test shopper cannot reach payment, real customers probably cannot either.
    When it alerts
    A test fails twice in a row (we double-check before counting it). Critical, alerted immediately. If a firewall blocks the test, it shows as "could not test", never as a failure.
    The owner is told to
    • Try to buy something on your store yourself, on your phone.
    • Forward the alert to your developer: it says which step failed.
    The developer is told to
    • Open the failing step (add to cart, checkout page, shipping or payment) and check var/log/exception.log.
    • Check deployments, extension or setting changes listed under "Recent changes".
    • Check the payment and shipping providers' status pages and API credentials.
    Full details

    Sales

    Orders compared with normal

    What it watches
    Orders in the last 10 minutes to 8 hours, compared with what is normal for your store at that time of day and day of week, adjusted for how the last day has been trading.
    Why it matters
    A sudden drop in orders is often the first sign that something is broken, even when every page loads.
    When it alerts
    Orders are at most half of normal and the chance of such a drop being normal ups and downs is under 0.02%. Needs about 2 days of reports first, and windows expected to have fewer than 4 orders are never judged. Critical when orders stop completely, high otherwise.
    The owner is told to
    • Check the checkout test result on this page.
    • Try to place a test order yourself.
    • Check whether a campaign ended or ads were paused: those lower orders without anything being broken.
    The developer is told to
    • Check checkout, payment methods and recent deployments.
    • Compare traffic in your analytics: if visitors are normal but orders are not, the problem is on the site.
    Full details

    Sales

    Payment methods

    What it watches
    For each payment method, how many orders in the last 3 hours ended up stuck waiting for payment or cancelled. Orders under 30 minutes old are left out, because customers may still be paying.
    Why it matters
    When a payment method breaks, customers who choose it cannot pay, and the orders sit unpaid.
    When it alerts
    A method has at least 3 orders in the last 3 hours and half or more of them are stuck or cancelled. High, alerted immediately.
    The owner is told to
    • Check your payment provider's dashboard and status page.
    • Consider switching that payment method off until it is fixed.
    The developer is told to
    • Check the payment module's logs and API credentials.
    • Check webhooks or IPN callbacks from the provider reach the store.
    Full details

    Background jobs

    Background jobs (cron) running

    What it watches
    The plugin reports through Magento's background jobs (cron) every 5 minutes, so a missing report means cron has stopped or the server cannot reach us.
    Why it matters
    Without cron, prices, stock, search, emails and indexes stop updating.
    When it alerts
    No report for 20 minutes. High, alerted immediately.
    The owner is told to
    • Forward the alert to your developer or host.
    The developer is told to
    • Check the Magento cron line in crontab -l and var/log/cron.log.
    • Run bin/magento storeoncall:status on the server.
    • Check the server can make outbound HTTPS calls.
    Full details

    Background jobs

    Failing background jobs

    What it watches
    Background jobs that ended in an error in the last hour.
    Why it matters
    Repeated failures usually mean emails, indexes or imports are not happening.
    When it alerts
    3 or more failed jobs in the last hour, lasting 15 minutes. Medium.
    The owner is told to
    • Forward to your developer; no action needed from you.
    The developer is told to
    • Check cron_schedule for status=error and the messages column.
    • The alert lists the job codes.
    Full details

    Background jobs

    Skipped background jobs

    What it watches
    Background jobs Magento skipped in the last hour, usually because the server is overloaded or cron runs too rarely.
    Why it matters
    Skipped jobs mean updates happen late or not at all.
    When it alerts
    10 or more skipped in the last hour, lasting 30 minutes. Medium.
    The owner is told to
    • Forward to your developer.
    The developer is told to
    • Check cron frequency (every minute), server load and long-running jobs.
    Full details

    Background jobs

    Stuck background jobs

    What it watches
    Jobs that have been "running" for over an hour.
    Why it matters
    A stuck job can block the same job from running again, for example price or stock updates.
    When it alerts
    Any job running for over an hour, lasting 30 minutes. Medium.
    The owner is told to
    • Forward to your developer.
    The developer is told to
    • Find the job in cron_schedule (status=running) and check whether its process is still alive.
    • Clear stale running entries once the cause is fixed.
    Full details

    Prices, stock and search

    Indexes up to date

    What it watches
    Magento's indexes, which keep prices, stock, categories and search results correct on the storefront.
    Why it matters
    An out-of-date index can show wrong prices, sell out-of-stock products or hide products from search.
    When it alerts
    Any index marked invalid for 30 minutes. High when it is prices, stock, search, categories or catalog rules; medium otherwise.
    The owner is told to
    • Forward to your developer.
    • Spot-check a few product prices and stock on the storefront.
    The developer is told to
    • Run bin/magento indexer:status, then bin/magento indexer:reindex for the listed indexes.
    • Check why they were invalidated: a failed reindex, cron, or an admin save.
    Full details

    Prices, stock and search

    Index updates waiting

    What it watches
    For indexes set to "update by schedule", how many changes are waiting to be applied.
    Why it matters
    A growing backlog means storefront prices and stock fall behind what is in the admin.
    When it alerts
    5,000 or more waiting, or 500 or more and growing by half within 30 minutes, lasting 30 minutes. Medium.
    The owner is told to
    • Forward to your developer.
    The developer is told to
    • Check the indexer_update_all_views and indexer_reindex_all_invalid cron jobs and the mview changelog tables.
    Full details

    Background jobs

    Message queues

    What it watches
    Magento's message queues (for example bulk actions, inventory and exports).
    Why it matters
    Stuck queues delay stock updates, bulk changes and exports.
    When it alerts
    A queue with 1,000 or more waiting and still growing, or new errors, lasting 30 minutes. Medium.
    The owner is told to
    • Forward to your developer.
    The developer is told to
    • Check consumers (bin/magento queue:consumers:list, cron consumers_runner) and RabbitMQ if used.
    Full details

    Background jobs

    Order emails

    What it watches
    Order confirmation emails waiting to be sent (only when Magento sends emails in the background).
    Why it matters
    Customers who do not get a confirmation contact support or order again.
    When it alerts
    5 or more order emails not sent, lasting 30 minutes. Medium.
    The owner is told to
    • Forward to your developer.
    The developer is told to
    • Check the sales_send_order_emails cron job and the mail server or SMTP extension logs.
    Full details

    Speed

    Page cache

    What it watches
    Whether Magento's full page cache is switched on.
    Why it matters
    With the page cache off, pages load much more slowly and the server can struggle at busy times.
    When it alerts
    Page cache switched off for 10 minutes. High.
    The owner is told to
    • Forward to your developer.
    The developer is told to
    • Run bin/magento cache:enable full_page and check why it was switched off.
    Full details

    Speed

    Caches needing a refresh

    What it watches
    Cache types Magento has marked as needing a refresh after changes.
    Why it matters
    Usually harmless; if it lasts, storefront changes may not show.
    When it alerts
    For 60 minutes. Low: shown here and sent to developers only, never to owners.
    The owner is told to
    • Nothing to do.
    The developer is told to
    • Refresh the listed cache types (bin/magento cache:clean <types>).
    Full details

    Sales

    Checkout test

    What it watches
    Every 15 minutes a test shopper adds a product to the cart, enters a test address and checks that shipping and payment options appear. It never places an order.
    Why it matters
    If the test shopper cannot reach payment, real customers probably cannot either.
    When it alerts
    A test fails twice in a row (we double-check before counting it). Critical, alerted immediately. If a firewall blocks the test, it shows as "could not test", never as a failure.
    The owner is told to
    • Try to buy something on your store yourself, on your phone.
    • Forward the alert to your developer: it says which step failed.
    The developer is told to
    • Open the failing step (add to cart, checkout page, shipping or payment) and check var/log/exception.log.
    • Check deployments, extension or setting changes listed under "Recent changes".
    • Check the payment and shipping providers' status pages and API credentials.
    Full details

    Sales

    Orders compared with normal

    What it watches
    Orders in the last 10 minutes to 8 hours, compared with what is normal for your store at that time of day and day of week, adjusted for how the last day has been trading.
    Why it matters
    A sudden drop in orders is often the first sign that something is broken, even when every page loads.
    When it alerts
    Orders are at most half of normal and the chance of such a drop being normal ups and downs is under 0.02%. Needs about 2 days of reports first, and windows expected to have fewer than 4 orders are never judged. Critical when orders stop completely, high otherwise.
    The owner is told to
    • Check the checkout test result on this page.
    • Try to place a test order yourself.
    • Check whether a campaign ended or ads were paused: those lower orders without anything being broken.
    The developer is told to
    • Check checkout, payment methods and recent deployments.
    • Compare traffic in your analytics: if visitors are normal but orders are not, the problem is on the site.
    Full details

    Sales

    Payment methods

    What it watches
    For each payment method, how many orders in the last 3 hours ended up stuck waiting for payment or cancelled. Orders under 30 minutes old are left out, because customers may still be paying.
    Why it matters
    When a payment method breaks, customers who choose it cannot pay, and the orders sit unpaid.
    When it alerts
    A method has at least 3 orders in the last 3 hours and half or more of them are stuck or cancelled. High, alerted immediately.
    The owner is told to
    • Check your payment provider's dashboard and status page.
    • Consider switching that payment method off until it is fixed.
    The developer is told to
    • Check the payment module's logs and API credentials.
    • Check webhooks or IPN callbacks from the provider reach the store.
    Full details

    Connection

    Store data can be read

    What it watches
    Every 5 minutes StoreOnCall reads the store's recent orders through the read-only BigCommerce app.
    Why it matters
    If we cannot read the orders, we cannot tell whether customers are buying.
    When it alerts
    No successful read for 20 minutes. High, alerted immediately. Removing the app stops reading without an alert.
    The owner is told to
    • Check the StoreOnCall app is still installed: Apps > My Apps in BigCommerce.
    The developer is told to
    • Check the BigCommerce status page.
    • Reinstall the app if its access was revoked.
    Full details

    10 / Who it is for

    Built for everyone a broken store keeps awake

    Store owners

    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 trial

    Developers

    The 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 rules

    Agencies

    Every client store on one screen, your name on alerts and reports, bulk scans for prospects, and 25% of what referred brands pay.

    For agencies

    11 / For agencies

    Every client store on one screen. Your name on the reports.

    • Portfolio of every client store, problems first, grouped by client
    • Bulk scan up to 50 stores at once: clients or prospects
    • Your agency name on alerts and monthly reliability reports
    • Acknowledge, assign, notes, escalation and an audit log
    • Partner programme: earn 25% of what referred brands pay, for as long as they stay
    Start an agency trial
    Agency overview listing client stores with status, problems and checkout test results (test data)

    12 / Pricing

    Simple pricing. 14-day trial, no card.

    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.

    Free

    See it working on one store

    $0forever

    1 store

    Start free
    • All inside checks
    • Daily summary email
    • Free store scans

    Store

    For one store that has to keep selling

    $149/month

    1 store

    Start 14-day trial
    • Real-time alerts: email, Slack, Teams, PagerDuty, Telegram, webhook
    • WhatsApp alerts
    • Checkout test every 15 minutes
    • Escalation if nobody responds
    • Audit log

    Agency

    For agencies that look after many stores

    $999/month

    10 stores, then $79 per store

    Start 14-day trial
    • Everything in Business
    • Client portfolio and bulk scan
    • Your agency name on alerts and reports
    • 25% partner share on referred brands

    Prices in US dollars. Taxes and invoices are handled by our payment partner. Cancel any time. Compare every feature.

    13 / Security

    Read-only. No customer data. Ever.

    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.

    • Read-only database queries; adds no tables, pages or admin users
    • Counts and statuses only: anything that looks like personal data is refused
    • Sign-in by single-use link, email on new devices, automatic sign-out
    • Every change and sign-in recorded in an audit log
    What StoreOnCall sees
    {
      "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 access

    Example of a report. Field names simplified.

    What never leaves your store
    • Customer names and emails
    • Addresses and phone numbers
    • Card or payment details
    • IP addresses
    • Passwords or admin access

    14 / Questions

    Questions

    I am not technical. Can I still set it up?

    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.

    Which stores does it work with?

    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.

    Will the plugin slow my store down?

    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.

    Will the app slow my store down?

    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.

    Does the checkout test place orders?

    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.

    Will I get false alarms?

    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.

    Can I stop at any time?

    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

    Rather talk to a person?

    Not sure it fits your store, or want a walkthrough for your agency? Message us on WhatsApp or email, and a person replies.

    Email hello@storeoncall.com

    WhatsApp +91 91806 04521, Monday to Friday, 10 am to 6 pm India time. Email any time.

    • A walkthrough of the dashboard on your own store
    • Help choosing a plan, or a quote for many stores
    • Help for your developer with the install
    • Partner programme details for agencies

    See what your customers would hit today

    The free scan takes a few minutes and needs no sign-up.

    Scan my store freeStart a 14-day trial

    WhatsApp us