WooCommerce and SAP Business One integration: 3 routes compared

Orders

WooCommerce orders become B1 Sales Orders – with the right Business Partner, tax code and freight; status and tracking flow back to the order.

Items

Simple and variable products map to B1 items, with each variation as its own item code – mastered in B1 and pushed to the store.

Inventory

Available-to-sell per warehouse into WooCommerce stock – the sync interval decides how often you oversell.

Pricing

B1 Price Lists, discounts and Business-Partner Special Prices – WooCommerce has no native place for them (see below).

Customers

WordPress user accounts map to Business Partners – matched by email or customer number, with billing and shipping addresses.

Where does the sync run – inside WordPress (plugin, WP-Cron) or in an external service that only calls the API?

Which B2B pricing plugin holds customer prices – and does the integration write Business-Partner Special Prices into it, or only whole Price Lists?

What happens to an order that fails to post – retry queue and alert, or a line in a log nobody reads?

If the store is a B2B channel, there is an alternative to rebuilding contract pricing in WordPress plugins: a storefront with a native SAP B1 adapter. The CS Order Suite reads customer-specific pricing, inventory and items straight from SAP Business One and posts Sales Orders back – no pricing plugin, no second pricing system, no WordPress stack to keep patched for the B2B side.

Is there a ready-made SAP Business One connector for WooCommerce?

Not from SAP or from WooCommerce itself – but third-party connector plugins, hosted connector services and iPaaS templates exist. They cover the standard flow: orders in as Sales Orders, inventory and tracking out. Before you commit, check two things: whether customer-specific Special Prices from B1 reach the store, and whether the connector is compatible with WooCommerce’s High-Performance Order Storage (HPOS).

How do WooCommerce orders get into SAP Business One automatically?

A WooCommerce webhook (order created or updated) or a scheduled pull via the REST API picks up the order; the integration matches the customer to a Business Partner, maps each SKU to a B1 item, applies tax code and freight, and posts a Sales Order through the Service Layer. Status, delivery and tracking number are written back to the WooCommerce order. Failed orders need a retry queue and an alert – not a silent log entry.

Can WooCommerce show customer-specific prices from SAP Business One?

Not out of the box: WooCommerce has one regular and one sale price per product. Customer- or group-specific prices need a B2B or wholesale pricing plugin, and the integration has to write the flattened B1 result – Price Lists, discounts and Business-Partner Special Prices – into that plugin’s data model and keep it current. That is the most common point where WooCommerce–B1 projects grow beyond the connector budget.

Which interfaces should a WooCommerce–SAP Business One integration use?

On the B1 side, the Service Layer (HTTP/OData) for new builds; the COM-based DI API still appears in older add-ons but needs a Windows host. On the WooCommerce side, the REST API (wc/v3) with consumer keys over HTTPS, plus webhooks for order events. Avoid writing directly into WordPress database tables: with HPOS, orders no longer live in the posts table, and direct writes bypass WooCommerce’s own logic.

Should the sync run as a WordPress plugin or outside WordPress?

For small catalogs and moderate order volume, a plugin is fine. Once you sync thousands of items, several price lists or frequent stock updates, run the heavy lifting outside WordPress – as an iPaaS flow or a small service – and talk to WooCommerce only through its API. Long-running sync jobs inside PHP requests, and WP-Cron that only fires on site visits, are the classic causes of slow stores and missed updates.