🛒 Orders & Stock ⏱ Hourly Database Backups 🧪 Staging Clone 🔒 Immutable (WORM) 🛒 Orders & Stock ⏱ Hourly Database Backups 🧪 Staging Clone 🔒 Immutable (WORM)
WooCommerce Backup

Back Up Your WooCommerce Site Automatically
Files · Database · Email — One Module

In a store, every hour between two backups is an hour of orders you could lose. Yedekalma lets you give each component its own schedule: back up product images daily and the order database hourly. Backups go straight to your own cloud storage.

No credit card required · 14-day free trial

Specific to WooCommerce

What Do You Actually Lose on a WooCommerce Site?

Before choosing a backup plan you need to know where each kind of data lives.

🛒

Orders

Orders, payment status and customer addresses are entirely in the database. A file backup will not bring them back.

📦

Products and stock

Product definitions and stock levels are in the database; their images are on the filesystem. You need both.

👤

Customer accounts

Memberships, addresses and order history are database-only — losing them resets the customer relationship.

🎟

Coupons and campaigns

Roll back coupon usage counters and the same coupon becomes redeemable again.

⚖️

Legal record keeping

Keeping order and invoice records is a legal obligation; losing them is a legal risk, not just a commercial one.

🦠

Payment page injection

Code injected into checkout can skim card data. Without a known-clean restore point it is hard to detect.

Setup

WooCommerce Backup in Four Steps

1️⃣

Download the module

Download the Yedekalma PHP Backup Module (.zip). Nothing is installed inside WooCommerce itself.

2️⃣

Upload to your web root

Unzip it and upload the yedekalma folder to your site root (public_html/yedekalma) via FTP.

3️⃣

Connect the API token

Open yoursite.com/yedekalma/ in a browser and paste the API token generated in your panel.

4️⃣

Create a schedule

Pick frequency, components and storage target. Backups run automatically and restore in one click.

Highlights

What You Get with WooCommerce Backup

🔐

We never see your passwords

The module runs on your own server. Your database and FTP credentials are never sent to our panel.

☁️

Straight to your own cloud

Backups go directly to Google Drive, Amazon S3 and S3-compatible services, Dropbox, OneDrive, Yandex.Disk — or a Receiver Module on your own server. They never pass through us.

Incremental transfers

Only changed files, changed tables and new emails are transferred. How it works.

↩️

One-click restore

Restore from the panel. When moving to a different server, connection settings are rewritten for you.

🦠

Malware scanning

File, database and email backups are scanned for malicious content.

🔒

Immutable copies

S3 Object Lock keeps a copy nothing can delete. Learn more.

Technical requirements for WooCommerce

The module needs PHP 7.0 or newer — virtually every WooCommerce installation qualifies. On the database side MySQL and MariaDB are supported: WooCommerce runs on MySQL, so no extra configuration is needed.

The module is installed as an independent folder in your web root. It does not touch WooCommerce core files and is not installed as a theme, plugin or extension — so WooCommerce updates never break your backups.

FAQ

WooCommerce Backup — Frequently Asked Questions

For a store taking orders, daily backups are usually not enough: everything between two backups is lost. A common setup is hourly for the database and daily for files, which brings the loss window down to one hour. Yedekalma lets you set a separate frequency per component so you can do exactly that.
Orders, customer records, stock levels and coupon definitions are all kept in the database, while product images live on the filesystem. This is why a file-only backup will not save your store — the database backup is the critical one.
Backups consume resources because they run on your own server, but compression is tuned for speed: media files are stored without recompression and the database is dumped with light compression. You can also schedule backups for your quietest hours.
Yes. Besides scheduled backups you can start a full manual backup at any time from the panel. This is recommended before a large campaign, a theme change or a plugin update.
A database restore replaces the current state of the store with the state in the backup, so orders that arrived afterwards are rolled back. Take a backup of the current state before restoring, and where possible test the restore on a staging copy first.

Protect Your WooCommerce Site Today

Try it free for 14 days. No credit card, and nothing is charged when the trial ends.

Create Free Account

See the four-step setup →