Brightpearl With Integration Hub for B2B and Omnichannel Commerce
Scale B2B, D2C, and marketplaces while keeping Brightpearl central
If Brightpearl is your operational backbone, integration decisions carry real risk. Adding B2B ecommerce, Shopify D2C, marketplaces, sales agents, and additional tools often creates point-to-point fragility—stock mismatches, pricing inconsistency, manual workarounds, and unclear ownership when things break.
Coretonomy's Integration Data Hub connects Brightpearl to every channel through one controlled orchestration layer—so Brightpearl remains the system of record while channels change around it.
ERP-first Brightpearl integration
Brightpearl integration hub architecture — Coretonomy's Integration Data Hub connects Brightpearl with B2B ecommerce, D2C (including Shopify), marketplaces, and operational systems while keeping Brightpearl as the system of record. Explore the interactive version →
One orchestration layer between Brightpearl and every channel
Coretonomy's Integration Data Hub sits between Brightpearl and your commercial channels, controlling how data is transformed, validated, and synchronised. It is designed to reduce integration risk by centralising:
Data normalisation
Products, customers, price lists, stock, and orders transformed consistently across all channels.
Business rules and validation
Rules enforced before anything reaches Brightpearl—preventing bad data from entering your ERP.
Pricing and stock orchestration
Consistent pricing and inventory across B2B, D2C, and marketplaces without manual reconciliation.
Order routing and synchronisation
Orders from all channels flow into Brightpearl with proper attribution and processing rules.
Monitoring and error handling
Visibility into sync activity, exceptions, and auditability when issues occur.
Controlled change
Add channels or replace tools without destabilising existing integrations.
What actually syncs — and in which direction
"Integration" only means something at the level of individual data flows. These are the ones the hub manages for Brightpearl businesses, each with Brightpearl authoritative:
Products & catalogue
Items, variants and attributes flow outward from Brightpearl, enriched for the web without touching ERP master data.
Stock & warehouses
Warehouse-aware availability synchronised to every channel, with allocation rules controlled centrally — channels never hold their own stock truth.
Price lists per customer group
Brightpearl price lists map to trade accounts online: each customer sees exactly their contracted pricing, and retail shoppers see only retail.
Back orders
Lines awaiting stock are tracked consistently across ordering channels, so trade customers see honest availability and nothing is lost between systems.
Orders
Orders from B2B, D2C and marketplaces validated before they reach Brightpearl — correctly attributed, with no manual rekeying.
Invoices & documents
Invoice data flows back out so trade customers self-serve documents online instead of emailing your accounts team.
Brightpearl stays the system of record
Coretonomy is built for ERP-led businesses. Brightpearl remains authoritative for:
Stock allocation and availability governed by Brightpearl, not fragmented across channels.
Customer terms, price lists, and account structure remain in Brightpearl as the single source.
Order history, reporting, financial accuracy, and fulfilment integrity stay in ERP.
The integration hub ensures you do not create a "shadow ERP" across ecommerce tools and marketplaces.
Live example: White Leaf and Last True Angel run on Brightpearl + Coretonomy
White Leaf, a UK giftware wholesaler, runs B2B trade ordering and D2C retail on Coretonomy — alongside sister brand Last True Angel — all against a single Brightpearl backend:
B2B and D2C, one backend
Trade ordering and retail ecommerce share Brightpearl's stock and pricing through the same hub — no parallel rule-books.
Customer-specific pricing
Trade customers log in to their own Brightpearl price list and account terms; retail shoppers see retail pricing only.
Orders straight into Brightpearl
Web orders from every store arrive validated and attributed — the operations team keeps working in Brightpearl as before.
Multiple brands and channels, one ERP, one integration layer — the pattern this page describes, running in production.
Connect Brightpearl to B2B, D2C, Shopify, and marketplaces
Wholesale / B2B
Coretonomy proprietary B2B platform
Purpose-built wholesale platform with customer-specific pricing, terms, and catalogues.
Account ordering
Trade customers order against their accounts with appropriate pricing and credit terms.
Assisted selling
Sales agents and trade show ordering that syncs directly to Brightpearl.
D2C
Coretonomy native D2C
Unified admin alongside B2B—shared inventory, consistent pricing rules, single dashboard.
Shopify D2C (optional)
Keep Shopify for D2C where it excels. Stock and orders sync through the Integration Hub.
Marketplaces
Faire
Wholesale marketplace integration with stock and pricing managed through the hub.
Mirakl-based marketplaces
Enterprise marketplaces supported with staged rollout to reduce risk.
Business systems around Brightpearl
Payments and gateways
Stripe, PayPal, and B2B credit terms integrated with order and accounting flows.
CRM
Customer data and sales activity sync for better account management.
Warehouse / fulfilment
3PL and warehouse tools connected through the hub, not point-to-point.
BI / reporting
Business intelligence tools fed consistent data from the integration layer.
All coordinated through the Integration Data Hub—no brittle point-to-point web.
Why Brightpearl integrations often fail at scale
Point-to-point connections can work early on, then break under real-world complexity:
Inventory drift
Stock levels diverge between channels, leading to overselling or missed sales.
Pricing discrepancies
Customer-specific pricing errors when rules aren't enforced centrally.
Manual reconciliation
Spreadsheet workarounds that consume time and introduce human error.
Expensive rework
Channel changes that require rebuilding integrations from scratch.
Unclear accountability
When integrations fail, no one knows where responsibility sits.
Add channels without disrupting operations
Most established Brightpearl businesses cannot afford a big-bang rebuild. Coretonomy supports controlled change:
Staged channel rollout
B2B first, then D2C, then marketplaces—each validated before moving to the next.
Parallel running
Measured migration with old and new systems running together during transition.
Clear rollback paths
If something doesn't work, you can revert without losing operational capability.
Documented patterns
Integration patterns you can rely on, not tribal knowledge that leaves when people do.
How this differs from SparkLayer and B2B Wave
Both are credible products, and for some businesses they are the right choice. The difference is architectural:
SparkLayer
Adds B2B ordering onto an existing Shopify store — a good fit if Shopify is already your centre of gravity and your wholesale needs fit its model.
B2B Wave
A standalone B2B webshop with connectors to the systems around it — a portal-first approach where the ordering site is the starting point.
Coretonomy
An ERP-first platform: a proprietary wholesale storefront plus an integration hub, with Brightpearl authoritative across B2B, D2C and marketplaces — one layer, one owner, one place to look when something needs attention.
The practical question isn't which product has more features — it's where you want the system of record to sit, and how many separate integrations you want to own as channels grow.
Designed for Brightpearl businesses where the cost of getting it wrong is high
This is a fit if you:
- Rely on Brightpearl operationally
- Run wholesale pricing, account terms, or complex catalogues
- Are adding marketplaces or additional channels
- Want stability, clarity, and accountability over hype
Brightpearl integration questions
Do you integrate with Brightpearl?
Yes. Coretonomy is designed to keep Brightpearl central as the system of record while connecting B2B, D2C, and marketplaces through one orchestration layer.
Can you connect Brightpearl to a B2B wholesale portal?
Yes. Coretonomy provides a proprietary B2B platform built for wholesale-first workflows, synchronised with Brightpearl via the integration hub.
Do you use Shopify for B2B with Brightpearl?
No, and it is worth being precise here, because a Brightpearl Shopify integration usually means one of two different things. If you mean selling D2C on Shopify with Brightpearl behind it, that is supported: Shopify connects to the hub as a D2C channel, and stock, orders and customer data stay in step with Brightpearl as the system of record. If you mean running trade ordering itself on Shopify, we do not. Customer-specific pricing, account terms and credit rules belong in a platform built for wholesale rather than a retail platform with B2B added on top.
Can you connect Brightpearl to Faire?
Yes. Faire connects through the same hub as your other channels, so stock, pricing and order routing stay controlled. Faire is the marketplace we have a built connector for; other marketplaces would be scoped as bespoke work.
How do Brightpearl price lists and customer groups work online?
Price lists stay in Brightpearl. The hub maps them to trade accounts so each customer sees their contracted pricing when they log in, while anonymous retail shoppers only ever see retail prices.
Do back orders sync with Brightpearl?
Yes. Lines awaiting stock are tracked consistently between Brightpearl and the ordering channels, so the availability shown to trade customers is honest and nothing is lost between systems.
Do invoices flow back from Brightpearl?
Yes. Invoice data flows out through the hub so trade customers can self-serve documents online instead of emailing your accounts team.
How does this compare to SparkLayer or B2B Wave?
SparkLayer adds B2B ordering to an existing Shopify store and B2B Wave is a standalone B2B webshop. Coretonomy pairs its own wholesale platform with an integration hub, so Brightpearl stays authoritative across B2B, D2C and marketplaces through one controlled layer.
Discuss your Brightpearl setup
We start with your current Brightpearl configuration, channels, and operational constraints, then recommend the lowest-risk path forward.