Oracle PeopleSoft and WooCommerce integration

What moves between them

Orders and customer records flow from WooCommerce into Oracle PeopleSoft. When a customer places an order in WooCommerce, ml-connector receives the webhook notification and creates or updates the corresponding customer record in PeopleSoft customer master data, then records the order as a voucher or journal entry in PeopleSoft's accounts receivable or general ledger for accounting. Customer profile updates in WooCommerce sync to PeopleSoft so billing addresses, email, and contact info stay current. The flow is unidirectional: PeopleSoft does not write back to WooCommerce. ml-connector also polls WooCommerce on a regular schedule to catch any orders created outside the webhook window, ensuring no orders are missed.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the PeopleSoft HTTP Basic Auth OPRID and password on the customer's unique hostname and port, and the WooCommerce Consumer Key and Consumer Secret. On the WooCommerce side, it registers a webhook listener to receive order.created and customer.created events, validates each webhook signature with HMAC-SHA256 using the webhook secret, and extracts order and customer data. For PeopleSoft, ml-connector makes REST API calls to read the customer CI (Component Interface) metadata, then upserts customer records via SOAP Component Interface calls using HTTP Basic Auth. Orders from WooCommerce are mapped to PeopleSoft journal entry line items with the order total, customer account code, and GL account for accounts receivable. Since PeopleSoft has no standardized pagination, ml-connector filters requests by order date range and polls on a schedule that aligns with your order volume. PeopleSoft's self-hosted nature means each customer has a different hostname, port, and node name, which ml-connector stores per customer. If a webhook fails or is disabled, ml-connector's polling loop catches up on the next scheduled run. The integration tracks every customer and order record with a full audit trail.

A real-world example

A mid-market retailer sells furniture and home goods through WooCommerce and manages fulfillment and accounting in Oracle PeopleSoft on-premise. Before the integration, the order fulfillment team exported orders from WooCommerce each morning and manually entered them into PeopleSoft as AR invoices and GL journal entries, then customer service updated PeopleSoft customer records when shipping addresses or email changed. With WooCommerce and PeopleSoft connected, each order flows into PeopleSoft automatically as soon as the webhook arrives, allocated to the correct GL account for sales revenue and AR, and customer changes sync immediately. The daily manual order entry step is eliminated, fulfillment staff spend less time on data entry, and accounting has current customer contact info for collections.

What you can do

• •Receive WooCommerce order.created and customer.created webhooks and validate their HMAC-SHA256 signatures.
• •Create and update customer records in Oracle PeopleSoft customer master using SOAP Component Interface calls authenticated with HTTP Basic Auth.
• •Map WooCommerce orders to PeopleSoft GL journal entry line items for sales and accounts receivable.
• •Poll WooCommerce and PeopleSoft on a schedule to catch orders and customers outside the webhook window and ensure no data is missed.
• •Store both credential sets encrypted and handle the self-hosted unique hostname and port for each PeopleSoft customer.

Questions

Does the integration support writing PeopleSoft data back to WooCommerce?

No. The integration is unidirectional: orders and customers flow from WooCommerce into PeopleSoft only. PeopleSoft is the system of record for accounting and customer master data. If you need to sync inventory or pricing from PeopleSoft to WooCommerce, that would require a separate integration configured in the opposite direction.

How does ml-connector handle PeopleSoft's self-hosted architecture and lack of webhooks?

Each PeopleSoft customer has a unique hostname, port, and node name. ml-connector stores these per customer and authenticates with HTTP Basic Auth using the customer's OPRID and password, or OAuth2 Bearer token if PeopleTools 8.58 or later is in use. Since PeopleSoft has no webhook system, ml-connector polls on a regular schedule aligned with your order volume to catch new orders and customer changes, and also listens for WooCommerce webhooks to react immediately when orders are placed.

What happens if a WooCommerce webhook is disabled or a PeopleSoft API call fails?

WooCommerce webhooks automatically disable after five consecutive non-2xx responses, in which case an administrator must manually re-enable them. ml-connector maintains a full audit trail of every sync and failed record. On the next scheduled polling run, ml-connector will retry the failed order or customer record. If a PeopleSoft API call fails, the record is logged in the audit trail with the error details so you can investigate and replay the sync.