Connecting SAP Business One to Magento: orders and stock sync in 2026

If you use SAP Business One as your ERP while simultaneously running a Magento webshop, you know the problem: manually retyping orders, inaccurate inventory figures, and customer data being maintained in duplicate. At a certain point, that system simply stops working — especially as order volume grows.

An integration between both systems solves this. But how do you approach it, and what should you look out for?

What do you actually want to synchronize?

Before choosing an integration route, it is wise to determine exactly which data flows you want to automate. The most commonly requested connections between SAP Business One and Magento are:

• Orders — Magento orders are automatically created as sales orders in SAP B1

• Inventory — Stock changes in SAP are sent to Magento in real-time or periodically

• Products — Item data (description, price, SKU) is managed and published from SAP

• Customer data — Business partners and contact persons are synchronized

• Customer-specific pricing — Discount groups and price agreements per account appear directly in the webshop

• Order statuses and tracking — Tracking numbers entered in SAP automatically appear for the customer in Magento

For B2B webshops, customer-specific pricing and assortments are often the most critical component. If that link is missing, the shopping cart is simply incorrect for logged-in business customers.

The three main routes for integration

1. Middleware / iPaaS platform

The most common approach for SMEs is a middleware platform that acts as an intermediate layer. SAP Business One offers two API options for this: the Service Layer (a RESTful OData API) and the older DI-API. Magento, on its side, offers REST and GraphQL APIs. A middleware platform translates messages between both systems, handles mapping, and monitors the data flow.

Examples of platforms used for this include Conneqt, APPSeCONNECT, and Alumio. Conneqt — the integration platform deployed by Epartment for ERP integrations with Magento — offers an out-of-the-box SAP Business One-Magento connector with proven data flows for orders, inventory, pricing, and customers. This saves a considerable amount of configuration time compared to custom development.

Portacon, a distributor of access control systems, saves up to 40% of time on order processing thanks to such an integration, according to their case study on the Conneqt website.

Pros: Fast implementation, monitoring dashboard, scalability, no deep SAP-SDK expertise required

Cons: Monthly subscription costs, limited flexibility with exotic business logic

2. Direct API connection (custom build)

With a direct integration, you build the connection between the SAP Service Layer and Magento's REST API yourself. This provides maximum control over the data flow and business logic, but it also requires development capacity that knows both SAP and Magento well.

Typical approach:

1. Authenticate via the SAP Service Layer (session token or OAuth)

2. Pull inventory data from SAP and push it to Magento via PUT /V1/products/:sku or bulk endpoints

3. Listen to Magento webhooks or queues for new orders

4. POST orders as SalesOrders to the Service Layer

A direct connection makes sense if you have very specific requirements — such as complex pricing logic, custom workflows, or integration with a WMS alongside SAP. In that case, ensure proper logging, retry logic, and monitoring: without these, troubleshooting production issues will become a nightmare.

Pros: Full control, no middleware licensing costs

Cons: Higher initial costs, maintenance entirely on your own account, more technical expertise required

3. Batch files (CSV/XML)

For organizations just starting with automation or needing a temporary solution, CSV or XML exports from SAP and imports via Magento's import feature are an option. This is not real-time — the minimum synchronization frequency is once a night — but it is easy to achieve and requires little technical knowledge.

This approach scales poorly as order volume increases and is prone to errors when file formats change. Consider it a temporary measure, not a long-term solution.

Real-time vs. batch: a hybrid approach works best

Not all data has the same urgency. A hybrid synchronization strategy is practical:

• Real-time (event-driven): New Magento orders → directly to SAP; order status changes and shipping information → directly back to Magento

• Periodic (scheduled): Full inventory sync once a night, product data updates once an hour

This protects your webshop's performance while ensuring critical operational data still flows quickly.

Data mapping: the most underestimated challenge

Setting up the technical connection is often done faster than expected. What companies underestimate is the data mapping: SAP identifies an item as ItemCode, Magento as SKU. A customer in SAP is a CardCode, in Magento a Customer ID. If that mapping is incorrect, duplicate customer records, wrong inventory updates, and missing orders will occur.

Before going live, create a mapping document for:

• Item codes ↔ SKUs

• Customer identifiers (CardCode ↔ Customer/Company ID)

• Tax codes and price lists

• Warehouse codes ↔ Magento sources (multi-warehouse)

• Order status mapping (SAP statuses ↔ Magento statuses)

Preparation steps for a successful go-live

A structured approach prevents most problems:

1. Map out data flows — Determine which data flows in which direction and which system is the 'single source of truth' (usually SAP)

2. Create a mapping document — Map all relevant fields before building begins

3. Test with production data — Use a copy of real SAP data, not fictitious test items

4. Phased rollout — Go live with a subset of products or customers, then expand

5. Set up monitoring — Ensure logging, alerts for failed syncs, and a clear point of contact in case of errors

6. Rollback plan — Determine in advance how to revert to the pre-integration state if something goes wrong

B2B-specific functionality

Does your Magento webshop operate primarily as a B2B webshop for business customers? Then there are additional synchronization needs that do not apply to consumers at all:

• Customer-specific pricing — Every business customer has their own price agreements in SAP; these must be visible per logged-in user in Magento

• Customer-specific assortment — Some accounts are only permitted to see certain product groups

• Quotes — A quote request in Magento is directly created as a quotation in SAP

• OCI/cXML punchout — For customers who want to order via their own procurement system (SAP Ariba, Onventis)

Epartment regularly implements this B2B functionality, including in combination with extensive SAP integrations. An example is Op den Velde Groep, where a full B2B portal with SAP integration and OCI punchout was realized.

Managing product data: the role of a PIM

SAP Business One excels in financial data, inventory management, and order processing. For rich product content — marketing texts, images, multiple languages, technical specifications — SAP is less suitable. For larger catalogs, a separate PIM system like Akeneo makes sense: SAP manages operational data, Akeneo handles content-rich product information, and Magento displays the combined result.

Which approach suits you?

As a Magento specialist with over 10 years of experience in ERP integrations for e-commerce, Epartment guides companies through the entire process: from technical mapping to go-live and ongoing support. Whether you choose a middleware approach via Conneqt or custom development — the key lies in thorough preliminary research before the first line of code is written.

An SAP Business One integration with Magento that truly works is always built on clear data mapping, solid monitoring, and an organization that knows which system is the single source of truth. That way, manual retyping sessions permanently become a thing of the past.