Store event
WooCommerce emits an order, product, customer or refund change.
WooCommerce ERP connector pilot
WooCommerce.
Orders in control.
Design the path from customer and order to inventory, settlement, accounting and company reporting.
Transparent status: WooCommerce Sync is currently offered as a controlled pilot. Production scope and support terms are confirmed before activation.
What is a WooCommerce ERP integration?
A WooCommerce ERP integration connects storefront events to back-office operations. Orders, customers, products, refunds, taxes and payments can be mapped into inventory, accounting and reporting workflows. WooCommerce remains the commerce engine while the ERP becomes the operational and financial source of truth.
Pilot workflow
Build the accounting contract before switching on sync.
A reliable connector starts with source ownership, event security, mapping policy and reconciliation behavior.
Signature check
Verify the webhook signature, source and delivery identity.
Commerce mapping
Resolve products, variations, tax, shipping and payment gateways.
ERP posting
Create linked sales, inventory, bank and accounting records.
Exception review
Retry recoverable work and flag unmatched or conflicting records.
Commerce coverage
The pilot scope buyers expect from a serious ERP connector.
The goal is a controlled revenue-to-ledger workflow, not a one-time CSV import.
Orders and refunds
Preserve order numbers, statuses, items, discounts, shipping, tax and refund relationships.
Products and inventory
Relate products and variations to ERP items, warehouses and stock policy.
Customer records
Match or create customers without allowing one company to see another company’s data.
Gateway settlement
Map each payment method to bank, clearing, fee and currency behavior.
Sync health
Show webhook delivery, processing status, retries, mapping conflicts and reconciliation gaps.
Proposed entity contract
What the production connector should cover.
This table is a release checklist for the pilot, not a claim that these items are live today.
| WooCommerce record | ERP outcome | Required control | Status |
|---|---|---|---|
| Customers | Customer relation | Tenant-scoped match policy | Pilot |
| Products and variations | Catalog and stock relation | SKU conflict and source ownership | Pilot |
| Orders | Sales and fulfillment context | Status mapping and idempotency | Pilot |
| Refunds | Credit and inventory reversal | Original order relationship | Pilot |
| Tax, shipping and coupons | Line and ledger mapping | Configurable rules | Pilot |
| Payment gateways | Bank and fee mapping | Settlement reconciliation | Pilot |
Official platform model
REST APIs for records. Webhooks for change.
WooCommerce documents webhooks for order, customer, product and coupon events. Deliveries include an HMAC signature header and are logged by WooCommerce, which provides the right foundation for a secure connector.
Read WooCommerce webhook documentation ↗WooCommerce owns commerce
Checkout, storefront data and source order state remain in WordPress.
JielianERP owns back-office context
Accounting, purchasing, bank, inventory and management reporting use governed mappings.
Reconciliation closes the loop
Operations teams can see what synced, what failed and what needs a policy decision.
Questions answered
Clear answers before a sales call.
Is the JielianERP WooCommerce connector available now?
No. This local marketing concept presents the WooCommerce connector as a pilot. Production availability should only be announced after order, refund, tax, inventory, gateway, security and reconciliation tests pass.
What should the WooCommerce connector synchronize?
The proposed scope includes customers, products, variations, orders, refunds, coupons, taxes, shipping, payment methods, inventory and settlement context.
Will WooCommerce remain the storefront?
Yes. WooCommerce should keep checkout, order capture and store operations. JielianERP should receive controlled events and provide accounting, procurement, inventory, reporting and wider company workflows.
How should webhooks be verified?
WooCommerce webhooks include a signature header generated from the configured secret. The ERP receiver should verify that signature, reject replayed or stale events and process each event idempotently.
Join the WooCommerce connector pilot.
Validate your store, tax, inventory and settlement workflow before production scope is finalized.