Which direction does data move between SYSPRO and Amazon Seller Central?

Inventory and pricing move primarily from SYSPRO to Seller Central so your listings stay current. Orders and financial settlement data flow from Seller Central back into SYSPRO for fulfillment and GL posting. This allows SYSPRO to be the source of truth for product costs and inventory allocations, while Seller Central supplies demand and revenue data.

How does the integration handle differences between SYSPRO's two authentication methods?

ml-connector supports both e.net Business Objects (for inventory and pricing writes) and OData (for inventory reads). Session tokens obtained from e.net Utilities/Logon are refreshed before expiry. Separate HTTP Basic Auth credentials for OData are cached after the first call. This dual-track approach lets you leverage the right API for each operation without re-authenticating.

What happens if Seller Central orders are older than 2 years or settlement events change?

Seller Central's SP-API does not return orders older than 2 years in most regions, so historical syncs only capture recent 24-month activity. Financial settlement events are polled on your schedule and marked with their settlement timestamp; if an event is adjusted or disputed, the latest data is fetched on the next poll. All records in SYSPRO carry the source transaction ID so duplicates and reversals are tracked.

SYSPROAmazon Seller Central

SYSPRO and Amazon Seller Central integration

SYSPRO runs your manufacturing and distribution. Amazon Seller Central sells your products to buyers worldwide. Connecting them keeps your inventory levels and revenue posting in sync. Products added or repriced in SYSPRO flow to your Amazon listings automatically, order volume from Seller Central feeds back into SYSPRO demand forecasts, and the revenue and fulfillment fees that Amazon settles post into your GL without manual re-keying. ml-connector bridges the two platforms and moves the data on a schedule you control.

How SYSPRO works

SYSPRO (versions 8 and later, cloud or on-premise) exposes inventory masters, pricing, purchase orders, invoices, customer records, and general ledger accounts through three API layers: e.net Business Objects (REST/SOAP, read and write), OData (REST, read-only), and Workflow Service (limited). Authentication uses a session token obtained by logging in to Utilities/Logon and passing the UserId GUID on subsequent calls. OData uses HTTP Basic Auth with auto-generated SQL credentials. SYSPRO does not push outbound webhooks, so inventory and order data must be polled on an interval you define, typically 5-15 minutes for financial records.

How Amazon Seller Central works

Amazon Seller Central exposes orders, inventory levels, financial events, and catalog items through the Selling Partner API (SP-API), a REST service with regional endpoints for North America, Europe, and Far East. Authentication uses OAuth2 with Login with Amazon (LWA); the seller authorizes once and a long-lived refresh token is stored and used for all calls. Access tokens expire after one hour. Seller Central can push order and inventory change notifications via Amazon EventBridge or SQS, but financial settlement events must be polled. Key entities include Orders, OrderItems, FinancialEventGroups, FinancialEvents, Inventory Summaries, and CatalogItems.

What moves between them

Inventory and pricing flow from SYSPRO to Seller Central so your Amazon listings reflect current stock and cost. Orders placed on Seller Central flow back into SYSPRO as sales orders or demand signals. Financial settlement data, including fees and adjustments, is polled from Seller Central and posted to SYSPRO's GL, allocated to product lines and fulfillment cost centers. Older orders (beyond 2 years in some regions) are not returned by SP-API and are not synced. All pricing updates require e.net Business Objects write access; inventory reads come from OData.

How ml-connector handles it

ml-connector stores both credential sets encrypted and manages two token lifecycles in parallel: SYSPRO session tokens (requested on login and refreshed before expiry) and Amazon OAuth2 access tokens (refreshed every 50 minutes to avoid the 3600-second expiry). It polls SYSPRO OData on your schedule for inventory masters and pricing, pushes updates to Seller Central listings via the Catalog and Inventory SP-API operations, and polls Seller Central Orders and Finances APIs for new sales and settlements. SYSPRO prices and ASIN/SKU mappings are validated before any write to Seller Central. Financial events are mapped to SYSPRO GL accounts by product line and cost center. Seller Central's Orders API returns orders from the past 2 years (older orders in most regions are not available); financial events are read from FinancialEventGroup within the same window. Retry logic backs off on rate limits and re-queues failed postings to your GL so reconciliation is never blocked by a transient outage.

A real-world example

A mid-sized distributor of industrial components sells through their own website and Amazon Seller Central. Before the integration, warehouse staff manually updated Amazon listings when SYSPRO inventory changed, and the accounting team exported weekly settlement reports from Seller Central, then coded them by hand into SYSPRO journal vouchers. After the integration runs, inventory updates from SYSPRO reach Amazon within 15 minutes, so stock levels stay current without manual intervention. Settlement events post into SYSPRO automatically each night, coded to the correct product cost center, and the finance team closes month-end with all revenue and fees already in the ledger.

What you can do

Push SYSPRO inventory allocations and pricing to Amazon Seller Central listings, keeping your marketplace catalog current without manual updates.
Retrieve orders from Seller Central and create corresponding sales orders in SYSPRO for fulfillment planning and demand forecasting.
Post Amazon settlement events, fees, and adjustments into SYSPRO's general ledger, allocated by product line and fulfillment cost center.
Manage SYSPRO session tokens and Amazon OAuth2 bearer tokens, refreshing before expiry so no call fails due to authentication timeout.
Poll both systems on your schedule with automatic retries on rate limits and a full audit trail for every inventory sync, order, and GL posting.

Questions

Which direction does data move between SYSPRO and Amazon Seller Central?: Inventory and pricing move primarily from SYSPRO to Seller Central so your listings stay current. Orders and financial settlement data flow from Seller Central back into SYSPRO for fulfillment and GL posting. This allows SYSPRO to be the source of truth for product costs and inventory allocations, while Seller Central supplies demand and revenue data.
How does the integration handle differences between SYSPRO's two authentication methods?: ml-connector supports both e.net Business Objects (for inventory and pricing writes) and OData (for inventory reads). Session tokens obtained from e.net Utilities/Logon are refreshed before expiry. Separate HTTP Basic Auth credentials for OData are cached after the first call. This dual-track approach lets you leverage the right API for each operation without re-authenticating.
What happens if Seller Central orders are older than 2 years or settlement events change?: Seller Central's SP-API does not return orders older than 2 years in most regions, so historical syncs only capture recent 24-month activity. Financial settlement events are polled on your schedule and marked with their settlement timestamp; if an event is adjusted or disputed, the latest data is fetched on the next poll. All records in SYSPRO carry the source transaction ID so duplicates and reversals are tracked.

Connect SYSPRO and Amazon Seller Central

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started