The shop opens, products can be browsed, and your monitoring reports no downtime. Even so, not a single order has come through in hours.
An online shop breakdown does not always mean an unreachable website. Payment notifications might not return from the gateway, stock levels may stop updating, orders might fail to reach the ERP, or the checkout form could be blocking a segment of your customers.
Technically, the shop is running, but one of the core processes driving sales is broken. These silent failures are especially expensive because you often only notice them hours later—or after customer complaints start rolling in.
A Shop Can Be Up and Running Without Making Any Sales
Basic uptime monitoring only answers one question: is the website online? That is useful information, but in e-commerce, it is nowhere near enough.
Your homepage may respond perfectly while customers are unable to proceed to payment. The basket might work, but the order never gets sent to the warehouse. A payment can be successfully captured, yet the shop still marks the order as unpaid.
That is why, whenever issues arise, the first question shouldn't just be "is the site working?", but "can a customer complete the entire purchase journey?".
Payment Has Been Taken, but the Shop Doesn't Know It
This is one of the nastiest scenarios. A customer places an order, gets redirected to the payment gateway, and completes payment. The money leaves their account, but the confirmation never reaches your store.
From the customer's perspective, things look broken. They paid, but received no confirmation. In the store backend, the order remains stuck on "pending payment". Your customer support team sees one thing; the payment operator sees another.
If the issue goes unnoticed, the fallout escalates quickly. The customer might attempt to pay again, contact support, or place a duplicate order. Meanwhile, your system might automatically cancel the initial order and release the reserved stock back into inventory.
If you suspect payment issues, always cross-reference recent store orders against transactions recorded with your payment provider. A sudden spike in orders pending payment is a red flag you should never ignore.
The Store Can Sell Products That Are Already Out of Stock
Many online shops do not track stock levels exclusively in WooCommerce or PrestaShop. Data syncs continuously from an ERP, a wholesaler, a warehouse, or a supplier's internal system.
If that sync fails in the morning, the shop might spend the rest of the day running on outdated inventory numbers.
On the front end, everything seems normal. The product is listed as in stock, can be added to the cart, and paid for. The problem only becomes obvious during order fulfillment, when it turns out the last unit was sold hours earlier through another sales channel.
In this case, checking whether the integration returned an explicit error isn't enough. What matters most is when the last successful sync took place.
If your inventory is configured to refresh every 15 minutes, going hours without a new sync should be treated as an outage in its own right.
Orders Roll In, but Get Stuck Halfway Through
When a customer hits "order", that is often just the first step in a much longer sequence.
The order might need to flow into an ERP, warehouse software, Baselinker, an accounting suite, a logistics carrier, or other fulfillment tools.
If one of these integrations breaks, the shop itself stays online. Customers can keep buying, and orders show up in the admin dashboard. But hours later, someone realizes the warehouse hasn't received a single new packing slip.
Whenever you troubleshoot an outage, don't just look at total order volume—check whether orders are actually progressing through every stage of the pipeline.
The more third-party systems involved in your sales pipeline, the more crucial it becomes to actively monitor data flow between them.
The Customer Made a Purchase, but Received No Confirmation
A failure in transactional email delivery won't bring sales to an immediate halt. At least not right away.
A customer places an order and pays, but never gets a confirmation email. Within minutes, doubt creeps in. Some check their bank statement, others try placing the order again, and many reach out to customer service.
A silent technical glitch quickly turns into a flood of tickets for your support team.
Make sure you verify not just that your store generates transactional emails, but that they are actually being delivered. Pay special attention to order confirmations, payment receipts, dispatch notices, and order status updates.
Checkout Might Only Be Broken for a Subset of Users
Not every outage affects your entire audience.
The bug might only trigger for a specific payment method, a particular shipping carrier, one country, a certain discount code, or when specific products are combined in the cart.
This makes detection tricky, as an internal team member running a standard test checkout might complete it without spotting a single flaw.
Sudden deviations in conversion data are your best warning signs. If 70% of initiated checkouts usually turn into completed orders, and that number suddenly plummets, investigate the checkout journey immediately—even if no one has formally reported a bug.
Treat it with the same urgency when a traditionally popular payment gateway suddenly records zero transactions.
Your Product Feed Might Stop Updating
A silent failure doesn't have to live inside the checkout funnel itself.
Stores that rely on Google Merchant Center, price comparison engines, marketplaces, and advertising platforms continuously sync data about products, pricing, and availability.
If the feed stops refreshing, the online store can still take orders. The real damage unfolds elsewhere.
External platforms keep serving stale pricing or out-of-date stock levels. Items may drop out of live campaigns or get disapproved entirely.
When monitoring product feeds, check more than just whether the feed URL responds—verify when the file was last generated and successfully fetched.
The Shop Runs Fine in the Morning, but Collapses During a Campaign
Performance bottlenecks frequently lie dormant until traffic spikes.
Homepages and category listings are usually served directly from cache, meaning they remain fast even under heavy visitor loads. The basket, checkout, user authentication, promo code engines, and order generation logic operate completely differently.
Before launching a major advertising push, product drop, or seasonal sale, verifying that pages load quickly is not enough.
You need to test the entire checkout flow alongside every connected system. The real bottleneck might not be your web server, but your payment gateway, ERP, warehouse software, or another integrated API.
A Lack of Orders Should Be an Alert in Itself
Most uptime monitoring listens for things that happened: an application crash, an unreachable server, an expiring SSL certificate, or a slow response time.
In e-commerce, it is just as critical to monitor events that should have happened, but never did.
If your shop normally processes a dozen orders every Saturday between 6:00 PM and 8:00 PM, and on one particular evening none come in, that demands investigation.
It doesn't guarantee a technical failure—sales fluctuate for many reasons. But sudden silence is an invaluable early warning, especially if initiated checkouts or pending-payment orders are climbing at the same time.
Apply the same logic to last-sync timestamps, confirmed transaction counts, and transactional email volume.
What to Do When Sales Suddenly Stop
If the store is reachable but sales drop off unexpectedly, start by walking through the purchase flow exactly like an end customer.
Add an item to the basket, proceed through checkout, pick a common shipping method, and run a real payment. Then confirm whether the order shows up in the backend, whether the payment status updates properly, whether stock deducts as expected, and whether the details reach your fulfillment tools.
At the same time, cross-check recent store orders against transactions logged in your payment gateway dashboard and verify the timestamps on your latest sync jobs.
This hands-on check tells you far more than repeatedly refreshing the homepage ever will.
Sometimes It Is Smarter to Disable One Feature Than the Entire Store
If the failure is isolated to a single payment option, consider temporarily switching it off while keeping the rest live.
You can take the same approach with a broken shipping provider or integration, provided the store can continue fulfilling orders reliably without it.
The situation changes if customers are being charged while their orders fail to register in the database. In that scenario, leaving checkout open only multiplies the number of transactions your team will have to untangle by hand.
When an incident happens, the challenge isn't just fixing the root cause as fast as possible. You must also decide whether the shop can safely keep taking orders while the repair is underway.
Don't Forget Active Ad Campaigns
If your checkout is down while Google Ads, Meta Ads, or other campaigns keep driving traffic, the cost of the outage climbs with every paid click.
Whenever an issue blocks the path to purchase, evaluate whether you should temporarily pause campaigns pointing to the broken funnel.
You don't always need to turn off all advertising. If the issue is confined to a specific category, product line, or regional market, you can pause only the relevant campaigns.
Once sales are running smoothly again, remember to unpause them.
How Much Does an Hour of This Kind of Outage Cost?
There is no universal figure that fits every online business.
The simplest starting point is baseline revenue generated on the same day of the week and at the same hour. An issue at 4:00 AM on a Monday carries very different financial weight than a broken checkout on a Friday evening during a promotion.
Lost gross revenue alone doesn't tell the full story, either.
You must factor in lost margins, wasted advertising spend incurred during the downtime, customer support overhead, developer troubleshooting time, and subsequent manual cleanup of orphaned orders and payments.
On the flip side, not every affected customer is gone forever—some will return once things are fixed. After a major incident, look at the historical data and calculate real revenue impact instead of relying on a generic hourly downtime estimate.
What to Audit After the Outage Is Resolved
Getting the site back to working order doesn't always mark the end of the job.
If the root issue involved payments, reconcile transactions captured during the incident against your order records. If data syncs stalled, verify whether missed updates will queue and process automatically. If inventory tracking failed, confirm whether out-of-stock items were accidentally sold during the downtime.
It is equally important to audit queued transactional emails, warehouse integrations, ERP connections, and any downstream fulfillment steps.
Fixing the root cause and resolving the secondary fallout are two distinct tasks.
How to Catch These Failures Before Your Customers Do
Uptime monitoring remains essential. It ensures you know right away when your server goes dark, throws 500 errors, or drops an SSL certificate.
In e-commerce, however, you have to go further by monitoring the business processes that actually generate sales.
That means tracking synthetic end-to-end checkout paths, monitoring pending-payment order thresholds, watching sync timestamps with your ERP or warehouse, validating feed generation, and checking third-party API health.
Crucially, monitoring must mirror the actual architecture of your store. Critical checkpoints for a boutique store dispatching a dozen orders a day look very different from an omnichannel operation handling multiple warehouses, marketplaces, and an external ERP.
The Store Is Up. But Is It Actually Selling?
A green uptime dashboard cannot tell you if customers can complete payment. It won't tell you if an order synced to the warehouse, if product quantities are accurate, or if ad platforms are pulling an updated feed.
That is why e-commerce monitoring needs to be built around the critical events that impact sales, not merely whether a server responds with HTTP 200.
At DOCK, we handle ongoing maintenance and development for WooCommerce and PrestaShop stores. When taking over support for a store, we audit the checkout journey, payment pathways, integrations, sync pipelines, and existing monitoring setups to expose the failure points that typical alerts miss.
If your online store is a vital revenue engine, it pays to identify those blind spots before your first warning comes from an unhappy customer.
