A WooCommerce site contains not only content, but also customer accounts, orders, payment integrations and often links with logistics or accounting. That makes continuity and security extra important.
Limit access
Give staff only the rights they need. Secure administrator accounts with strong unique passwords and two-factor authentication, and remove old accounts straight away.
Update in a controlled way
WooCommerce, payment plugins and themes change regularly. Test updates on staging and then run through critical processes: product page, cart, checkout, payment method, email and order status.
Protect and monitor the environment
Combine an up-to-date PHP and WordPress stack with firewall rules, malware checks, login protection and monitoring. Do not only watch for downtime; errors in checkout or background tasks can also cost revenue while the homepage is still reachable.
Match backups to transactions
For an active web shop, one daily database backup can be too coarse. Decide the desired recovery time and the maximum acceptable data-loss period based on order volume.
Keep integrations in view
Payment providers, APIs and webhooks are part of the chain. Document which integrations are critical and test them after relevant changes.
Payments and customer data
In a web shop with a payment service such as Mollie, payment details are not processed on your own server. That reduces the risk, but customer data such as names, addresses and orders is stored in your database. That data falls under the GDPR. Limit who can access it in the admin area, and remove old staff accounts.
Fake orders and card testing
Web shops are sometimes abused to test stolen payment cards with small orders. You recognise it by many failed payments in a short time. A CAPTCHA at checkout, a limit on the number of attempts and the payment service’s fraud protection help prevent this.
Extra attention for
- Administrator accounts with two-step verification
- Updates of payment and shipping plugins, which are often vulnerable
- Frequent database backups, because orders change every day
- A log of who changes what in prices and orders
Frequently asked questions
Does my web shop need to be PCI-DSS compliant?
With an external payment service that processes the payment details itself, most of those requirements lie with the payment service. Your web shop must still be set up securely, with HTTPS and up-to-date software.
How do I recognise a hacked web shop?
Signs include unknown administrators, changed payment settings, scripts on the checkout page you do not recognise, or customers reporting that they end up somewhere else after paying.
How often should a web shop be backed up?
At least daily, and more often for a busy web shop. That is why we make more frequent database backups with Managed Commerce.
Rather not manage this yourself?
We combine managed hosting, WordPress maintenance and support in one service.