# i95Dev Connect for Adobe Commerce and SAP Business One: store sync

> Source: https://netray.co/stack/i95dev-adobe-commerce-connector-sap-business-one
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Stack

## Short answer

The i95Dev SAP Business One Connect syncs orders, customers, products and inventory between Adobe Commerce (Magento) and SAP Business One running on SQL Server or HANA. It is delivered as an Adobe Commerce Marketplace extension plus an SAP B1 component. It suits manufacturers selling parts or finished goods online that want B1 as the system of record.

## Erp

SAP Business One

## Erp Key

sap-b1

## On Prem

true

## Product

i95Dev SAP Business One Connect for Adobe Commerce

## Vendor

i95Dev

## Category

E-commerce connector

## Integration

**Method:** Adobe Commerce Marketplace extension

**Detail:** An extension installed in the Adobe Commerce (Magento) store adds the sync configuration, queues and data mapping on the storefront side.

**Method:** SAP Business One component

**Detail:** A component on the Business One side moves data in and out of B1. The exact transport (for example Service Layer or DI API) is the vendor's design, so confirm it and the supported B1 versions with i95Dev.

## Data Flows

**From:** Adobe Commerce

**To:** Business One

**Data:** Web orders, new customers, payment and shipping details

**Trigger:** Order placed, or scheduled sync

**From:** Business One

**To:** Adobe Commerce

**Data:** Products, prices, categories and attributes

**Trigger:** Item master change or scheduled sync

**From:** Business One

**To:** Adobe Commerce

**Data:** Available inventory by warehouse

**Trigger:** Stock movement or scheduled sync

**From:** Business One

**To:** Adobe Commerce

**Data:** Order status, shipment and tracking information

**Trigger:** Delivery posted in B1

## Setup

### Confirm versions and database

**Detail:** Match Adobe Commerce version and Business One version (SQL or HANA) with the connector's supported list.

### Install the extension and B1 component

**Detail:** Install the Marketplace extension in a staging store and the B1 component in a test company.

### Decide the system of record

**Detail:** Normally B1 owns items, prices and stock; the store owns web content and checkout. Write this down per field.

### Map customers, tax and payment

**Detail:** Map web customer groups to B1 business partner groups, tax codes to B1 tax codes, and payment methods to B1 payment terms or incoming payments.

### Map warehouses and shipping methods

**Detail:** Choose which B1 warehouses feed web availability and map shipping methods to delivery methods in B1.

### Run end-to-end tests

**Detail:** Place test orders with discounts, partial shipments, cancellations and returns, and compare both systems.

### Go live and monitor queues

**Detail:** Watch sync queues and error logs for the first weeks, with a named owner for failed records.

## Pitfalls

- Product attributes and units of measure that do not map between B1 and Magento, creating items sold in the wrong unit.
- Inventory counts that lag, leading to overselling.
- Tax codes and rounding that differ, so order totals do not match between store and B1.
- Duplicate customers created because web emails do not match existing B1 business partners.
- Large catalog syncs slowing the live store or B1 during business hours.
- Magento or B1 upgrades without retesting, breaking the connector mapping.

## Ai Layer

### Failed sync record triage

**Description:** A private assistant reads the connector's error queue with the related B1 and store records and explains each failure in plain language, such as a missing tax code, and drafts a fix for the owner to approve.

### Store versus B1 reconciliation

**Description:** Ask which web orders from the past week are missing in B1 or have different totals, and get the list with the query shown.

### Catalog data quality review

**Description:** The assistant scans B1 items marked for the web for missing descriptions, weights or units, and drafts a cleanup list for the merchandiser to review.

## Alternatives

- A manual CSV import of web orders into B1 can work at very low order volumes.
- A different connector or an integration platform may suit you if you also connect marketplaces, 3PLs or EDI.
- A B1-native web store or portal avoids syncing two catalogs if your needs are simple.

## Faq

### Which Business One databases are supported?

**Answer:** The vendor describes support for Business One on SQL Server or HANA. Check the supported B1 versions and Adobe Commerce versions with i95Dev before you plan, as both platforms move on their own release schedules.

### What syncs between the store and Business One?

**Answer:** Orders, customers, products and inventory are the documented items. Details such as price lists, order status and shipping tracking depend on how the connector is configured, so confirm each in a test before relying on it.

### Who should own failed records?

**Answer:** Name one person or team who reviews the error queue daily. Without an owner, failed orders sit unnoticed. A private AI assistant can summarize the queue, but a person should approve any fix that changes data.

## Source

https://commercemarketplace.adobe.com/i95dev-i95devsapconnect.html

## Search terms

magento sap business one connector i95dev, adobe commerce sap business one integration, sap b1 magento order sync, i95dev sap business one, sap business one ecommerce connector, magento sap b1 inventory sync

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json