GUIDE DE
Book a demo
Guide / B2B commerce

Connecting SAP Business One to an online store: 4 approaches compared

August 18, 20265 min read

There are four common ways to connect SAP Business One to an online store: manual CSV export and import, a generic connector or iPaaS platform, a plugin for a standard shop system such as Shopify, BigCommerce, or WooCommerce, or an integrated B2B platform with a native SAP B1 adapter. Automated routes use the interfaces SAP provides, primarily the Service Layer and the DI API. Which one fits depends on how current inventory and prices must be, and how much B2B logic, such as customer-specific price lists, has to travel with them.

01Starting point

Why connect the store to SAP Business One at all?

In most companies running SAP Business One, the ERP is the system of record: Items, inventory, Price Lists, Business Partners, and Sales Orders live there. A store without a connection is a second data world: inventory and prices go stale, web orders are re-keyed by hand, and every manual step is a chance for error.

It bites hardest in B2B. With terms negotiated per account, the Price Lists and Special Prices in SAP Business One have to reach the store exactly as customer-specific prices. Integration means the store works from the same data as inside sales, nothing maintained twice.

02The four approaches

Which options do you have?

All four have their place. They differ in data freshness, ongoing effort, and how well they carry SAP B1 pricing and other B2B specifics.

Approach Strengths Limits Typical use
Manual export/import (CSV) No integration project, full control over every run; the Data Transfer Workbench (DTW) covers the B1 side Delayed and error-prone; inventory and prices age between runs; customer-specific price lists impractical Small catalogs, infrequent changes, pilot phase
Generic connector / iPaaS One platform for several systems; mapping in one place; prebuilt blocks for common systems (lighter flows via n8n, Make, Zapier) Another system to run and pay for; one more link that can fail; B1 pricing has to be rebuilt in flows Many endpoints: store, marketplaces, PIM, 3PL
Plugin for a standard shop system Fast to switch on; proven for standard cases; B1 connectors exist for Shopify, BigCommerce, WooCommerce, Adobe Commerce Only the fields and processes it was built for; Special Prices, approval workflows, other B2B specifics need customization; tied to both release cycles Standard shop systems with little custom logic, often B2C
Integrated B2B platform with SAP B1 adapter Built into the platform; Price Lists, Special Prices, and Sales Orders end to end; no intermediate system Tied to the platform vendor; more alignment at project start B2B stores and dealer portals with B1 as system of record and negotiated terms per account

The same routes apply beyond your own store: see Importing Amazon orders into SAP Business One for marketplaces and ERP–e-commerce integration for the ERP-agnostic view.

03Data types

Which SAP B1 objects belong in the store?

Whichever route you choose, six kinds of data move between B1 and the store:

B1 → STORE

Items

Item master, descriptions, units of measure, item groups; presented in the store as SKUs.

B1 → STORE

Inventory

Available quantity per warehouse (on hand minus committed), so the store never promises what you cannot ship.

B1 → STORE

Price Lists & Special Prices

Price Lists per Business Partner plus Special Prices and volume breaks: the most demanding data type in any B1 integration.

BOTH DIRECTIONS

Business Partners & contacts

Customers, contacts, and ship-to addresses, so every store login maps to the right B1 account and terms.

STORE → B1

Sales Orders

Web orders land in B1 as Sales Orders with customer PO number, ship-to, and tax code, no re-keying. The main reason to integrate.

B1 → STORE

Order status

Deliveries, tracking numbers, and A/R Invoices flow back so customers see where their order stands.

04In practice

What to watch for with SAP Business One

01

Take over the price list logic, don’t rebuild it

SAP Business One assigns each Business Partner a Price List. Carry that assignment one to one: the store shows what the ERP delivers. Price rules rebuilt in the store drift from the ERP.

02

Don’t forget Special Prices

Special Prices per Business Partner override the list, including quantity breaks and date ranges. Move only list prices and the customer who negotiated a deal sees the wrong number.

03

Choose the integration point deliberately

Service Layer (HTTP/OData) or DI API (COM, Windows): the choice affects hosting, maintainability, and upgrade behavior, so settle it early. Same for sales tax: the Sales Order tax code must match what your store or tax service (Avalara, TaxJar) calculated.

04

Test with realistic data

Full Price Lists, the real item master, special characters, and units of measure belong in the test, against a test company, never production. Bugs live at the edges of real data.

05Where we fit

Where does the CS Order Suite fit in this picture?

The CS Order Suite, our multi-tenant B2B e-commerce platform, takes the fourth route: a native adapter architecture, one adapter per ERP. The adapter for SAP Business One is ready today. Items, inventory, customer-specific Price Lists, and Sales Orders move between B1 and the store with no intermediate system; pricing stays in the ERP.

Honest fit check

Selling B2C on Shopify or BigCommerce and only need orders and inventory in B1? A plugin is usually the faster path. We fit when the store is a B2B channel: contract pricing, verified dealer accounts, ship-tos, quick reorder, punchout, and SAP Business One as system of record.

06Frequently asked

SAP Business One and online stores: short answers

Does SAP Business One come with a built-in online store connector?

No. SAP ships integration tooling (Service Layer, DI API, Integration Framework), but no turnkey storefront connector. Connections come from shop-system plugins, iPaaS platforms, SAP partners, or e-commerce platforms with their own B1 adapter.

Service Layer or DI API – which one should an integration use?

The Service Layer (HTTP/OData) is the usual choice for new integrations: no Windows client, predictable across upgrades. The DI API is the older COM-based interface, still common in existing add-ons.

Can one B1 company serve a Shopify store and a B2B dealer portal at the same time?

Yes. Both channels can post Sales Orders into the same company. Separate them by Business Partner or customer group, a channel field or numbering series, and separate warehouses where stock is physically split.

Read next: Importing Amazon orders into SAP Business One Read the guide →

Questions about connecting SAP Business One?

Bring your B1 setup and requirements; in a live demo we look at which route makes sense for you. Pricing is something we cover personally.

Book a demo
Demo slots available for US time zones (ET/CT/PT) as well as CET.
Christian Stockerl
Your contact
Christian Stockerl
Managing Director
CS Management & IT-Beratung GmbH
Direct contact
Email
info@cs.gmbh
Address
CS Management & IT-Beratung GmbH
Ulrichsberger Str. 17 · 94469 Deggendorf · Germany