WooCommerce Store Connector

The problem

A WooCommerce store and a SAP Business One company database describe the same business with two different vocabularies. WooCommerce knows wp_posts product IDs, guest checkouts, coupon lines and payment gateway fees. SAP B1 knows OITM item codes, Business Partners, Sales Orders, A/R Invoices and Journal Entries. Nothing bridges them by default, so somebody in the office opens the WooCommerce admin every morning, reads an order, and retypes it into SAP B1.

That manual bridge fails in predictable ways. Item codes get mistyped, so stock in SAP B1 drifts from the storefront and the website oversells goods that are physically committed elsewhere. Price list changes made in SAP B1 never reach the storefront, so the shop sells at last quarter's price. Customers who bought online exist as one-off Business Partners with no email, no tax ID and no credit terms, which makes the A/R subledger unusable for collections. When the store runs a flash sale, order entry becomes a queue and the warehouse waits.

What ECOSIRE builds

ECOSIRE builds a per-tenant SAP Business One add-on that treats WooCommerce as an integrated sales channel rather than a spreadsheet source. It is not an off-the-shelf download — the connector is built against your item master, your price lists, your tax setup and your WooCommerce configuration after a scoping call.

Order intake into SAP B1

The connector polls the WooCommerce REST API (or receives WooCommerce webhooks, depending on your hosting) and posts each order into SAP B1 through the Service Layer. Depending on the workflow you choose in scoping, a WooCommerce order becomes a Sales Order (Orders), a Sales Delivery, or a draft A/R Invoice. Line items map to item codes; shipping and handling map to a service line or a freight code; discounts map to the line discount percent or a dedicated discount item; payment gateway fees map to a separate expense line or a Journal Entry, as you specify.

Every synced document carries UDFs on the marketing document header recording the WooCommerce order ID, the store code, the gateway transaction reference and the raw payload checksum. That makes reconciliation between the storefront report and the SAP B1 sales report a query, not an investigation.

Customer and address handling

The connector resolves each WooCommerce customer to a Business Partner. Matching rules are configurable — email, tax ID, or a WooCommerce customer ID stored in a UDF on OCRD. New shoppers create a Business Partner in the customer group, series and payment terms you nominate. Billing and shipping addresses are written as BP addresses so that tax determination and delivery routing behave the same for web orders as for phone orders. Guest checkouts can be routed to a single catch-all Business Partner or to individually created ones, whichever your accountant prefers.

Stock, price and catalogue push

Running the other direction, the connector pushes SAP B1 data to WooCommerce. Available-to-promise quantity is calculated per warehouse (or across a nominated set of warehouses) from OITW, with configurable buffers so you never sell the last unit twice. Prices are read from a nominated price list, with special prices and period/volume discounts respected where they apply to your web customer group. Item master changes — description, weight, dimensions, barcode, status — can update the matching WooCommerce product. Items marked inactive or frozen in SAP B1 can be set to draft or out-of-stock on the storefront.

Fulfilment and financial write-back

When the warehouse picks and delivers in SAP B1, the connector updates the WooCommerce order status and writes the tracking number and carrier into the order notes so the shopper gets a real shipping email. When an A/R Invoice is added, the invoice number and PDF (Crystal Report layout, if you use one) can be attached back to the WooCommerce order. Refunds issued in WooCommerce can raise an A/R Credit Memo, or be queued for approval before doing so.

Reliability and observability

Every message is queued and idempotent, keyed on the WooCommerce order ID, so a retry after a timeout never creates a duplicate Sales Order. Failures land in a UDT-based error log with the payload, the Service Layer response and a retry button, plus optional email alerts. A UDO-based configuration screen inside the SAP B1 client holds the mapping tables — item code mapping, tax code mapping, payment method to G/L account, store to warehouse — so your team edits rules without touching code.

Who it is for

SMB distributors and manufacturers running SAP Business One 10.0 who sell through one or more WooCommerce storefronts and are currently rekeying orders or maintaining a home-grown CSV process. It suits businesses with a real item master, real price lists and real warehouses — the more structure exists in SAP B1, the more the connector can enforce.

How delivery works

1. Scoping call. We walk your WooCommerce configuration, your SAP B1 company database, your document flow (order vs delivery vs invoice), your tax setup and your fulfilment process. You get a written scope listing every mapping and every edge case we agreed to handle. 2. Fixed quote. One price for the agreed scope. Changes after sign-off are quoted separately, never silently absorbed or silently dropped. 3. Build. ECOSIRE develops against the SAP Business One Service Layer and DI API, with UDFs, UDTs and UDOs created by a scripted installer rather than by hand. 4. Install into your test company. The add-on goes into your test company database first. We run your real order shapes through it and you sign off on the documents it produces. 5. Production install. Once test is signed off, we install into the production company database, configure the mappings, and run a supervised first live sync. 6. Support window. A defect-fix support window follows go-live, covering anything that does not behave as the signed scope describes.

Typical build and delivery time for a single storefront is one working week from signed scope, depending on how many document types and mapping rules are in play.