Your store takes orders at 2 am. Someone should be watching it. Including stores someone else built.
Updates tested on a copy first, the store and payments watched, stock and feeds checked, and campaign season planned. Every month, by the engineers who know your store.
Care from €49 a month · cancel with 30 days’ notice
Store checked every five minutes
Updates tested on a copy first
Every update is checked on a copy of your store first, cart and checkout included.
No more skipped updates
50+
Live WordPress and WooCommerce sites we have run
2019
Running Alice & Grace’s WooCommerce store since
Daily
Off-site backups, with restores we have tested
2018
Building and running live software since
What we usually hear
What store owners usually tell us when they hand over, and what we do first
“Plugin updates have been skipped for months.”
Overdue updates go to a copy of the store first. We check cart and checkout, then they go live.
Seen in: E-Commerce & Retail
“The developer is gone, and so are some logins.”
We recover hosting, domain, licences and code, and move everything onto accounts in your name.
Seen in: E-Commerce & Retail
“Product feeds break and nobody notices.”
Feeds for ads and marketplaces are checked, so a broken feed is found before ad spend drops.
Seen in: E-Commerce & Retail
“The store gets slower every season.”
We find the plugins, slow database queries and hosting limits behind it, and fix them on a copy first.
Seen in: E-Commerce & Retail
“Campaign week is when things break.”
Changes land weeks before, checkout is tested under load and nothing changes during the campaign.
Seen in: E-Commerce & Retail
What you get
Six things every month, done by engineers who know your store
Updates tested on a copy first
WordPress, WooCommerce, theme and plugin updates are applied to a copy of the store (staging) and checked, cart and checkout included, before they go live.
The store and payments watched
The store is checked every five minutes. Where your payment provider allows it, a daily check matches payments against orders, so a lost order is found the same day.
Stock and product feeds checked
Stock syncs with marketplaces and the feeds your ads run on are checked, so oversells and broken feeds are caught early.
Campaign season planned
Updates land weeks before your campaigns, cart and checkout are tested under load, and nothing changes during the campaign.
Backups you can restore
Daily backups of the store and its orders, kept on another server. We test the restores, so a bad update costs hours, not a day of orders.
Small changes every month
Small changes such as prices, a banner or a new photo, done by the engineers who already know the store.
Who it is for
For stores where downtime costs orders
A good fit
Your store brings in real revenue.
An hour of downtime or a broken checkout costs orders, so it needs engineers watching it, not a plugin that updates itself.
- Downtime and a broken checkout cost real orders.
- You want named engineers who know the store, not a ticket queue.
- You want updates, checkout and stock looked after all year.
WooCommerce · Marketplaces · Payments
Not a fit yet
A few products that rarely sell?
A low-cost plugin-update service will do, and we will say so.
Come back when the store starts earning.
Checkout already losing orders?
Some stores need fixing before they can be looked after.
Start with the checkout and payment review.How a handover runs
Access and a backup first, then the monthly routine
-
Step 01
Recover access and back up
Before anything changes, we get the logins in order and save a full copy of the store and its database somewhere safe.
-
Step 02
Review the store
Plugins, theme, custom code, payments, stock syncs, feeds and hosting, written up: what is broken, fragile and fine.
-
Step 03
Stabilise before the next campaign
Overdue updates tested on a copy, checkout and payment gaps closed, and speed problems fixed.
-
Step 04
Keep it right every month
Tested updates, checkout and payment checks, backups and small changes, with the same engineers every month.
In production
Stores we build and run
FAQ
