WooCommerce
How often should a WooCommerce store back up?
There is no correct number. The interval between backups is the amount of order data you are prepared to lose, so the answer comes from your own store. One store we run backs up every two hours.
By itmarkerz Technologies. Updated 30 October 2026.
Work it out from your own orders
- Find your busiest hour from your order history, and count the orders in it.
- Multiply by the interval you are considering. That is the most orders a restore could lose.
- Ask what it would take to rebuild those orders from payment records and emails, and who would do it.
- If that sounds acceptable, the interval is fine. If not, shorten it, and repeat.
Don’t forget what else changes between backups: new customer accounts, refunds, stock levels, and edits by your staff.
What a backup has to contain
WooCommerce’s backup guide describes two locations: the wp-content folder and the database. Orders live in the database, so a files-only backup misses them, and the guide notes that the standard WordPress export leaves out order and product tables. A plugin that backs up only some tables deserves a close look too, especially if your store uses High-Performance Order Storage, where orders sit in their own tables.
Schedules we run
| Where | Schedule | Suits |
|---|---|---|
| Premium plan (USD 89/month) | Daily database and offsite backups | Daily updates and backups, with a small-edits allowance |
| Enterprise plan (USD 159/month) | Set to suit your site | For demanding sites |
| High-volume Belgian store | Every two hours to S3-compatible storage, with tested restores | A store that must stay up, inside a wider maintenance engagement |
Two hours isn’t a recommendation for every store. It is the schedule on that one, a store that must stay up. Prices are invoiced in the customer's local currency.
Store the copy somewhere else
A backup on the same server fails along with the server, and may be reachable by whatever compromised the site. Keep a copy in separate storage, under separate credentials. S3-compatible object storage works well for this, and it’s what we use on the store above. Decide how long copies are kept too, because a problem such as malware can go unnoticed for days, and then all your recent copies contain it.
Test the restore
Until you have restored one, you only have a file. Try this on a separate environment, never over the live store:
- Restore files and database from your latest copy, and time it.
- Log in, open recent orders, and check that the newest one is as recent as you expect.
- Place a test order, with payments in test mode and outgoing email turned off.
- Write down the steps and the time, so someone else could do it under pressure.
- Repeat on a schedule, and after any large change to the store.
Plan what happens to orders after a restore
Going back to a copy means losing whatever came after it. Before you restore, export any newer orders you can reach, and compare with your payment provider’s records afterwards. If orders also travel to an ERP, it may hold orders the restored store no longer knows about, and numbering can collide. Our order sync guide covers reconciling the two. And take a fresh backup before any update, as WooCommerce advises.
See what maintenance should include for the wider picture, or our WooCommerce maintenance plans.
The store on two-hourly backups
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
Is a daily backup enough?
For a store with few orders, it often is. Work out what a day's lost orders would mean for you. If you could rebuild them from payment and email records without much pain, daily may be fine. If not, shorten the interval.
Isn't my host's backup enough?
It may be, but check how often it runs, how long copies are kept, whether you can restore on your own, and whether a copy is held away from the host. A backup on the same account as the site can be lost along with it.
How long does a restore take?
It depends on the size of the store and where the copy is held, so we won't give you a general figure. The only reliable number is the one you get from timing a restore of your own store.
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.
- What WooCommerce maintenance should include for a store that can’t go downThe questions to ask any provider, with our own plans compared.
Not sure your backups would work?
Tell us how the store is backed up today, and whether anyone has tried a restore.
We reply within one business day (IST).