Big Brands using Multi-storefront on BigCommerce Part 2 with Brent Bellm (Live from ShopTalk)

Just going back to to multi-store front the, if we put all these pieces together, you have a solution now that will work across borders, across currencies, across languages maybe help us understand how big you've already helped us understand how big of a hurdle it was, but some of the solutions now that people can go to market with and the speed in which they could do.

Yeah. So one example I love to use. I think it might've been the first or second multi-store customer to go live with us in beta.

This was months ago. This was last year. It's company called The Bullet Group that had. Motorola rugged phones. So these are phones that you can they're dustproof waterproof drop proof, rugged phones, and another brand called cat phones, like Caterpillar phones that they sell all across Europe.

They launched. I think they're up to I don't know, 20 plus stores for each of those two brands that are selling different currencies, different languages, all around the world. And they did this in a headless way. Meaning they've got, I think a WordPress front-end is the design. And then the backend is Big Commerce multi-store and it's a multi geo scenario.

Ted Baker is doing the same thing. Ted Baker just launched this great apparel brand. They have something like a dozen different stores, different languages, and different currencies. Again, that's the multi-tiered. Use case, but you could also instead do a multi-site current use case. Like maybe your initial store sells to consumers, but then you wanted a B2 B store to sell to your wholesalers and your retailers.

You can do that with multi-store. You could also come up with different brands. Sub-brands promotional launches, a store that you spend off and then spend. And the power of this is that when you spend one of these stores up, you can use the same integrations that were on your main store, all the investment you put into building that initial big store, integrating into your ERP or accounting system, your email marketing, whatever your payment solution is.

You don't have to replicate all that work. You can leverage it. That's really the power and the speed of multi-store, but I think it's illustrative that those first couple of examples I gave you they have a dozen or more stores and they did it out of the gate.

And I think the difference right now in the landscape of SaaS at least is the other, your competitors are all having to have a storefront and a different backend. And then they have to figure out how to manage all those multiple backends.

That is correct.

You're letting the client effectively manage one place, one place to do everything and then distribute out those SKUs and even multiple currencies with different checkouts in different countries.

My understanding is that with Shopify, you can clone a store and it's pretty easy to clone a store. You push a button. You've got another store. That's like your initial store, same theme, same integration, same currency of that. You can't do multi-store, which is one account. And then start changing all of that changing the theme and the currencies and the that have like same integration, same backend one account, one store, lots of storefronts.

You have multiple stores and we've always been able to do that too. This is much more powerful. This is. Very appropriate for many of the world's mid-market and large enterprise businesses who do have multiple brands, segments, and, or geographies, but so many small businesses want to do the same thing.

And that's one of the neatest things that we'll be doing next. We the announcement today is live launched for our enterprise stores, but we'll be bringing this to our small business stores, our $30 a month for $80 month. Our $300 a month plan, you'll be able to click a button at a store and boom, there you go. Storefront, I should say.

So you did mention that these cons are these new things coming up for the smaller merchants. What else is coming up with? Multi-store front? What are the things we have to look forward to?

So in addition to bringing it to a small business and click of a button store addition, another major area of investment for us is in international capabilities within our native Stencil framework.

So having multi-language we already have multi-currency, but especially multilanguage and some other geographic capabilities built into individual stores. Multi-store front will benefit from this. If you're using. Our native design framework and theming engine called stencil. If you don't want those limitations today, then you can go headless with us and do your front end and WordPress or content stack or content full or pick any other front-end framework.

We're a leader in headless but we're bringing some of that native in as well. And then a final release, which should happen next month. It's March should happen next month in April is multi location inventory. So this is also going to be helpful because for businesses who have multiple warehouses and, or the addition of retail point of sale, we'll have the full inventory API capabilities for you to use logic within Big Commerce to track.

Where is the inventory for each SKU, and then present that either to the customer. If the customer wants to make a choice, buy online pickup in store or within your shipping optimization to say customers located here closest warehouse is there shipped from that warehouse. So a multi-location inventory APIs are coming out soon and that's quite complimentary.

Multi-store front and the

multi-store, the multi location inventory is going to help in the omnichannel world. If somebody is trying to connect some of their outbound POS systems into Big Commerce, that'll allow the, that inventory to be available to the storefront. Yes. And today you can manage that logic outside of Big Commerce, but bringing it in is nice and scalable.

It's the sort of thing that would let us, for example, we're integrated in partner. With point of sale platforms like Teamwork Commerce, and Square and Clover. Another differentiator from Shopify who has its own proprietary. One size fits all point of sale. We partner with the market leaders and EPAD now in Europe ISEL these partners can then integrate the knowledge of inventory counts that they have in individual stores into the API.

And then the merchant who may be. Remote ship warehouses that are outside. The point of sale can integrate those as well. And so that complexity can all be orchestrated within Big Commerce relieving you from having to have an outside order management system or ERP that's handling all of that.

A lot of your enterprise clients are going to have an ERP there's this enhances that allowing actually to connect multiple ERP is each store or each you can grab the inventory from each of those ERP systems with the multi, with multiple inventory locations. So you'd have to have that. So that's right. I think that, that gives another advantage to that. We did mention a little bit about headless and I'm always interested in headless.

Where do you think headless is going in the next five to 10 years? Do you think the the idea of having this of a monolith where we have an easy. Easily added front end that's part of the system. Or do you think a lot of stores are going this headless route?

I think headless will only grow. For example, when people talk about the metaverse, if you start creating storefronts in the metaverse that won't be based on pre-packaged themes coming out of Big Commerce or Shopify, you'll be designing that outside of our framework and then integrating a Big Commerce in as a backend, more broadly.

There is a very rich set of frameworks and content management systems and digital experience platforms that companies can use for their front ends. I gave the Ted Baker example, they're using BloomReach, which is a re...