{"id":20400,"date":"2026-11-02T12:26:03","date_gmt":"2026-11-02T11:26:03","guid":{"rendered":"https:\/\/stage.surver.nl\/kennisbank\/woocommerce-veilig-updaten\/"},"modified":"2026-11-03T12:15:09","modified_gmt":"2026-11-03T11:15:09","slug":"how-to-safely-update-woocommerce","status":"publish","type":"kennisbank","link":"https:\/\/stage.surver.nl\/en\/kennisbank\/woocommerce-veilig-updaten\/","title":{"rendered":"How to Update WooCommerce Without Breaking Your Checkout"},"content":{"rendered":"
\"How<\/figure>\n\n\n\n

There's a new version of WooCommerce waiting for you in your dashboard, and you're hesitant to click on it Update Now<\/strong> Click here. And rightly so, because this is the plugin through which your revenue flows. Always update WooCommerce first on a staging environment, check the checkout process, payment methods, and emails there, create a full backup, and then roll out the update live outside of peak hours. Place a test order immediately after going live. Below, you\u2019ll find the sequence I follow myself, what to test, and what to do if things do go wrong. The bigger picture is outlined in WooCommerce Maintenance and Management<\/a>.<\/p>\n\n\n\n

Why a WooCommerce update poses more risk than a regular plugin update<\/h2>\n\n\n\n

A WooCommerce update is riskier than a regular plugin update because it affects checkout, payment gateways, inventory, and emails all at once. If a slider plugin breaks, you\u2019ll end up with an ugly page. If WooCommerce breaks, no one can check out anymore, and you won\u2019t notice until the orders stop coming in. On top of that, many WooCommerce updates include a database update. A database update involves modifying the structure of your database so that it\u2019s compatible with the new version of the plugin. After such an update, you can\u2019t simply revert to the old version, because it no longer recognizes the new structure.<\/p>\n\n\n\n

The third risk lies in everything that builds on WooCommerce. Your theme, your payment plugin, and extensions for shipping, invoicing, or subscriptions are sometimes a few weeks behind a new WooCommerce version. The most common complaint I hear after an update isn\u2019t that WooCommerce itself is broken, but that one extension is causing issues. That\u2019s exactly why the order in which you work is so important.<\/p>\n\n\n\n

What to Check Before Updating<\/h2>\n\n\n\n

Before you update WooCommerce, check the changelog, the compatibility of your extensions, outdated templates, and the timing. In the changelog, you can see whether it\u2019s a major release or a maintenance release, and whether it includes a database update or a higher minimum PHP version. Next, I check the \u201cWC tested up to\u201d value for each extension and read the changelog for the payment plugin. If your new version isn\u2019t listed there yet, you know you\u2019re taking a risk.<\/p>\n\n\n\n

You can see outdated templates below WooCommerce > Status<\/strong>. These are copies of WooCommerce files in your theme, which may cause the checkout or shopping cart to display incorrectly after an update. Also, choose a quiet time when there are no ongoing promotions or campaigns, and avoid doing this right before a weekend or holiday. Around Black Friday, Sinterklaas, and December, I don\u2019t perform any functional updates on online stores at all\u2014you don\u2019t remodel the store during a sale. My own rule of thumb is not to install a major WooCommerce version on the day it\u2019s released, but to wait for the first maintenance release. By then, extensions will have had time to update. The exception is security updates. Test those on staging the same day and deploy them immediately, because outdated plugins are a favorite entry point for hackers. If something\u2019s already gone wrong, check WordPress hacked<\/a>. For the same reason, I put automatic updates<\/a> Not suitable for major WooCommerce releases.<\/p>\n\n\n\n

How to Safely Update WooCommerce in Eight Steps<\/h2>\n\n\n\n

A safe WooCommerce update is like a pit stop, where everything is ready and the car is stopped for as short a time as possible. This is the order I follow.<\/p>\n\n\n\n

    \n
  1. Make a fresh one staging environment<\/a> of your live online store.<\/li>\n\n
  2. Isolate the staging copy. Disable outgoing email, live payments, webhooks, and scheduled actions, and prevent search engines from indexing it. The copy contains customer data subject to the GDPR, so delete it after use.<\/li>\n\n
  3. Update the staging environment in this order: WordPress, WooCommerce, extensions and payment plugin, and finally the theme. If a critical extension does not yet support the new version, hold off on the entire update.<\/li>\n\n
  4. Run the database update when WooCommerce prompts you to do so, and wait until it's completely finished.<\/li>\n\n
  5. Test the ordering process using the checklist below.<\/li>\n\n
  6. Just before the live update, make a complete backup of the live online store, including files and the database.<\/li>\n\n
  7. Perform the same updates live, outside of peak hours.<\/li>\n\n
  8. Clear the cache in LiteSpeed Cache or your own caching plugin, and place a test order right away.<\/li>\n<\/ol>\n\n\n\n

    Note the difference between step 3 and step 7. You do not restore the staging copy to the live environment; instead, you repeat the update on the live store. While you were testing, orders likely came in, and those orders will be lost if you merge the staging database with the live store.<\/p>\n\n\n\n

    What to Test After the Update<\/h2>\n\n\n\n

    After a WooCommerce update, test the entire ordering process\u2014first on the staging environment and then again on the live site. I always walk through it as a customer, from the product page to the order confirmation, and then check the admin panel to make sure everything was processed correctly.<\/p>\n\n\n\n

    Component<\/th>What You're Checking<\/th><\/tr><\/thead>
    Product Page and Shopping Cart<\/td>Prices, variants, and a discount code<\/td><\/tr>
    Checkout<\/td>Fields, shipping costs, and sales tax<\/td><\/tr>
    Payment Methods<\/td>iDEAL and credit card via your payment provider's test mode (such as Mollie); place a small, real order in production mode and then reverse the transaction<\/td><\/tr>
    Order Confirmation and Emails<\/td>Does the email arrive, and is the content correct?<\/td><\/tr>
    Inventory<\/td>Will the inventory be written off?<\/td><\/tr>
    Links<\/td>You Payment, shipping, and accounting integrations<\/a><\/td><\/tr>
    Scheduled Actions and Notifications<\/td>Failed actions under WooCommerce > Status > Scheduled Actions<\/strong> and management notifications in the dashboard<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Finally, check the error log under WooCommerce > Status > Logs<\/strong>. You'll often see an error message from your payment plugin there before a customer emails you about it.<\/p>\n\n\n\n

    What if something goes wrong? Here's how to fix it<\/h2>\n\n\n\n

    If something goes wrong after the update, restore the backup from just before the update\u2014not just the plugin. After a database update, the old plugin version will no longer be compatible with your database, and attempting a standalone downgrade will often make the problem worse.<\/p>\n\n\n\n

      \n
    1. Set the online store to maintenance mode and pause your ads.<\/li>\n\n
    2. Export the orders that were received after the backup, and back up the current state. This data will not be automatically preserved when you restore the system.<\/li>\n\n
    3. Restore the backup from just before the update. For step-by-step instructions, see restore a backup<\/a>.<\/li>\n\n
    4. Clear the cache and try again.<\/li>\n<\/ol>\n\n\n\n

      For more detailed troubleshooting, read Site Down After an Update<\/a>. If you're having trouble, please contact our support team.<\/p>\n\n\n\n

      How it works at Surver with Managed WooCommerce Hosting<\/a>, is quite simple. You can create a staging environment by cloning your installation in Installatron, and you can restore the automatic backups yourself at no cost using JetBackup 5 in cPanel, where you can choose to restore either files or databases. You can create that extra backup right before the update yourself in Installatron, and restore it there as well. If you\u2019d rather not do all this yourself, we\u2019ll test and monitor it for you at WooCommerce maintenance<\/a> Set up your checkout, payment methods, and integrations such as Mollie, Sendcloud, and your accounting software, and let our firewall allow the webhooks from those services to pass through.<\/p>\n\n\n\n

      My final piece of advice is to make updating a regular monthly habit, rather than waiting until you have ten pending updates. Install security updates right away. See also Updating WordPress Safely<\/a> and WooCommerce Backup<\/a>. If you want to outsource updates for your entire site, check out WordPress maintenance<\/a>.<\/p>\n\n\n\n

      Frequently Asked Questions<\/h2>\n\n\n\n

      How long does a WooCommerce update take?<\/strong><\/p>\n\n\n\n

      The update itself usually takes a few minutes; testing takes the most time. Based on my experience, I estimate about an hour, including a test order. A database update can take longer when there are many orders and runs in the background via scheduled tasks.<\/p>\n\n\n\n

      What is the difference between a staging environment and a backup?<\/strong><\/p>\n\n\n\n

      A staging environment is a working copy of your online store that you can use for testing. A backup is a snapshot that you restore if something goes wrong. You need both of them to ensure a safe update. At Managed WordPress Hosting<\/a> Surver's WooCommerce hosting plans include daily automatic backups as standard.<\/p>\n\n\n\n

      Do orders get lost during updates?<\/strong><\/p>\n\n\n\n

      No, not if you run the update on the live environment again instead of migrating the staging database to the live environment. With Surver, you create the staging environment as a clone in Installatron and restore backups using JetBackup 5 in cPanel.<\/p>","protected":false},"excerpt":{"rendered":"

      In je dashboard staat een nieuwe versie van WooCommerce klaar en je durft niet goed op Nu bijwerken te klikken. Terecht, want dit is de plugin waar je omzet doorheen loopt. Update WooCommerce altijd eerst op een staging-omgeving, controleer daar checkout, betaalmethoden en e-mails, maak een volledige back-up en voer de update daarna live uit […]<\/p>\n","protected":false},"author":2,"featured_media":20483,"template":"","kennisbank_categorieen":[61],"class_list":["post-20400","kennisbank","type-kennisbank","status-publish","has-post-thumbnail","hentry","kennisbank_categorieen-woocommerce"],"acf":[],"_links":{"self":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank\/20400","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank"}],"about":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/types\/kennisbank"}],"author":[{"embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/users\/2"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/media\/20483"}],"wp:attachment":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/media?parent=20400"}],"wp:term":[{"taxonomy":"kennisbank_categorieen","embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank_categorieen?post=20400"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}