The original 2017 article was a list of extensions I used, among other things, while working on a client’s Scandinavian furniture store. At the time it made sense to show specific plugins and customizations. Today, the same list could send readers toward unmaintained code, an incompatible checkout, or a feature WooCommerce now handles differently.
That is why I no longer look for a bombastic number of extensions. I look for the smallest set that reliably handles the catalog, order, payment, shipping, stock, analytics, and after-sales care.
Start with the store map
Before opening the extension catalog, write down the main flow:
- How will the customer discover and compare a product?
- Which variants, prices, taxes, and stock data do you need?
- Which countries, currencies, payments, and shipping methods do you actually serve?
- What is transferred after an order to accounting, stock, CRM, and support?
- Which steps must work when an integration is unavailable?
Assign every plugin to one need and one owner. If you cannot say who will check it after an update, it has not been selected yet.
Check the core capabilities first
WooCommerce continually moves formerly optional features into its core. Before installing a plugin, review the current settings for products, taxes, shipping, accounts, privacy, and advanced features. The official documentation summarizes advanced WooCommerce settings, including cart and checkout pages, the REST API, webhooks, and features.
The same applies to WordPress. I describe the general foundation and cleanup in the article about the best WordPress plugins. A store does not need a second SEO plugin, a third cache, or a custom duplicate of a feature just because “WooCommerce” appears in its name.
Categories where an extension can make sense
Payments and shipping
Use an official or long-term maintained provider integration. Verify supported countries, currencies, refunds, webhooks, recurring payments, sandbox operation, and handling of unavailability. For shipping, check pickup points, dimensions, cash on delivery, labels, and returns on real orders.
Invoices, taxes, and accounting
The plugin must match your accounting process, not a generic screenshot. Test rounding, discounts, shipping, credit notes, multiple rates, cross-border sales, and repeated exports. An accountant or tax adviser should confirm legal and tax correctness.
Stock and ERP connections
Define the main source of truth. If the ERP controls stock, WooCommerce must not independently overwrite availability at the same time. The integration needs a queue or retry handling, logs, and alerts. A manual “synchronize” button is not an operations plan.
Search, filters, and variants
Deploy an extension according to catalog size and customers’ actual queries. A filter that adds hundreds of indexable URL combinations can damage both performance and SEO. Define canonical URLs, indexing, and behavior without JavaScript in advance.
Commerce features
Wishlists, bundles, subscriptions, reservations, personalized products, or B2B prices make sense when they fit the business model. Each changes orders, taxes, stock, and support. Do not buy them for the sake of having them.
Measurement
Analytics integrations must send consistent product identifiers, value, currency, and transaction status without duplication when the thank-you page is reloaded. Connect the measurement design with GA4 and Google Tag Manager. Handle consent and advertising platforms before deploying scripts, not after the first complaint.
Three current compatibility tests
HPOS
High-Performance Order Storage stores orders in dedicated tables. WooCommerce documents how to enable HPOS and check incompatible extensions. A plugin working with orders must explicitly declare compatibility, and you must verify it on staging.
Cart and Checkout blocks
The modern block cart and checkout use different integration points from the old shortcode templates. Extensions for payments, shipping, fields, upsells, or measurement must support the specific checkout you use. Do not assume compatibility merely because the product page works.
Current WordPress and WooCommerce
For extension authors, WooCommerce lists compatibility with current versions of WooCommerce and WordPress, the block cart and checkout, and HPOS among its basic requirements; see the official compatibility rules. Also check the supported PHP and database versions.
Safe selection
- Write down the requirement and acceptable outage.
- Check the author, update history, documentation, and support.
- Review permissions, stored data, external services, and the licensing model.
- Test installation on staging with a copy of typical data.
- Run a card and another payment, discount, shipping, refund, emails, and export through the flow.
- Measure catalog, product, cart, and checkout speed.
- Prepare rollback and data export before production deployment.
WooCommerce security recommendations emphasize regular updates, removing unmaintained or vulnerable plugins, staging, and backups. The full overview is in the official security best practices.
What I no longer repeat from the original article
- a sales list of paid plugins without knowing the specific operation,
- old PHP snippets tied to the WooCommerce interfaces of that time,
- an extension for every tiny text or field change,
- automatic recommendations for social or marketing features without measurement,
- tools whose maintenance and current compatibility cannot be verified.
Custom code can be the right choice for a small, stable change, but it needs version control, tests, documentation, and someone to update it when WooCommerce changes. Copying a random snippet from a discussion is not a cheaper plugin. It simply has no invoice yet.
Quarterly review
Review active and inactive extensions, available updates, security notices, licenses, owners, and compatibility. Then test the main purchase scenarios and performance on staging. Pay particular attention to extensions that affect prices, taxes, orders, payments, and exports.
Handle the speed of the entire store according to how to speed up a website. If you want to inventory the current plugins, remove overlaps, and prepare a safe migration plan, get in touch via contact.