Today's Deep-Dive: Vendure
Ep. 289

Today's Deep-Dive: Vendure

Episode description

This deep dive explores the concept of headless commerce and introduces vendor, an open-source, enterprise-ready framework designed for complex B2B sales and multi-vendor marketplaces. Unlike traditional all-in-one platforms, headless commerce decouples the front-end (customer interface) from the back-end (commerce logic) using APIs, offering greater flexibility. Vendor, built with TypeScript and Node.js, provides a robust commerce framework and a customizable admin dashboard. Its key advantage lies in its extensible plug-in architecture, allowing businesses to tailor the platform to unique needs, such as intricate B2B pricing, multi-step approval chains, marketplace management, and custom D2C experiences. The platform emphasizes developer experience with tools like GraphQL for efficient data fetching and a CLI for automation. Vendor offers full ownership and control, with a GPL v3 license for the core and optional commercial licenses for enterprise support. The project boasts a healthy ecosystem with significant GitHub stars, forks, and a large contributor base, alongside an active developer community. Ultimately, vendor represents a shift towards flexible, developer-centric solutions for businesses whose models outgrow standardized platforms, potentially becoming the new default in e-commerce.

Gain digital sovereignty now and save costs

Let’s have a look at your digital challenges together. What tools are you currently using? Are your processes optimal? How is the state of backups and security updates?

Digital Souvereignty is easily achived with Open Source software (which usually cost way less, too). Our division Safeserver offers hosting, operation and maintenance for countless Free and Open Source tools.

Try it now!

Download transcript (.srt)
0:00

Welcome to the deep dive your essential shortcut to gaining real knowledge quickly.

0:04

Hey everyone. So today we're

0:06

We're really diving into the engine room of modern enterprise retail. We actually

0:11

had a request from a listener. Oh, yeah

0:13

Yeah, someone looking to understand how these

0:15

Massive companies, you know the ones handling complex B2B sales are running huge

0:20

multi-venture marketplaces

0:22

Uh-huh how they manage their commerce ops without just using simple off-the-shelf

0:26

software, right?

0:27

We're definitely moving way beyond the basic online shopping cart here. Our mission

0:31

today is

0:32

Well, it's to demystify one of the biggest shifts in digital commerce this whole

0:37

idea of headless architecture

0:38

And we're gonna use a framework called vendor as our guide

0:42

We'll explain why this kind of customizable open source solution is becoming well

0:46

pretty essential for businesses with really complex

0:50

Unique needs especially trying to make it clear for beginners. Exactly. We've been

0:55

digging through the key info

0:57

pulling insights straight from

0:59

The vendor github repository their docs in there kind of core marketing philosophy

1:04

It really spells out why they're built for scale and flexibility

1:07

Okay, but before we unlock the power of headless commerce, let's quickly thank the

1:12

supporter of this deep dive

1:13

This segment is brought to you by safe server great partner

1:17

Yeah

1:17

Safe server takes care of the specialized hosting you need for advanced software

1:20

like vendor and they support you on your whole digital transformation journey

1:25

You can find out more and get started at

1:27

www.safeserver.de

1:30

Awesome. Thanks safe server

1:32

Right, then let's focus on vendor. It calls itself a customizable commerce platform

1:38

built for scale

1:39

Okay, so let's start at ground zero for our learner

1:42

Like you said when most folks think about selling online

1:44

They probably picture one single platform doing everything right the storefront

1:48

inventory payments. Yeah all in one

1:51

So what exactly is headless commerce and maybe more importantly?

1:56

Why would a major company pick a specialized open source thing like vendor over say

2:01

a big standard sauce platform?

2:03

Yeah, that's the key question

2:04

See the core problem with those traditional all-in-one systems is they can be

2:07

really rigid

2:08

Everything's tightly coupled tightly coupled meaning the front end the website the

2:13

customer sees is stuck together with the back end the inventory the pricing

2:16

Logic all that stuff. Yeah, if you want a new mobile app or maybe some fancy voice

2:19

interface

2:20

Yeah, you just have to hope your big platform supports it easily often. It doesn't

2:25

headless commerce completely decouples those parts think of it like

2:30

Like a body and a head they're separated but they're connected by let's say a

2:36

central nervous system and that nervous system

2:38

That's the API the application programming interface precisely vendor is the body

2:43

in this analogy

2:44

It's that robust back end built with TypeScript and no JS. This is the brain the

2:50

logic center

2:50

Inventory pricing rules order security everything

2:54

Okay, the head is the front end the part that customer actually interacts with and

2:58

that could be anything a website sure

3:00

But also a mobile app of VR experience, maybe even a smart kiosk in a store

3:03

So the vendor core doesn't really care how you're shopping whether it's your phone

3:07

or some smart fridge screen

3:09

It just does the commerce part exactly that and that separation is absolutely key

3:13

to doing real

3:14

Multi-channel commerce effectively you use the same single back end that vendor

3:19

core to power every single customer touch point

3:22

You can dream up and for big companies that consistency and scale is

3:26

Critical got it. So the source is defined vendor as an open source headless

3:31

commerce platform an enterprise ready framework

3:34

Let's talk tech for a second. Why type script and no JS. What's the benefit there?

3:40

Well, it's really a choice geared towards stability and speed type script. It adds

3:45

static typing to JavaScript for non-devs

3:48

That just means the code is more robust less prone to certain kinds of errors

3:52

Developers can build faster and with more confidence fewer bugs basic your bugs.

3:56

Yeah, and no GS

3:57

It's built for handling lots of connections at once high concurrency means the

4:00

platform is designed for speed and can handle massive traffic spikes without

4:04

You know falling over which is important for enterprise scale

4:06

And what is the core platform actually give you right out of the box? It provides

4:10

two main pillars really first

4:12

There's the commerce framework. They describe it as lean unopinionated foundational

4:17

blocks

4:17

It's built on another powerful framework called nest.js nest.js. Yeah, I think of

4:23

nest.js is like a

4:24

Really solid well understood architectural blueprint for building complex

4:28

applications

4:29

It helps ensure the whole system is structured logically like a big organized Lego

4:34

kit

4:34

Scalable defendable. Okay Lego kit. I like that and the second pillar that sounds

4:39

like it's more for the business users

4:41

The ones not writing code exactly. That's the operational side a highly

4:44

customizable admin dashboard

4:46

This is the interface for the day-to-day stuff managing orders products customers

4:51

pricing

4:52

Yeah, it's built with modern tools like react and tailwind. So it feels

4:55

Well modern. Yeah, not like some clunky system from 10 years ago, right and

4:59

something that really jumped out

5:01

Especially thinking about developers is the speed they claim you can get started

5:04

the sources boast vendor can be up and running locally in

5:07

Less than two minutes. Just one command. Yeah, that seems fast that immediate

5:11

feedback must be a huge draw

5:13

Oh, it absolutely is that rapid setup just lowers the barrier to entry massively

5:18

teams can kick the tires test it out

5:20

Almost immediately see if it fits. Okay, but let's pivot to the really critical

5:24

question the trade-off

5:26

Why would a huge company choose to build their commerce system on an open source

5:30

framework?

5:31

I mean that means taking on more the engineering load themselves, right?

5:35

Why not just pay a subscription to a big convenient sauce platform? That is the

5:40

core conflict, isn't it?

5:41

It's control versus convenience saws definitely offer simplicity upfront

5:45

But you are fundamentally constrained by their platform their features their

5:50

roadmap. You're locked in they're locked in

5:52

Vendor is explicitly built as they say for when standard saws platforms can't

5:57

accommodate your unique business model

6:00

If your business needs something special and you have to create three clunky

6:04

painful workarounds

6:05

Just to launch your new product line on a saws platform. What's not convenient

6:09

anymore. Is it?

6:10

It's actually holding you back costing you time and money. Okay, so if my business

6:14

has really complex needs

6:15

Maybe I offer a unique service alongside physical products or I have intricate

6:20

loyalty tiers or

6:22

Weird shipping rules. I need a system that bends to my needs not the other way

6:26

around precisely and that deep

6:28

Customization is primarily handled through vendors extensible plug-in architecture.

6:33

This is the key

6:34

This is where you build that say 10% of unique functionality that really differentiates

6:38

your business, right?

6:39

You can tailor pretty much every single aspect of the commerce solution using these

6:43

dynamic plug-ins and they become reusable modules, too

6:47

So you're not hacking the core system. You're extending it properly in a structured

6:51

maintainable way. That makes a lot of sense

6:53

What about those big enterprise level features? Does it handle things like global

6:58

operations out of the box?

6:59

Yes, internationalization is built right in from the start. It's designed for

7:03

seamless global operations

7:05

It supports multi currency transactions cross-border omni-channel commerce

7:09

Complex tax rules all without needing massive re-engineering later on okay and

7:15

critically important for big companies

7:16

Mm-hmm security and ownership. We keep hearing vendor is 100%

7:21

Independent OSS open source software

7:24

What does that actually mean for a company putting its business on this platform?

7:29

It means they achieve full ownership of the platform. That's a really powerful

7:33

argument, especially for large

7:35

Maybe more risk averse organizations

7:37

They avoid being tied to the whims the roadmap changes the sudden pricing hikes of

7:42

a closed proprietary SaaS provider

7:44

They control their own destiny technologically speaking doesn't open source

7:48

sometimes come with worries about support maintenance

7:51

Guarantees if something breaks who fixes it

7:53

That's a fair point and that's where the licensing model comes in

7:56

The core platform is licensed under the GPL v3 now for the listener

8:01

This basically ensures the core code stays free and open the community can review

8:04

it improve it use it

8:06

But for those large enterprises that need, you know legal assurances dedicated

8:11

support channels guaranteed response times

8:13

They offer a commercial license to the VCO this list companies manage their risk

8:18

effectively

8:18

While still getting all the flexibility and ownership benefits of the open source

8:23

core

8:23

So you get the ownership and the flexibility but you can buy a safety net if you

8:26

need it. Got it

8:27

Okay, let's shift gears now to the practical side. Where is all this power actually

8:32

being used?

8:33

When we talk about complex commerce, what specific real-world business models are

8:39

we seeing vendor enable?

8:40

Yeah, vendor really seems to shine in I'd say three main areas where those

8:44

traditional

8:45

Simpler commerce solutions tend to struggle or just break down completely. Okay

8:49

area one first up B2B e-commerce business to business

8:52

Right. Give us a simple example of why a standard online store platform often fails

8:57

here

8:58

Well, B2B is just fundamentally more complex than selling directly to consumers,

9:02

right?

9:02

Think about a distributor network. Maybe customer a gets a special 15% discount,

9:07

but only on bulk orders over ten thousand dollars

9:10

Meanwhile customer B needs all their orders over

9:13

$5,000 to be approved by two different managers in their company before the order

9:18

is even processed a

9:19

Typical D2C platform just can't handle that kind of granular logic. Yeah

9:23

So vendor allows companies to take these really complex workflows things involving

9:28

custom pricing tiers per customer

9:30

multi-step approval chains

9:32

Deep account hierarchies where one person manages multiple sub accounts and turn

9:37

them into smooth reliable digital experiences

9:40

It adapts to those specific industry needs that level of custom roles. Yeah,

9:44

definitely beyond the usual Shopify store

9:46

Okay, what about marketplaces? That sounds complex, too

9:49

That's the second major area multi-vendor or multi-tenant commerce think building

9:53

your own Etsy or maybe a specialized b2b marketplace

9:56

Or even an Amazon competitor if you're ambitious building that requires really

10:00

sophisticated tools

10:01

You need to manage potentially hundreds or thousands of separate sellers each maybe

10:06

with their own separate inventories

10:08

You need to give them customizable storefronts so they can maintain their brand

10:12

identity

10:12

They need their own individual seller dashboards to manage their products and

10:17

orders

10:17

Wow. Yeah, and all the while the central platform operator

10:21

You needs to handle the commissions the payout schedules the overall permissions

10:26

taxes

10:27

It's a huge architectural challenge and vendor provides the framework to manage

10:31

that complexity without building everything from scratch

10:34

Okay, b2b marketplaces. What's the third area custom D2C exactly custom D2C models?

10:41

This is really about breaking free from what they call cookie cutter commerce

10:44

It's for brands whose business model is their unique selling proposition. Give me

10:48

an example

10:48

Okay, think of a company selling highly personalized maybe made to order furniture

10:53

They might have a dynamic 3d configurator on their website where you choose the

10:57

wood the fabric the size and that

11:00

Configuration needs to link directly to complex supply chain logic, maybe even

11:04

trigger specific manufacturing processes

11:06

Or think about a subscription box service with five different tiers

11:10

Complex bundling rules variable shipping schedules and maybe add on purchases

11:15

things that require unique logic unique logic

11:18

Exactly, if your brand's vision relies on that kind of custom experience

11:22

Maybe blending digital and physical touch points in a novel way

11:26

Vendor use you the underlying toolkit to actually write and execute that unique

11:31

business logic

11:31

Okay, so for those kinds of complex niche applications, the flexibility is

11:35

definitely worth the extra engineering effort compared to sauce

11:38

Let's talk about that engineering effort for a sec the developer experience or DX

11:43

What is the tech stack offer developers to make building and crucially maintaining

11:48

these complex systems easier?

11:49

Yeah, they seem to focus heavily on tools that boost developer productivity and

11:53

importantly maintain ability

11:55

We already mentioned TypeScript in nest.js which provide that structure and safety

11:59

net and crucially a really big one

12:01

Is that they expose pretty much all their functions in data via graph QL. Okay

12:06

graph QL for the beginner listening

12:08

What does graph QL actually do for the business? Why is that better than older ways?

12:12

Okay, think of it like a

12:13

Really efficient very specific waiter in older systems using something called rest

12:20

API's

12:21

often when your app asks for data the server might send back a whole bunch of

12:26

information maybe way more than you actually need for that specific

12:29

Screen like getting the entire menu when you just ask for the price of coffee

12:33

wasted data exactly wasted data wasted bandwidth

12:37

Graph QL lets the developer writing the front-end app request exactly the specific

12:41

pieces of data

12:42

They need for that particular view and absolutely no more

12:45

Just give me the product name price and inventory account for this specific ID

12:49

Okay, this dramatically reduces the amount of data flying back and forth which

12:53

makes the website or app feel much faster much more responsive

12:57

Especially on mobile networks. It's way more efficient and those saved milliseconds

13:01

as we know can translate into millions in revenue for big e-commerce sites

13:05

Absolutely performance is key. They also focus a lot on automation tools for

13:10

developers. They provide a CLI

13:12

That's a command line interface basically text commands and an automation SDK a

13:16

software development kit

13:18

Okay, that sounds like pure tech jargon again

13:20

Can you translate the business benefit of a CLI and an automation SDK? Sure think

13:25

of it like this

13:26

These are tools that automate the boring repetitive error prone parts of coding

13:32

testing and deploying the software

13:34

Okay

13:35

So it helps streamline the workflow when a developer makes a change say they add a

13:39

new discount rule

13:40

These tools help ensure that change gets automatically tested in various ways and

13:44

the deployed reliably across the entire system

13:47

Maybe to multiple servers it saves tons of developer time

13:50

Reduces the chance of human error during deployment and helps keep the whole

13:53

complex infrastructure running smoothly and consistently

13:56

It's about efficiency and reliability got it less manual work fewer mistakes

14:01

Okay, and finally the lifeblood of any open source project like this the community

14:06

What do the sources tell us about the health and activity of the vendor ecosystem?

14:10

Is it alive and well?

14:10

Yeah, the stats look pretty solid. Actually, it's a good sign of project health on

14:15

Github, which is where the code lives. It has six point six thousand stars and one

14:19

point two thousand forks

14:20

That indicates quite a bit of active interest in usage stars and forks

14:25

Basically measures of popularity and people tinkering with it pretty much. Yeah

14:29

popularity and engagement

14:30

But maybe more importantly it has a large contributor base

14:34

239 contributors listed Wow

14:36

239 people have actually submitted code or improvements. That's significant

14:41

That means a huge amount of peer review and development happening outside of just

14:45

the core founding team

14:46

Correct that diversity of contribution is really healthy for an open source project

14:50

The source has also mentioned an active community of over 3,000 developers globally

14:55

interacting in places like slack or discord and there are testimonials highlighting

14:59

the quote

15:00

Astonishing level of involvement from the core vendor team themselves in those

15:04

community channels

15:06

providing apparently fast and helpful support

15:09

For an enterprise that's going to rely on this platform as a core piece of

15:12

infrastructure for years having that active supportive ecosystem is

15:17

Basically a non-negotiable requirement. It provides confidence. Absolutely

15:20

Okay, let's try to wrap this deep dive up thinking back to our learner the person

15:25

just trying to get their head around this complex

15:27

commerce landscape

15:30

What's the key takeaway here? What does vendor really represent?

15:33

I think vendor represents the modern necessity for businesses whose models just don't

15:38

fit in the standard box

15:39

It's the flexible powerful back-end the body for commerce systems that have

15:44

fundamentally outgrown the limitations of those

15:46

Easier but more rigid standardized sauce platforms, right? It provides that

15:51

essential separation

15:52

the headless architecture we talked about

15:54

Allowing you to build any front-end you want and it gives you the enterprise grade

15:58

tools and the extensibility needed to manage truly complex

16:02

Business logic whether that's b2b marketplaces or unique DTC offerings

16:07

So it frees businesses from the constraints of someone else's pre-built roadmap

16:12

Exactly by offering true code ownership and massive extensibility

16:17

It's the ultimate customization toolkit really but specifically designed for

16:22

commerce complexity

16:23

Makes sense the ultimate customization toolkit for commerce complexity

16:26

I like that and before we sign off just a final reminder that this deep dive was

16:30

supported by safe server

16:31

They're your partner for the specialized hosting and digital transformation

16:34

solutions that help you actually leverage the power of platforms like vendor

16:38

You can learn more at www.safeserver.de

16:42

Thanks again safe server

16:44

okay, finally as always a provocative thought for you the listener to consider as

16:48

The demand for these hyper customized online experiences keeps growing needing

16:54

complex b2b pricing unique subscription models

16:57

Multi vendor logic will this shift towards flexible developer centric headless

17:01

frameworks like vendor actually become the new default

17:04

Could they eventually leave the traditional monolithic ecommerce platforms behind

17:09

kind of like relics gathering dust in the face of accelerating digital?

17:13

Complexity hmm definitely something worth mulling over where does the balance

17:17

Thanks for joining us on the deep dive. We'll catch you on the next one

17:17

Thanks for joining us on the deep dive. We'll catch you on the next one