WooCommerce in 2025: Building a platform for the future

When WooCommerce launched in 2011, we set out with a clear purpose: to democratize commerce on WordPress, making the power of ecommerce accessible to everyone. Today, WooCommerce is the engine behind 35% of all online stores and 9.2% of the entire internet, and the clear choice when adding commerce functionality to any WordPress website. The growth we’ve seen — from a modest plugin to a platform powering millions of diverse, high-scale businesses worldwide — is both humbling and inspiring.

Along the way we’ve learned a thing or two about what modern commerce demands. Now, as we look to the future, we’re committed to evolving WooCommerce to meet the increasingly sophisticated needs of merchants and developers, delivering a platform that’s robust, flexible, and built to scale.

a decorative collage of information from this post about the growth and future of Woo.

Evolving ecommerce needs

WooCommerce’s evolution is a community-driven journey — one where developer feedback continuously shapes how we meet the increasing needs of modern merchants. Stores built on WooCommerce today handle complex operations, serve global audiences, and process hundreds of thousands of orders across thousands of products.

Universal Yums is a great example. They’ve shipped over 10 million subscription snack boxes through their WooCommerce store. Experiences like these highlight the real-world requirements of large-scale merchants and drive us to build a more capable, future-proof platform.

As we head into 2025, our platform priorities and roadmap are taking shape with the ultimate goal of being the most popular commerce platform for builder-supported stores operating at scale. 

A strong foundation for high-volume stores

We’re focusing on three key areas that merchants and developers have consistently told us matter most:

  1. Performance at scale — Our new High-Performance Order Storage (HPOS) system demonstrates what’s possible when we rethink core functionality. Early tests show 5x faster order processing and 1.5x faster checkouts. For developers, this shift means less time spent optimizing custom database solutions, with WooCommerce handling larger data volumes out of the box. HPOS also opens up new possibilities for integrations by providing a more streamlined and scalable data structure.
  2. Modern commerce experiences — The new block-based checkout isn’t just a new interface—it’s a complete rethinking of the purchase experience. We’re leaning into WordPress’ efforts to modernize, and taking the opportunity to make the WooCommerce experience truly commerce-centric.
  3. Essential commerce features — We’re bringing critical commerce capabilities directly into core. The recent addition of built-in brand management functionality shows our approach to providing powerful features out of the box. These updates are designed to streamline setup and simplify customization. By moving essential functionality—like brand management—into core, we’re reducing the need for custom solutions, speeding up launch times, and freeing up developers to work on more unique store experiences.

Building essential commerce features into our core platform

Over recent years, we’ve heard consistent feedback from merchants and developers on the complexity of managing numerous extensions — each with its own updates, dependencies, and potential conflicts. Balancing flexibility with ease of use has become a growing challenge as WooCommerce merchants expect more foundational commerce features directly within the core platform, not in separate add-ons. 

We’re now expanding WooCommerce core to include essential features that previously required extensions, ultimately creating a more integrated, user-friendly foundation. You may have heard us refer to this as “more in core”. This shift aligns WooCommerce more closely with industry expectations and simplifies the experience for everyone involved. It allows developers to focus on building custom experiences rather than reimplementing and managing common functionality, and it gives merchants a fully-integrated set of functionality out of the box. Here’s how we’re approaching this shift:

  • Addressing customer pain points: Many merchants feel overwhelmed by extension management. By bringing high-demand features like brand management, unique product identifiers, and more robust inventory tools into core, we reduce the need for add-ons, which simplifies setup and ongoing maintenance.
  • Prioritizing performance and interoperability: Adding additional functionality into core requires us to deepen our focus on interoperability and stability, reducing the risk of conflicts and delivering a smoother experience.
  • Streamlining decision-making: As WooCommerce moves towards a more integrated experience, the initial setup process becomes less overwhelming. Merchants can get started with essential features available out of the box, while developers enjoy a cohesive framework that grows with the needs of high-volume stores.

This approach also includes plans for making the experience of our payment, shipping, and tax services more native to WooCommerce core. While alternative solutions will remain available, this default integration ensures merchants have access to robust, reliable tools immediately upon installation. Our “more in core” approach means carefully choosing which features add value and are required for the majority of modern ecommerce stores. Not all functionality makes sense for core, and we will retain a focus on quality and coherence, ensuring that what we bring in complements and supports the rest of the platform naturally.

We’re already making significant progress on this initiative. Brands functionality has been successfully added to core, and we’re actively developing an MVP for Cost of Goods Sold (COGS), with designs finalized and implementation in progress. Looking ahead to next year, we’ll begin development on Back in Stock Notifications, which is currently undergoing performance optimization work. We’re also excited about Shipment Tracking – the design phase is nearly complete, and we’ll share more details about this feature in an upcoming dev blog post before development begins in 2025. We’ll continue to shape our roadmap and keep you updated as we thoughtfully expand WooCommerce core’s capabilities.

Investing in a shared vision

Driving this evolution forward is a team-wide effort, and our recent appointment of James Kemp as Core Product Manager reflects our deepening investment in core development. James is now helping shape WooCommerce’s core vision, working closely with our teams to make WooCommerce a powerful, user-friendly platform for everyone. From streamlining the mobile app for shop managers to delivering efficient tools for developers, this expanded role helps us stay aligned with a clear vision for WooCommerce’s future.

Join us in shaping the future

With dedicated leadership, and insights from our community, we’re focused on making WooCommerce the go-to platform for builder-supported stores at scale. Every step of the way, feedback from developers like you has shaped these decisions. To influence which capabilities are added to WooCommerce core, join the discussion on GitHub and share your insights with us. Together, let’s shape the future of WooCommerce.


23 responses to “WooCommerce in 2025: Building a platform for the future”

  1. pacmanito Avatar

    Great news indeed! Default tracking functionality is a MUST in 2024. Without it integrating WC with other services via Zapier, Make itc. is a pain.

    1. jameskemp Avatar

      What kind of tracking – event tracking? shipment tracking?

      1. pacmanito Avatar
        pacmanito

        Shipment tracking. Currently there are numerous plugins providing such functionality and thus numerous ways of tracking data storage. Therefore there’s no standard way of retrieving it resulting in a need for custom code instead of out of the box solution. I suppose for the very reason Zapier and Make do not have standard actions for WC tracking – e.g. https://community.zapier.com/how-do-i-3/how-to-setup-a-zap-to-automatically-update-shipping-data-in-woocommerce-12347

  2. Thanks this seems logical. Would suggest addressing things that touch across various parts of the platform, like multi-currency or improved discounts / coupons.

    Both are a massive pain to implement on stores that are extended with other plugins.

    Also interested to know if you’d be implementing these as modules that can be enabled so simpler stores aren’t overwhelmed with settings that are irrelevant?

    1. Shani Banerjee Avatar
      Shani Banerjee

      Hey Ian,

      I am certain some features will be flagged to enable or disable for your store’s needs. Ultimately we want to make sure performance is still a focal point and we certainly understand not every store will require such robust tools. Ultimately we are trying to strike the balance between what we can provide out of the box to improve overall performance so plugin and extension additions can be truly additive.

  3. In the new product editor please add bulk editing variants on barcode and sku.

    1. Brent MacKinnon Avatar
      Brent MacKinnon

      Thanks for the feedback Frank!

  4. Hello,
    – you don’t say much about the new product editor !
    do you plan to make it the default one soon, and finalize the blockification of templates / filters / blocks.
    For now, we are still in a in a “inbetween status”, making it hard to move more definitively to FSE.
    the sooner is the better 🙂
    – what about the HPPS (High Performance Product Storage) ?

    1. Brent MacKinnon Avatar
      Brent MacKinnon

      Hey Marc. The latest developments re: the Product Editor are captured here: https://developer.woocommerce.com/2024/11/06/whats-next-in-the-product-editor/.

      We’ve decided to pause on the current iteration of the product editor, so we can develop a new version that will better integrate with WordPress and address feedback from the previous version.

      what about the HPPS (High Performance Product Storage

      Beau commented on this recently on twitter, where he said: “We’re looking for additional tweaks and improvements to make on top of HPOS, yep. We’re also exploring some indexing, optimizing queries, and things like that. Right now we are not seeing the types of improvements from “HPPS” (Products) that would justify the size of the project.”

      https://x.com/beaulebens/status/1867355521487077824

    2. Marco Lucio Giannotta Avatar
      Marco Lucio Giannotta

      finalize the blockification of templates / filters / blocks. For now, we are still in a in a “inbetween status”, making it hard to move more definitively to FSE.

      Great to hear some love for FSE! And, yes! We’re working very hard on that side of Woo. Some of the things which are happening:

      · The new Product Collection block became the new default
      · We are incrementally improving existing blocks, for example: Stepper Layout
      · Product Filters work in progress is going strong and is awesome. The new filters will be easier to use, more extensible, and an immense jump in performance. You can follow along on GitHub, and you can try a sneak peek by enabling the experimental-blocks setting if you are so inclined.
      · We are working on blockifying further all the templates. Currently hard at work on creating a more modular experience for the “Add to Cart Form”. Read more here and follow along with the technical improvements here.

      We really have an exciting new year ahead for FSE!

  5. Tien Dung Dao Avatar
    Tien Dung Dao

    After so many years, Woo still hasn’t had any breakthroughs. Recently, the only thing that seems better is to separate the table to store orders.

    1. Marco Lucio Giannotta Avatar
      Marco Lucio Giannotta

      Of course, from the inside, things feel different: I have seen Woo grow so much in the recent years that I’m excited to see what’s coming.

      What are some “breakthroughs” that you would expect?

      1. Tien Dung Dao Avatar
        Tien Dung Dao

        In addition to security, performance needs to come first, for example separating the database product table instead of just orders as currently.

        1. Agree – would love to see more separation of the WordPress tables.

          HPPS would be really welcome to me as I do a lot of scripted product updates as well.

          Having products in their own table would most like simply those automation beside the obvious performance benefits it could deliver when you have a bit more products in your shop.

  6. Brands and GTIN were great integrations.
    Google, facebook and all other 3rd party shareholders need them and also MPN.
    Manufaturer Product number.
    https://support.google.com/merchants/answer/6324482?hl=en

    If you can add MPN in to core, and allow us to show these 3 under product details, then we can stop using attributes for brand, GTIN and MPN.

    Otherwise, we still have to use attributes even brand and GTIN are in the core.

  7. Hi, another idea to put in the list of “more in core”: Sequential order ID.
    It’s always had to explain to clients that woocommerce is not offering this out of the box. And Woo has this “offical” premium plugin, while there are plenty of free plugins in the repo.
    So, i guess it would be awesome to see this is core as an optinal setting.

    1. It would indeed make clients (and accountants) happy if this was a build in feature. I can imaging that with a dedicated orders table this is only a ‘small’ thing to implement.

    2. Greg Sevastos Avatar
      Greg Sevastos

      This is definitely needed in core!

  8. pacmanito Avatar
    pacmanito

    What about order statuses revamp announced in summer?
    This is a good idea as currently many workflows are mixed into one.
    Orders should have separate statuses for payment and fulfillment.

  9. Hello,

    Will the legacy orders post table method be deprecated in favor of HPOS and no longer supported? If so, when?

    Thanks!

  10. Making Woocommerce even better suitable for a wider variaty of use cases… Attribute Stock (Shared Stock & Variable Quantities).

    Then it would be able to have the size/volume as a variant (via a ‘stock multiplier’) for any bulk stock items.

    In my opinion this should be something out of the box rather than a plugin (which I actually use for it at the moment).

  11. Martin McShane Avatar
    Martin McShane

    It’s disappointing to see that many standard main features of Shopify are still lacking in the core of Woo. For example, POS and multi-location stock control, importing and exporting of customers and orders.

    This article is very much buzz word salad, as while there is some progressive changes to core, in reality, Woos development is still lacking and slower than Shopify and prestashop.

Leave a Reply

Your email address will not be published. Required fields are marked *


Keep yourself in the loop!

This field is hidden when viewing the form
This field is hidden when viewing the form
This field is hidden when viewing the form