Headless commerce for B2B: when it pays off
Headless commerce makes sense for B2B when prices are negotiated per customer, the ERP has to drive stock and prices in real time, and you sell through several channels at once. With a simple price list and a single market, a SaaS platform is usually enough. Unlike DTC, B2B means each customer can have their own price, credit limit, assortment and order-approval process. SaaS platforms handle this better every year, but at a certain scale they start to get in the way.
When SaaS is enough for B2B
In 2025 Shopify Plus has native B2B features: customer-specific catalogues, pricing rules, order limits and company accounts with roles. For a B2B store with a simple pricing model, one market and no deep ERP integration, that is often enough and much cheaper than headless.
If you vary prices only by customer group, have fewer than 5,000 SKUs and don't need real-time stock sync with a legacy ERP, stay on SaaS. Headless won't solve problems that configuration can.
Three signs that SaaS is no longer enough
The first is custom pricing logic: prices negotiated with each customer, long-term contracts with escalation clauses, volume discounts based on purchase history. SaaS handles these through third-party apps that don't see the full customer context.
The second is the ERP as the source of truth. If stock, prices and customer data must stay in sync with a legacy system in real time, and a five-minute discrepancy is already an operational problem, the SaaS architecture starts to get in the way. The third is multiple channels. A B2B business that sells through an online store, field sales reps with a mobile app and EDI at the same time needs one backend that manages the data, instead of three two-way syncs.
Pricing logic, the main case for headless B2B
In Medusa.js you can build any pricing model as a backend module: per-customer prices with change history, automatic contract escalations, volume tiers, and different currencies and taxes per market. It is your own code, so you don't depend on an app whose vendor can change the API.
With more than 50 customers on individual pricing agreements, keeping pricing logic in SaaS (apps, workarounds, team time) often costs more than building your own module once. We model this in the audit before recommending a direction.
ERP integration decides the business case
Most B2B headless projects run into trouble with the ERP integration rather than the platform. Customer data lives in a system with its own account IDs, its own data model and its own validation rules. Connecting it to a new platform is a project in its own right.
We do this regularly with Comarch, Subiekt and MS Dynamics. The key decision is what to sync in real time and what to send through queues. Stock and prices need to be current immediately, while order history and invoicing data can go in batches with reconciliation. That choice feeds straight into infrastructure cost.
Cost and payback for headless B2B
A headless B2B project with full ERP integration, custom pricing logic and a sales rep panel takes 16–24 weeks, and the budget is worth modelling carefully before you start. Payback depends mainly on what your current workarounds in SaaS and the ERP cost you.
If your team spends more than 20 hours a week manually sorting out discrepancies between systems, the investment pays back faster than you might expect. If not, headless is a more expensive way to the same result. It is worth knowing this number before you write the agency brief.
- Shopify Plus is enough for B2B with simple pricing and no deep ERP dependency
- Three signs for headless: custom prices, real-time ERP, several sales channels
- The ERP integration, more than the platform, decides the business case for headless B2B