Vendure Engineering

Vendure development by the people who build its plugins

Vendure is the right commerce framework when you need full ownership of your business logic in TypeScript. When a hosted platform serves you better, we will say exactly that.

Oronts engineers Vendure commerce systems from Munich: headless storefronts, custom plugins, B2B capabilities and migrations. We wrote the Data Hub ETL plugin, published open source, and run Vendure-grade architecture in production.

Scope your commerce project Book a 30-minute call

CartCheckout

HeadlessB2B pluginsOwn the logic

The stack we build on

Vendure

When Vendure is the right call

Choose Vendure, the open-source headless commerce framework, when your business logic is the product and you want to own it in TypeScript. It fits when off-the-shelf shop rules break under real B2B complexity: customer-group pricing, quotes, approval chains, multi-channel catalogs, ERP and PIM sync, and a storefront you control over GraphQL. You keep the code, the data, and the deployment. The trade is that it is a framework, not a hosted product, so it rewards teams that have or want engineering ownership. Where a hosted shop covers the need, we will tell you plainly in the first call.

Headless by design: any storefront, app, or B2B portal over one GraphQL API
B2B is native territory: customer groups, quotes, approval flows as typed code
You own the source, the database, and the hosting, no vendor lock-in
Deep integration with ERP, PIM, and payments through engineered pipelines

Proof before promises

Vendure Data Hub

Open Source

Enterprise ETL plugin: 9 extractors, 61 transform operators, 24 entity loaders, marketplace feed generators. Published open source on GitHub.

View on GitHub

Customer Intelligence

Oronts Product

Wishlists, verified-purchase reviews, loyalty and cart recovery as one coherent engagement domain on Vendure's event bus.

See in portfolio

Headless commerce guide

Published

Our architecture thinking is public: how we design Vendure systems, when headless pays off, and where the traps are.

Read the guide

Production AI on commerce

Live

Agentic commerce is coming. Our published protocol work covers how AI agents buy safely: approval gates, receipts, audit trails.

Read the protocol

$addB2BPricing(ctx, order, customerGroup)|

How a Vendure B2B commerce flow fits together

One backend, one GraphQL API, every channel and system connected through it.

Storefronts

Web
App
B2B portal

API gateway

GraphQL

Commerce services

Catalog
Pricing
Orders
Customer groups

Integrations

ERP
PIM
Payment

Storefronts and the B2B portal call a single GraphQL gateway. Behind it, Vendure runs catalog, pricing, orders, and customer groups, while engineered pipelines keep ERP, PIM, and payments in sync. You own each layer.

What we do with Vendure

Vendure implementation

Complete commerce builds: catalog architecture, checkout, payments, shipping, search and a React or Next.js storefront connected over GraphQL.

Custom plugin development

Plugins built to Vendure's extension patterns in TypeScript, with automated tests and documentation. The same standard as our published Data Hub plugin.

B2B commerce on Vendure Core

Customer-specific pricing, quote workflows, approval chains and organization accounts engineered as custom plugins on the open-source core.

Migration and replatforming

From WooCommerce, Magento, Shopware or custom shops to Vendure, with data migration through pipeline engineering instead of one-off scripts.

ERP and PIM integration

Order sync, inventory, product data: connected with idempotent, monitored pipelines. This is literally what our Data Hub plugin was built for.

Enterprise readiness

Multi-channel setups, performance under real catalog sizes, observability and deployment architecture for teams that run Vendure seriously.

Fixed scope

Vendure architecture review

Two to four days: we review your Vendure installation or your replatforming plans, assess plugin architecture, data flows and scaling risks, and deliver a written engineering assessment with a concrete roadmap.

Fixed price, scoped to your system. Request the exact quote.

Request the review

Built for your team

Headless commerce is a committee decision. Here is what each seat needs to see.

CTOs and IT leaders

You want headless commerce you control, not a SaaS you rent.

Open-source Vendure with custom B2B logic, your code, model-neutral integrations, no lock-in.

Startup CTOs and founders

You need to launch commerce fast without boxing in the roadmap.

A focused Vendure pilot in 90 days, then scale on a stack you own.

Agencies and partners

Your client needs senior headless commerce under your brand.

White-label Vendure delivery; our Data Hub plugin is open-source, with Customer Intelligence as a proprietary product on the same core.

Enterprise and procurement

Procurement needs auditable B2B workflows and clear exit terms.

Auditable order logic, full handover, AVV and TOM readiness.

How we deliver Vendure

From commerce fit to a launched, owned platform: scoped, built and supported by senior engineers, with the plugins and the roadmap in your hands.

Discovery & fit

We scope your commerce model, B2B rules and integrations, and confirm Vendure is the right fit before committing.

Commerce model
B2B rules
Integration map

Architecture & plugins

We design the Vendure architecture and the custom plugins your case needs, on top of the open-source core.

Plugin design
Data model
Auth & roles

Build & integrate

We build the storefront, the plugins and the integrations: ERP, PIM, payment and search, wired cleanly.

Storefront
Plugins
ERP / PIM

Launch

Staged launch with data migration, testing and a cutover plan that targets zero downtime for your customers.

Migration
Testing
Cutover

Scale & support

We tune, extend and support the platform, with the code, the plugins and the roadmap owned by you.

Performance
Roadmap
Support

Vendure in 2026: what the platform shift means

Vendure restructured in 2026, and the change matters for every build decision.

Vendure Core stays open source

The open-source project, now Vendure Core, remains MIT-licensed and TypeScript-native. Everything we build on it you own completely. The framework reached version 3.6 with a steady release cadence and an active community.

Enterprise features go commercial

SSO, advanced B2B pricing, quotes and approval workflows, organization hierarchies: these ship as commercial enterprise features, with Vendure Cloud announced for late 2026. The build-versus-license decision is now real: custom B2B plugins on Core versus the enterprise tier. We engineer both paths and tell you honestly which fits your case.

The German Vendure gap

Vendure adoption is growing in Germany while almost no German agency has published Vendure engineering work. We have: our Data Hub plugin is open source, our architecture guides are public, and our commerce engineering is documented in the portfolio. That gap is your advantage when you need a partner who has actually shipped on this framework.

Hosted shop, self-run Vendure, or Vendure with Oronts

The same framework gives very different outcomes depending on who engineers it. This is where a hosted platform stops, where self-running Vendure leaves you, and what changes when we build and own the hard parts with you.

Scroll sideways to compare all three columns.

	Hosted shop	Vendure (self-run)	Vendure + Oronts
Headless flexibility (any storefront)
B2B features (customer groups, quotes, approvals)		Build it yourself
Full data and code ownership
Deep ERP / PIM integration		Custom work	Data Hub plugin
Control over checkout and business logic
Production architecture and observability	Vendor-run	Your responsibility
Senior engineering team behind it		If you have it

A check means the capability is there out of the box. A minus means it is partial or needs work. Text cells say what it actually takes.

Where Vendure earns its place

Six situations where a TypeScript commerce framework beats a hosted shop, and the outcome we engineer for each.

B2B distributor

Replatforming from WooCommerce that buckles under real catalog and pricing complexity

A clean Vendure rebuild with customer-group pricing, bulk ordering, and account hierarchies, plus an engineered data migration so order history and customers move intact.

Manufacturer

Every customer segment needs its own negotiated price list and the current shop forces one global price

Customer-group and contract pricing built as typed plugins on Vendure Core, driven by ERP-synced price lists, so each buyer sees their agreed terms at login.

Multi-channel brand

One catalog has to feed a web storefront, a native app, and a partner portal without three separate backends

A single Vendure backend exposing one GraphQL API to every channel, so catalog, pricing, and orders stay consistent while each frontend stays independent.

Procurement-driven seller

Enterprise buyers want marketplace listings and punchout into their own procurement systems

Marketplace feed generation through the Data Hub plugin and punchout-style integration engineered against the buyer's procurement flow, so you sell where your customers buy.

Conversion-focused team

A hosted checkout blocks the custom flow, financing step, or B2B approval the business actually needs

A bespoke checkout built directly on Vendure's order process and state machine: your exact steps, your validation, your payment logic, with nothing locked behind a platform.

Scaling commerce org

The team wants to stop renting its commerce platform and own the stack end to end

Vendure deployed in your cloud with production architecture, observability, and documented plugins, handed over so your engineers can run and extend it without us in the loop.

AI product enrichment

New SKUs land in the catalog with bare titles and no SEO or merchandising copy, slowing every launch

AI enriches products from their structured data into titles, descriptions, and facets, written back through Vendure with a review step so an editor approves before they go live.

Agentic checkout assist

B2B buyers want a guided way to assemble large or repeat orders without clicking through the whole catalog by hand

An agentic assistant proposes carts and reorders against your real Vendure catalog and pricing, while the order itself stays behind your normal approval and confirmation steps.

Catalog data-quality

Broken prices, missing images, and duplicate variants slip into the live shop and surface as customer-facing errors

Catalog data-quality checks flag outliers and incomplete records against your rules, so the team fixes them in Vendure before they reach the storefront.

Replatforming you onto Vendure, in stages

Moving a live shop to Vendure is a sequence, not a switch. We replatform you onto Vendure Core in defined stages, each verified against a copy of production before it touches anything customers see. The result is a TypeScript commerce system you own end to end, delivered without a surprise downtime window.

Current-state audit

We map your existing shop in full: catalog and variant structure, customer and order data, payment and shipping setup, ERP and PIM integrations, and the custom logic the business depends on. The output is a clear inventory of what migrates to Vendure cleanly, what is rebuilt as plugins or storefront, and what is retired.

Model the domain in Vendure

We model your catalog, variants, channels, and B2B rules in Vendure Core: product structure, customer groups, pricing, and the order flow your business actually runs. Decisions like build-versus-license for B2B pricing or quotes are made here, on facts, before any storefront work starts.

Build server, storefront, and plugins

We build the Vendure server, the headless storefront over GraphQL, and any custom plugins your domain needs, to the same standard as our published Data Hub plugin. Each plugin ships with tests and documentation so your team can read and extend it, not just run it.

Staged data migration and integration

We migrate data in increments through idempotent pipelines, the discipline our Data Hub plugin encodes, and connect ERP, PIM, and payment providers one system at a time. Every increment is verified against a copy of production before the next begins, so a re-run is safe and nothing is lost in transit.

Validation and controlled cutover

We validate catalog, pricing, order flow, and integrations against criteria agreed with you, then run a controlled cutover with a defined fallback. We stay on hand through the first production cycle, and you keep the source code, the data, and the runbook to operate it without us in the loop.

What your buying committee needs to check

The ownership, hosting, and support facts a procurement and IT review will ask about, answered up front and without fabricated certifications.

Code ownership: Built on the MIT-licensed Vendure Core. Every plugin, storefront, and integration we write is yours: full source, in your repository, with no Oronts license gate on running or changing it.
Hosting in your cloud: Deployed into your own AWS, Azure, GCP, or container platform. Vendure is self-hostable by design, so there is no mandatory vendor cloud and no per-order platform fee.
Data and AVV: Your commerce data stays in your database under your control. We sign a German Auftragsverarbeitungsvertrag (AVV) and design GDPR-conscious data flows where we touch personal data.
Owned plugins: We bring the open-source Data Hub ETL plugin and our proprietary Customer Intelligence engagement product. You inherit production-tested building blocks instead of paying to invent ERP sync, feeds, reviews, and loyalty from zero.
Support: Founder-led, senior-only delivery from Munich. After handover, an optional technical retainer covers maintenance, upgrades, and on-call to an agreed SLA target. No retainer is required to keep running what you own.
Exit: Because it is standard Vendure plus documented TypeScript plugins, any competent Vendure or Node team can take over. We hand off source, tests, deployment docs, and architecture notes so leaving us is never a rebuild.

Who owns what

How responsibility splits across the delivery chain on a Vendure engagement.

Responsibility ownership across the delivery chain
Responsibility	Oronts	Your agency / partner	You	Cloud provider
Vendure build and plugins	Oronts owns Vendure build and plugins
Source code and IP			You owns Source code and IP
Hosting and infrastructure			You owns Hosting and infrastructure	Cloud provider owns Hosting and infrastructure
Commerce and customer data	Oronts owns Commerce and customer data		You owns Commerce and customer data
Security and patching	Oronts owns Security and patching	Your agency / partner owns Security and patching
Acceptance and sign-off			You owns Acceptance and sign-off
Incident response	Oronts owns Incident response	Your agency / partner owns Incident response

When Vendure is not the right call

A small, simple catalog with standard checkout and no custom business logic: a hosted shop will ship faster and cost less, and we will point you to the platform that fits instead of selling you a framework.
A team with no engineering capacity and no plan to acquire it: Vendure is a TypeScript framework that rewards ownership, and without engineers to run and extend it the freedom turns into a burden.
A pure off-the-shelf checkout need where the standard flow already works: that is exactly what a hosted product solves cleanly, and building it on a framework adds cost without buying you anything you will use.

Who you're working with

HRB 288224

Registered in Munich

15+

Years, founder-led

DE · EN · AR

Delivery languages

Open source on GitHub

Data residency, Frankfurt

AVV/DPA

Ready to sign, Art. 28

Engagement levels

Oronts works with serious teams that need senior delivery, not low-cost outsourcing.

Production Pilot: from 25k EUR
Custom software and AI projects: from 50k EUR
Ongoing technical retainers: from 15k EUR/month

Exact pricing depends on scope, responsibility, delivery speed, team size, integrations, support expectations and production risk.

Scope the 90-Day Pilot

Funding programs such as Digitalbonus Bayern may cover part of eligible digitalization projects; Oronts can support with the technical project description and application preparation.

Vendure questions, answered directly

Ownership and control. Vendure is a TypeScript framework, not a hosted product: your business logic lives in your codebase, extensible without platform limits, and you own every line. The price is that you need engineering. If you do not have custom logic worth owning, Shopify or Shopware serve you better, and we say so in the first call.

Not necessarily. Customer-specific pricing, quotes and approval flows can be engineered as custom plugins on the open-source core; the enterprise tier packages them as supported features. The decision is build-versus-license economics, and it depends on how specific your B2B logic is. We have built both ways.

Yes. Catalog, customers, orders and content move through engineered pipelines with dry-run previews and idempotent imports, the discipline our Data Hub plugin encodes. The storefront migrates incrementally where the domain allows it.

Your team can: every plugin ships with tests, documentation and versioned releases. If you want us to maintain them, that is what the technical retainer covers. Our published Data Hub plugin shows the standard before you commit.

Yes, with engineering: VAT handling, invoice requirements, payment providers like Mollie, Stripe and PayPal, GDPR-conscious data flows and German-language storefronts are all solved problems. We build them as reusable patterns, not one-offs.

Vendure engineering, published

Talk to the engineers, not a sales team

Founder-led, senior-only delivery from Munich. Scope your Vendure project in one conversation.

Scope your project

See the engineering work