The real cost of an hour of downtime for a small ecommerce store

Ask a store owner what an hour of downtime costs and most will guess low. They picture a handful of missed sales, maybe a refresh-and-retry from an annoyed customer, nothing that shows up on the P&L. The number is usually bigger than that, and most of it is invisible until you sit down and calculate it. Below is that calculation, worked through for a hypothetical $250,000-a-year store, the kind run by one or two people who are also doing customer service, inventory, and marketing.

The math: what one hour actually costs

Start with the simplest version. A store doing $250,000 a year in revenue, spread evenly across 365 days and 24 hours, averages about $28.50 an hour. That number is almost meaningless on its own, because ecommerce traffic is never evenly spread. Most stores see a large share of their sales concentrated in a handful of hours: evenings, weekends, and the hours right after an email campaign or ad set goes live.

Assume a $65 average order value, which is typical for a small general-merchandise store. At $250,000 a year, that's roughly 3,850 orders annually, or about 10.5 a day on average. During a peak evening window, though, a store might process two to three times its average hourly order volume. That puts a realistic peak hour at 1 to 1.3 orders, or roughly $65 to $85 in sales that simply don't happen if the site is down or broken during that window.

One hour, one order or two, doesn't sound catastrophic. But that's only the direct, visible piece of the cost. The two pieces underneath it are where the real damage sits.

Ad spend doesn't pause when your site does

If the store runs paid acquisition, whether that's Google Shopping, Meta ads, or both, that spend keeps running whether or not the site is reachable. A small store spending 10% of revenue on ads, a common benchmark for growth-stage ecommerce, is spending around $25,000 a year, or about $68 a day. Concentrated into active campaign hours rather than spread across 24, that can easily be $10 to $20 an hour of live spend.

Every click during an outage is a click paid for and wasted. Worse than wasted, actually, since a visitor who clicks an ad, lands on a timeout error or a broken checkout, and bounces is a visitor who cost money and also formed a negative impression of the brand on the platform's dime. Ad platforms don't refund clicks because your site was down. The spend is gone, and depending on the platform's learning phase, an outage during an active campaign can also disrupt the algorithm's optimization, extending the cost beyond the outage window itself.

This is one reason outages tied to routine changes are more expensive than they look. A theme update that quietly breaks checkout, for example, can run for hours before anyone notices, all while ad spend keeps flowing toward a page that no longer converts. We've written in more detail about why Shopify stores lose orders during theme updates, and the pattern generalizes: the outage doesn't have to be dramatic to be expensive, it just has to be unnoticed.

The trust cost that outlasts the outage

The direct sales loss and the burned ad spend are both calculable. The trust cost is not, but it's real, and reasoning about it qualitatively still matters for decision-making.

A customer who hits a broken checkout once will often simply buy the same product elsewhere rather than try again later. Some will return, most people are more forgiving than store owners assume, but a meaningful share will not, and there's no clean way to measure the ones who quietly left. A returning customer who hits an error may also start wondering, even briefly, whether the store is still operating, which is a strange thing to have to overcome for a business that was working fine an hour earlier.

There's also a compounding effect with reviews and word of mouth. A single bad experience rarely gets mentioned publicly. A pattern of them does. Repeated outages, even short ones, are the kind of thing that shows up in a one-star review six months later as "site kept crashing when I tried to check out," attached to a purchase decision made by someone who never even experienced the outage directly. That's the cost that compounds quietly and shows up nowhere on a dashboard.

Why the timing of an outage matters more than the length

A ten-minute outage at 3am costs almost nothing. A ten-minute outage during a flash sale, a holiday campaign, or the hour after a big email send can cost more than a routine outage that lasts all afternoon on a quiet Tuesday. This is the part that makes downtime cost hard to estimate with a single number, and it's also the part that matters most for how an owner should think about risk.

Most small stores don't have someone watching the site around the clock, and they shouldn't need to. The realistic failure mode isn't a total server crash that's obvious within seconds. It's a partial failure: checkout throwing errors for one payment method, a broken theme update that only affects mobile, a stock sync issue that lets people add out-of-stock items to cart. These are the outages that run for hours because nothing looks obviously wrong from the storefront's homepage, and they tend to land during exactly the high-traffic windows where the cost is highest, because that's when changes get pushed and when load-related bugs surface.

What continuous monitoring actually changes

The lever an owner controls in all of this isn't preventing every possible failure. Software breaks, third-party payment processors have incidents, hosting has bad days. Shopify, WooCommerce, and BigCommerce all publish their own status and incident histories, and none of them promise zero downtime. The lever is detection time: the gap between something breaking and someone finding out.

This is the core idea behind Cassian™. It checks a store continuously, not just uptime but order flow, pricing, stock levels, and page speed, and alerts the owner through the channel they've chosen the moment something looks wrong. It won't stop a payment processor's outage or catch every possible failure mode, but it shortens the gap between "broken" and "noticed," which is usually the single biggest factor in how much an outage ends up costing. The Cassian Score™ gives a quick read on overall store health, so an owner can tell at a glance whether things are fine or worth a closer look, without needing to check five different dashboards.

For context on how a seemingly small, routine change can turn into exactly this kind of slow-burn outage, see why Shopify stores lose orders during theme updates, which walks through a common failure pattern in more detail.

The bottom line

The sticker price of an outage is never just the sales missed during the outage window. It's the ad spend burned against a site that can't convert, and it's a trust cost that shows up weeks later in ways no dashboard attributes correctly. None of this requires alarm, most stores go through occasional outages and recover fine. It's simply a reason to treat detection speed as a real, budgetable part of running a store, rather than something to worry about only after the fact.