How Vision33 Saltbox (Adobe Commerce connector) connects to SAP Business One
Saltbox iPaaS with ExpressConnect templates
Vision33's documentation describes ExpressConnect templates that sit between Adobe Commerce and Business One. The Business One side is reached through the platform's own interfaces (the Service Layer or DI API, depending on version), and the storefront side through the Adobe Commerce REST API. Templates define the field mappings and schedules, and you adjust them per project.
Scheduled and event driven sync
Orders typically flow from the storefront to Business One as sales orders, while item master data, prices and stock levels flow back out. Exact scheduling options depend on the template and the Saltbox plan, so confirm them with Vision33 before design.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Adobe Commerce | SAP Business One | Web orders as sales orders, with customer and ship-to | New or paid order, polled on a schedule |
| Adobe Commerce | SAP Business One | New customer accounts as business partners | Customer registration or first order |
| SAP Business One | Adobe Commerce | Item master, descriptions, price lists | Item or price change, scheduled sync |
| SAP Business One | Adobe Commerce | On-hand and available stock by warehouse | Inventory movement, scheduled sync |
| SAP Business One | Adobe Commerce | Shipment and tracking details from deliveries | Delivery document posted |
Setting it up
- 1Define scopeDecide which flows are in scope: orders only, or orders plus items, prices, stock and shipments. Decide which system owns each field.
- 2Prepare Business OneCreate an integration user with the minimum authorisations, and confirm item groups, warehouses, price lists and payment terms that the storefront will reference.
- 3Register the Adobe Commerce integrationCreate an integration or API token in the Adobe Commerce admin with only the resources the template needs.
- 4Configure the ExpressConnect templatesMap storefront attributes to Business One item and user defined fields, and map payment and shipping methods to Business One equivalents.
- 5Map customersDecide whether web customers become individual business partners or map to a single web customer with ship-to addresses.
- 6Test with a sandbox companyRun orders through a Business One test database including partial payments, backorders, discounts and tax cases.
- 7Go live in stagesStart with order import, add stock and price export once orders are clean, and monitor the Saltbox error queue daily at first.
What usually breaks
- !SKU or item code mismatches between Adobe Commerce and Business One cause orders to fail on import. Keep one authoritative item code.
- !Unit of measure differences (each versus case) lead to wrong quantities on the sales order. Map them explicitly.
- !Tax codes in Adobe Commerce rarely match Business One tax groups one to one, so totals can differ by a few cents or by whole tax lines.
- !Stock sync that reads on-hand instead of available (on hand minus committed) oversells items already allocated to other orders.
- !Duplicate customers are created when email or address formatting differs between the two systems.
- !Upgrading Adobe Commerce or Business One can change APIs or custom attributes, so retest the templates after each upgrade.
A private AI layer across both systems
Failed order triage
A private assistant reads the Saltbox error log and the Business One master data, explains in plain language why an order failed (inactive item, missing tax group, credit hold) and drafts the fix for a person to approve.
Order and stock reconciliation
Compares storefront orders against Business One sales orders and flags missing, duplicated or mismatched ones, plus items whose web stock differs from available stock.
Plain language questions across both systems
Lets sales and support ask where an order is, whether it shipped and what it cost, without opening two admin consoles. Answers are read only and show the query used.
Catalogue data cleanup
Finds items with missing weights, inconsistent descriptions or unmapped attributes before they break a sync, and proposes corrections for approval.
When something else fits better
- Alumio or another iPaaS if you already use it elsewhere and want one integration platform.
- A Business One add-on or certified connector from an SAP partner if you prefer a fixed product over configurable templates.
- For low order volumes, a CSV import and export routine may be enough and costs far less to maintain.
Frequently asked questions
Does Saltbox work with on-prem SAP Business One?
Vision33 documents Saltbox for Business One generally. On-prem installations normally need a network route from the integration platform to the Business One server, such as a secure agent or VPN, so confirm the connectivity model with Vision33 during design.
Which data does the Adobe Commerce template move?
Per Vision33's documentation, orders, items and customers. Stock, prices and shipments are commonly added in the same project but should be confirmed per template version.
Can we change the field mappings?
Yes, ExpressConnect templates are meant to be adapted per project, including user defined fields. Keep a record of changes so they survive template updates and platform upgrades.
Where does AI fit without touching the connector?
A private assistant can read the Saltbox logs, Adobe Commerce orders and Business One tables read only, then explain failures and suggest fixes. Any change is proposed to a person rather than written automatically.
Pairing documented at help.vision33.com/integrate-adobe-commerce-and-sap-business-one . Vision33 Saltbox (Adobe Commerce connector) is a product of Vision33; Netray is independent and not affiliated with either vendor.