Magento and Adobe Commerce Connector

The problem: two systems, two versions of the truth

A B2B storefront that cannot see SAP Business One is a catalogue with a shopping cart bolted on. Your contract customer logs in and sees list price instead of their negotiated price. Someone at their end orders past a credit limit that was reduced last week. Stock shows available because the last export ran overnight and two Warehouses have shipped since. Orders arrive as emails or CSV files and are keyed into SAP B1 by hand, which is where the wrong Business Partner, the wrong price list and the wrong tax code get introduced.

Meanwhile nobody on the customer's side can see an order once it leaves the cart. They phone to ask whether it shipped, and someone opens SAP Business One to read the Delivery aloud.

The usual attempt at fixing this is a pile of scripts: a nightly product feed, a cron job that pulls orders, a spreadsheet for pricing. It works until a price list changes shape, a payload arrives twice, or a run fails at 2am with no log and no retry.

ECOSIRE builds a connector that treats SAP Business One as the master for commercial data and Magento or Adobe Commerce as the channel, with explicit ownership per field and a durable queue between them.

What ECOSIRE builds

The connector is a SAP Business One integration built on the Service Layer (REST) for reads and document creation, the DI API where a document needs transactional control, and UDF/UDT extensibility to carry channel identifiers and sync state on SAP B1 records. On the commerce side it uses the platform's REST and GraphQL APIs and its asynchronous bulk endpoints for volume operations.

Catalogue and inventory

Item master data flows from SAP B1 to the storefront: descriptions, unit of measure, item groups mapped to categories, weights and dimensions, and attribute values sourced from item fields or UDFs. Stock is published per Warehouse with a configurable availability formula, so you can publish on-hand, on-hand minus committed, or a specific subset of warehouses per store view. Multi-store and multi-website setups map to different price lists and warehouse sets.

B2B pricing that actually reflects the contract

This is where most integrations quietly fail. The connector resolves the price the customer would receive in SAP Business One — Price Lists, special prices by Business Partner, period and volume discounts, and discount groups — and publishes it to the storefront as customer-group or customer-specific pricing, or resolves it live at cart time through a real-time price call when your contracts are too dynamic to precompute. Currency and tax treatment follow the Business Partner's setup rather than a store default.

Credit limits and account status

Before an order is accepted the connector checks the Business Partner's credit limit, current balance and open deliveries, plus hold status, and can block checkout, force prepayment, or route the order to a pending queue for a human decision. That check is served from SAP B1, not from a cached number that was true last night.

Orders, shipments and invoices

Storefront orders become Sales Orders in SAP Business One with the correct Business Partner, contact person, addresses, price list, payment terms, tax codes and a channel reference stored in a UDF. Line-level mapping handles bundles, configurable products and free-text lines. Going the other way, Deliveries post shipment and tracking information back to the order, and A/R Invoices publish to the customer's account area, so the storefront becomes a genuine self-service portal instead of a phone queue. Returns can be mapped to Returns and A/R Credit Memos where your process requires it.

Reliability, not hope

Every direction runs through a durable queue with idempotency keys, so a replayed webhook or a retried batch cannot create a duplicate Sales Order. Failures land in a dead-letter view with the exact payload and error, retried on a schedule or by hand. A mapping table records every SAP B1 key against its channel key, which is what makes reconciliation possible. An operations dashboard shows queue depth, last successful run per entity and unresolved failures.

Who this is for

B2B and mixed B2B/B2C merchants running Magento Open Source or Adobe Commerce with SAP Business One as the system of record — distributors, wholesalers and manufacturers with negotiated pricing, credit terms and multi-warehouse fulfilment. It suits companies whose current integration is a set of scheduled exports they no longer trust.

Compatibility

SAP Business One 10.0 on Microsoft SQL Server or SAP HANA, on-premise or cloud-hosted, against Magento 2.4-line and Adobe Commerce releases including Cloud. Delivered per tenant, installed into your test company database and a non-production storefront first.

How delivery works

1. Scoping call. We map entity by entity: which system owns each field, which price mechanisms are in play, how many store views and warehouses, and what your order volume looks like at peak. 2. Fixed quote. A written scope naming every synchronised entity, the direction and ownership of each field, the mapping rules, and a fixed price. 3. Build. Typical lead time is two to four weeks from scope sign-off. Complex pricing logic, many store views or unusual product types extend that, and the quote says so. 4. Install in test. Installed into your test company database against a staging storefront, then loaded with your own catalogue and your own contract customers so you can verify prices person by person. 5. Production. Cutover with an agreed initial-load sequence and a rollback point, then live monitoring through the first order days. 6. Support. A defined support window covering defects, mapping adjustments and handover questions.

This is build-to-order software. There is no instant download and no trial instance — the connector is developed for your SAP Business One schema and your storefront configuration.