Oracle Fusion Cloud ERP and WooCommerce integration

What moves between them

The main flow runs from WooCommerce into Oracle Fusion Cloud ERP. New and updated orders from WooCommerce are read via polling on a schedule tied to your sales reporting cycle, typically every 5 to 15 minutes. Each order is transformed into a sales invoice and recorded in Oracle Fusion Cloud ERP as a receivables invoice, with the customer linked to the matching Oracle Fusion customer record and each line item mapped to the appropriate GL account and cost center. Customer records are kept in sync when WooCommerce customers are created or updated. Payments recorded in WooCommerce are written back as cash receipts in Oracle Fusion Cloud ERP. Reference data such as customers and GL accounts are aligned in both directions to ensure orders land on valid accounts.

How ml-connector handles it

ml-connector stores the WooCommerce API Key encrypted and the Oracle Fusion Cloud ERP OAuth 2.0 credentials encrypted, refreshing the OAuth token when a call returns 401 to prevent outage. Because WooCommerce can deliver webhooks when orders are created and updated, ml-connector listens for those events and applies them immediately. For orders delivered in batches or when webhooks are delayed, it polls WooCommerce on a configurable schedule using LastUpdateDate filtering to catch any missed records. Customers from WooCommerce are matched to Oracle Fusion Cloud ERP customers by external ID or exact name match, and the mapping is stored to avoid duplicate customer records. Each order line is mapped to an Oracle Fusion GL account and cost center based on the product category or SKU, configured per customer. WooCommerce's lack of accounting dimensions means ml-connector must handle account selection logic in the flow configuration. The integration tracks both successful posts to Oracle Fusion Cloud ERP and failures, and can replay failed orders once the downstream issue is resolved. Rate limits and API timeouts are handled with exponential backoff and jitter.

A real-world example

A mid-size retail company operates an online store built with WooCommerce, selling directly to customers across multiple regions. The finance team previously exported orders from WooCommerce daily and manually re-entered them into Oracle Fusion Cloud ERP as sales invoices, then spent hours each week reconciling revenue and accounts receivable between the two systems. Customer overpayments and refunds often went unrecorded in Oracle Fusion Cloud ERP until month-end close, creating unexpected GL variances. With WooCommerce and Oracle Fusion Cloud ERP connected, every order automatically posts as a receivables invoice with the customer linked, every payment is recorded as a cash receipt, and every refund adjusts the invoice balance in real time. The finance team no longer re-keys orders, and accounts receivable reconciliation against WooCommerce is complete on day one of close.

What you can do

• •Post WooCommerce orders into Oracle Fusion Cloud ERP as sales invoices allocated to the correct GL account and cost center.
• •Keep customer records in sync between WooCommerce and Oracle Fusion Cloud ERP by external ID or name match.
• •Record WooCommerce refunds and partial refunds in Oracle Fusion Cloud ERP as credit memos against the matching sales invoice.
• •Authenticate WooCommerce with API Key and OAuth 1.0a, and Oracle Fusion Cloud ERP with OAuth 2.0, refreshing tokens automatically.
• •Poll WooCommerce on a schedule tied to your sales reporting cycle, with webhooks for real-time order capture and a full audit trail on every transaction.

Questions

Which direction does data move between WooCommerce and Oracle Fusion Cloud ERP?

Orders, customers, and payments move from WooCommerce into Oracle Fusion Cloud ERP. Customer and GL account reference data are aligned in both directions so orders map to valid accounts. WooCommerce has no purchase order or accounting features, so data flows primarily one way from the storefront into the general ledger.

Does ml-connector use WooCommerce webhooks or polling?

ml-connector listens for WooCommerce webhooks for real-time notification when orders are created or updated. For orders delivered in batches or when webhooks are delayed, it falls back to polling every 5 to 15 minutes using LastUpdateDate filtering. The combination ensures no orders are missed and reduces latency compared to polling alone.

How does the integration handle the lack of accounting features in WooCommerce?

WooCommerce has no native GL accounts, cost centers, or accounting dimensions. ml-connector relies on flow configuration to map product categories or SKUs to Oracle Fusion GL accounts and cost centers per customer. Customer contact methods such as email are used to look up the matching Oracle Fusion customer record and prevent duplicate customer creation in the ERP.