Infor CloudSuite and Amazon Seller Central integration

What moves between them

The flow runs from Amazon Seller Central into Infor CloudSuite. ml-connector reads orders and settled financial events from the SP-API and posts the resulting journals into the CloudSuite general ledger: captured sales, refunds, and Amazon selling and fulfillment fees, each mapped to the matching Infor GL account. Order and customer detail can be summarized into Infor customer and sales records so marketplace revenue is recognized in the ERP. Marketplace SKUs and ASINs are aligned with Infor item numbers so every posted line references a valid item. Infor CloudSuite is treated as the system of record for accounting, so ml-connector never writes GL entries or financial data back into Amazon.

How ml-connector handles it

ml-connector stores both credential sets encrypted and trades the Amazon refresh token for an hourly access token, sending it with the marketplace ID on every SP-API call, while on the Infor side it reads the .ionapi file fields per customer to build the tenant base URL and exchange the service account keys for an ION bearer token, refreshing each token before it expires. Because Amazon delivers push events only through EventBridge or SQS rather than HTTP webhooks, the connector polls Orders and Finances on a schedule and pulls the settlement report as the authoritative disbursement record, since financial events only appear after Amazon releases a settlement. SP-API uses token-bucket rate limits that return HTTP 429, and the ION Gateway throttles per tenant and also returns 429, so the connector backs off with jitter on both sides. Infor M3 Add transactions are not idempotent, so before posting a journal it queries by the Amazon settlement or order identifier to avoid creating duplicates, and GL accounts and item mappings are resolved first so every line lands on a valid account. Buyer address and phone require a Restricted Data Token, which the connector requests only when that detail is actually needed. Every record carries a full audit trail and can be replayed if an Infor post fails.

A real-world example

A mid-sized consumer goods manufacturer runs Infor CloudSuite for production, inventory, and finance, and sells finished goods to shoppers through Amazon Seller Central across the US and Canada marketplaces. Before the integration, the finance team downloaded the Amazon settlement report every payout cycle and hand-keyed the gross sales, refunds, and Amazon fees into CloudSuite, then spent the start of month-end close trying to tie the bank deposit back to the orders it covered. With Infor CloudSuite and Amazon Seller Central connected, each settlement posts into the ERP automatically, split into the right GL accounts with the selling fees recognized, and marketplace SKUs stay matched to Infor items. Close starts with the marketplace deposits already reconciled and the daily re-keying step is gone.

What you can do

• •Post Amazon settlement sales, refunds, and selling fees into Infor CloudSuite's general ledger after each payout.
• •Read Amazon orders and financial events on a schedule and recognize marketplace revenue in the ERP.
• •Align Amazon marketplace SKUs and ASINs with Infor item numbers so every posted line references a valid item.
• •Bridge the Amazon Login with Amazon refresh token and the Infor ION OAuth2 tenant token, refreshing each before it expires.
• •Pull the Amazon settlement report as the authoritative disbursement record, with query-first dedup, retries, and a full audit trail.

Questions

Which direction does data move between Infor CloudSuite and Amazon Seller Central?

The flow is Amazon Seller Central into Infor CloudSuite. Orders, settled financial events, and settlement reports move from Amazon into the CloudSuite general ledger, while item references are aligned so postings land on valid Infor items. Infor CloudSuite is the accounting system of record, so ml-connector does not write GL entries or financial data back into Amazon.

Does Amazon Seller Central support webhooks, or does the connector poll?

Amazon delivers push events only through AWS EventBridge or SQS, not plain HTTP webhooks, and there is no notification type for settlement or invoice results. Because of that, ml-connector polls the Orders and Finances APIs on a schedule and pulls the settlement report for reconciliation. Financial events only appear after Amazon releases a settlement, so the settlement report is treated as the authoritative disbursement record.

How does the integration avoid duplicate postings in Infor CloudSuite?

Infor M3 Add transactions are not idempotent, so a duplicate post would create a duplicate record. ml-connector queries CloudSuite by the Amazon settlement or order identifier before posting and tracks the mapping between Amazon records and Infor entries. Combined with retries and a full audit trail, this keeps each settlement posted exactly once even when a call has to be retried.