What’s next in the Product Editor

Last summer, we introduced a new product editing experience, meant to modernize the existing classic product editor (v1).

One of our top priorities for this work was to create a WordPress-native experience that feels like it belongs in WordPress. Initially, we experimented with core APIs, but after feedback and discussions with WordPress Core contributors, we agreed that the newer WordPress Data Forms and Data Views projects are a better fit for our use case.

As a result, WooCommerce is shifting focus to work on a new beta of the Product Editor Experience, v3. This new beta will incorporate feedback from the second beta, along with integrating more closely with the planned direction for the WordPress admin. 

What happens to the existing API?

We intend to maintain compatibility with public APIs for the current Product Editor beta throughout the transition to minimize disruption, though some adjustments may be required.

Clear, well-documented guidelines will be available before the Product Editor v3 release to ensure that developers can transition smoothly and take full advantage of the improvements in the Product Editor v3.

We heard your concerns 

The current beta API has received ample community feedback in GitHub Issues. The new approach we are taking in the Product Editor v3 will tackle many of those concerns, and ultimately deliver a better integration experience. 

Why we are making this change

One of the most important principles guiding our work on WooCommerce is that all users of WooCommerce are also users of WordPress. Commerce has unique needs and the best experience, for end user and developers alike, will be one that integrates with WordPress in a way that feels native but also accommodates those unique needs.

Background: Insights and alignment

With the Product Editor beta, we explored creating the experience with, what at the time were, the current WordPress core APIs available. We gained valuable feedback on what is working well and what wasn’t. 

At the same time, WordPress introduced new APIs, specifically WordPress Data Forms and Data Views, that aligned closely with our interface needs. As these APIs matured, we saw an opportunity to use them as a solid foundation for the next version of the Product Editor. By collaborating with WordPress Core contributors, we could help shape these APIs to meet WooCommerce’s needs more effectively.

This new iteration will utilize components like WordPress Data Forms and Data Views. However, it will also consider the transition from managing a product and its details and how it is rendered to shoppers. This shift allows WooCommerce to adopt a unified framework that benefits from WordPress’ native extensibility and stability.

Product Editor v3: A unified, WordPress-native approach

With this new iteration, we’re leveraging WordPress Data Forms, Data Views, and other native components to enhance compatibility with WordPress themes and plugins. The goals for Product Editor v3 are to:

• Create a Seamless Experience: Unifying the product form editor, product visual editor, and front end for a cohesive, and familiar interface for users and developers alike.
• Support Native Extensibility: By aligning with WordPress’ extensibility, the editor can better integrate with core plugins and themes. This approach enables WooCommerce to implement extensible, user-centric solutions that grow with the WordPress platform.
• Enable Flexible, Scalable Solutions: Our tight feedback loop with WordPress contributors ensures this editor remains adaptable as WordPress evolves.

Working in WordPress Core

Our engineering teams are currently contributing directly in WordPress Core to introduce features to the Data Views library that will be necessary to allow the Product Editor V3 to make use of Data Forms and Data Views components. 

As a part of that work, we are currently exploring how to integrate the following features into the experience:

• Use of WordPress Core DataForms/Fields Packages, which provides baked-in extensibility directly within the WordPress ecosystem.
• Custom Field Type Registration that allows developers to register custom field types that are consistent across all newer WordPress interfaces.
• Validation Schema and Parsers allowing for the possibility of unique field validation, meant to create a consistent validation across both client and server sides.

Timeline and Further Support

Our engineering teams are currently contributing upstream to WordPress Core, in order to prepare the path to launching a Product Editor v3 beta. That path includes creating documentation that provides clear guidance and migration support. 

It’s still very early to have a solid timeline, but we will continue to update you as we gain more clarity. 

Join the conversation and provide feedback

We welcome feedback from our community to make the Product Editor experience fit users’ needs. You can share your thoughts and questions in the official Slack channel: #woocommerce-product-editor-extensibility.

To join the WooCommerce Community Slack workspace, follow the instructions on this guide to joining the conversation. 

If you have specific issues you’d like to rise as we begin rolling out the experience, you can create GitHub issues using the issue label “focus: new product ux”. 

We look forward to hearing from you!