Oracle JD Edwards and BigCommerce integration

What moves between them

The main flow runs from BigCommerce into Oracle JD Edwards. As orders are placed and paid, ml-connector reads each order, its line items, and its payment transactions and posts the financial result into JD Edwards as an AP voucher or GL journal entry, mapped to the matching accounts and cost centers. New and changed BigCommerce customers flow into the JD Edwards Address Book and Customer Master. In the other direction, JD Edwards item master and price changes are pushed to the BigCommerce catalog so SKUs and prices stay current. Refunds read from BigCommerce post as offsetting JD Edwards entries; the ledger is never written back into the store.

How ml-connector handles it

ml-connector stores both credential sets encrypted and attaches the BigCommerce X-Auth-Token on every store call, while re-authenticating to the JD Edwards AIS Server whenever a request returns HTTP 444 for an invalid token, since JDE tokens expire on inactivity and are dropped on any AIS Server restart. It registers BigCommerce order, customer, and product webhooks, and because each webhook is only a stub it immediately calls the v2 order or v3 transaction endpoint to fetch the full record before posting. JD Edwards has no outbound webhooks, so item and price reads are polled on a schedule using a date-updated filter and a saved last-run timestamp. Store SKUs are mapped to JD Edwards item numbers and order totals to GL accounts and cost centers first, so every voucher or journal line references an account that already exists. Writes into JD Edwards go through named Orchestrator endpoints that the customer imports and configures, and because JDE exposes no idempotency header the connector checks for an existing document before creating one. BigCommerce rate limits return HTTP 429 with a reset header, so the connector backs off and retries, and webhooks that go quiet are re-registered before BigCommerce auto-deactivates them.

A real-world example

A mid-sized consumer goods distributor sells through a BigCommerce storefront and runs Oracle JD Edwards EnterpriseOne for inventory, purchasing, and finance. Before the integration, a clerk exported the day's web orders from BigCommerce and re-keyed the sales and payment totals into JD Edwards, while the catalog drifted out of step with the item master whenever prices or new products changed in the ERP. With the two systems connected, each paid order posts into JD Edwards automatically against the right revenue and cost center accounts, customers land in the Address Book, and item and price updates flow out to the storefront. The daily re-keying is gone and the catalog matches the ledger.

What you can do

• •Post paid BigCommerce orders and payment transactions into Oracle JD Edwards as vouchers or GL journal entries on the correct accounts.
• •Sync BigCommerce customers into the JD Edwards Address Book and Customer Master.
• •Push JD Edwards item master and price changes out to the BigCommerce catalog.
• •Bridge the BigCommerce X-Auth-Token and the JD Edwards session-token login, re-authenticating automatically on token expiry.
• •Listen for BigCommerce order webhooks while polling JD Edwards tables on a schedule, with retries and a full audit trail.

Questions

Which direction does data move between Oracle JD Edwards and BigCommerce?

The main flow is BigCommerce into Oracle JD Edwards. Orders, payment transactions, and customers move from BigCommerce into JD Edwards, while item master and price changes are pushed from JD Edwards out to the BigCommerce catalog. Refunds read from BigCommerce post as offsetting JD Edwards entries, and the ledger is never written back into the store.

Does BigCommerce post directly into the JD Edwards ledger?

No. BigCommerce has no GL accounts, vendors, or purchase orders, so order and transaction totals are mapped to JD Edwards accounts and cost centers first. ml-connector then writes the result through named JD Edwards Orchestrator endpoints, since JDE supports no direct table inserts over its REST API.

How does the integration handle JD Edwards having no webhooks and BigCommerce having stub webhooks?

JD Edwards has no outbound webhooks, so ml-connector polls its data service tables on a schedule using a date-updated filter and a saved last-run timestamp. BigCommerce does push webhooks, but each one carries only a resource type and id, so the connector immediately calls the BigCommerce REST API to fetch the full order or transaction before posting it into JD Edwards.