Open Channels FM
Open Channels FM
Flexibility Meets Simplicity: Smarter Defaults for Merchants and Developers
Loading
/

In this episode host Jonathan Wold welcomes Beau Lebens, head of engineering at WooCommerce, to discuss the development and future of WooCommerce within the WordPress ecosystem which grew out of his post on Woo, WooCommerce in 2024 and beyond: Roadmap update.

Beau shares his extensive experience within Automattic and provides insights into the uniqueness of WooCommerce as it evolves from a WordPress plugin to a complete commerce solution with its ecosystem. The conversation covers topics such as the challenges and responsibilities of maintaining backward compatibility, the role of WooCommerce in the broader WordPress evolution, and the strategic alignment with new WordPress technologies like blocks and full site editing.

Beau highlights ongoing efforts to improve the integration of merchant and agency experiences, focusing on performance optimization and ecosystem collaboration. They also chat about new additions like the Business Services tab and emphasizes the importance of providing integrated, merchant-centric solutions.

Our sponsors keeps our network independent and actively publishing.

Since 2005, Automattic has built tools for the open web including WordPress.com, WooCommerce, and Jetpack that are used by millions of people to create, sell, and publish online. They believe in ownership, flexibility, and open source and we’re grateful for their support. Learn more at automattic.com.


Logo of Omnisend featuring a stylized 'i' icon and the brand name in lowercase letters.

In five days, Omnisend moves every flow, list, and template off your current platform, and you could be paying up to 35% less without lifting a finger. You just show up when it’s done. We’re glad to have them supporting the show and the community we’re building around it. Use the code OpenChannels and get 30% off your first 3 months of any paid plan.

Takeaways

  • WooCommerce’s Growth: WooCommerce started as a simple plugin but has evolved into a robust ecosystem, tightly integrated with WordPress, providing flexibility for both developers and merchants.
  • Stronger Defaults for Merchants: To reduce complexity and decision fatigue for merchants, WooCommerce is focusing on providing stronger defaults, particularly in payments, shipping, and taxes, while still maintaining flexibility for developers.
  • Backward Compatibility: WooCommerce is deeply committed to backward compatibility, even when implementing complex changes like the High-Performance Order Storage (HPOS) project, to ensure stability for merchants and developers.
  • Developer Engagement: WooCommerce is increasingly engaging with its developer community through GitHub, Slack, and blogs, seeking feedback to shape future updates and features.
  • Ecosystem Thinking: WooCommerce embraces ecosystem thinking, encouraging third-party developers to build integrated solutions that work seamlessly within the WooCommerce platform rather than as standalone products.
  • Commerce and Content Performance: One of WooCommerce’s unique challenges is balancing the performance needs of real-time commerce with content-focused caching, requiring continuous optimization.
  • Future Investment: WooCommerce is investing heavily in key areas such as payments, shipping, taxes, and technologies like blocks and full-site editing, aligning with WordPress’s long-term roadmap.

Links

Chapter Titles with Timestamps

  • 00:00 Introduction and Welcome
  • 00:38 Beau Lebens’ Journey at Automattic
  • 02:38 The Evolution of WooCommerce
  • 05:14 WooCommerce as an Ecosystem
  • 10:18 Challenges and Responsibilities in WooCommerce Development
  • 16:49 High Performance Order Storage (HPOS)
  • 25:00 Open Source Dynamics in WooCommerce
  • 28:16 Understanding Performance Bottlenecks
  • 28:28 WooCommerce and Hosting Ecosystem
  • 29:03 Commerce and Content: A Performance Perspective
  • 30:01 Engineering Challenges and Merchant Experience
  • 31:12 WooCommerce’s Evolution and Stronger Defaults
  • 34:49 Business Services and Holistic Merchant Support
  • 36:59 Interplay Between WooCommerce and WordPress
  • 41:41 Future Directions for WooCommerce Builders
  • 46:27 Guidance for WooCommerce Product Companies
Episode Transcript

Jonathan:
Welcome to another episode of Inside Woo. I’m your host, Jonathan Wold, and with me today is Beau Lebens, the head of engineering at WooCommerce. How are you, Beau?

Beau:
I’m doing well, Jonathan. Thanks for having me on.

Jonathan:
It’s good to have you, and we have a lot to cover inside of WooCommerce. Before we get to that, though, for those who don’t know, would you mind giving us just a bit of background on yourself? You’ve been at Automattic for, if I’m counting right, 15 years now?

Beau:
Yeah, a little like that. Yep. A little over 15 years.

Jonathan:
And WooCommerce, you’ve been focused on WooCommerce for over five years now at this point, and you’ve worn a lot of different hats. Can you just give us some context for your work broadly at Automattic and what you’ve been focused on at Woo for the past five-plus years?

Beau:
Sure thing. Yeah, so as you mentioned, it’s been a little over 15 years with Automattic now. I came on originally as an engineer, just the one engineer person, and worked on a bunch of different parts of Automattic. I originally actually came on working, ironically, not directly on WordPress. The first few things I actually worked on were IntenseDebate and then Gravatar, but then I got deep into WordPress.com. I worked on Jetpack for a number of years and then came over to the Woo team, I guess it was five and a half years ago, and joined originally on what was then the core engineering team, with an eye towards being in this sort of engineering leadership role, helping to steer the future of WooCommerce in the WordPress space as someone who had actually worked in the WordPress world before joining Automattic as well. So, really early on in the WordPress space, and so that’s sort of always been my forte. And since coming onto Woo, I have really helped, I guess, steer Woo alongside WordPress, which is something I believe we’ll talk about. There’s something we’re still doing, which is having Woo be kind of in lockstep with the evolution of WordPress itself, but then also steering it towards this whole green space as far as the commerce world goes, and what it looks like and what it means to be not just the de facto commerce solution for WordPress, but being a real commerce ecosystem of its own.

Jonathan:
So, you’ve worn a lot of different hats, and with Automattic broadly—myself as a former Automattician—there’s a lot of flexibility and freedom that you have to pursue interests. So, you have a lot of autonomy in what you do. I’m a big fan of a wide-ranging experience. I think it makes you better at the work that you do. Are there any particular experiences that stand out to you from your 15 years that have especially helped shape the work, I guess the experience and the approach, that you take to the work that you do now in WooCommerce?

Beau:
Definitely, yeah. So as I mentioned, I sort of was working with WordPress before I even started at Automattic. Originally, I got involved with WordPress—I guess very originally—just because it was an interesting new platform. I was in the web space already and was building websites and doing all sorts of things that WordPress looked interesting for. But then what really got me deep into it was actually attempting a startup with a friend of mine, which, as many startups do, failed miserably. But the premise there was actually leveraging what was, at the time, WordPress MU (which is now a multisite feature that is baked into core), and integrating with bbPress, which is sort of a bulletin board or forum system based on WordPress. So, it was taking those, mashing them together, and then completely changing the front-end experience, so the user didn’t actually know they were using WordPress or bbPress for that matter. So, it was this really customized WordPress-based system.

And when I look back, that’s actually something that has been a little bit of a thread and feels relevant now, the way that we look at WooCommerce, which is: Yes, this thing is based on WordPress. Yes, it is WordPress-powered. Yes, it brings WordPress’s ability to manipulate and manage content to the forefront, but it’s also something else. And it’s leaning into that—leveraging this operating system, if you like, and customizing it towards a specific experience, in our case commerce, and then doing everything that’s possible with that power that comes under the hood. And so, that’s still something that we’re doing today. We are leveraging all of the power of WordPress’s posts and users and settings management, all of this stuff that comes under the hood, all of that portability and flexibility that allows it to run on any web host, but we’re applying that same approach to commerce.

Jonathan:
I think that’s part of what I’ve always found interesting about WooCommerce in particular, is it’s such a great example of an ecosystem within WordPress. And I think it’s especially so because, for most folks who are using WooCommerce, they have this clear business intention, this clear commercial intention, but the way that they got there can vary quite a bit. They could have started out in WordPress with a blog and suddenly, like, add commerce, and then that sort of takes off. And now you have this commerce business. There are people who came in just for WooCommerce—that was something that we began to see early on in WooCommerce is people coming into the ecosystem for Woo. So, it’s always sat at this unique intersection.

And I think what I’m interested in hearing first is, you have this evolution of WooCommerce starting out as a plugin that gave you a lot out of the box from the outset and introduced this whole new range of capabilities to WordPress. And already, from your perspective, when did ecosystem thinking first come into WooCommerce? Was that driven by how people began to use it and what they demanded of it? What’s your perspective as an observer first, and then coming into where that thinking about WooCommerce as a plugin evolved into an ecosystem?

Beau:
Yeah, that’s a great question. I want to actually just really quickly touch on that mention of these overlapping ecosystems or communities between WordPress and WooCommerce, because I think that’s the really fascinating one. There’s a couple of different ways you can look at it, and I often look at it—there are two specific ways I tend to look at it. One is, if you try and Venn diagram those worlds, right? WooCommerce has huge overlap with WordPress, obviously, as a product and as a community and an ecosystem, but it’s not 100%. So, to your point, there’s a certain slice of people, whether they’re developers or the merchants themselves, who really aren’t thinking about WordPress much at all. It’s just there, it’s the foundation of WooCommerce, but they’re thinking of it through a sort of WooCommerce-first lens. And so, that may be a merchant who just wants to set up a store…

Jonathan:
…which I think is worth pointing out that that’s pretty unique. In WordPress, oftentimes there’s a lot of ecosystems, sub-ecosystems—forms are good examples—but with WooCommerce, I think you’ll have people who really aren’t thinking about the WordPress part, which is something a lot of people in WordPress, it may not be obvious unless you point it out.

Beau:
Absolutely. Yeah, absolutely. It’s something that, especially if you’re sort of steeped in this WordPress background (which, I’ll be the first to say, I am myself), it’s actually kind of hard to wrap your head around that reality and accept that, no, some of these people, they just heard about WooCommerce, and they heard WooCommerce is how you put a store on the internet. And so, they go looking for that, and that’s what they want. And then, as they unpeel the onion, if you like, they see, oh, there’s this WordPress thing under here as well, and I have access to this whole other, what they think of as a whole other ecosystem of WordPress solutions and flexibility and everything else that comes.

Jonathan:
Like, “Oh, I can have a blog as well, that’s cool.”

Beau:
Right. “And I can add complicated forms to it, and I can optimize my SEO,” all these other things that come along with that WordPress world. They maybe didn’t appreciate that they were getting that out of the box with WooCommerce.

The other lens that I look at it—so first, you’ve got that Venn diagram world. The other one is this sort of stacked platforms, if you like, where WordPress is very much a platform, it’s a whole ecosystem—it’s WordPress the solution, and then all of the plugins and themes and everything that come with it. WooCommerce is kind of like, oh, add another core platform on top of that, and then another whole ecosystem of WooCommerce-specific solutions. So we refer to them as extensions, but at a code level, they’re really just WordPress plugins that rely on WooCommerce specifically. And there’s a whole other world of them, which is sort of this next layer on this commerce solution, if you like.

And so, when you think about it as slices rather than a Venn diagram, we have basically everything that you have at

the WooCommerce level, whether that’s communities or meetups or plugins or any of the solutions that exist for WordPress. We have all of that at the WooCommerce layer as well. And so then, that’s a really interesting way of slicing it out. And then you can look at just what’s happening at the WooCommerce level, but then also how does that interact with the layer below it? So you end up in a pretty complex environment, but it’s a really interesting one to work in.

Jonathan:
So, if you start to take its origins as a plugin, from your perspective, how did we get there? I like the layers idea. What are the things that stand out to you?

Beau:
I actually think early on in WooCommerce’s trajectory, if you like, there was kind of this acknowledgment that you can’t build everything that you need for a commerce solution in a single plugin for WordPress. It’s hard enough to do as a complete standalone, entirely controlled SaaS service. Even in that environment, you can’t build everything that you need to cater to every commerce solution all in one native package. You have to have something of an ecosystem to provide all of the unique solutions that all of these different commerce scenarios require.

So from day one, I think whether it was fully acknowledged or not, WooCommerce has sort of embraced this idea that it takes an ecosystem to provide all of these solutions. And what we’ve done over the years is really lean into that. And we’ve really said, yeah, that’s core to how WooCommerce works. No matter how much we may or may not build into that core experience, you’re always going to need the flexibility that WordPress and, by extension, WooCommerce provide. You’re always going to need some extra workflow modification, or maybe you need, I don’t know, a specific shipping carrier in a region that’s not very big, whatever it may be. And so the way that we can provide that is that we as Woo—that distinction is there, the company rather than WooCommerce the product—something that’s really important to us is figuring out how to build an excellent experience but retain this flexibility and extensibility so that developers and builders can customize and tailor it.

And then, I think one of the other big challenges for us is making sure that interoperability is there so that once you start putting together a solution, it still feels like a meaningful, singular commerce experience. And that exists both at that WooCommerce layer and that WordPress layer. And that’s where it gets really interesting, frankly, and challenging. And where I think the direction that WordPress is going (which we can talk about if that’s interesting) is really sort of enabling a level of integration and flexibility that actually is not great at the moment in WordPress. WordPress has some, I think, almost a lack of opinion that has been great for flexibility but has resulted in some experiences that feel a bit disjointed and that aren’t as deeply integrated as they could be.

Jonathan:
I started writing about this concept of ecosystem plugins a number of years back, and WooCommerce was the one that really stood out to me. And when I think about this concept of an ecosystem within WordPress, there were three characteristics that stood out. First, you have to introduce a suite of functionality, which WooCommerce clearly does—a whole new category. You also have to provide an integration layer that can be extended. But the third thing—and I’ve felt from the beginning that WooCommerce, whether inadvertently or not, has done this better than most—is you also need to influence and shape that ecosystem, like taking an active role. Because I think a lot of the ecosystems we have in WordPress, up until more recently, it’s been fairly hands-off. And I think in WooCommerce, there’s a degree, at least from my perspective, to which just the demands of the growing business required active curation. The partnerships team did a lot of work to help shape and influence what came into WooCommerce.

But from your perspective, through your lens and the roles that you’ve played, and from an engineering perspective, how do you think about the responsibility of WooCommerce the business to shape the ecosystem, especially when it’s so large? There are people who use WooCommerce in so many different ways, and you’re already beginning to allude to the importance of opinions there. But how do you think about that responsibility?

Beau:
Yeah, it’s a tricky one. It can be, as you said, it’s really broad, and so people are doing all sorts of things with WooCommerce, some of which we would never imagine. And so, it’s very difficult to plan for that. We do take backwards compatibility really seriously. Similar to one of the things that is actually sort of fundamental to WordPress’s success over the 20 years that it’s existed, is this commitment to backwards compatibility. What does that look like? What does that mean? And frankly, it’s something that, as engineers and developers, it’s easy to get really annoyed with and wish that we didn’t have to do and just wish that we could move forward, change things, build the new shiny thing, build a new system, whatever. But I think that’s fundamental to WordPress’s success and WooCommerce’s success.

We do need to break it sometimes—there are some unavoidable situations where maybe it’s a security fix or a specification change, or whatever it might be where we just can’t figure out how to maintain backwards compatibility or, frankly, staying backwards compatible is not in everyone’s best interest, and so we have to move things forward.

Jonathan:
Let’s talk about that specifically because I think it’s a really good example of where the tension, especially from an engineering perspective, lies because, at least from my perspective, having worked with many engineers, you can kind of move on. You see better ways to do something. You see, okay, there’s this new set of practices that we want to bring in. This makes a lot of sense. And from an end user’s perspective, oftentimes it just doesn’t matter. And if you look at it, I feel similarly that WordPress’s and WooCommerce’s success is in large part due to the confidence and stability that comes from that. People don’t have to think about it often; it’s just not breaking. Is there an example that stands out to you of where you did the harder work—usually the much harder work—to maintain the backwards compatibility? I think for builders listening to me, this is an important part of success in the WordPress ecosystem, is internalizing why this compatibility, why the work matters. Is there any example that stands out to you?

Beau:
Yeah, I have a huge one, which is very relevant. We can talk about the past version and the future version of it, and that’s HPOS—so high-performance order storage. For anyone who’s not familiar, this is a pretty fundamental change where, historically, WooCommerce had stored all of its order information, so someone places an order on your website, you make a sale, that information was stored in the WP post table, because that was the sort of most flexible place to store that data in a WordPress install, where historically it was somewhat frowned upon to introduce your own custom tables. And so back in the day, WooCommerce was built as a plugin. It was intended to be installed on WordPress, spun up pretty quickly, and you could just go about your way, start taking orders.

So HPOS was this project to shift all of that data to a custom set of tables, which were optimized for storing large volumes of order data and for processing at high capacity. And the actual engineering work to just do that, if we were just changing WooCommerce core, was done in about two months max. And that’s with even sort of trying to allow for the fact that the way that we did it, the planning process, everything was very different because we were catering to an entire ecosystem. So we did this work, and then it took almost two years before that was actually the default on new WooCommerce installs.

And that’s because all of the work was really around the ecosystem and adoption and educating other developers and introducing systems to allow different plugins to declare compatibility or incompatibility and how we handle all of those different combinations of things that are or are not compatible. That’s where all the complexity came in. And that, frankly, is all about backwards compatibility, whether that’s at the sort of user level or the code level, it’s handling all of these different scenarios that exist in the WordPress world because you’ve got these different versions of things out there running, and you can’t just update them all at once. We can’t just go tell people, you have to update WordPress, WooCommerce, and every plugin that you’re running to X version and they’re all compatible and then you’re good. And so since we can’t do that, we have to deal with this complexity.

Jonathan:
That’s a great example because I think instinctively it feels to me like it was the right approach to focus on the lowest common denominator of experience, which is the merchant, and also the most important in this case. So, it takes that time, yet if you can make it available to your builders, to the agency ecosystem sooner, then there’s more winning that can happen. They’re able to successfully roll this out for their merchants, their clients, your merchants, and you can probably get a productive feedback loop that also gives confidence that makes what you ultimately roll out to everyone more effective. And if I contrast this to other ecosystems, part of the problem is that they don’t have that first focus. I don’t remember the details of it, but my sense of what happened with Magento, for instance, was this sort of big cut from one to the next. And from what I recall, there were developers who were

quite happy about the changes, and probably also the work that they’d have to be paid for to make the migration successful. But a lot of merchants ended up being disenfranchised and just lost in the process. So, you’ve done a good job, from my perspective, to remain merchant-centric in those decisions. And it sounds like you’ve recognized the role that your ecosystem can play in supporting that, and you can create a win for them as well in the process.

Beau:
Yeah, that’s definitely a learning for us. And I think also a challenge and just something that we’re still getting better at is how to really engage with this developer ecosystem. You mentioned earlier that there are people out there building WooCommerce solutions, and we frankly just don’t even know who most of them are. That’s both the beauty and the struggle of, I think, WordPress itself, but also WooCommerce is that they’re out there in the world. The code base is available, people can go build them and deploy them anywhere, and they may not interact with us in any way. And so, it can be very difficult for us to communicate with that ecosystem of builders and developers. And it’s something that actually, I think we haven’t done as good of a job as we should have in the last few years, but I guess a few years ago, the last year plus, you may have seen we’re much more active out there in public now. That’s a really conscious and intentional shift. We really want to engage with developers through GitHub, through our Slack community, through our developer blog. We’ve been putting a ton of work into tightening up and aggregating all of the, what was disparate documentation for our platform, bringing that all into a single developer hub, and then also leaning into tooling—do we have CLI commands and all of the stuff that we know developers actually prefer to work with. They shouldn’t have to dig through the code to find out how to do something. We should have better documentation for that.

So that’s really a foundational thing for us that we’re investing a lot in. And we really want that feedback loop with community developers who are building on top of WooCommerce or they’re building solutions for WooCommerce. Frankly, a lot of that has happened without us hearing about it. And so sometimes we get these blowups of feedback where people get frustrated and they say, “Why aren’t you doing X?” And we say, “Oh, we actually hadn’t heard that that was such a big deal to you.”

Jonathan:
So, this is one of the things that’s standing out to me in this—some of these problems, these challenges, we’ll call them challenges—that you’re experiencing are quite unique to open source. If we contrast this to proprietary platforms, in a proprietary platform, you wouldn’t have that. Typically, you wouldn’t have that two-year period.

Beau:
You’d just do it.

Jonathan:
You just do it. “This approach is deprecated as of this year. We’ve upgraded everything.”

Beau:
Exactly.

Jonathan:
You take care of it for them. And you also know your constraints, who’s working in your platform more often than not. And if you don’t, you can solve that a lot more readily. I’m curious from your perspective, I guess I’m not asking about just the benefits of it in this open-source ecosystem. And I think that’s a big part of why it’s grown to where it is. It’s a key factor in all of this. But I guess, how do you think about—you grew up in the WordPress space—how do you think about the impact that the open-source nature has, the benefits, and the trade-offs to WooCommerce? Because you started from a plugin, now you have an entire ecosystem that happens to be open source. It’s quite unique and very commercial in its nature, and there are all these dynamics at play. And yeah, I think it’s worth touching on that because that’s a single characteristic that has a lot of impact on what you’re trying to work on.

Beau:
Definitely. Yeah, it’s an interesting and very difficult question to answer because, as you said, it seems like a relatively narrow question…

Jonathan:
Right? “Oh, it’s just open source.”

Beau:
Yeah, it has so many implications. So I do think it is fundamental both to our previous success—I think it is what got us here—and it poses some unique challenges in going forward. There are certain things that, especially in a commerce space, would be much, much easier to do if we controlled the full stack, if all of WooCommerce was hosted in a single environment and we could just deploy updates, or we could optimize certain things. Performance is a favorite topic, which is actually an area that we are investing in more this year. We mentioned HPOS, but there are a ton of different performance characteristics that, when you control the whole system, you can just optimize for the way that system works. Whether it’s, I don’t know, adding an index in a database or optimizing a specific query or whatever it might be—adding a specific caching layer—we don’t even know what people do with most WooCommerce stores. And so, it makes it very, very difficult to optimize the performance profile of something that you don’t know what it is.

So that sort of thing can be really challenging. But I think what we’re seeing is, over the years, there’s a certain number of pretty consistent profiles that we see. For example, people use WooCommerce in certain ways, and it’s actually one of the beauties of being housed within Automattic, which has multiple hosting environments, is that we can just go look at real stores and see how they’re going, what they’re doing, what software they’re running, what performance bottlenecks do they ever run into, and then just working directly with them and improving it and then bringing those improvements back to the rest of the platform.

Jonathan:
It’s such a unique challenge. I remember when I worked at WooCommerce, one of the debates at the time was this: how does WooCommerce relate to the hosting ecosystem? And this is such a good example because someone can have really low-cost hosting on WordPress, which is great, and then wake up one day and decide to install WooCommerce and run WooCommerce and start to take orders. All of this can be happening in an environment that was not designed, intended for that, right? And that’s not necessarily going to be apparent to the user.

Beau:
They have a bad experience potentially, and they think, “Oh, it’s WooCommerce’s fault.” And I think commerce and content are really interesting when married together, but they’re also almost opposed from a performance perspective, right?

Jonathan:
Caching versus not caching.

Beau:
Exactly.

Jonathan:
Right out of the gate.

Beau:
Right out of the gate. The fundamental strategy for content performance is just cache everything, and basically, it’s a static website, and to the moon. And it’s the opposite with commerce—you basically have to not cache everything, or there are definitely caching strategies that you can go down, but you probably can’t just static cache everything. You probably have a very different profile of users coming back to your website. And so, there are just fundamental differences there that really do require us to think about the way that we approach WooCommerce as: it’s on WordPress, but it’s also quite different from WordPress.

Jonathan:
So then, here comes the tension, right? Because from an engineering perspective, and especially if you didn’t come up in the WordPress space—which is part of why I think you’re in such a unique position—if you came from a proprietary ecosystem, the answer would be clear: “Well, we need to control this.” “Let’s not deal with all these hosts out here. We need to control as much of this as possible.” And you could argue, I think successfully, that from what’s best for the merchant’s perspective, that’s a fair line of reasoning. Let’s give them a great experience. And hosting is a good example of an open-source variable that can have a big impact. But yet, that’s also a big part of why WooCommerce has grown as much as it has. You have this vast ecosystem. And while it’s much harder, I’ve been really happy to see WooCommerce take an approach over the past couple of years of working with the hosts and figuring out, okay, how do we support that? So how do you think about that? And I think for the merchant in particular, ideally, they wouldn’t even have to care about this, but yet there is real-world impact to that. There’s a lot there, but how do you think about that?

Beau:
Yeah, so I think it’s really interesting that you’re sort of bringing it from the merchant’s perspective because we try and do that a lot. Ultimately, even though we know that builders and developers are involved with many WooCommerce deployments, ultimately, it’s a merchant who has to use the product. And so, however we get there, we need to get to a good merchant experience. And frankly, something that we’ve seen over the years is that if you look back originally to the sort of WooCommerce early days, WooThemes days, and then all the way through—frankly, until now—the model for WooCommerce is you get WooCommerce, and then you will definitely add all of these other solutions. You’ll add a payment gateway, a shipping carrier, a tax solution probably, who knows—all sorts of things. Actually, fun fact, I think the number I’ve seen recently is an average Woo store has something like 44 plugins. So you’re talking about a lot of extra stuff.

And so that was intentional. That was the approach—

give builders and merchants the flexibility to get this core and then plug in any solution that they need and mix and match to get exactly what they want. And what we’ve seen over the years is, I guess, two things. One, that introduces a level of decision fatigue, discoverability, and complexity that people don’t actually love. No one really wants to manage a bunch of software. So there’s this level of complexity that it introduces. And then, the other one is frankly that the expectations of people on the internet have changed. WooCommerce has been around for over a decade. Things have changed in that time.

And so, what we are seeing is we actually need, as the platform, as WooCommerce, we actually need to have a little bit stronger of an opinion on what good looks like. And so, you will see us start to shift a little bit more towards, hey, if you don’t have a preference or you don’t have a specific need, you should just use this solution.

Jonathan:
Stronger defaults.

Beau:
Right, stronger defaults, which is theoretically something that WordPress has always had—decisions, not options. This has been a mantra forever, and we’ve usually tried to do that at the technical level, but we haven’t always done it at the sort of product experience level. And you’ll see us do that a little bit more going forward, and that’s directly based on feedback where we’ve just heard, “Look, there are too many things to manage. There are too many choices to make. I actually don’t want to do this. I just want to be told which ones work together. I want them to work really well. I want them to be integrated. If I’m using a specific payment solution, I want to get comprehensive payment reports, and I want it to perfectly handle my taxes,” whatever the combination may be.

And when you’re mixing and matching from the ground up, that level of interoperability can be pretty tricky to get right. So, you’ll see us do a little bit more of that—saying, “Hey, these solutions work together.” We still want to maintain the option—if you don’t want to use that, you’ve still got the flexibility. That’s the beauty of everything being open source and extensible. But if you go that route, then obviously, you’re taking all of that into your own hands, and now you need to figure out, do they work together as well as they could, which is frankly how things are right now. And that’s part of the value that builders provide in the equation—putting together a package of solutions and then making sure that they work well together.

Jonathan:
So, you guys just recently launched the business services category, and to me, that was good. I was happy to see that. It was a good example of, at least from an outside perspective, this continued evolution to take in a more holistic view of the things that merchants need. If you’re a merchant and you’re having any kind of success, there’s a whole series of additional things you are going to need at some point, right? And yeah, I think I’d love to hear more from you on anything that stands out to you in that evolution—the impact of thinking more holistically, of thinking about better decisions, not options, of thinking about that end-user experience. How is that affecting what you prioritize in terms of developing new features and introducing new things like the business services category?

Beau:
Yeah, that’s a great one. So, I guess just to touch on that briefly, for anyone who’s not familiar with it, I guess a few months ago now we introduced the business services tab within our marketplace. And this is basically where you go as a merchant to find sort of WooCommerce-adjacent services. So, the idea is they don’t necessarily need a technology integration; they may not be part of your website or part of your baked-in business workflow, but you need them to run a business. And I think this sort of breaking out of the idea of WooCommerce as just a plugin to, no, for a lot of people, WooCommerce represents their business. It is the hub, how they run their livelihood. And so, what can we do to help them do that? What are all the other pieces that are relevant when running a business, and how do we connect people to those solutions? I think previously, we just relied on, I guess, developers to either do that or for a business owner to engage with a developer and a tax professional or an accountant or whoever, and for them to just figure it out themselves. And if we’re in a world where we’re trying to enable merchants to get up and running and get going, then the more we can do to help them, the better. So, that’s really where that’s coming from.

Jonathan:
I like that a lot. One thing I want to touch on—so I think WooCommerce and WordPress, especially being in Automattic, there’s always been a unique interplay between what’s happening in core WordPress and what’s happening in WooCommerce. I remember WooCommerce was doing early work on blocks, and there was an alignment of interest there, I think because it was at Automattic, that might not have been there otherwise. It was a lot of work to try and figure out how do we do this. And I remember some of the early—at least from my perspective—there was a lot of pioneering work that was done in Woo on improving user interfaces and experiences that also had a positive impact on the work that was happening in core. So, how do you think about the interplay? WooCommerce, to me, is the largest and most impactful sub-ecosystem of WordPress, and that can be something that can be lost at times. How do you think about the relationship between what’s happening in WooCommerce versus what’s happening in WordPress? How does WooCommerce, from an engineering perspective, think about what’s happening in the project and where WordPress itself is evolving?

Beau:
Yeah, I think you’re spot on with the reality that if WooCommerce wasn’t within Automattic, things might be a little different here, and that would impact both WooCommerce and WordPress. The work that you’re referring to, investing early in blocks and thinking about what’s happening in WordPress core, is very much still happening. Actually, a perfect example of that—a couple of examples, actually—the product editor that you’ve seen us working on, if you’re watching the sort of things that are feature-flagged and available, if you jump into the right spot, that’s undergone a couple of really major changes, and there’s probably still another one coming, which is part of why we haven’t pushed that out as any sort of default experience for the majority of users. And that’s because it’s evolving alongside what’s happening in WordPress. And frankly, WordPress itself is still figuring out a lot of things related to full-site editing, to data views, to all these new components and new UX patterns and things. And so, we’re right there with them. We’re actually working alongside core Gutenberg teams and really bringing to them, “Hey, we have this complex experience that’s critical for commerce that you haven’t considered yet. Let’s work together and solve for that.”

Actually, a kind of random good example—we’re having a conversation at the moment around, should data views—so these are effectively the replacement for a WP list table—should they support drag-and-drop? On the surface, you’d say, yeah, absolutely. But there are a lot of scenarios where it breaks. If you’ve got a sort or a filter applied and you change the order, what happens now? So, there’s a bunch of things like that where the fact that we represent commerce, we represent a lot of really complex user interactions and a certain way of interacting with what is technically WordPress (which WordPress focused purely on content may not be taking into account). And so, what I like to think is that WooCommerce is basically one of the most complex applications of anything that WordPress could come up with. And so, if the WordPress platform can support that, it can support almost anything.

Jonathan:
I like that example a lot, and I think one of the strengths—it’s a double-edged sword—one of the strengths is that interplay of content and commerce that merchants see, right? They love the idea of being able to create content, which is often key to the marketing, the sales side of a commerce business. And it’s easy to take for granted—that’s not just trivial in these other platforms. They tend to be, “Okay, this is commerce, and maybe there’s some light content layer.” So, there’s a lot of complexity that comes with that because they’re not the same, yet they can have a clear relationship with each other. But the needs in commerce—it’s a different workflow, different expectations, different problem set, the caching versus non-caching. So, it seems like it’s a lot more work to do that and to stay with that.

As we’re nearing the end, what I’d love to touch on is—you see that work firsthand, and I think that’s increasingly appreciated for those who’ve been in the space for a while and been following. It could be frustrating that things don’t happen quickly. At the same time, I think people who are paying attention can also see that care and consideration and thinking long-term is also part of what you’d want in a steward of the ecosystem. So, for the builders who are listening and they’re looking to the future of WooCommerce, what are some of the things that you would be encouraging builders to be thinking about? Where should they be focusing some of their energy and efforts? Let’s start with the agency folks first. For folks who are building for merchants, they have clients, whether freelancers or agencies, what are some of the things that

you recommend that they be thinking about in the context of where you see the platform going?

Beau:
Great question. Yeah, so I think we’ve talked about blocks and the future of WordPress and where WordPress is going. So, I’d say part of it would be to understand that as much as you can, especially for bigger agencies—I think they tend to be better connected to what is happening with WordPress. So, understand that and be looking at what does this mean for the sites that I’m building, especially on the backend. So, in the admin experience, things are shifting towards blocks, towards this new WP admin design that is sort of coming slowly down the pike—the full-site editor. So, think about how that all applies to the type of work that you do and look at which solutions you’re picking. So, which extensions or plugins are you choosing to build new sites on? Especially, are they compatible with this future? I would frankly be really thinking about that at this point. If they’re not and you are not the developer of that solution, start working with that developer to understand how they can make it compatible with that future. Start engaging with us. Like I said before, we really are out there trying to engage more directly with developers and agencies because we want to hear what is happening out there. I think people actually forget that agencies are often—agencies and solo developers—they’re actually often the front line that’s really understanding the reality of applying software like WordPress or WooCommerce in a way that we frankly may not understand because we are building the software and they’re applying it in certain scenarios. So, getting that real-world feedback loop of, hey, how are you using it? What problems are you running into? Are there limitations we can remove? Are there things that we’re not doing that we should be doing, or whatever?

Really closing that feedback loop with us is the biggest thing. I mentioned earlier, I think we have a community Slack channel—that’s a great spot to start. We have a developer blog, which is at developer.woocommerce.com. There’s a developer-specific newsletter on there now, which I would strongly recommend anyone building for WooCommerce to be on. And then, we’ve started using GitHub discussions pretty actively as well. So, I’d suggest jumping in there. You’ll see RFCs for major changes that we’re looking at doing—things like that. We need real feedback from people who are frankly outside of that cycle of Gutenberg development (and I use Gutenberg there loosely just to refer to the whole roadmap). But yeah, real-world uses of WooCommerce—we want to hear about them.

And I guess I would say—this sounds a little “Matrix-y”—but open your mind a little bit. We’ve heard feedback from builders specifically or developers who don’t necessarily want change. They know how to build for the current system, and they want it to stay the same. We need to change to stay up with WordPress. WooCommerce and WordPress are inextricably tied together. That’s not going to change. So, we are going to stay deeply integrated with WordPress. We believe that’s actually the thing that makes us unique in the market and which gives us the strength and flexibility and the reach of WordPress itself. So, we fully intend to stay integrated with WordPress, and that means that the future is going in a certain direction. So, I would encourage everyone to understand that direction and come along with us.

Jonathan:
I like that a lot. The business services category launch, I think, is a good illustration of what I’m observing in the market, which is a growing interest from products to play in the WooCommerce space. More product companies are coming in, they’re seeing the opportunity, they’re seeing the size of the ecosystem, and that’s been an important part for a long time now—people building extensions. And you’re seeing bigger and bigger companies come in. There’s a full partnerships team at WooCommerce. For the people listening who are building products for the WooCommerce ecosystem, what guidance do you have to offer them? How would you encourage them to be thinking about the evolution of WooCommerce as a platform, as an ecosystem, and what should they be paying attention to?

Beau:
Yeah, that’s a good one. So, I think, as you said, there are a lot of people trying to enter the WooCommerce market, if you like. And for us, we’re in this weird spot. We’ve talked a lot about ecosystem thinking and the community and working with developers and builders, and that is the strength of what we’re doing. But frankly, if we’re to remain running as a business, we also need to commercialize certain parts of it. We need to be part of the money that’s flowing through this ecosystem so that we can continue funding the development of what we’re doing.

So, I mentioned there’s a few sort of central commerce experiences that we’re investing heavily in. I’d say off the top-line list of that is payments, shipping, taxes. These are areas that you’re going to see us invest in heavily, and you’ve already seen us probably building WooPayments. We also recently relaunched WooCommerce Shipping. So, these are areas that we know that it’s critical for merchants to have a great experience, and we believe that the best experience is one that’s going to be deeply integrated with WooCommerce. So, there are plenty of other solutions for payments and shipping in particular where it’s a plugin and then you go use some other dashboard to manage that part of your business. And we fundamentally believe that there is at least a certain audience who want that all in WP admin. They want an integrated experience, they want to be able to bounce between different parts. I mentioned earlier like payments and taxes, let’s say. You can imagine that actually extending to all three—so, if you’re taking a payment that includes taxes, that covers shipping, you want to be able to understand all of that in the performance of your business. And if that’s spread out across multiple systems, that can be really difficult. So, I’d say we’ll be investing more heavily in those areas, which is not to say that other people shouldn’t, but I guess know that we will be playing in those spaces a lot.

Jonathan:
For someone who is coming into the space—you just made that point about the importance of the integrated experience. If they’re new, how would you encourage them to be thinking about that? For instance, in the business services category, you introduced banking, for instance. And unless your intention is to get into banking (which, who knows?), but it’s—for someone who’s in the banking space and coming in, how would you be encouraging them to be thinking about things like that? Should it be integrated? There’s not existing precedent, right? It could be outside the space; they could go to a separate dashboard. How would you think about that example?

Beau:
Yeah, banking is an interesting one. Obviously, that’s a really complicated space.

Jonathan:
But also fundamental to commerce.

Beau:
Fundamental to commerce, pretty connected to payments, interestingly. So, it is an area that we’re sort of touching on. But I would say in general, what we would love to see more of is people who are really thinking about WooCommerce as a whole complex system and how can they build something that’s part of that complex system rather than, “I represent banking; I want to just make my banking visible.” That’s the first step. But actually building it in some sort of integrated way is really where we see things succeed more.

So, I mentioned that the business services tab is largely for things that really probably won’t integrate deeply or are somewhat separate or somewhat adjacent to the website itself. There may be some crossover—so actually, banking is maybe a good one. We probably could, and probably will, have more flows and better seamless handoff between your WooCommerce store and whatever that banking solution is. But we’re probably not going to, for example, replicate your entire banking website and banking experience all within WooCommerce. In business services, just as a specific example, I think is also really interesting for connecting things like developers. And this is an interesting sort of crossover—one of the services you may need as a business is a developer to customize your business website.

Jonathan:
Right.

Beau:
So, I think there’s an interesting crossover there, which we’ve just started exploring—opening up the ability for merchants to get access to various forms of technical support, to use a loose term there, as part of running their business.

Jonathan:
Well, I’m excited. There’s a lot to the ecosystem, and I think this is why you coming on episodes like this is especially helpful from my perspective, to give a broader sense of what’s going on behind the scenes. And I really appreciate you taking the time to share. We’ve given folks a lot of things to think about and work with. If someone wants to reach out to you, Beau, what’s the best way to get in contact?

Beau:
The best way is probably to tweet at me, or I guess “X” at me, however you say that now. Yeah, you can get me on there. It’s just @BeauLeins, which I’m sure we can put in the show notes or something for the spelling. Or frankly, you can also just email me: beau@automattic.com.

Jonathan:
Excellent. Beau, thank you for the time. Thank you for the work that you and the team have been doing, and talk to you soon.

Beau:
Yeah, thanks, Jonathan. Appreciate it. Been fun.

Share this episode
Sponsors
Open Makers (archived)