How to integrate SAP Business One with ecommerce
May 19, 2026 · 7 min de lectura · Equipo OpusGo
To integrate SAP Business One with ecommerce, connect the store to B1's data via the Service Layer or DI API, map items, price lists, business partners and orders, and run two-way sync. Hand-built projects take months; AI-mapped platforms like OpusNext typically go live in 2-6 weeks on both HANA and SQL.
Every ERP, fluent in commerce.
Know your B1 flavor first
SAP Business One runs on two databases - SAP HANA and Microsoft SQL - and two hosting models, on-premise and cloud. Integration tooling differs across them: the Service Layer is HANA-first, the older DI API covers SQL installs. Any platform you evaluate should state, in writing, which combination it supports.
What to sync from B1
The commercial core lives in a handful of B1 objects: Items (OITM) with warehouse stock, Price Lists with special prices per business partner, Business Partners (OCRD) with credit limits and payment terms, and Sales Orders (ORDR). A serious integration covers all four plus deliveries and A/R invoices for status.
- Items + warehouse stock
- Price lists + BP special prices
- Business partners + credit terms
- Sales orders, deliveries, A/R invoices
Three ways to connect
One: custom code against the Service Layer or DI API - maximum control, maximum maintenance. Two: a connector or iPaaS with prebuilt B1 adapters - faster, but field mapping and UDF (user-defined field) handling is still manual work. Three: an AI translation layer that reads the B1 schema, UDFs included, and generates the mapping - the approach OpusNext takes, which is why B1 connections land in weeks.
Mistakes that stall B1 projects
Ignoring UDFs until UAT, when half the catalog logic turns out to live in them. Mapping one price list when sales actually runs on twelve. Posting web orders as drafts that someone re-keys anyway. And testing against a tiny dev database, then discovering sync performance problems at the real 80,000-SKU catalog.
Puntos clave
- Confirm HANA vs SQL support in writing
- Sync items, price lists, BPs and orders - minimum
- UDFs are where B1 projects go to die; map them early
- AI-generated mapping turns months into weeks
Preguntas frecuentes
Does SAP Business One have built-in ecommerce?+
No. B1 ships without a storefront; every web channel is an integration - which is why the integration approach you pick matters more than the storefront.
Service Layer or DI API?+
Service Layer for HANA and new projects; DI API remains common on SQL installs. A good platform abstracts the choice away from you.
How long does a B1 ecommerce integration take?+
Hand-built: 3-6 months. Connector-based: 6-12 weeks. AI-mapped platforms like OpusNext: typically 2-6 weeks.