WooCommerce → SAP Business One
Apps Required
A scheduled trigger polls WooCommerce every three minutes for newly created orders. Each order payload includes the order ID, customer ID, order date, line items with SKUs, quantities, and subtotals, shipping lines, tax lines, and the current order status.
A filter node passes only orders with a status of 'pending', ensuring that only new, unprocessed orders continue through the workflow. Completed, cancelled, or already-processed orders are dropped at this stage.
The workflow searches SAP Business One for an existing sales order that matches the WooCommerce order ID using a custom field (U_WEBORDID) and the customer reference number (NumAtCard). This prevents the same WooCommerce order from being entered into the ERP more than once.
A decision node evaluates the SAP search result. If a matching document number (DocNum) is found, the order already exists and the workflow stops. If no match is found, the workflow proceeds to create a new sales order in SAP Business One.
A new sales order is created in SAP Business One with comprehensive field mapping. The WooCommerce order date becomes the document date, the customer ID is prefixed to form the SAP card code, and the WooCommerce order ID is stored in both the customer reference field and a custom web order ID field for traceability. Document lines include each product line item with its SKU, quantity, unit price, and tax code, plus a separate line for shipping charges with the shipping method as the item code.
| Modules | Trigger |
|---|---|
| New orders created | Trigger when new orders are created in WooCommerce. |
| Orders updated | Trigger when orders are updated in WooCommerce. |
| New products created | Trigger when new products are created in WooCommerce. |
| Products updated | Trigger when products are updated in WooCommerce. |
Every pending WooCommerce order is automatically captured and entered into SAP Business One as a sales order—eliminating manual data entry and reducing order processing time from hours to minutes.
1
2
Before creating any order, the workflow searches SAP for an existing record matching the WooCommerce order ID. This ensures no order is entered twice, even if the trigger picks up the same order in consecutive polling cycles.
Product line items with SKUs, quantities, prices, and tax codes are mapped directly from WooCommerce, and shipping charges appear as a separate document line—giving finance and warehouse teams a complete picture of every order.
3
4
The WooCommerce order ID is stored in both the customer reference field and a custom web order ID field in SAP, creating a clear audit trail that links every ERP sales order back to its original eCommerce transaction.
1
Every pending WooCommerce order is automatically captured and entered into SAP Business One as a sales order—eliminating manual data entry and reducing order processing time from hours to minutes.
2
Before creating any order, the workflow searches SAP for an existing record matching the WooCommerce order ID. This ensures no order is entered twice, even if the trigger picks up the same order in consecutive polling cycles.
3
Product line items with SKUs, quantities, prices, and tax codes are mapped directly from WooCommerce, and shipping charges appear as a separate document line—giving finance and warehouse teams a complete picture of every order.
4
The WooCommerce order ID is stored in both the customer reference field and a custom web order ID field in SAP, creating a clear audit trail that links every ERP sales order back to its original eCommerce transaction.
Common questions about this automation template.
Automate smarter with an AI-native platform designed for the way mid-market businesses really work.