SAP Business One ecommerce integration — without risking your ERP
B2B trade ordering, D2C and marketplaces on top of SAP B1 — with SAP staying in control
If SAP Business One runs your operation, it holds years of carefully configured price lists, customer terms, stock rules and financial history. The risk in any ecommerce project is not the website — it is what a badly built integration does to that configuration: duplicated customers, stock levels that drift, trade prices leaking to the wrong buyers, and orders that need rekeying by hand.
Coretonomy connects SAP Business One to B2B trade ordering, D2C ecommerce (including Shopify) and marketplaces through one controlled integration hub. SAP B1 remains the system of record; the channels around it can change without touching your ERP.
ERP-first SAP Business One integration
SAP Business One integration architecture — Coretonomy's Integration Data Hub connects SAP B1 with B2B ecommerce, D2C (including Shopify) and marketplaces while keeping SAP as the system of record. Explore the interactive version →
Why point-to-point SAP B1 integrations break
The common approach is a direct connector: webshop plugged straight into SAP B1's Service Layer or DI API. It demos well. Then real-world complexity arrives:
Price list leakage
SAP B1 price lists per customer group are subtle. Naive connectors show trade prices to retail shoppers — or worse, the reverse.
Stock drift
Each channel holding its own stock copy diverges from SAP under load, causing overselling and cancelled orders.
ERP overload
Every page view hitting SAP B1 directly couples website traffic to ERP performance — and takes the shop down with every SAP maintenance window.
Duplicate records
Business partners and orders created twice when retries aren't handled properly, polluting SAP data that took years to keep clean.
Upgrade fragility
Each new channel means another direct connection to maintain — and another thing to break on the next SAP B1 upgrade.
One controlled layer between SAP B1 and every channel
Coretonomy's Integration Data Hub synchronises the data that matters, in the right direction, with SAP Business One authoritative throughout:
Products & catalogue
Items, variants and attributes flow from SAP B1 outward — enriched for the web without touching ERP master data.
Stock & availability
Warehouse-aware stock levels synchronised to every channel, with allocation rules and back-order handling controlled centrally.
Prices per customer group
SAP B1 price lists mapped to trade accounts online, so each customer sees exactly the pricing SAP says they should — and retail shoppers see only retail.
Customers & accounts
Business partners, account terms and credit rules from SAP govern who can order what, on which terms.
Orders
Orders from B2B, D2C and marketplaces validated by the hub before entering SAP B1 — 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.
SAP Business One stays the system of record
Coretonomy is built for ERP-led businesses. SAP B1 remains authoritative for:
Stock allocation and availability governed by SAP B1, not fragmented across channels.
Price lists, customer groups and account structure remain in SAP 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: LandscapePlus runs on SAP Business One + Coretonomy
LandscapePlus, a UK landscaping supplies business, runs its trade ordering at sap.landscapeplus.com on Coretonomy, integrated with SAP Business One through the hub:
SAP-governed pricing
Trade customers log in and see their own SAP B1 price list — quotes and phone-order discrepancies eliminated.
Real stock, online
Availability on the site reflects SAP stock, synchronised continuously through the hub rather than read live off the ERP.
Orders straight into SAP
Web orders arrive in SAP Business One validated and attributed — no rekeying, and the office team works in SAP as before.
The pattern is repeatable: your SAP B1 configuration stays as it is, and the hub adapts to it — not the other way round.
Implementation approach: staged, parallel, reversible
Most established SAP B1 businesses cannot afford a big-bang rebuild — and don't need one. The rollout is designed around change control:
Discovery against your SAP setup
We start from your actual SAP B1 configuration — price lists, warehouses, customer groups, UDFs — not a generic template.
Staged channel rollout
B2B trade ordering first, then D2C, then marketplaces — each validated before the next goes live.
Parallel running
Existing processes keep working during transition; nothing is switched off until its replacement is proven.
Monitoring & clear ownership
Sync activity is visible and auditable, exceptions are surfaced, and when something needs attention you know exactly who owns it.
Connect SAP Business One to trade ordering, D2C, Shopify and Faire
Every channel connects to the hub rather than directly to the ERP system. That distinction compounds: the second and third channel become configuration against a layer that already exists, instead of another bespoke connection into SAP Business One for someone to maintain.
B2B trade ordering
Trade customers log in to their own SAP price lists, terms and account history. Order processing that previously ran on phone calls, emails and rekeying becomes a validated flow into the ERP.
D2C storefront
Retail selling from the same stock pool, with retail pricing kept strictly separate from contract pricing — so a consumer never sees a trade price.
Shopify
Already running Shopify for D2C? Keep it. The hub keeps stock, orders and customer information in step between Shopify and SAP Business One instead of forcing a replatform.
Faire
Wholesale marketplace reach without a separate stock pool to reconcile — see the Faire integration.
What the channels share is the same product information, the same real-time inventory position and the same customer records, because all of it is governed by one ERP rather than copied into each ecommerce platform. That is what stops your business processes fragmenting as you add channels — and what removes the manual processes that otherwise grow with every one you add.
Which front end can SAP Business One run behind?
Most people arrive at this page asking a version of the same question: can SAP Business One work with Magento, BigCommerce, WooCommerce, or the storefront we already run? The architectural answer is yes — the hub connects to SAP Business One on one side and to a channel on the other, and it does not much care what the channel is. The useful answer depends on which of three groups your front end falls into.
Built, and running today
Our own B2B trade ordering platform, our own D2C storefront, Shopify for D2C, and Faire for wholesale marketplace. These are live connectors, all in production today. SAP Business One runs behind our own trade ordering platform for a UK wholesaler now; tell us your pairing and we will say whether it is configuration or a build.
Possible, as scoped bespoke work
Magento, BigCommerce, WooCommerce, PrestaShop, Shopware and similar — and marketplaces other than Faire. The hub can be extended to any of them, but that is a scoped and quoted piece of work with its own timeline rather than an existing connector we switch on. We will tell you the cost before you commit, and we will tell you if we think it isn't worth it.
Not what the hub is for
Carrier and shipping platforms, and channel managers. These sit outside what the Integration Data Hub does, and where SAP Business One needs to reach them a specialist tool will serve you better than asking us to build one.
The same is true of EDI. If a retailer has mandated EDIFACT or AS2 in your supplier agreement, that is a specialist product and you should buy one — we do not provide it, and we would rather say so now than three months into a project. What we do handle is structured file exchange in agreed formats between systems that have agreed them, which solves the same business problem where no external standard is being imposed.
When a hub is the wrong answer
We would rather say this here than in month three of a project. A hub is probably not what you need if:
- You need SAP Business One connected to exactly one storefront, with no second channel planned — one well-built point-to-point connection is cheaper, and you should buy that instead
- Your storefront already has a maintained SAP Business One connector from its own vendor or partner — use it, because a hub earns its keep across several channels, not one
- You sell only through marketplaces — a channel manager is the right category of product, and we are not it
- You have no trade complexity — no customer-specific price lists, no account terms, no credit rules. Most of what the hub does is protect exactly those things
It earns its place when:
- More than one channel runs off a single SAP Business One instance
- Customer-specific pricing and terms must never leak between accounts
- SAP Business One must stay the system of record, not become one copy among several
- A stock or pricing error is expensive — in margin, in credit notes, or in trust
If you are not sure which group your platform falls into, tell us what you are running and we will tell you plainly — including when the answer is that you don't need us.
Designed for SAP B1 businesses where the cost of getting it wrong is high
This is a fit if you:
- Rely on SAP Business One operationally
- Run wholesale price lists, account terms, or complex catalogues
- Want trade customers ordering online instead of by phone and email
- Are adding D2C or marketplace channels alongside B2B
- Want stability, clarity, and accountability over hype
SAP Business One integration questions
Do you integrate with SAP Business One?
Yes. Coretonomy's Integration Data Hub connects SAP Business One to B2B trade ordering, D2C ecommerce and marketplaces while SAP B1 remains the system of record for stock, pricing, orders and invoices.
Can SAP Business One power a B2B wholesale ordering portal?
Yes. Coretonomy provides a proprietary B2B ordering platform synchronised with SAP B1 — customer-specific price lists, account terms and catalogues come from SAP; orders flow back in validated and correctly attributed.
Can you connect SAP Business One to Shopify?
Yes, for D2C. Shopify connects through the same hub, sharing the stock and pricing rules SAP B1 governs. Coretonomy does not use Shopify for B2B — wholesale runs on our own platform.
How do customer-specific price lists work?
Price lists and customer groups are maintained in SAP Business One. The hub synchronises them so each trade customer sees their own prices online, and anonymous retail shoppers only see retail pricing.
Do orders and invoices sync back into SAP B1?
Yes. Orders from every channel are validated by the hub before they reach SAP B1, and invoice data flows back out so customers can see documents online without anyone rekeying.
Will the integration disrupt our existing SAP Business One setup?
The integration is designed around your existing SAP B1 configuration. Rollout is staged and runs in parallel with current operations, with validation before each channel goes live and clear rollback paths.
Can you connect SAP Business One to Faire?
Yes. Faire connects through the same hub with controlled stock allocation and order routing, added once B2B and D2C channels are stable. Faire is the marketplace we have a built connector for; other marketplaces would be scoped as bespoke work.
Can you connect SAP Business One to Magento, BigCommerce or WooCommerce?
Not as an off-the-shelf connector today. We have built connectors for our own B2B and D2C platforms, for Shopify and for Faire. Connecting SAP Business One to another storefront is possible through the Integration Data Hub, but it is bespoke work — scoped and quoted before you commit, rather than presented as an existing integration.
Does the hub connect SAP Business One to carriers or channel managers?
No. Shipping platforms and channel managers sit outside what the Integration Data Hub does. Where SAP Business One needs to reach them, a specialist tool is usually the better answer, and we will say so.
Do you provide EDI for SAP Business One?
No. If a retailer has mandated EDIFACT or AS2 in your supplier agreement, that is a specialist product and you should buy one. What we handle is structured file exchange in agreed formats — which solves the same business problem where two parties agree the format themselves, and is considerably cheaper, but is not a substitute where a standard is being imposed on you.
Discuss your SAP Business One setup
We start with your current SAP B1 configuration, channels and operational constraints, then recommend the lowest-risk path forward.