We connect SAP Business One to your online store through its Service Layer, so items, price lists, stock and orders stay in step, with network access and licensing agreed with your SAP partner first.

Service Layer basedSecure network routePartner-aligned design

Start a project

Service Layer basedDesigned around how your team already works.

Secure network routeDesigned around how your team already works.

Partner-aligned designDesigned around how your team already works.

Start a projectTell us what you are building. The first conversation is free.

01Our Approach

SAP Business One usually sits on a server inside the company, so reaching it safely matters as much as mapping the fields.

02Overview

Your web store connected to Business One

01Service Layer based
02Secure network route
03Partner-aligned design

SAP Business One ecommerce integration publishes items, price lists, customer-specific prices and warehouse stock from Business One to your store, and writes web orders back as sales orders with their business partner, taxes and freight. We build on the Service Layer, SAP's web API for Business One, with a service between the two systems that maps, queues and retries each document.

It suits distributors, manufacturers and retailers who run Business One and sell through Shopify, WooCommerce or a custom B2B portal. Two questions come before any design. The first is how an outside service can reach your Business One server securely. The second is which SAP licences cover access by an integration. Both are settled with your SAP partner and your IT team at the start.

Talk to us about your project

03What We Do

Capabilities, End to End

Master data mapping

Items, item groups, price lists, special prices, business partners, warehouses, tax codes and user-defined fields are mapped to the store's products, customers and orders.

Document ownership

Business One owns items, prices, stock and all posted documents. The store submits orders, and Business One assigns the document number and controls every later step.

Sessions and network access

The service signs in to the Service Layer as a dedicated user over an encrypted, restricted route such as a private tunnel, never through an openly exposed port.

Error queue

A document Business One refuses, such as an order exceeding a credit limit or naming an inactive item, waits with the error text for a decision.

Retries and session renewal

Expired sessions are renewed automatically, interrupted calls are retried with a reference that prevents a duplicate order, and updates are paced to protect the server.

Sync and server monitoring

Connection status, sync delay, failures and stock differences are tracked, and an alert is raised when the Business One server cannot be reached.

04In Production

What It Looks Like When It Ships

app.atlasfreight.io/overview

Live

Atlas Freight

Shipments / Live

Search...

⌘K

WORKSPACE

Shipments

Fleet

Routes

Customs

Analytics

Partners

Settings

Usage

72% of plan

Inventory

1,204 SKUs across 3 warehouses

AllLowOut

Reorder

3 items below reorder point - suggested PO ready

Review

Product

SKU

Stock level

Status

Track

SKU-1042

82 units

In stock

Dispatch

SKU-1043

34 units

In stock

Documents

SKU-1044

12 units

Low

Trail Jacket

SKU-1045

0 units

Out

Service Layer based

Secure network route

Partner-aligned design

Price listsOrder documentConnection statusHeld documents

05What You Receive

Handed Over, Ready to Run

SCROLL

Master data and document mapping

Network access design

Integration service with source code

Web orders as sales orders

Stock and price publication

Error queue with replay

Connection and sync monitoring

Runbook for IT and partner

06How It Runs

From Kickoff to Launch

Check the foundations

Map the documents

Build and verify

Go live together

Check the foundations

With IT and your SAP partner we confirm the Business One version and database, whether the Service Layer is installed, how it can be reached and which licences apply.

Map the documents

We agree how items, prices and stock appear online, how a web order becomes a sales order and how deliveries, invoices and returns report back to the customer.

Build and verify

Development uses a test company database and a development store, and the scenarios cover your special prices, several warehouses, backorders, approval procedures and deliberately failed documents.

Go live together

Production access is opened under your IT team's control, live orders begin to flow and the first trading days are reconciled jointly with your SAP partner.

07Technology

The Stack We Use

SAP sideService Layer (OData)User-defined fieldsSQL viewsApproval proceduresIntegration serviceNode.jsTypeScriptPostgreSQLMessage queuesSAP sideService Layer (OData)User-defined fieldsSQL viewsApproval proceduresIntegration serviceNode.jsTypeScriptPostgreSQLMessage queues

Store sideShopify Admin APIWooCommerce REST APICustom portal APIsWebhooksConnectivityPrivate tunnelsIP allow listsTLS certificatesConnection checksStore sideShopify Admin APIWooCommerce REST APICustom portal APIsWebhooksConnectivityPrivate tunnelsIP allow listsTLS certificatesConnection checks

08Who It Is For

Built for Teams Like Yours

FLAGSHIP

Business One knows your stock and the store does not

Prices and quantities are exported from Business One and uploaded to the site. Web orders are printed and keyed in as sales orders. B2B customers phone to ask for their own prices. Your SAP partner maintains the ERP but does not build storefronts.

Distributors selling online

B2B portals with special prices

Shopify on Business One

WooCommerce on Business One

Stock across several warehouses

Manufacturers selling spare parts

09Questions

What buyers ask before they start

If yours is not here, ask us directly. The first conversation is free and useful whether or not we work together.

Book a call

The Service Layer installed and reachable, a dedicated user for the integration and a test company database. SAP has specific licensing rules for access by third-party applications, often described as indirect access, and they have changed over the years. Your SAP partner confirms which licences your installation requires. We do not advise on SAP licensing, and we build only once that question is answered in writing.

The Service Layer was introduced for the SAP HANA version and later made available for the Microsoft SQL Server version in recent releases of Business One. Older SQL Server installations may have only the DI API, an older interface that requires a component on your network. We confirm your version first, because it decides the approach and sometimes makes a Business One upgrade the sensible first step.

Through a route your IT team controls. Common choices are a private tunnel between our service and your network, or publishing the Service Layer behind a gateway that accepts only our addresses over encrypted connections. We never recommend exposing Business One directly to the internet. If your installation is hosted by a partner, we agree the access method with that host instead.

Yes. Business One holds price lists, special prices for individual business partners and discount groups, and the integration can show each signed-in customer the price that would apply to them. Stock can be shown by warehouse or as a single available quantity. Volume permitting, prices are checked again when the order is placed, so that the document matches what Business One would calculate.

An essential one. The partner knows your configuration, user-defined fields and add-ons, controls the server and advises on licensing. We ask them to review the mapping and anything touching approvals or posting. In return, the integration is documented so they can support Business One without needing to understand the store. Clear boundaries between the two of us keep later maintenance simple.

GuidesFree to use with any company