With the release of WordPress 6.9, the block editor introduces a native Accordion block. This addition creates an overlap with the existing WooCommerce Accordion block, originally included to serve the needs of product details layouts and other expandable content areas.
The long-term goal is to encourage users and developers to migrate from the WooCommerce-specific accordion implementation to the new, standardized WordPress Core version. Doing so improves compatibility, reduces duplicate functionality, and ensures future consistency across themes and plugins.
However, early versions of WooCommerce running on WordPress 6.9 do not yet provide any guidance, UI cues, or upgrade prompts. As a result, users can continue inserting the WooCommerce Accordion block without realizing that a newer, more stable, and core-supported option is now available.
This guide explains the situation, the expected behavior, the migration goals, and practical recommendations for developers and site owners.
1. Background: Why the Migration Matters
Before WordPress 6.9, WooCommerce supplied its own Accordion block to support expandable sections—most notably in product templates such as the Product Details block.
Now that WordPress includes a native Accordion block in core, maintaining parallel implementations is counterproductive. Having two blocks:
-
complicates the editing experience
-
leads to user confusion
-
duplicates maintenance work
-
increases long-term technical debt
-
makes block libraries feel inconsistent
The goal is to transition users to the core block, while maintaining backward compatibility for already published content.
2. What Should Happen in WordPress 6.9+
The intended roadmap includes:
A. Hiding WooCommerce Accordion Block from the inserter
If the user is running WordPress 6.9 or later, the WooCommerce-specific block should no longer appear as an available option when adding new blocks.
B. Updating the Product Details block
Whenever WooCommerce inserts new accordions inside Product Details, it should automatically use the WordPress Core Accordion block, not the WooCommerce version.
C. Encouraging users to upgrade existing instances
The editing interface should notify users when a legacy WooCommerce Accordion is detected. Ideally, the editor would display:
-
a banner
-
a warning
-
a conversion prompt
-
or automatic block replacement
—similar to how WooCommerce handles the migration of the Product Search block.
In short: the editing experience should guide users toward the modern block.
3. The Problem Today: Missing UI Guidance
At present, if you:
-
Add a WooCommerce Accordion block to a post, page, or template,
-
Open it in the WordPress 6.9 editor,
—you will not see any message, notice, or visual prompt suggesting that you switch to the core Accordion block.
Expected behavior:
A clear UI banner or notice should appear, indicating:
-
that the WooCommerce version is deprecated,
-
that WordPress 6.9 provides a better alternative,
-
and offering a one-click upgrade or replacement action.
Because this prompt is not yet implemented, users may unknowingly continue using the older block.
4. How This Should Ideally Work (Conceptual UX Flow)
Although the final design is still being discussed, the ideal workflow would mirror existing patterns used by WooCommerce for other block migrations.
Step 1 — Detection
When the editor loads, WooCommerce checks:
-
The current WordPress version
-
Whether the content contains WooCommerce Accordion block instances
-
Whether the core Accordion block is available
If WP ≥ 6.9, the WooCommerce Accordion block is considered deprecated.
Step 2 — Replacement UI in the Editor
When a deprecated block is detected, it should be replaced with a placeholder banner in the editor (not on the frontend).
This banner might:
-
Inform users that the WooCommerce Accordion block is outdated
-
Recommend switching to the WordPress Accordion
-
Provide a button to convert existing content automatically
-
Offer a link to documentation or additional context
Step 3 — Automatic Conversion (Optional but recommended)
The conversion would ideally:
-
Replace the block type
-
Map each accordion panel to the core block structure
-
Preserve content
-
Maintain styling as closely as possible
This ensures a smooth user experience with no manual recreation required.
Step 4 — Prevent New Insertions
The WooCommerce Accordion block should not appear in the block inserter in WordPress 6.9+. This prevents new instances from being created and ensures all new content uses the core implementation.
Step 5 — Maintain Backward Compatibility
Sites with existing WooCommerce Accordion content should continue displaying correctly on the frontend even if users do not convert.
5. How Developers and Store Owners Can Handle the Issue Today
Even before WooCommerce ships official UI guidance, there are several steps you can take.
A. Avoid inserting the WooCommerce Accordion block on new WordPress 6.9+ sites
When working with new designs or templates:
-
Prefer the WordPress Core Accordion block
-
Avoid adding the WooCommerce version unless absolutely necessary
This limits future migration work.
B. Begin manually replacing WooCommerce Accordions in editable content
On pages, posts, and templates, manually swap out legacy WooCommerce accordions with the core equivalents:
-
Add the WordPress Accordion block
-
Copy panel titles and content
-
Remove the old block
This ensures future-proof layouts.
C. Update custom block patterns or templates
If your theme or plugin contains patterns that reference the WooCommerce Accordion:
-
Update them to use the WordPress version instead
-
Test the output in both the editor and frontend
This avoids pushing deprecated blocks into your content.
D. Disable the WooCommerce Accordion block in WordPress 6.9+
Developers can unregister the block conditionally using a simple filter or plugin logic. This prevents editors from accidentally inserting deprecated blocks.
E. Prepare for automatic migrations
When WooCommerce eventually implements the upgrade banner or conversion UI, your existing content will be ready for a straightforward transition.
6. Why Migration Should Happen Sooner Rather than Later
The WooCommerce Accordion block is not broken, but continuing to rely on it introduces long-term risks:
-
Styling and functionality may diverge from WordPress standards
-
Future WooCommerce releases may fully deprecate it
-
Block patterns using the old version may become difficult to maintain
-
Theme developers may need to support two variations indefinitely
-
Users may become confused if both blocks coexist
Moving toward the core block simplifies your environment and makes your content more portable across themes and plugins.
7. Summary
WordPress 6.9 introduces a built-in Accordion block, making the WooCommerce version obsolete for most use cases. WooCommerce intends to encourage users to migrate, but the current UI still lacks the necessary upgrade prompts.
What should eventually happen:
-
The WooCommerce Accordion block disappears from the inserter
-
Existing blocks display a migration banner in the editor
-
The Product Details block uses the WordPress Accordion for new instances
-
A simple conversion flow allows users to update existing content
What you can do now:
-
Favor the WordPress Accordion block in all new content
-
Update templates and patterns
-
Consider unregistering the WooCommerce version in WordPress 6.9+
-
Begin manual migrations where feasible
-
Prepare for WooCommerce’s upcoming user interface updates
As the block editor ecosystem matures, consolidating duplicated blocks—such as accordions—helps maintain a cleaner, more predictable, and more future-proof editing experience.
