If you run a WooCommerce seed shop, you’ve probably lived this: you click “Update all” on a Tuesday morning, and by lunch the cart is broken, product pages are blank, or orders have stopped coming in. We’ve been there with our own stores more than once. It’s the main reason we changed how we handle updates for every site we look after.
Why seed shops are fragile
A typical seed shop isn’t a simple store. It usually runs a stack of plugins that all hook into the same checkout:
- Product filters for genetics, flowering time, feminized or regular, and breeder
- Age verification or location gates
- Alternative payment methods, because many card processors won’t work with cannabis-adjacent businesses
- Shipping and order tracking add-ons
- Email marketing, reviews, loyalty points and caching
Each plugin is maintained by a different developer on a different schedule. When WooCommerce itself changes, or one plugin updates ahead of the others, the pieces stop fitting together. Large catalogs make it worse: a store with thousands of strains puts real load on anything that touches every product.
Why “just don’t update” isn’t the answer
Skipping updates trades a broken checkout today for a hacked store later. Outdated plugins are the most common way small sites get compromised, and attackers scan for known vulnerabilities automatically. The fix isn’t fewer updates. It’s safer updates.
How we update stores now
- Back up first. A full site backup goes off-site before any theme, plugin or core update, on top of the host’s own backups.
- Update a clone, not the live store. We keep a staging copy of the site and apply updates there first.
- Test the money path. On the clone, we browse products, use the filters, add to cart, check out with a test order, and confirm the order emails go out.
- Read the changelogs. Major version jumps, especially for WooCommerce and payment plugins, get extra attention.
- Push to live during a quiet window. Never right before a drop or a sale.
- Watch afterward. We check the store and error logs after the update and keep the pre-update backup ready.
It takes a bit longer than clicking one button. It’s a lot faster than restoring a broken store in the middle of a release.
What to do if an update already broke your shop
- Note which plugins were updated and in what order.
- If you can reach wp-admin, deactivate the most recently updated plugin first and test again.
- If you can’t reach wp-admin, rename that plugin’s folder over SFTP to switch it off.
- If nothing works, restore the backup taken right before the update, then test the update on a copy before trying again.
Let us handle it
We build and maintain WooCommerce stores for seed, clone and hemp shops, and every update goes through the process above. If your store keeps breaking after updates, email us, or see how we approach website security.