1. Home
  2. Blog
  3. Backup and Restore

Back Up a WooCommerce Store Often Enough to Keep Every Order

Backup and Restore

October 15, 2026

The worst restore on a WooCommerce store is the one that works. The site comes back exactly as it was at the time of the backup, and every order placed since then is gone. A blog can lose a day of edits and recover. A store that loses a day of orders has customers who paid and now have no record of buying anything.

Snapshotify works with WooCommerce out of the box. The harder question is how often to back up. This post covers backup frequency, retention and restore habits for stores specifically.

Where your store actually lives

The Snapshotify FAQ answers the WooCommerce question in two sentences. Yes, it works with WooCommerce. Orders, products and customers are in the database, which is in the backup. Then comes the important part: take backups often enough that the gap does not cost you orders.

The gap is the time between your last backup and the moment something goes wrong. Everything in that window, including orders, new customers, stock changes and refunds, exists only on the live site. A restore replaces the live site, so anything in the gap is lost.

Pick the frequency by the work you can lose

Snapshotify Pro schedules backups daily, weekly or monthly. The docs tell you to choose by how much work you would be willing to lose, and they use a store as the example: a store taking orders every day should back up daily.

StoreSensible schedule
Orders most daysDaily
A few orders a weekDaily still costs little, weekly at most
Catalogue site, rare ordersWeekly

Scheduled backups run in the background with the browser closed. On Pro they finish within the cron request, which the docs say makes them reliable on hosts where the site cannot make requests to itself.

Keep the database in every backup

Snapshotify lets you exclude WordPress Core, Media Library, Plugins, Themes and Database, separately for scheduled and manual backups. For a store, the database is the one thing you never exclude. The docs say excluding it is almost never right, because it holds your posts, settings, users and orders.

If full daily backups are too large, trim elsewhere. Core is a reasonable first exclusion, because it can be downloaded again and the manifest records the version. Media is the usual second, but only if your product images are backed up somewhere else. Then take a full backup by hand from time to time. Manual backups have their own exclusions in the create dialog, so a lean daily schedule and a full manual backup can exist side by side.

Store copies off the server

A backup on the same server fails along with the server. Snapshotify Pro sends scheduled backups to Google Drive, Dropbox or OneDrive, to more than one at a time if you like, and retries uploads that fail. We covered the setup in scheduling automatic WordPress backups to cloud storage.

Retention so daily backups do not fill the disk

Daily backups add up quickly. With Auto-Remove Backups on, Snapshotify keeps the newest few (Keep Latest Backups, default 3) and deletes older automatic runs. The docs explain why this matters: without retention, scheduled backups pile up until the disk fills, and a full disk breaks the site you were protecting. Manual backups and uploaded archives are never pruned automatically, so a backup named “Before Black Friday” stays until you delete it.

Restoring a store without losing new orders

When you need to restore, the gap is still the risk. A few habits help:

  1. Back up the current state first. The docs warn that a restore cannot be undone. Even a broken site holds orders placed since your last backup.
  2. Note the time of the backup you are restoring. Export or write down any orders placed after it, so you can re-enter or reconcile them.
  3. Pick a quiet moment. The site is in maintenance mode while the restore runs, so customers see a maintenance page instead of a half-restored shop.
  4. Clear your cache afterwards. Caches are excluded from backups because they regenerate. The FAQ says to clear yours after a restore so old pages are not served.

Before a big change, take one more

A plugin update, a payment gateway change, a sale: take a fresh backup before any of them. A database-only backup takes a fraction of the time of a full one. The Snapshotify product page shows a full backup at 1.8 GB taking 14 minutes, against 62 MB and 38 seconds for the database alone. That is short enough to do every time.

Common mistakes

Weekly backups on a store that takes orders daily. That is up to a week of orders in the gap.

Excluding the database to save space. You keep the files and lose the store.

Keeping backups only on the server. If the server goes, so do they.

Restoring without checking for newer orders. The restore works and the orders disappear.

Scheduling, retention and cloud destinations are in Snapshotify Pro, under one licence that covers every DaftPlug plugin; see pricing.