Credential isolation
Encrypt and scope credentials to the company and connector instance.
Use signed events, tenant-scoped credentials, mapping rules and visible reconciliation instead of silent data copying.

A connector authenticates the source, receives or fetches records, verifies the company boundary, applies mapping rules and creates linked ERP records. Every event needs an idempotent identity, visible processing status, retry policy and reconciliation path so automation cannot silently duplicate or lose transactions.

WHMCS can remain the hosting billing source. WooCommerce can remain the storefront. A custom API can connect another approved system. JielianERP owns the mapped company record, operational context and reporting result.
Explore Custom API →A buyer should know what is available now, what is in pilot and what requires a scoped implementation.
| Connector | Primary records | Security model | Availability |
|---|---|---|---|
| WHMCS | Customers, invoices, transactions, credits, payment methods, catalog | HMAC signature, replay protection, connection identity | Available |
| WooCommerce | Customers, products, orders, refunds, taxes, shipping, gateways | Webhook signature, idempotency and tenant-scoped credentials | Pilot design |
| Custom REST API | Defined during data-contract review | Scoped token, source allowlist and audit log | Scoped build |
This architecture is more important than the number of logos on an integrations page.
Encrypt and scope credentials to the company and connector instance.
Authenticate every call, verify signatures and reject stale or replayed events.
Make product, tax, currency, gateway and ledger decisions visible and editable.
Retry safely without creating duplicate customers, invoices or transactions.
Show delivered, received, processed, failed and attention-needed states.
See how JielianERP can fit the way your company already works.