Most commerce platforms hand the operational backbone back to you
You can build it yourself: a separate Temporal cluster, a custom job queue, an iPaaS for the integrations, and a thin webhook contract gluing it all to the commerce platform. Or you can accept the platform's limits and never automate the operations that actually move the business.
Vendure Platform ships durable execution and a typed integration pattern inside the same platform.
Workflows resolve Vendure services through the same dependency injection, operators observe and intervene in the dashboard they already use, and operational logic stays inside your codebase, versioned and testable, end to end.
Two extension points, one platform
Both live as Vendure plugins on the same NestJS application as the rest of your commerce backend, so there's no second runtime to operate.
Workflow engine, durable by default
@vendure-platform/workflow-engine is the durable execution engine. Powered by DBOS, it persists every step to Postgres and recovers in-flight workflows on process restart, with typed signals for human-in-the-loop decisions. Workflows are TypeScript classes that resolve Vendure services through dependency injection, and you inspect, signal, and cancel them from the admin dashboard.
Enterprise plugins, wired together
@vendure-platform/integration is the single entry point that wires the enterprise plugins together. One import composes quote management with org hierarchy, approval workflows with tax-ID validation, and audit trails across quick order, with shared permissions, scope strategies, dashboard composition, and seeded data pre-configured. The integration concerns that normally land on the consumer stay inside the package.
Operations resolve through the same dependency graph
Workflows live inside the Vendure application and resolve OrderService and your own plugin services through the same dependency injection the rest of your code uses. The workflow engine plugs into Vendure's job queue too: opt in, and every Vendure job runs on the same durable substrate. Crashed workers no longer lose work.
The integration package follows the same NestJS dependency model. It imports the plugins it bridges, fails fast if a required plugin is missing, and owns the shared concerns that don't belong to either plugin alone.
Identity, request context, and retry semantics come from Vendure itself, so plugins share them instead of inventing webhook hops between services.
The shape of a real operational backbone
Three engineering scenarios that map onto code already shipping in Vendure Platform.
Trusted by complex B2B commerce and enterprise retail.
What engineering leads ask before they bet on the workflow engine
One category in a wider plugin library
The operational backbone is one piece of Vendure Platform. The same plugin model powers B2B workflows, pricing and promotions, search and discovery, and governance and compliance. See the full plugin overview.
