WooCommerce
What WooCommerce maintenance should include for a store that can’t go down
Most plans list the same words: updates, backups, security. The difference is in the detail behind each one. Here are the questions we would ask of any provider, including us.
By itmarkerz Technologies. Updated 30 October 2026.
The checklist
| Area | Ask | A weak answer sounds like |
|---|---|---|
| Updates | How often are core, theme and plugins updated, and is a backup confirmed first? | “Updates are automatic.” |
| Backups | How often, where are they stored, and do they include the database? | “Your host does that.” |
| Restores | When was a restore last carried out, and who does it in an emergency? | “We have never needed to.” |
| Monitoring | What is watched, and who gets the alert? | “You’ll get an email.” |
| Security | Is malware scanning included, and is cleanup included or extra? | “We scan”, with nothing on cleanup. |
| Changes | How much small work is included, and how do you ask for it? | No stated allowance or channel. |
| Exit | What are the notice terms, and is there a setup fee? | A long minimum term you only find in the contract. |
Updates: the order matters on a store
WooCommerce’s own update guide advises having a current backup and testing on staging first. On a store, a plugin update can stop orders, and you might not know until a customer complains. So after an update, look at more than the home page: add to cart, check out, and check that the order email and any payment confirmation arrive.
Backups and restores are two different things
A backup only matters on the day you restore it, and a store’s database changes with each sale. WooCommerce treats the store as two locations, the wp-content folder and the database, and a backup needs both. We wrote a separate guide on how often a store should back up.
Monitoring should reflect how you make money
Uptime monitoring tells you the site responds. It doesn’t tell you that checkout is failing while the home page loads fine. Ask what is watched. Speed matters too, since a slow store can be a failing store before it is a stopped one. If orders travel to another system, somebody should check that as well, as our order sync guide explains.
Our plans, against that list
| Plan | Price | For | Includes |
|---|---|---|---|
| Premium | USD 89/month | Daily updates and backups, with a small-edits allowance |
|
| Enterprise | USD 159/month | For demanding sites |
|
No setup fee, no lock-in, cancel anytime. Unused edit minutes don't roll over. Prices are invoiced in the customer's local currency. Full details are on our WooCommerce maintenance page.
What it looks like on a store we run
The clearest example we can show is a high-volume Belgian beverage retailer. We have looked after it for three years: PHP moved from 7.4 to the current release, plugins and theme brought current, performance work, backups every two hours to S3-compatible storage with tested restores, uptime and speed monitoring, a standing change-request channel, and an order and customer sync with Microsoft Dynamics. That is a wider engagement than a standard plan, and it shows what maintenance can grow into when a store depends on it.
If your store is on an old PHP version, deal with that first. See moving a live store from PHP 7.4. For new features or a takeover, see WooCommerce development.
The store described above
Three years keeping a high-volume Belgian WooCommerce store up, fast and in sync with Microsoft Dynamics: PHP 7.4 to current, two-hourly backups to S3-compatible storage, monitoring, and every change request handled.
- Sector
- E-commerce & retail
- Region
- Belgium
- Stack
- WordPress, WooCommerce, Microsoft Dynamics
- Engagement
- Maintenance, three years and ongoing
Questions
What do your WooCommerce plans cost?
Premium USD 89/month or Enterprise USD 159/month, invoiced in the customer's local currency. No setup fee, no lock-in, cancel anytime. Unused edit minutes don't roll over.
Can maintenance prevent every failure?
No, and be wary of anyone who says so. An update can still cause a problem. Good maintenance makes that less likely, helps you find out quickly, and leaves a recent copy to go back to.
Is a store different from an ordinary WordPress site?
Yes. A brochure site changes when someone edits it. A store changes every time somebody buys, and its failures cost sales straight away. That affects how often you back up, what you test after an update and what you monitor.
More on WooCommerce
- WooCommerce to Microsoft Dynamics: field mapping and sync guideOrders, customers, products and invoices, field by field, with conflict rules.
- WooCommerce and Microsoft Dynamics: plugin, connector or custom build?A neutral comparison of the three ways to connect them.
- Business Central, Sales or Finance: how each changes a WooCommerce integrationDifferent APIs, limits and change notifications for each product.
- Syncing WooCommerce orders to Dynamics at high volumeQueues, duplicate protection, throttling and daily reconciliation.
- WordPress forms into Dynamics, without a plugin that almost fitsMapping, validation and retry for enquiries that must not go missing.
- Moving a live WooCommerce store from PHP 7.4 to currentThe order of work on a store that has to keep selling.
- How often should a WooCommerce store back up?Working out a schedule from your own orders, and testing the restore.
Want your store looked after?
Tell us what the store sells, which plugins it depends on and what worries you most.
We reply within one business day (IST).