Oracle E-Business Suite and Amazon Seller Central integration

What moves between them

The main flow runs from Amazon Seller Central into Oracle E-Business Suite. ml-connector reads Amazon orders and financial events and, on each released settlement, the settlement report, then posts the resulting journals into the EBS general ledger interface and stages marketplace sales as AR invoices in the receivables open interface, with item charges, shipping, refunds, and Amazon fees mapped to the correct GL accounts and operating unit. Item and product data can flow the other direction from EBS so Amazon listings stay aligned with the catalog. Amazon is treated as a read-only accounting and order source, so ml-connector never writes financial entries back into Amazon; only listing or inventory updates move toward Amazon when that flow is enabled.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Amazon side it exchanges the seller refresh token for a one-hour access token through Login with Amazon, caches it, and refreshes before expiry, passing the marketplace id on each call and routing to the correct regional base URL. On the EBS side it accepts the full instance URL per customer, logs in for a session token, and attaches the responsibility, application, and operating unit org id on every request, re-authenticating on a 401 because EBS sessions expire. Because EBS has no webhooks and Amazon pushes only through EventBridge or SQS, both systems are read on a schedule: orders and financial events are paged with NextToken, and settlements are pulled from the Reports API once a report is DONE and downloaded from its presigned URL. GL accounts and the operating unit are mapped first so every journal line lands on a valid combination, and writes stage into the AP or GL interface tables, so a 200 means rows were inserted, not that the import ran; ml-connector triggers or confirms the concurrent import. Amazon 429 responses are retried with backoff and jitter, EBS calls are kept to low concurrency since it has no rate limiter and is a shared system, and every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized consumer goods brand with about 150 staff sells through Amazon as a major channel and runs Oracle E-Business Suite R12.2 for finance and inventory. Before the integration, accounting downloaded Amazon settlement reports every two weeks, then manually keyed gross sales, refunds, FBA and referral fees, and the net deposit into the EBS general ledger, and month-end close stalled while they reconciled the bank disbursement against the orders behind it. With Oracle E-Business Suite and Amazon Seller Central connected, each settlement posts into EBS automatically, split across the right revenue, fee, and clearing accounts for the correct operating unit, and order data lands as receivables so the deposit ties out. The manual re-keying step is gone and close starts from reconciled numbers.

What you can do

• •Post Amazon settlement reports into the Oracle E-Business Suite general ledger after each payout, split into revenue, fee, and clearing accounts.
• •Stage Amazon orders as AR invoices in the EBS receivables open interface, allocated to the correct operating unit.
• •Record Amazon refunds, FBA and referral fees, and chargebacks against the matching EBS GL accounts.
• •Authenticate Amazon with its OAuth2 refresh-token flow and regional endpoint, and EBS with its per-instance session token and org context.
• •Poll both systems on a schedule with retries, and confirm the EBS import program ran before marking a write complete.

Questions

Which direction does data move between Oracle E-Business Suite and Amazon Seller Central?

The main flow is Amazon into EBS. Orders, financial events, and settlement reports move from Amazon Seller Central into the Oracle E-Business Suite general ledger and receivables open interface. Amazon is treated as a read-only accounting and order source, so ml-connector does not write financial entries back into Amazon; only item, listing, or inventory updates move toward Amazon when that flow is turned on.

Does Amazon push events to EBS, or is everything polled?

Everything is polled. Oracle E-Business Suite has no webhooks for external connectors, and Amazon delivers events only through AWS EventBridge or SQS rather than plain HTTP. ml-connector reads Amazon orders and financial events on a schedule, pages through them with NextToken, and pulls the authoritative settlement report from the Reports API once it is ready.

How does writing to Oracle E-Business Suite actually work?

Most EBS writes are two-step and asynchronous. ml-connector inserts rows into the relevant open interface table, such as the GL or receivables interface, and a separate concurrent import program then validates and posts them into the base tables. A successful insert does not mean the record exists yet, so ml-connector triggers or confirms the import program and uses a unique source value to avoid duplicates.