WooCommerce in 2024 and beyond: Roadmap update

Image of Beau Lebens against Woo developer themed background

Welcome to a special edition post, brought to you by Beau Lebens, Head of Engineering for Woo.

Today, I’d like to share some insight into our plans for WooCommerce, Woo’s core product, over the course of the rest of the year and beyond.  

In this post, I’ll outline our priorities for the coming year, highlighting our commitment to invest in the core platform, as well as enhancing the developer experience, deepening our engagement with the developer community, and leveraging the open-source ethos to drive continuous improvement and innovation. 

Big things are in store for our developer community, including a revamped developer blog, improvements to documentation, and a developer-focused newsletter. We’ll also cover major updates to core WooCommerce, including REST API, extensibility, Blocks, accessibility, product editing, and store customization, as well as improvements to onboarding, analytics, and the checkout experience. 

Whether you’re a seasoned contributor to the project, a newcomer to the WooCommerce ecosystem, or simply passionate about software development or commerce, this post aims to bring you closer to our roadmap and invite you to join us in building a better WooCommerce together.

Open source at the root of our vision 

WordPress is the open-source software that powers over 43% of the internet (W3Techs). WooCommerce is built to be a deeply-integrated, native commerce solution for WordPress, giving us unparalleled reach and flexibility, as well as a vast ecosystem of users, developers, and solutions. For Woo, embracing open-source means fostering flexibility, configurability, and customization, allowing you to tailor nearly every facet of the merchant and shopper experience. From adjusting business models to selecting payment processors and shipping carriers, the open-source nature of WooCommerce supports extensive customization while providing high-quality default experiences. We build WooCommerce to feel like a natural extension of WordPress, leveraging everything it has to offer, bringing content and commerce together like no other solution.

I’ve been immersed professionally in web technology for about 25 years, and have seen firsthand the transformative power of open-source communities and software in shaping the digital world we all inhabit. In the coming year, we plan to deepen this commitment by incorporating more essential commerce functionality into our core offering.

Enhancing the developer experience 

Developers play a pivotal role in the Woo ecosystem, and in providing a great commerce experience to merchants. Through a series of targeted improvements, we aim to make it easier for you to create, innovate, and excel with WooCommerce.

Launching the developer newsletter

We’ve introduced a dedicated developer newsletter to keep you updated with all the latest on WooCommerce. This platform, crafted by developers for developers, will offer early insights into new features, practical tips, and previews of our roadmap. It serves as a direct line to stay informed, engage in discussions, and collectively shape the future of WooCommerce.

Upgrading our blog and documentation

We’re upgrading the Woo developer blog and documentation to make it easier for you to find what you need, when you need it. Expect improved navigation that helps you quickly access the most relevant information, and documentation that’s continuously updated to reflect the latest in product developments and industry best practices. We’re also introducing new collaborative features, allowing developers to contribute their insights and learn from the community, making our resources more useful and accessible.

We know that documentation is the foundation of a great experience for developers, so we’re working to significantly improve our docs across the board. This includes comprehensive guides on new and existing features, best practices, and step-by-step tutorials. Our goal is to fill crucial knowledge gaps in areas such as extensibility, block development, and theme customization, empowering developers to start and thrive on our platform.

Enhancing the WooCommerce REST API

We’re focusing on vital improvements and fixes to the current REST API v3, ensuring all changes are backward-compatible. Our goal is to reduce the backlog of issues and feature requests, streamlining API performance without disruption. Alongside this, we’re upgrading API documentation, error handling, and debugging capabilities to better support anyone creating integrations.

Extensibility

For WooCommerce, extensibility isn’t just a feature — it’s a core philosophy that shapes how we build and roll out new features and experiences. By designing features that can be extended and adapted, we enable developers to tailor our platform to fit the specific needs of merchants. This approach ensures that as we develop new core experiences, they can evolve through community innovation to become more versatile and powerful.

As we make new features the default experience, we are working to create space for collaboration with our developer community in order to refine these features, incorporate feedback, and gradually move towards full adoption. In the past year, we have begun using GitHub Discussions, Developer Office Hours, and other sources of feedback to shape and prioritize extensibility points in particular. This iterative process not only enhances the platform but also strengthens the ecosystem, making WooCommerce a more robust solution for everyone. 

Our future is block-based 

We’re building with the future in mind. Starting late last year, the default user experience with WooCommerce became primarily block-based, and all new feature development is targeting this environment. By shifting control from raw code to a block-based model, WooCommerce is opening up a world of flexibility and customization previously inaccessible to non-coders. This is a tectonic shift that we’re working closely with the WordPress project and team to usher in.

This transition to a fully block-centric ecosystem is not just about enhancing user experience; it’s about paving the way for future innovations in ecommerce. While maintaining compatibility with older methods, the focus is clearly on a future where block-based experiences dominate, marking a significant shift towards a more intuitive and adaptable ecommerce platform.

To continue to evolve, to stay aligned with WordPress, and to compete in the commerce and CMS landscape, we need the community to start moving towards this block-based future. If your solutions are still relying on shortcodes or other legacy APIs, it’s time to embrace blocks and modernize your approach.

We are actively adding resources to the Developer Docs site as well as here on the developer blog, including deep dives on blocks-related topics like our Getting to Know Woo: A Series on the Cart and Checkout Blocks, and video tutorials to help you with the transition.

Building the definitive commerce solution for WordPress

We are investing in improving the store experience, providing a better day-to-day experience for merchants, and a better foundation for developers to customize. At the same time, we’re adding capabilities and extensibility options to enable new possibilities for developers. Understanding upcoming features and enhancements for merchants and shoppers is essential when building those enriching solutions, which ultimately attract and serve merchants from various industries and with different needs.

Subsequently, the shopping experiences that WooCommerce stores provide are really where the rubber meets the road. While we aim to give merchants full control over their storefront and checkout experience, we deliver an out-of-the box default that’s a world-class starting point.

Here are some highlights of where we are concentrating our efforts right now. 

Store experience

Streamlined onboarding: We began simplifying the onboarding flow for new stores last July and saw a ~60% increase in completion rates for users who started the profiler. We’ll continue to streamline the setup journey from the very beginning, ensuring that new users can quickly and efficiently set up their stores. We’ll also look at optimized flows for users creating Woo stores on behalf of others.

Modern store customization: As we look to the future of store customization, we’re excited to further integrate with WordPress’s site customization tools. We heavily leverage WordPress’ emerging drag-and-drop site editing capabilities to handle everything from on-brand font and color selections, to complex store layouts, to dialed-in product sliders and collections — all built on the blocks system. While we’re ensuring compatibility with all block-based themes in the WordPress ecosystem, we’re also exploring what it would look like to provide our own fully block-based, commerce-optimized theme out of the box.

Flexible product management: Our new product editor is not only faster and more intuitive, but it is also nearing feature completion. We are now heavily focused on extensibility and customization. This approach is about rounding out the experience for developers, enabling them to fully leverage and integrate the editor into their solutions. We’re on a path to making this the default experience, contingent on deeper integration with WordPress Core work and widespread adoption and integration by developers.

Optimized order management and fulfillment: We are improving order management, but before embarking on any kind of major redesign, we’re stepping into some more targeted and heavily requested improvements. Right now, we’re working with friends at Kestrel and Mindsize to improve order statuses for managing the various states an order can be in, including handling multiple payment options for orders and various fulfillment scenarios.

Revamping merchant analytics: We’ve recently kicked off an effort to completely rethink how we help merchants understand what’s happening in their store, what’s working, and what they could do to make their business more successful. To this end, we will be improving the basic analytics function available to all merchants, including working with developers to finally retire the legacy “Reports” section, which has been officially deprecated for years.

Accessible stores: We are investing in enhancing the platform’s accessibility, ensuring it is available to the broadest audience possible. We are focusing first on improving shopper-facing accessibility, and then will shift to admin functionality. Our partners at 10up are supporting us here, and we’re preparing for an external accessibility audit to guide future priorities.

Shopper experience

An unbeatable checkout: Our block-based checkout is continuing to evolve and only gets better. We’re reducing cart abandonment, boosting mobile conversions, and simplifying user interactions. We’re really emphasizing performance here, so we’re reducing bundle sizes, improving load times, and optimizing for rapid user input. This new checkout sees conversions up to a few percentage points higher than the classic one, and we have ambitious goals to see a 25% improvement in block-based checkout conversion compared to short-code by the end of the year.

Local pickup options are being combined and simplified, and options around shopper account creation have been tightened up. We’ve added the number one developer-requested feature: an additional fields API that allows developers to add custom fields to the checkout process to support more complex needs. 

These cart and checkout features are all part of the default experience on new stores right now, so we strongly recommend you get to know the Cart and Checkout blocks and pursue compatibility now with your own integrations. 

Elegant order confirmation: This feature is already heavily customizable, but we’re enhancing the default to integrate better shipping details and order summary info, while also providing the option for shoppers to create an account after paying for their order. This is all part of reducing friction, increasing conversions, and avoiding cart abandonment.

For more detailed information on features and WooCommerce releases, follow our Changelog.  

Building the future together

As we wrap up this exploration of WooCommerce’s roadmap and the exciting opportunities ahead, we want to extend our thanks to the collective efforts of developers, merchants, and the wider WooCommerce community. By embracing open-source principles and fostering a culture of collaboration, we’re not just building a platform — we’re creating a movement that empowers individuals and businesses alike to thrive in the digital age.

If you are reading this, you are part of the journey. I encourage you to make your voice heard by joining GitHub Discussions to share ideas, ask questions, and provide feedback on the platform’s evolution. Engage with us and the rest of the community on the Community Slack, where you can connect with other developers, join office hours, and stay updated on the latest news. Contribute to WooCommerce core code or enhance the documentation to help improve WooCommerce for everyone. Let’s continue to create, innovate, and excel together.

You can connect with me directly on https://x.com/beaulebens, or follow along with the Woo Developer Experience team at https://x.com/DevelopWoo.


Keep yourself in the loop!

Sign up for the WooCommerce developer newsletter:
This field is hidden when viewing the form
This field is hidden when viewing the form
This field is hidden when viewing the form


37 responses to “WooCommerce in 2024 and beyond: Roadmap update”

  1. Heraldo Avatar

    Well, I needed a catalyst to finally make the shift to Shopify. Thanks for the push!

    1. Jacklyn Biggin Avatar
      Jacklyn Biggin

      Hey Heraldo! We’re really excited about what Beau shared in this post, and there’s a lot of very positive changes coming for merchants and developers alike.

      I’d love to learn more about what you’re against in this roadmap. We’re always open to feedback.

    2. Anonymousahole Avatar
      Anonymousahole

      Unfortunately Shopify has all the same issues + will want to take not only the money but the entire wallet too.

      1. True facts:
        https://trends.google.com/trends/explore?date=today%205-y&q=%2Fg%2F11c1wk85q7,%2Fm%2F0xpxtgc&hl=en-EN

        People can say since 2021/2022 Shopify is the Global eCommerce Goat or FTW …

    3. It’s true! Many people with shops / retailers and factories are now familiar with Shopify… And looking at the utilisation statistics over the years, customers are moving away from WP / Woocommerce more and more.
      Shopify for example is faster, saves a lot of time with the platform that is automatically prepared for sales.
      The processes are secure, the server is highly stable for the platform and the configuration is native ‘All in One’.
      It’s very easy to configure the process.
      All these years… Woocommerce needs better native configuration for the shop and the products, it needs evolution/progress, it needs a lot of things. We have to depend on plugins to have a shop and on the whole configuration and stability process.
      Sooner or later the alternative is to change platform and forget about WP, I don’t know exactly when yet.

  2. Steven Avatar

    I would love to see the Block stuff being taken out of the Woo core.

    It has been generating loads of new (sub)versions with their fair share of issues and rollbacks.

    Why not have a clean Woo core, with a Woo Blocks addon for those who perfer to use Blocks (/Gutenberg) as their page builder?!

    That way the core of Woo can become more stable again in terms of versions, that’s worth a lot in my opinion!

    1. Beau Lebens Avatar
      Beau Lebens

      Hi Steven, I’d love to understand more about your use case and approach here. We’re working hard to build something that works for developers, and also appeals to/is usable by merchants; that’s a tough balance to strike. I’ve sent you an email to see if we can connect and discuss further.

      1. Hi Beau, what i have diffucult to achive in my custom theme with blocks is to have something more powerful than the normal “checkout” or “cart”.

        For example for a site that i have built i have the necessity of have the images uploaded in the product from the user inside the cart and the checkout.

        The details of the user is displaied in my function (like the customized text from the user), but is impossible to show something else other than text, so is impossibile to see the custom images uploaded from the user.

        So i have to use the classic editor (that is really ugly compared to the block version) and use the hook for develop the thing myself (and works fine).

        So for me the possibility are two

        Leave the blocks as are now, but gave a modern UI for the classic shortcode
        Gave more powerfull and customization to blocks like cart and checkout (like we did with hooks in the past).

        1. This make so much sense to me. The entire point of the block editor is to be able to have flexibility. In many cases, and in this case with Woo it is actually limiting extensibility because it is almost acting like a shortcode. Place it and enjoy, unless it is not what you want and then there is a not a clear way to use hooks and filters as in the past…which was lovely by the way!

  3. what's the point Avatar
    what’s the point

    Blocks is unstable, slower and terrible to work with and tbh no use what so ever compared with simple code, checkout is no use with blocks, most third parties softwares are not compatible or barely catching up, nightmare for the amount of files and difficulties with csp.

    Most devs do not use blocks, but then nobody listens to what we say.

    Please do not drop support or stop developing the original methods and classic editor. Why keep breaking what’s not broken.

    Steven above has the right idea and if nobody listens then people will keep leaving.

    In the mean time, older plugins under woo belt are totally forgotten about, years without an update and pull requests ignored. Talk about waste our time contributing.

    1. Deepak Avatar

      100% agree. There have also been so many errors in releases recently. I think because the codebase is so big now, it is easy to miss issues in testing. Things will only get worse.

    2. I agree with this, but sadly don’t see it happening.

    3. Thanks. Thats exactly my point! No one needs blocks or a bloated webshop builder in core.

  4. That all sounds great, thanks.
    It’s fantastic to see the developers are getting a centralized point and embrace the community even more. And i was the one that ring the bel for a better changelog, and i am happy to see it was taken care for. Thanks again.
    But to get knowledge or help, it is still a jungle to know where a ‘community’ can get help or info. Let it be a merchant, a developer or a Woo builder like me.
    Woo has a lot of communication channels, that’s i’m referring as ‘a jungle’. It would be great to have clearity in this space, to make sure a beginning merchant don’t mingle in a hard-core dev group and runs away cause they don’t understand a thing. 🙂
    So, a dedicated page to guide the whole group to their “other” peers would be very helpful.

    Another think: no word about “marketing” in the article. I believe Woo can do much better with their site; so as i mentioned the page for guidance on help (for different user segments)
    A few examples:
    – when i am logged in, i can’t reach the homepage. A big marketing fault and brand impact. People always wants to go to the “start”. And a dashboard is not a homepage.
    – focus on the positive. The red dot on the “my subscription’ of expired ones, why? Turn that around, set a green dot with the active ones. And put the actives ones above the expired and thank them even extra to be a Woo fan!

    1. Jacklyn Biggin Avatar
      Jacklyn Biggin

      Hey Dave! Thanks for the kind words and the really valuable feedback!

      I’ve passed on your thoughts about redirects/subscriptions on the team responsible for woocommerce.com.

      In terms of Woo’s communication channel’s being a “jungle”, we’ve been working to streamline things for certain groups. For example, for developers, we now have @DevelopWoo on Twitter which posts about dev-focused blog posts and news, and developer.woocommerce.com / developer.woocommerce.com/docs for developer-specific posts and documentation. I’d love to learn more about how you think would be helpful – what are you thinking?

      1. The part around developers is indeed outligned, with the twitter handle @DevelopWoo and a whole separate website part. That’s the outgoing communication. And yes; this IS a developer blog article. But I’m more taking about incoming communication from all kinds of users to WooCommerce.
        For example the Slack setup which is more dev oriented: it’s not clear (for me) in which channel is what type of communication. What’s the use of #core channel when there’s also github discussions… what’s the difference between #developers and #extensions, and what’s the role of #core in relation to #product-editor.

        About merchants. Do merchants also have an incoming communication channel like that? Is that the forum on wp.org? Of something other? Somewhere in the docs there a reference to the ‘advanced woocommerce’ FB group

        So, all of these questions can have some or what more guidance i guess.

    2. Florent Avatar

      It does not smell good. It is high time after 5 years on woo to switch to Shopify. Bye bye.

      1. yes… i see more and more people changing, for me is getting a waste of “working” time, and “money” after changing from Joomla many years ago to WP .. maybe sooner I feel that i need to offer new solutions that even customers say.

    3. Please leave the block stuff out of the core. Listen for once to the devs… why? Woocommerce is a tool to build a store, it should be performant, reliable and not a bloated webshop builder. if you are not a dev and want something like wix, shopify or others install the block extension, done. For custom shops, whats a better experience than having a template (php, html even golang) sprinkle the css and js you need on top, done. A hook or filter here and there or even plain woo rest calls. It is as performant as you write your code. its based on standards, with tons of tooling, documentation, validators and so on. Can you break things? yes. Can you write beautiful code thats fast reliable and not bloated? yes definitly.

      The question is if woocommerce core should become a shop builder for non devs, or a tool for devs with an extension to become a shop builder.

      It’s already a pain to strip the not needed js/css from the page.

      i’m a dev, i like sport cars, blazing fast only the needed parts to be as performant as possible, if something breaks i fix it, want to add something? I develop my own plugin. some style tweaks? every day. Some new js event, ok add it. it is as simple as that.

      Others like limousines with a hot tub in the back, a weight of 3 tons and a waiter serving drinks at 30kph. Both is ok, both is good.

      BUT: you can build a limousine(shop builder with blocks in core) from a sports car(plain good woo shortcodes/templates) but no one builds a sports car starting with a limusine!!! 😉

      Cheers

  5. Jason @ pip3 Avatar
    Jason @ pip3

    Thanks for this update, it is helpful to see what the general direction for development is going to be.

    Sadly, this misses the mark for me. I feel like WooCommerce is moving into very murky territory. Whilst trying to catch up to the level of customisation in Shopify, we’re greatly losing focus on stability and performance. So it is kind of a lose-lose situation where Shopify becomes the better solution for both small and large stores alike. What exactly is the point in WooCommerce now? Who is the primary target user?

    Whilst hoping that I’m wrong about this over the past year or so, things seem to continue degrading. For example, increasing numbers of emergency point-releases to fix fatal errors and broken checkouts, assumedly due to the complexity of the codebase or loose testing procedures.

    One minute we’re being told the focus is on performance/HPOS, the next minute a “coming soon” page is announced pretty much out of the blue. It feels like there is an attitude of “yeah! that would be super cool to add this feature!” behind the scenes without much quality control or long term planning.

  6. Riitta Korpipää Avatar
    Riitta Korpipää

    Not too keen on blocks either, I hope you keep developing the more traditional methods as well. Keep in mind that Woo is integrated in all sorts of sites. It is simply impossible to update all sites and build them from a scratch. Also, I find the blocks approach in general still too complicated and not at all intuitive. The “old” page builders and themes will still be around for quite a while.

  7. Anonymousahole Avatar
    Anonymousahole

    No one has anything good to say and for good reasons. You guys never listen to your customers and treat us like garbage. You don’t provide any support AT ALL either.

    The support is a trainwreck, and if you try to get any help with Woo Core they say garbage like “We CAn HeLp yoU wiTH PAiD eXtEnSionS BuT foR WoO CoRE YOuR On YOUr OwN!”

    What kind of support is that?

    They also always recommend the useless shortcode checkout instead of… idk fixing the bugs with the blocks checkout???

    1. Jacklyn Biggin Avatar
      Jacklyn Biggin

      Hey there!

      As a free product, WooCommerce Core support is primarily provided via our docs and the WooCommerce forums on WordPress.org. However, if you’d like one-to-one support via email, you can purchase our premium support addon at https://woocommerce.com/products/woocommerce-premium-support/.

      With that said, if you’re running into bugs with our Block-based checkout, we want to fix them! Do you have any specific ones you’d like to share? Alternatively, if you already shared them via an email to support, if you can provide me with the ticket number I’d be happy to pass them onto our engineering team. 🙂

  8. Dennis Avatar

    I love(d) Woocommerce, but this post makes me really sad. Even after all those years of backlash against the blocks editor, you still decide to push this. The block editor does NOT work faster, the interface is still terrible. Even the most basic things are multiple clicks away in the interface. When you have larger website it is terrible to manage content. The only users it is great for are the people new to WordPress who have no experience in setting up a webshop.

    This feels so much like when the blocks got first introduced. The feedback pre-launch was negative, but they still released. After the release the feedback was even worse, and they kept on pushing it is the way to go. The classic editor is still the most downloaded plugin, and not without reason. I still remember developers posting on twitter the community just does not understand them and their vision for WordPress. They got mad like a little kid not getting its way. After all these years they are too deep into the block idea to abandon it. They chose to ignore their community again and again and again, while they should have embraced their community and listen to them!

    Will I stop using Woocommerce if you push this through? No(, not yet), but I will be very disappointed in the Woocommerce team for years to come. The WordPress block push of the developers is still a huge scar in the community trust. And now you push the blocks as a core feature.

    1. Jacklyn Biggin Avatar
      Jacklyn Biggin

      Heya Dennis. I appreciate you sharing your concerns, and would love to chat more. I’ll send you an email. 🙂

  9. We need to get custom product tables schema for SQL. This would help migrating stores from old layouts to new layouts so damn easy together with the new order tables 🙂

  10. Excited about what’s on the roadmap, and I know all of us want to see a better cart and checkout page.

  11. We’ve done 63k net profit so far this quarter. I would give my left pinkie to have Woocommerce focus on developing core features that are already shipped in the core versions of other e-commerce solutions instead of integrating and loosing developer time with FSE. Only this month we got a native GTIN field, that should have happened years ago. HPOS? Same thing. As a designer/developer + merchant I want stability and core improvements in functionality. Love Woo.

  12. Thanks for the updates on the direction of WooCommerce. I’m eager to be able to use the block editor on product pages. I’ve embraced it everywhere else on my sites and miss the advantages it brings every time I work on product pages. I have to admit that I don’t see blocks as that important for checkout, though.

    The other thing I’m excited about is the option for shoppers to create an account after paying for their order. To me, this is one of the most important and practical features that can be added!

  13. Ronak Ganatra Avatar
    Ronak Ganatra

    Fantastic plan

  14. PrinceJammy Avatar
    PrinceJammy

    I want to share some concerns about the recent developments in WooCommerce. The block-based product editor, although aimed at improving usability, isn’t as intuitive as the older version. Small example – It has become difficult to add HTML to product descriptions—both long and short—which was a straightforward process before.

    Another issue is that new features often come at the expense of existing functionalities. For instance, in the block checkout, there’s no option to leave the billing address unchecked by default anymore. This limitation can hinder the checkout experience for customers who prefer a faster, streamlined process.

    Usability features like plus-minus buttons on product pages should be basic inclusions, yet they are missing. These buttons enhance user experience by making quantity adjustments more straightforward. Additionally, the ability to duplicate orders in the backend is a common requirement for store management, and it’s surprising that this isn’t an inbuilt feature.

    I appreciate the forward-thinking approach and the new checkout design; however, it’s crucial for the development team to engage more with store owners to understand their pain points fully. Regarding WooPayments, it has the potential to be a significant revenue stream, but current user reviews indicate that it may not be reliable enough for adoption just yet.

    If you want to increase renvenue from WooPayments you need to nail on the core functionality, and not make store ownders rely on finding coders, plugins, themes just to run a decent efficient store.

    I would say the Woo team just need to take a look at what companies like SureCart, WC Checkout etc etc are doing to understand what store owners need. The original iteration of WooCommerce is good and just needed to be consitently improved but each new iteration seems like a step backwards for real world usability.

    Overall, while I acknowledge the efforts to innovate and improve, these issues impact the day-to-day usability of WooCommerce. I hope future updates will address these concerns to enhance the platform for all users.

    1. Brent MacKinnon Avatar
      Brent MacKinnon

      Hey PrinceJammy,

      Thanks for taking the time to share your feedback and concerns in such detail – it’s clear you put a lot of care into this message, and we really appreciate this kind of detailed feedback from our community.

      You’ve raised some great points about the block-based product editor and HTML editing. We hear you, and we’re working on improving the Product Editor experience as we speak. The checkout process concerns you mentioned, like billing address defaults and quantity adjustment buttons, are definitely on our radar too.

      We totally get that the transition to blocks can be tricky. Our goal is to make it smoother while keeping the flexibility you’re used to. Our shift towards block-based experiences also aligns with WordPress core development and should enhance our customization capabilities, not detract from them. We’re not quite there yet, but we’re working on it.

      Your feedback on WooPayments and core functionality is spot-on. We’ve recognized the need for more comprehensive, integrated experiences, and we’re pushing hard to make WooPayments more reliable and user-friendly. And you’re right – we should be looking at what others in the space are doing well.

      This past year we’ve been ramping up our efforts to engage more with developers like yourself. We want to make sure we’re addressing real-world needs, not just ticking feature boxes. If you’re up for it, I’d be happy to connect directly and hear more about how you’re building with Woo, and your needs. I’m in the Woo Community Slack if you want to shoot me a DM.

      Thanks for keeping it real with us. Your insights are extremely valuable and are being shared with our product teams. We’re committed to making WooCommerce better for everyone, and feedback like yours helps us get there.

      Keep the comments coming – we’re listening!

  15. Hello!
    Why after many years, Woocommerce lack ambition to be in the top?
    Is the ambition just to remain a normal plugin, along with so many others that are appearing in many different platforms?
    There no ambition to offer more and better?
    I feel that over time Woocommerce is inviting WP devs to change platforms. We have to spend our time configuring systems, servers, plugs, updates, themes, … when there are nowadays better/faster offers.
    Why not create a better and wide product configuration option? A system where users can easily opt to setup from B2C, B2B, etc.. Drag and Drop Design, etc…
    Theme, Plugins make this whole process slower, more expensive, less secure, more vulnerable, more conflicting, …

  16. Roy Brand Avatar

    Dear Woocommerce, I am already using wordpress and woocommerce over 11 years now its a fantastic system. But now I am starting to think the revamping goes to slow.

    Why must woocommerce crash a server / take minutes when working / changing status of 50 orders at ones? This should be way more efficient now with php 8.3.

    Is it time to support more javascript features?

    Woocommerce has to step up in my opinion and take a better look to shopify.

    Shopify is not self hosted also due using woocommerce and wordpress over 11 years I can manage it better then newer systems.

    So I wanna stay with the wordpress / woocommerce eco system but upgrades need to happen.

    1. Brent MacKinnon Avatar
      Brent MacKinnon

      Hey Roy, thanks for the feedback.
      Question: have you adopted High Performance Order Storage for your stores?

      https://woocommerce.com/document/high-performance-order-storage/

      HPOS optimizes how orders are stored in the database, moving away from the traditional WordPress posts and postmeta tables to dedicated WooCommerce order tables. it reduces database load and improves query efficiency, leading to faster operations, including bulk order status updates.

      FYI HPOS is enabled by default for new installations from WooCommerce 8.2 onward. For existing stores, enabling HPOS can enhance performance.

  17. I do love blocks, but half finished blocks make me sad and to be fair that is the state now within woo and worse is when you start using them its like a one way street downhill without brakes.

Leave a Reply

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