A wholesale client called last week with a problem that had nothing to do with conversion rate or theme quality. They run most revenue through B2B accounts. Buyers pay by bank transfer. Sage holds inventory, invoicing, and finance. BigCommerce was the catalogue and order record.
For years, draft orders and manually logged POs did not attract the same platform charges as card checkout. Recently, BigCommerce started billing for those orders anyway, even though payment never touched BigCommerce and fulfilment logic lives in Sage.
On a growing B2B book, a single new fee line adds up fast. Treat it as a signal that platform economics no longer match how the business actually trades.
Introduction
Established B2B brands choose BigCommerce for sensible reasons: structured catalogues, customer groups, and a middleweight platform that feels more controlled than open-source chaos. When the stack works, finance stays in Sage, sales stay in CRM, and the storefront captures what buyers need to see.
The break happens when the commerce platform starts charging like a payment processor for orders it never processed.
This article compares BigCommerce draft order and manual order billing against Shopify's model for ERP-led B2B, where bank transfer and purchase order workflows are common. It is for decision makers who need a clear total cost picture before a replatform, not a generic "Shopify wins" pitch.
If you are already mapping a move, start with Migrating from BigCommerce to Shopify and the Migration Readiness Assessment. For where platform fees sit in the wider stack, see The Real Cost of Running a Shopify Store.
What merchants are running into
The pattern from recent audit and migration calls looks like this:
- B2B-heavy order mix, PO, net terms, and bank transfer dominate; card checkout is a minority
- ERP owns truth, Sage (or similar) runs stock, invoicing, and settlement
- BigCommerce captures orders via draft orders, admin entry, or buyer portals for visibility
- Payment happens offline, finance matches bank credits in Sage, not through BigCommerce gateways
- New billing lines appear on draft or manual orders that previously sat outside fee calculations
- Nobody replatformed for UX, the trigger is margin leakage on orders the platform did not monetise
Merchants feel mis-sold because the storefront still "works." Buyers still browse. Ops still sync. The invoice changed underneath a stable workflow.
That frustration is rational. You are not failing at ecommerce. You are discovering that your commerce platform's pricing model assumes every order is a platform transaction, even when your architecture deliberately routes money and fulfilment elsewhere.
Why platform fee creep hits ERP-led B2B hardest
1. Draft orders are workflow, not checkout
On B2B stacks, draft orders are often how account managers quote, how insides sales log phone orders, or how ERP-triggered demand becomes a visible order record for customer service. The cart and gateway may never run.
When those records incur per-order or GMV-tier charges, you pay for administrative capture at the same rate as self-serve checkout. That punishes high-touch wholesale models.
2. Sage outside the platform is the point
Keeping Sage as system of record is a feature, not a workaround. Finance needs audit trails, stock reservations, and VAT logic that match how the business already runs. The storefront's job is to present catalogues, capture structured demand, and emit clean order data.
If BigCommerce charges as though it processed payment and fulfilment end to end, the bill disconnects from value delivered.
3. Subscription price was never the full story
Both platforms advertise monthly plans. B2B operators learn to model transaction fees, order volume tiers, app subscriptions, and agency reconciliation time. A draft order fee is easy to miss until wholesale volume makes it visible.
The same lesson appears on Shopify stacks with app sprawl; see The Hidden Cost of Running a Shopify Store When 12 Apps Quietly Eat Your Margins. Here the leak is platform order accounting, not an App Store invoice.
4. Migration triggers are economic, not aesthetic
Teams tolerate Stencil friction for years. They replatform when fee structure, B2B capability, or integration depth blocks the next commercial plan. A sudden draft order charge is often the forcing function that makes a twelve-month Shopify model worth building.
How Shopify fits ERP-led B2B (without pretending it is free)
Shopify, especially Plus, carries real subscription cost. For this architecture the billing model is often more predictable when you separate three cost layers:
- Subscription, plan or Plus contract
- Payment processing, only on revenue that actually flows through Shopify Payments or a connected gateway
- Integration and ops, Sage connector, middleware, and internal time
For bank transfer and PO workflows, orders can be created as draft orders or completed with manual payment methods, then marked paid when finance confirms settlement. Card transaction fees apply to card revenue, not to every order row sitting in admin for ERP sync.
Native Shopify B2B on Plus adds company locations, catalog-specific pricing, payment terms, and buyer self-serve reordering when you want to grow beyond rep-entered drafts. Advanced and lower tiers can still run wholesale with apps and custom pricing, but Plus is the usual target for Sage-backed brands scaling account complexity.
Efficiency shows up in integration surface area: more Sage connectors, mature middleware patterns, and admin APIs your agency pool already ships. That reduces the hidden cost of keeping two systems aligned.
Mermaid diagram
Framework: compare what you actually pay for
Use this matrix against your last twelve months of orders. Split card checkout, draft or manual B2B, and ERP-origin PO lines before you trust a headline plan price.
| Decision factor | BigCommerce (ERP-led B2B) | Shopify (ERP-led B2B) |
|---|---|---|
| Monthly platform fee | Plan tier based on GMV or order bands; verify what counts as billable orders | Plan or Plus contract; order count limits on lower tiers, soft caps on Plus |
| Draft or manual orders | Merchants report new charges on admin and draft orders even without gateway capture | No card transaction fee; subscription applies. Manual payment methods supported |
| Bank transfer / PO settlement | Order still lives in BC; fee treatment depends on current billing rules | Mark as paid offline; Sage settlement parallel to Shopify order record |
| ERP sync (Sage) | Connectors exist; Script Manager customisations may need rewrites on exit | Strong connector and iPaaS market; webhook-first order export patterns |
| Wholesale pricing and accounts | Customer groups and price lists | B2B companies, catalogs, payment terms on Plus; apps on lower plans |
| Storefront agility | Stencil rebuilds slower for many agencies | OS 2.0 theme ecosystem; faster merchandising iteration |
| Migration cost | N/A (incumbent) | Theme rebuild, redirects, ERP re-test: typically 12–18 weeks mid-market B2B |
Run the numbers twice: status quo with new BC fees versus Shopify subscription plus migration plus connector. Include internal ops hours. A platform that looks expensive on paper can be cheaper when it stops taxing orders that never used its payments stack.
Recommendation by scenario
Scenario A: Majority bank transfer, Sage is truth, draft orders are daily workflow
Likely move: Evaluate Shopify Plus with B2B and a Sage integration partner. Prioritise order object mapping and payment terms before marketing features. If BC draft fees are material on hundreds of monthly lines, migration math often clears within the first year after build cost.
Scenario B: Mixed B2B and DTC, card revenue growing
Model both channels separately. Card checkout fees apply on any platform. The argument for Shopify strengthens when B2B draft volume is large but DTC also needs modern checkout and Shop Pay. Plan tier choice matters; see Choosing the Right Shopify Plan.
Scenario C: BigCommerce fees rose slightly but ERP sync is fragile
Do not migrate to escape a line item if Sage sync is already broken. Fix integration ownership first. Migration magnifies weak data models. A structured stack audit clarifies whether fees or architecture drive the pain.
Scenario D: Contract lock-in and low IT capacity
Renegotiate or reduce order creation in BC (fewer duplicate draft rows, ERP as sole order origin with BC as read-only catalogue) until migration is funded. Anger is not a project plan.
What Shopify does not magically fix
- Sage sync still needs design. Shopify does not replace ERP; it replaces the customer-facing order layer.
- Plus is a real commitment. Budget contracted platform fees honestly.
- B2B complexity moves into catalogs and permissions. Simpler than Stencil scripts, still a build.
- SEO and URL structure change. Redirect planning is non-negotiable; the BigCommerce migration guide covers it.
Shopify wins on clarity and ecosystem for many ERP-led brands. It is not a free lunch.
Conclusion
BigCommerce charging for draft orders on a Sage-led B2B stack is more than billing annoyance. It exposes a mismatch: you built a workflow where the platform records demand while finance settles elsewhere, and the platform now prices every record like a checkout transaction.
Shopify is often the more efficient home for that model when you need predictable separation between subscription, payment processing, and ERP integration, especially at wholesale scale on Plus.
Before you replatform, model twelve months of true cost, validate Sage order mapping, and scope migration as an integration project with a storefront rebuild, not a theme refresh.
If you are weighing BigCommerce exit after fee changes on manual or draft orders, book a discovery call or start with our replatforming and migration services. We map Sage sync, B2B catalog rules, and fee impact before anyone touches Liquid.
