Commerce that fits the systems you already run
Your ERP, CRM, PIM, OMS, payments and fulfilment stay in place. Your team connects them to Vendure through its GraphQL APIs and plugins, so orders, stock, customers and prices move between systems without re-keying.
Model commerce around your customers, not your back office
Vendure lets you model customer accounts, pricing, catalogues, checkout, and order workflows around how your business sells, independent of how your ERP, CRM, PIM, or OMS structures its data.
Those systems can remain authoritative. Your team connects them through the GraphQL APIs and plugins and syncs the data each commerce process needs, so orders, inventory, customers, pricing, and status move between systems with less manual re-entry. You decide where each kind of data is mastered and how it stays current in Vendure.
The systems you run today, connected
Every business already has an operational stack. Vendure ships no ERP or CRM connectors. Your team or a partner builds them on the APIs, plugins and the Workflow Engine in every plan.
ERP
Your integration pushes orders out as they are placed and writes back the sales-order number, stock and prices. Your finance and inventory numbers stay owned by the ERP, kept current in Vendure through real-time, event-driven, or scheduled synchronisation.
CRM
Accounts, contacts, and sales activity stay where your sales team works. Your integration reads the relationships Vendure needs and writes back the orders your reps want to see, without asking anyone to maintain two customer lists.
PIM
Product data keeps a single master. Your integration brings the catalogue your PIM publishes into Vendure, so a product change happens once and shows up everywhere it should.
OMS and fulfilment
Your integration hands orders to the system that picks, packs, and ships them, and takes back the status your customers ask about. Fulfilment stays with the warehouse and courier systems built for it.
Payments and settlement
Take payment through any provider that has a Vendure payment handler, or one you write: cards, bank transfer, payment on delivery or pay on account. Company payment methods decide which of these each customer company can use.
Automation
Build each hand-off as a workflow on the Workflow Engine, included in every plan. If a step fails, only that step retries, so nobody spends their morning re-running a failed sync.
Data flows both ways, and keeps flowing when something fails
The everyday problem with integrations is not the happy path. It is the ERP being slow for ten minutes, or a network call dropping halfway through, and cheap integrations losing the order or leaving two systems disagreeing until someone notices.
Build each hand-off as a workflow on the Workflow Engine, included in every plan. If a step fails, only that step retries, and if a worker restarts mid-flow, the work resumes where it left off. Anything genuinely stuck surfaces in one place, with the full history attached.
When an order is placed, your order workflow pushes it to the ERP, waits for the sales-order number, and writes that number back onto the order. A slow response retries the one call that failed, not the customer's checkout. The customer does not have to wait on your back office, and both systems stay aligned.
Your integration brings inventory and price changes into Vendure at the cadence each buying process needs. Use real-time or event-driven updates where buyers need the latest value, and scheduled synchronisation where a batch is the better operational fit.
The manual steps a person does today, copy an order into the warehouse tool, check it against the ERP, email a confirmation, become steps in a workflow your team builds on the Workflow Engine, with clear checkpoints. Where a human decision is genuinely needed, the flow pauses and waits for someone to approve it from the dashboard, then carries on.
Take payment through any provider, on one model
Vendure takes payment through one consistent model, and the provider sits behind it. Your checkout stays the same whether the money runs through a card gateway, a bank transfer, or an in-house arrangement, and adding or switching a provider is a change behind the scenes, not a checkout rebuild.
The same model handles refunds, cancellations, and more than one payment method on a single order.
Charge now, or hold and settle when you ship
B2B rarely charges at the click of a button. Vendure lets you take the money at checkout, or authorise it now and settle later when you actually ship, on the same model. That covers card gateways, payment on delivery, and bank transfer without a separate flow for each.
The customer pays and the funds are captured in one step. This is the common path for card payments, and it needs no extra handling.
Hold the funds at checkout and take them when you ship or confirm the order. If the order is cancelled first, cancel the authorisation from the Dashboard or in your payment workflow.
Non-card payment follows the same shape. Record the intent at checkout, then settle when the money arrives or the courier collects it, from the dashboard or automatically as your systems confirm it.
Teams building complex commerce with Vendure
What teams ask about connecting Vendure
No. Your ERP, CRM, PIM, OMS, and fulfilment systems can stay in place and remain authoritative for the parts of the business they already run. Your team connects them to Vendure through its GraphQL APIs and plugins, and Vendure becomes the buying experience and commerce layer on top.
Your integrations move data in both directions as events happen: orders out, sales-order numbers, stock, and prices back. Your team builds each hand-off as a workflow on the Workflow Engine, included in every plan, so a brief outage in one system retries only the affected step rather than losing the order or leaving two systems disagreeing. Anything that genuinely gets stuck surfaces in one place, with its full history, for someone to resume or correct.
Yes, if it has a Vendure payment handler or your team writes one. Vendure takes payment through one model with the provider behind it, so you can add or switch a provider without rebuilding checkout. The model handles single and two-step capture, refunds, and more than one payment method per order.
Your team builds those hand-offs as workflows on the Workflow Engine, included in every plan. If a step fails, only that step retries. Where a real human decision is needed, the flow pauses for an approval and then continues. The day-to-day operations that sit on top of this live in Operations and governance.
Connect the systems you need to keep
Try Vendure for 14 days and test an order flow against a sandbox of your ERP or payment provider, or compare the plans to see what each one includes.