Epicor Kinetic and Amazon Seller Central integration

What moves between them

The flow runs from Amazon Seller Central into Epicor Kinetic. ml-connector reads Amazon orders and the settlement and finance data, then posts the resulting sales and fee journals into Epicor Kinetic against the matching GL accounts. Order line items map to Epicor parts by SKU, and the captured sales, Amazon fees, refunds, and disbursements from each settlement become ledger entries. Product reference data is aligned so every line references a part and account that already exists in Epicor. Amazon settlement data is treated as a read-only accounting source, so ml-connector does not write financial entries back into Amazon, though it can confirm order shipment from Epicor fulfillment where that flow is enabled.

How ml-connector handles it

ml-connector stores both credential sets encrypted. For Amazon Seller Central it exchanges the LWA refresh token for an access token, caches it, and refreshes before the one-hour expiry, sending the access token and marketplace ID on each call to the correct regional base URL. For Epicor Kinetic it accepts the full tenant URL, instance, and Company per customer, and sends the API key in the x-api-key header alongside Basic or bearer auth, since the key alone does not establish identity. Reads follow Amazon's NextToken cursor and the async report pattern: create the settlement report, poll until it is done, then download the document. Because Epicor has no webhooks, part and reference reads run on a schedule. Amazon returns HTTP 429 from its per-operation token bucket, so ml-connector backs off and retries, and because Epicor enforces invoice uniqueness on InvoiceNum plus VendorNum, re-posting the same record is rejected rather than duplicated. Orders older than two years are not returned by the Orders API, so backfill is bounded by that limit.

A real-world example

A mid-sized consumer goods manufacturer runs Epicor Kinetic for production, inventory, and finance, and sells a growing share of its catalog on Amazon through a Professional seller account. Before the integration, a clerk downloaded the Amazon settlement report every two weeks and keyed the sales totals, referral fees, FBA fees, and refunds into Epicor by hand, and month-end close stalled while finance reconciled the Amazon payout against the bank deposit. With Epicor Kinetic and Amazon Seller Central connected, each settlement's sales and fee journals post into Epicor automatically against the right accounts, orders flow in as they arrive, and the manual settlement re-keying is gone.

What you can do

• •Post Amazon settlement sales, referral fees, FBA fees, and refunds into Epicor Kinetic against the correct GL accounts.
• •Bring Amazon Seller Central orders into Epicor as sales records, mapped to Epicor parts by SKU.
• •Align Amazon listings and Epicor parts so each posted line references a valid part and account.
• •Bridge Amazon Login with Amazon OAuth2 refresh tokens and Epicor's Basic-plus-API-key authentication.
• •Poll on a schedule with backoff on Amazon 429 throttling and a full audit trail on every record.

Questions

Which direction does data move between Epicor Kinetic and Amazon Seller Central?

The main flow is Amazon into Epicor. Orders and settlement finance data move from Amazon Seller Central into Epicor Kinetic, while product reference data is aligned so postings land on valid parts and accounts. Amazon settlement data is read-only for accounting, so ml-connector does not write financial entries back into Amazon.

How does ml-connector handle Amazon settlement data that arrives only after a payout?

Financial settlement on Amazon is async, and the settlement report is the authoritative disbursement record. ml-connector uses the Reports API workflow, creating the settlement report, polling until it is done, then downloading the document. It posts the sales and fee journals into Epicor once the settlement is released rather than guessing at event-level totals.

Does Epicor Kinetic support webhooks for near-real-time updates?

No. Epicor Kinetic has no native outbound webhooks, so ml-connector reads Epicor parts and reference data by polling its OData endpoints on a schedule. On the Amazon side, order and finance data is also polled through the Orders, Finances, and Reports APIs rather than relying on plain HTTP push, since Amazon delivers events only through AWS EventBridge or SQS.