WooCommerce Plugin Stack Auditor
Checks the plugins you're using against your WooCommerce version, and flags the ones a core feature has already replaced.
Your details
Your plugin audit
WooCommerce plugin stack audit (your version: 10.3)
[Likely droppable] Product brands
Core has covered this since WooCommerce 9.4. Brands moved into core in WooCommerce 9.4 (Oct 2024) and have been on by default since 9.6 (Jan 2025). A dedicated brands plugin is very likely redundant now.
[Likely droppable] Cost of Goods Sold / product cost & profit tracking
Core has covered this since WooCommerce 10.3. Cost of Goods Sold became a stable core feature in WooCommerce 10.3 (Oct 2025), after a beta period. Check Settings → Products → General for the COGS options.
[Likely droppable] Order attribution / UTM & traffic source tracking
Core has covered this since WooCommerce 8.5. Order Attribution has been a core feature since WooCommerce 8.5 (Nov 2023), on by default, using a last-click model. See the Attribution column in Orders, or Analytics → Orders.
[Likely droppable] Email preview / customizer
Core has covered this since WooCommerce 9.8. A built-in email preview (and modernized email templates) shipped in WooCommerce 9.8 (Apr 2025): WooCommerce → Settings → Emails now has a Preview column.
[Keep your plugin] Color/image variation swatches
Core only picks this up from WooCommerce 10.9; you're on 10.3, so keep your plugin until you update, then re-check.
"Likely droppable" means core WooCommerce now covers that job, not that your specific plugin has no other features. Compare feature-for-feature before deactivating.
Deactivate one plugin at a time and check the storefront and checkout afterward, rather than removing several at once.
Also worth a look: the HPOS/checkout-block compatibility checker, since an old plugin you're keeping may itself be blocking a WooCommerce feature.
What moved into core, and when
| Feature | In core since | What it replaces |
|---|---|---|
| Product brands | WooCommerce 9.4 (on by default since 9.6) | A dedicated brands taxonomy plugin |
| Cost of Goods Sold / profit tracking | WooCommerce 10.3 (stable, after a beta) | A separate COGS or profit-margin plugin |
| Order attribution / UTM tracking | WooCommerce 8.5 | A separate attribution or traffic-source plugin |
| Email preview | WooCommerce 9.8 | A dedicated email-preview plugin |
| Color/image variation swatches | WooCommerce 10.9 (opt-in, block themes only) | A swatches plugin, on a block theme only |
Enter your WooCommerce version and toggle on whichever of these you currently use a separate plugin for. The tool compares your version against each feature's own "since" version and tells you which ones are very likely safe to drop.
Removing a plugin safely
- 01
Check the core equivalent actually covers what you need
"Droppable" means core now does that job, not that your plugin has zero other features. Compare feature-for-feature first.
- 02
Deactivate one plugin at a time
Rather than several at once, so any regression is easy to trace.
- 03
Check the storefront and checkout afterward
Especially anywhere the removed plugin added a shortcode, widget or block.
Pitfalls
- The color/image swatch feature only applies to the
wc-visualattribute type on a block theme; a classic theme still needs a plugin regardless of your WooCommerce version. - Data migration isn't automatic for every feature: check whether your existing plugin offers an export, or whether core WooCommerce reads its data directly, before deactivating.
- Update WooCommerce itself before relying on any of these version numbers; run
wp plugin listor check WooCommerce → Status if you're not sure of your exact version.
Questions people ask
Where do I find my WooCommerce version?
WooCommerce → Plugins in wp-admin, or the top of the report at WooCommerce → Status.
Will removing a plugin lose my existing data?
It depends on the plugin. Brands and Order Attribution data both generally carry over cleanly since core reads the same underlying taxonomy/meta most plugins already used. Check your specific plugin's own deactivation notes for COGS and swatches data before removing it.
Does this check HPOS compatibility too?
No, that's a separate concern. Use the HPOS/checkout-block compatibility checker for that.
I'm on an older WooCommerce version. Should I update just for these features?
It's a reasonable secondary reason to update, but update primarily for the security and performance fixes in each release; the feature parity is a bonus.
Related tools
Want this builtinto your store?
I'm Emmanuel, a Shopify and WooCommerce developer. If this tool pointed at something you'd rather have fixed for you (a faster store, cleaner product data, a migration, a custom feature), send me a note.
Emmanuel Asika
Shopify & WooCommerce developer, Dublin
I build and fix online stores: new builds, migrations, speed, SEO and the custom bits apps can't do.