Oracle Fusion Cloud ERP and Shopify integration

What moves between them

The main flow is Shopify into Oracle Fusion Cloud ERP. Shopify webhooks trigger on new and updated orders, and ml-connector creates a customer invoice in Fusion with the order total, billing address, and customer reference. Customer records flow the same direction so Fusion AR sees current shop customers. Optional: Shopify can receive transaction receipts and settlement records from Fusion via pull-then-push if a Fusion sales invoice is needed upstream.

How ml-connector handles it

ml-connector accepts Shopify webhooks for orders/create, orders/updated, orders/paid, and customers/create/update events, validates signatures using the Shopify shared secret, and refreshes the GraphQL bearer token on 401 responses. On the Fusion side, it polls for updated customers and invoices using LastUpdateDate filters and maintains the OAuth2 client credentials token for the pod-specific Fusion instance. Shopify orders map to Fusion customers (via email or external ID) and receivables invoices (via a configurable GL account for Shopify revenue). Customer addresses normalize across both systems and refunds in Shopify create credit memos in Fusion. Rate limits on both sides are handled with exponential backoff, and every order and customer record carries a full audit trail.

A real-world example

An online retailer sells furniture and home goods via Shopify to wholesale and direct consumers. Monthly, the accounting team manually exported Shopify order reports and re-entered each sale into Oracle Fusion Cloud ERP with the correct customer and revenue account. Reconciling Shopify sales to AR in Fusion took two days every month, with errors from transposition and duplicate entries. With Shopify and Fusion integrated, each order and customer flows into AR automatically with correct billing address and GL coding. AR aging reports in Fusion now match shop revenue within minutes, and reconciliation is instant.

What you can do

• •Create receivables invoices in Oracle Fusion Cloud ERP from Shopify orders, automatically mapped to the correct customer and revenue GL account.
• •Synchronize Shopify customer records into Fusion customers so AR, aging, and credit limit management stays in sync.
• •Map Shopify refunds to Fusion credit memos and track order amendments as invoice updates.
• •Handle OAuth2 tokens, Shopify webhook signatures, and pod-specific Fusion REST API endpoints with full credential encryption and audit trails.
• •Poll Fusion customers and invoices on a configurable schedule while receiving real-time order and customer events from Shopify webhooks.

Questions

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

The main flow is Shopify into Fusion. Orders and customers move from Shopify into Fusion as receivables invoices and customer records, automatically mapped to the correct revenue account and billing address. Optional: transaction receipts and settlements can flow from Fusion back to Shopify if needed for reconciliation, but Fusion invoices are typically read-only for revenue recognition.

How does the integration handle Shopify webhooks and Fusion's lack of outbound webhooks?

ml-connector listens for real-time Shopify webhooks (orders/create, orders/updated, customers/create, customers/update) and validates signatures using the shared secret. On the Fusion side, it polls the REST API on a configurable schedule with LastUpdateDate filters, since Fusion has no direct webhook system without Oracle Integration Cloud middleware.

How are customers and invoices mapped between the two systems?

Shopify customers are mapped to Fusion customers via email address or external ID. Orders become receivables invoices with the shop total as the line amount, the Shopify revenue GL account as the posting account, and the customer name and billing address carried through. Refunds in Shopify create credit memos in Fusion against the original invoice.