Oracle E-Business Suite and WooCommerce integration

What moves between them

WooCommerce orders and customer records flow into Oracle E-Business Suite in one direction. When a customer places an order or updates their profile in WooCommerce, ml-connector receives the webhook notification, transforms the order into an accounts receivable transaction, maps the customer to EBS customer records, and posts the revenue entry to the general ledger. Customer name, email, and billing address changes sync to the customer master in EBS. Orders are treated as AR invoices, and refunds create credit memos in EBS. Reference data such as customer credit limits and revenue accounts are configured once and reused for all subsequent orders.

How ml-connector handles it

ml-connector registers a webhook endpoint with WooCommerce for order and customer events, validates each incoming webhook signature with the HMAC-SHA256 secret, and transforms the order into an EBS AR transaction. On the EBS side, it authenticates to the ISG using HTTP Basic Auth or session tokens, supplies all required application context headers (responsibility, organization ID, GL date, and language), and inserts the order into RA_INTERFACE_LINES_ALL, an open interface view for accounts receivable. The concurrent program that converts interface records into binding AR invoices runs asynchronously, typically within minutes but sometimes hours depending on EBS load and validation rules. ml-connector polls the interface status to confirm successful import and raises an error if validation fails so the order can be retried. Because EBS session tokens expire every 30 to 60 minutes, ml-connector refreshes the token on any 401 response. WooCommerce webhooks may be disabled if the endpoint fails too many times, so ml-connector tracks those disablements and alerts the customer to manually re-enable them.

A real-world example

A small retail business runs WooCommerce on a WordPress site to sell products online and uses Oracle E-Business Suite for accounting and inventory. Before the integration, every WooCommerce order required a manual entry into EBS AR to record the sale. The finance team received orders by email or manual export, typed customer names and amounts into EBS by hand, and reconciled discrepancies between the two systems at month-end. With WooCommerce and EBS connected, each order automatically creates an AR invoice in EBS with the customer name, order total, and correct revenue account. Customer changes flow back to the customer master so the accounting team always has current contact information. Month-end reconciliation is now instant because the systems are always aligned.

What you can do

• •Post WooCommerce orders into Oracle E-Business Suite as accounts receivable transactions with revenue account mapping.
• •Sync customer names, email addresses, and billing information from WooCommerce to EBS customer master records.
• •Create credit memos in EBS when a WooCommerce refund is issued.
• •Authenticate with EBS ISG using HTTP Basic Auth or session tokens and provide all required application context headers.
• •Validate WooCommerce webhook signatures and handle order events in real-time with retry and audit trail.

Questions

Which direction do orders and customers move between WooCommerce and Oracle E-Business Suite?

Orders and customer records flow from WooCommerce into EBS as AR transactions and customer master records. ml-connector receives WooCommerce webhooks in real-time, transforms each order into an EBS RA interface record, and posts it to the accounts receivable module with the correct revenue account and customer reference. Customer profile updates also sync one direction from WooCommerce into EBS.

How does ml-connector handle the EBS ISG and its authentication requirements?

ml-connector stores your EBS hostname, port, and ISG credentials encrypted and authenticates to the ISG using HTTP Basic Auth or session tokens obtained from the EBS login endpoint. Every API call includes the required application context headers for responsibility, organization, and GL date. Because EBS session tokens expire every 30 to 60 minutes, ml-connector refreshes the token automatically on any 401 response.

What happens if a WooCommerce webhook is disabled or fails?

WooCommerce disables webhooks automatically after 5 consecutive non-2xx responses from your webhook endpoint. ml-connector detects this condition and alerts you so you can manually re-enable the webhook through the WooCommerce admin panel. Once re-enabled, the webhook will resume receiving order and customer events.