Plex and Amazon Seller Central integration

What moves between them

Sales orders and order items flow from Plex into Amazon Seller Central, creating or updating listings and inventory reservations. Order status, shipment events, and refund events flow from Amazon back into Plex to update sales order fulfillment status and inventory quantities. Financial settlement events from Amazon flow into Plex general ledger and accounts receivable for reconciliation. The integration runs on a schedule aligned with your fulfillment and settlement cycle.

How ml-connector handles it

ml-connector stores Plex OAuth2 credentials and Amazon refresh tokens encrypted and refreshes each when a call returns 401. Because neither system offers bidirectional webhooks, ml-connector polls the Plex REST API for modified sales orders and the Selling Partner API for order status changes and financial events on a schedule you set, typically every 2 to 4 hours. Plex PCN company code and Amazon region are stored per customer so the integration routes to the correct data partition. Order line items are matched by external reference fields to detect duplicates. Amazon access tokens expire after one hour, so ml-connector refreshes them before each use. Shipment and refund events from Amazon are mapped to Plex sales order status codes so fulfillment staff see the real-time state. Settlement events are allocated to the correct GL accounts and customer accounts in Plex for month-end close. Every record carries audit metadata and can be replayed if a downstream call fails.

A real-world example

A mid-sized discrete manufacturer sells components and assemblies through the Amazon marketplace while running Plex for manufacturing, procurement, and finance. Before the integration, the sales team entered orders from Amazon manually into Plex, often hours or days after the sale, while finance manually downloaded settlement reports and allocated them to customer accounts in Plex during close. With Plex and Amazon Seller Central connected, orders appear in Plex automatically, inventory is reserved and updated as shipments occur, and settlement events post to GL and accounts receivable without re-keying. The finance team sees customer-level revenue and costs matched to their orders, and sales staff see fulfillment status reflected in Plex.

What you can do

• •Sync Plex sales orders and line items to Amazon Seller Central orders, with inventory reservations matched to Plex inventory locations.
• •Receive shipment events, refunds, and service fee adjustments from Amazon and post them to Plex sales order status and inventory on a schedule you control.
• •Pull Amazon financial settlement events and post them to Plex general ledger and accounts receivable, allocated to the correct customer and GL accounts.
• •Authenticate Plex via OAuth2 bearer token and Amazon via refresh token, refreshing each when it expires, and route Plex calls to the correct company code.
• •Track every order, shipment, and financial event in a complete audit trail and replay any record if a downstream call fails.

Questions

Which direction does data flow between Plex and Amazon Seller Central?

Sales orders flow from Plex into Amazon Seller Central to create or update order listings and inventory. Shipment events, refunds, and service fees flow from Amazon back to Plex to update sales order status and inventory quantities. Financial settlement events from Amazon also flow into Plex for reconciliation. Purchase orders and sourcing do not flow to Amazon.

How does ml-connector handle Amazon's one-hour access token expiry and Plex's company code routing?

ml-connector stores Amazon refresh tokens and Plex OAuth2 credentials encrypted per customer and refreshes each before every API call when needed, preventing token expiry outages. Plex PCN company code is stored per customer and included in every SOAP or REST call so the integration routes to the correct data partition without re-configuring.

How often does ml-connector sync orders and settlement events between the two systems?

Because neither Plex nor Amazon offers bidirectional webhooks for all record types, ml-connector polls both systems on a schedule you set, typically every 2 to 4 hours. Orders are polled first, then shipments and refunds, then financial settlement events, so downstream calls have all required context before posting to GL or inventory.