Downtime measured in orders

WordPress Maintenance for Online Stores Where Downtime Costs Orders

An online store on WordPress loses money by the minute, and the parts that break are the parts that take the money: the payment gateway, the tax extension, the shipping calculator. Put your hourly order value into the calculator to quantify what an outage costs in a trading hour, then see cover that exercises the checkout after every release and rehearses the restore before peak season.

Worldwide service, remote. No long-term contracts.

Get a free site audit See what it costs

30-day money-back guarantee · No setup fee · Cancel anytime

What does an hour offline cost you?

One incident$2,400
Per year$4,800
Cover costs$948/year

Excludes the enquiries that never arrive because the site was down when someone searched.

See what cover costs
  • Checkout completed end to end on a staging copy after every plugin release
  • Payment, tax and shipping extensions held back when a release breaks one
  • Daily off-site backups of orders and stock, restorable in one click
  • 100+ sites under management. Plans from $39 a month
store checkout verified after release and peak season
The sequence this interrupts: a gateway extension updates then the cart and address form still work then the payment step fails then found in the abandoned-cart rate.
1,000+ WordPress sites built
500+ hacked sites recovered
150+ malware removals
100+ sites under management
50+ popular plugins mastered
10+ years on one platform

What goes wrong in this sector

  • The checkout breaks on a Tuesday afternoonA gateway or tax extension updates, the cart still works, and the final step fails. Customers abandon, nobody reports it, and the day's revenue is a third of Monday's before anyone looks.
  • Stock and orders are one host failure from goneThe backup is on the same server as the store, or it is the host's nightly snapshot nobody has ever restored. A restore that fails on the day is not a backup.
  • Card handling drifts out of complianceA payment plugin two versions behind, a checkout page served with a mixed-content warning, an abandoned extension still loading on every page. Each is a finding on a PCI questionnaire.
  • Peak season lands on an untested siteBlack Friday traffic arrives on a store whose caching, database and image sizes were last looked at in the spring. The site does not fall over; it slows until the cart times out.
  • A plugin update changes the price displayTax-inclusive becomes tax-exclusive, or a currency rounds wrongly, and the store sells at the wrong price for a fortnight before a customer mentions it.

Why a store cannot be maintained like a brochure site

A brochure site that is down for a morning has lost some attention. A store that is down for a morning has lost the morning’s orders, and most of the customers who tried to place them.

The arithmetic is unforgiving because it is direct. Revenue on a store is the checkout completing, and the checkout is the most plugin-dependent page on the site: a gateway, a tax extension, a shipping calculator, a coupon engine and the cart itself, each shipped by a different developer on a different schedule. A release to any one of them changes the page that takes the money.

That is why automatic updates on a store are the wrong kind of safety. They close the security window and open the checkout one, and the checkout one costs more.

What actually breaks, in order of how often we see it

The failures are quiet, which is what makes them expensive.

  1. The payment step. A gateway extension updates, the cart and the address form work, and the final step errors or hangs. The store looks open and takes no money. Abandoned-cart rate is the only signal, and nobody watches it hourly.
  2. Tax and shipping. A rule stops applying and the store undercharges or overcharges for a fortnight. Customers do not report a price that favours them.
  3. The backup that was never restored. A host failure or a bad update takes the database, and the nightly snapshot turns out to be three weeks old, or on the same disk, or restorable only by a support ticket.
  4. Peak-season slowness. The site was fast in March. By November the image library has doubled, the database holds a year of sessions and the cache is misconfigured. The cart times out under load rather than failing outright.

Every one of those is caught by walking the checkout after every change and rehearsing the restore before it is needed – which is the difference between store maintenance and pressing the update button.

What this costs against what it protects

The calculator above takes your revenue per trading hour, the hours the checkout is down and how often that happens in a year. Run it for a peak week, because that is when an untested release lands on the most traffic.

The figure it leaves out is the customer who abandoned a cart, bought elsewhere and did not come back. On a store, an outage costs more than the hour.

The work that protects it is WordPress store upkeep: the checkout walked after every release, extensions held back when they break it, and a restore rehearsed rather than assumed. What each tier includes is on wordpress maintenance plans, and the hardening of the checkout itself is WordPress security service work. A property firm’s site fails differently and is covered under wordpress maintenance for real estate; a legal practice’s under wordpress maintenance for law firms. The full set of sectors is on WordPress audience segments.

Plans that include this

  • Starter$39/monthor $390 a year — two months freeBlogs, portfolios and brochure sites
    • UpdatesMonthly
    • BackupsWeekly, 30-day retention
    • Uptime5-minute checks
    • Malware removalNot included
    See what is includedKept current and backed up.
  • Business$149/monthor $1490 a year — two months freeStores, membership sites, anywhere downtime costs money
    • UpdatesWeekly, tested on staging first
    • BackupsDaily, 90-day, multi-location
    • Uptime1-minute + 2-hour restore
    • Malware removalIncluded
    See what is includedEverything, including unlimited hack recovery.

How the work runs

  1. We map what the store earns fromEvery gateway, every shipping method, every tax rule, every coupon type. That list is the test set; the checkout is submitted through each of them on the staging copy before an update is promoted.
  2. Updates are staged and the checkout is walkedAdd to cart, apply coupon, calculate shipping, pay with a test card, receive the order email. Any step that fails holds the update back, and the held plugin is named in the report.
  3. Backups run daily and live off the hostOrders, customers and stock go to separate infrastructure, restorable by you in one click. A restore is rehearsed at onboarding rather than discovered at the worst moment.
  4. The site is prepared for peak before peakAhead of a known window we clear the database, check caching, resize the image library and hold non-security updates. A release that can wait does not land in the trading week.
  5. Monitoring watches the checkout, not just the homepageUptime checks hit the cart and the payment step every minute from several regions. A store whose front page answers while its checkout errors is down.

The service that covers this

WordPress store upkeep

Protect a WooCommerce store the way WordPress maintenance has to work on something that takes payment. Every batch of updates is tested by buying something on…

More in Industries

Questions people ask before calling

Do you test the checkout after every update?

Yes, on a staging copy, with a test card, through to the order confirmation email. On Business this runs after every plugin release; on Professional it runs on the weekly cycle.

What happens if a payment extension update breaks something?

The extension stays on its previous version and the store keeps trading. The held update is named in the monthly report with what it broke.

Can you handle PCI compliance?

The technical findings, yes: current gateway versions, no mixed content on the checkout, no abandoned plugins, hardened logins. The questionnaire and the policies remain the merchant's.

Will you hold updates during Black Friday?

Yes. Ahead of a known peak, non-security updates are deferred and monitoring frequency is raised. Security releases still go through staging and are applied.

Which plan do stores take?

Business, for checkout testing after every release and the two-hour restore. A smaller store on a weekly release cycle fits Professional.