Loading…
B2B distributors and manufacturers who run SAP Business One often choose Adobe Commerce (Magento) for its customer groups, tiered pricing and quoting features that B2B storefronts need. The catch is that all of that pricing and stock data originates in SAP B1, and keeping Magento in step by hand is a full-time job that still leaves customers seeing the wrong price or out-of-stock items. An SAP Business One Adobe Commerce (Magento) integration syncs items, customer-group and tier prices and per-warehouse stock from SAP B1 to Magento, brings Magento orders and B2B company accounts into SAP B1, and returns shipment and invoice data. AIONDATA builds this using the SAP B1 Service Layer and Magento’s REST API, with an option for a custom Magento module where webhooks or bulk operations need to be added.
Outcomes
Orders can be pushed to SAP B1 within seconds using Magento event observers or a small custom module; without a module we poll new orders every few minutes. Stock and price updates are scheduled, typically every 5 to 15 minutes for stock and hourly for prices, using Magento’s bulk asynchronous API to stay within performance limits. We tune intervals to catalogue size and order volume.
We map SAP B1 ItemCode to Magento SKU, define how variants become configurable products, and map each SAP B1 price list to a Magento customer group or tier. Customers are matched on email or a stored CardCode and B2B companies on tax ID so accounts are not duplicated. Orders that fail in SAP B1 go to a retry queue with alerts and a dashboard showing the SAP error for correction.
Yes. We can build a custom MCP server that exposes the SAP B1 Service Layer and the Magento REST API as tools, so an assistant can check a customer’s price for an item, trace an order or trigger a re-sync. Write actions are restricted to approved operations.
A standard products, prices, stock, orders, customers and shipments sync usually takes a few weeks to build and test against a copy of your SAP B1 company and a Magento staging site. Large catalogues, configurable product hierarchies, multiple websites or B2B company approval workflows extend the timeline, typically to two to three months.
Other pairs involving SAP B1 or Magento.
Share your objects, volumes, and timing needs — we'll come back with a written scope.