Oracle Fusion Cloud ERP and BigCommerce integration

What moves between them

Orders flow from BigCommerce into Oracle Fusion Cloud ERP. When a customer places an order on BigCommerce, ml-connector either receives the webhook notification or polls for new orders, extracts the order total and line items with their product categories and store locations, maps those categories to GL accounts and cost centers in Oracle Fusion Cloud ERP, and posts a journal entry crediting the revenue account and debiting accounts receivable or a suspense account. Order refunds trigger a reversal or adjustment entry. Customer records and product catalogs can be synchronized in both directions to keep store structure aligned with ERP cost centers and business units.

How ml-connector handles it

ml-connector stores the BigCommerce API key encrypted and presents it in every REST call via the X-Auth-Token header. It verifies each webhook signature using HMAC-SHA256 and the client secret, then immediately fetches the full order details from BigCommerce to avoid relying on stub payloads. On the Oracle Fusion Cloud ERP side, ml-connector accepts the customer-specific pod URL, authenticates with OAuth2 Client Credentials to obtain a JWT bearer token valid for approximately 1 hour, and refreshes the token when a call returns 401. Order line items are mapped to GL accounts based on the BigCommerce product category, store, or custom mapping rules you define. Because BigCommerce webhooks can take up to 1 minute to activate and auto-deactivate after 90 days of inactivity, ml-connector maintains a fallback polling schedule to catch any orders that would otherwise be missed. Journal entries are posted as journal headers and journal line details, with full audit trails recorded in both systems so any discrepancy can be traced and replayed.

A real-world example

A mid-sized retailer runs BigCommerce across two regional storefronts (US and Europe) and uses Oracle Fusion Cloud ERP to manage accounting, revenue recognition, and statutory financial reporting. Before the integration, the finance team exported order reports from BigCommerce weekly, manually categorized each order by store and product line, and entered the aggregated revenue into Oracle Fusion Cloud ERP's general ledger. This process was slow, error-prone, and delayed financial reporting by several days. With BigCommerce and Oracle Fusion Cloud ERP connected, each order posts to the ledger within minutes, allocated to the correct store and GL account automatically. Month-end close becomes straightforward because revenue is already in the books, and the retailer can generate accurate financial statements on the day the month ends without waiting for manual data entry.

What you can do

• •Post BigCommerce order revenue to Oracle Fusion Cloud ERP's general ledger as journal entries within minutes of order placement, allocated to the correct GL account and legal entity.
• •Map BigCommerce product categories and store locations to Oracle Fusion Cloud ERP cost centers and revenue accounts so every order lands on the right GL account automatically.
• •Process BigCommerce refunds as reversal or adjustment entries in Oracle Fusion Cloud ERP, keeping revenue accounts reconciled with actual collected sales.
• •Verify webhook signatures using HMAC-SHA256 and handle webhook activation delays and auto-deactivation by maintaining a fallback polling schedule.
• •Maintain full audit trails on every order-to-journal entry transaction, enabling replay and reconciliation if a posting fails or requires correction.

Questions

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

Orders and refunds flow from BigCommerce into Oracle Fusion Cloud ERP. Customer records and product catalogs can be synchronized in both directions. Oracle Fusion Cloud ERP general ledger entries are read-only in the integration, since accounting records are managed within the ERP.

How does ml-connector handle BigCommerce webhook reliability and Oracle Fusion Cloud ERP's lack of direct webhooks?

ml-connector verifies each BigCommerce webhook signature using HMAC-SHA256 to confirm authenticity. Because BigCommerce webhooks can take up to 1 minute to activate and auto-deactivate after 90 days of inactivity, ml-connector maintains a fallback polling schedule that periodically checks for new or updated orders. On the Oracle Fusion Cloud ERP side, ml-connector posts journal entries via REST API calls authenticated with OAuth2 tokens.

What happens if an order posts to Oracle Fusion Cloud ERP but the BigCommerce refund is delayed?

ml-connector tracks each order's posting state in its audit log. When a refund arrives from BigCommerce, ml-connector creates an adjustment or reversal journal entry in Oracle Fusion Cloud ERP to reverse the original revenue posting. Both entries are linked in the audit trail so the finance team can trace the full lifecycle of each order.