SAP Business One e-commerce integration.

In shortAn SAP Business One e-commerce integration connects your online store to SAP so that items, stock and prices flow from SAP Business One to the shop, and orders, customers and payments flow back without re-typing. Kodenova builds this for Shopify, WooCommerce and Magento (Adobe Commerce): products are matched to SAP item codes, stock comes from the warehouses you choose, web orders become sales orders and A/R invoices, and fulfilment status goes back to the store. The integration writes through the Service Layer (or the DI API where needed), never with direct SQL, on SQL Server and SAP HANA. Fixed price per phase, 3 months of free post-go-live support, and the client owns the code, database and documentation after each paid phase.

By Zain Abbas, Founder & Lead SAP Business One / AI Engineer · Last updated 2 November 2026

Discuss this service → What’s included

What’s included

What we build.

Items and SKU mapping

Each store product or variant is mapped to an SAP Business One item code. Item master data and descriptions flow from SAP to the store, and unmatched SKUs are reported instead of guessed.

Stock by warehouse

Available stock is read per warehouse from the item-warehouse data (OITW) for the warehouses you choose, and sent to the store on a schedule or when stock changes.

Price lists

Prices from one or more SAP price lists (ITM1, OPLN) published to the store, including customer-specific or group prices where your setup uses them.

Orders into SAP

Web orders created in SAP Business One as sales orders (ORDR), or straight as A/R invoices (OINV) where that is your process, through SAP’s own validation. Duplicates are blocked by the store order number.

Customers and business partners

A web customer is matched to an existing business partner or created as a new one, by the rules you set (email, tax ID, guest checkout to one shared customer).

Payments and invoices

Gateway payments recorded as incoming payments (ORCT) against the invoice, and invoice numbers or PDFs sent back to the store or to the customer.

Fulfilment status

Delivery and invoice status from SAP Business One sent back to the store so customers see processing, shipped or completed without a phone call.

Error queue, retries and logs

Every order and update is logged. A failed one waits in an error queue with the reason, is retried, and can be fixed and replayed by your team.

Who it’s for

Built for teams like yours.

Companies running SAP Business One that sell online and re-type web orders or update stock by hand

Distributors and manufacturers opening a B2C or B2B web shop on Shopify, WooCommerce or Magento

SAP Business One partners who need a team to build the shop connection for a customer

SAP B1 Service LayerDI APIShopifyWooCommerceMagento (Adobe Commerce)REST APIWebhooksSQL ServerSAP HANAC# / .NET

Process

How a project runs.

Discovery: a free discovery call about your store, your SAP Business One setup (SQL Server or HANA, version, warehouses, price lists) and how orders are handled today.
Specification: what syncs in which direction and how often, how SKUs, warehouses, tax codes, shipping and payment methods map to SAP, and what happens on errors, written into the proposal with a fixed price per phase.
Build: the integration middleware, with weekly demos on a test company and a test store, never on your live data first.
Testing: real order scenarios: partial stock, refunds and credit notes, guest and returning customers, failed payments, and retries after an error.
Go-live: initial item and stock load, cut-over, and close watch on the first live orders.
Support: 3 months of free support after go-live: fixes and small adjustments, then optional monthly support.

How does a store connect to SAP Business One?

A small integration service sits between the store and SAP Business One. It reads and writes SAP through the Service Layer (REST), or the DI API where the Service Layer does not cover a case, so every document passes SAP’s own validation and nothing is written to the database with SQL. On the store side it uses the platform’s API: Shopify and WooCommerce through their APIs and webhooks, Magento (Adobe Commerce) through its REST API.

Updates run either on a schedule or when the store sends a webhook, depending on the platform and how fresh the data must be. The same design works on SQL Server and on SAP HANA.

SAP Business One Service Layer guide →

What syncs between the store and SAP Business One?

From SAP to the store: items, prices, stock and order status. From the store to SAP: orders, customers and payments. The exact list, direction and timing are agreed in the specification, because they depend on who owns each piece of data in your business.

Who owns the integration code?

You do. After each paid phase the client owns the source code, database and documentation, so you can keep maintaining it with your own team or your SAP Business One partner, or ask us to keep supporting it.

Free tools: Service Layer request builder · SAP B1 table reference · ORDR: sales order table · OITW: stock per warehouse

FAQ

SAP Business One e-commerce integration: common questions

Which e-commerce platforms can you connect to SAP Business One?

Shopify, WooCommerce and Magento (Adobe Commerce). Shopify and WooCommerce are connected through their APIs and webhooks; Magento is integrated through its REST API. Other platforms with an API can usually be connected the same way, which we confirm in the discovery call.

How do web orders get into SAP Business One?

The integration creates a sales order (or an A/R invoice, if that is your process) in SAP Business One through the Service Layer, after matching or creating the business partner and mapping each SKU to an item code. The store order number is kept on the document, so the same order is never created twice.

How is stock kept correct in the store?

Stock is read per warehouse from SAP Business One for the warehouses you choose, and sent to the store on a schedule or when it changes. Which warehouses count as sellable, and whether committed stock is deducted, is decided in the specification.

What happens when an order fails to sync?

It goes to an error queue with the reason, for example an unknown SKU, a blocked customer or an item out of stock, and nothing is lost. It is retried automatically where that makes sense, and your team can fix the cause and replay it. Everything is logged.

Does it work with SQL Server and SAP HANA?

Yes. The integration talks to the Service Layer and the DI API, not to the database, so it works the same on both. Any SQL used for reporting is written for the database you run.

Is Kodenova an SAP partner?

No. Kodenova is independent and works alongside your SAP partner. Your partner keeps the licences and the SAP Business One system; we specify, build, test and support the integration between your store and SAP.

Related services

SAP Business One

Ready to get started?

Tell us what you need. You get a clear technical answer, a fixed scope and a price, usually within 24 hours.

Start a project Chat on WhatsApp