On Webshop Connector is a middleware component that connects an online shop (Shopware, Shopify, Magento, WooCommerce, OXID, etc.) with SAP Business One. The connector's task is bidirectional synchronisation: articles, prices, and stock data flow from B1 into the shop; orders, customer data, and status updates flow from the shop back into B1 — the speed, depth, and scope of fields in the synchronisation depend on the business model.
Context
Technically, a webshop connector is based either on B1if scenarios or on proprietary middleware products (e.g. Magnalister, i-views, Sync4, Pickware). The information flow typically runs via REST/JSON (Shop-API) and the SAP B1 Service Layer or DI API. Article attributes (description, images, variants, tax classes) are mostly synchronised per product, stock is updated daily or hourly, prices depend on the price list structure. Incoming orders land as customer orders in B1; payment methods are mapped to B1 payment channels. For B2B scenarios, customer login, differentiated price lists per business partner, discount logic, and approval processes are added. Advanced scenarios link the shop to PIM systems (e.g. Perfion) and DMS (CKS.DMS) for product data and document storage.
Demarcation
A webshop connector is neither a shop system nor ERP logic – it mediates. The business logic (credit checks, delivery status, dunning) remains in B1, the customer experience in the shop. It is also not a generic ETL tool: product packages for Shopware, Magento etc. bring pre-defined mappings and update cycles that generic ETL would not provide. It must also be distinguished from pure Marketplace Integrations (Amazon, eBay), which require their own tool landscapes — even if marketplace orders can ultimately also land in the webshop connector or a variation thereof.
ReAct and RLEF: How Artificial Intelligence Learns from Real Mistakes — and What Automated Bank Reconciliation in SAP Business One Has to Do with It
SAP B1 10.0 FP2608: Service Layer AI as a transactional layer
Process Reward Models: Why a correct result does not yet prove a correct method
Test-Time Compute Scaling: Why a Smaller AI Model Can End Up Winning — and What Supplier Comparison in SAP Business One Has to Do With It
RLHF and reward models: AI hype or what the approval process in SAP Business One has to do with it
