Amazon SP-API integration for Business Central
Technical guide to Amazon SP-API and Business Central. Understand Orders, Listings, Reports, Finances, API design and error handling.
· 3 min read
Amazon SP-API integration for Business Central: what happens technically behind the integration?
An Amazon integration is often described very simply:
“We connect Amazon with Business Central.”
Technically, considerably more is going on.
Amazon makes its Selling Partner API — SP-API — available as a REST-based API platform for integrating with Amazon selling partner data. Amazon Developer Docs
At the same time, Microsoft Dynamics 365 Business Central offers standard REST APIs and the option of developing your own APIs through AL. Microsoft Learn
That is the foundation.
But a reliable integration also requires architecture around it.
Orders API
Amazon’s Orders API is used to retrieve order information and can form the basis for order synchronisation. Amazon Developer Docs
The integration then has to:
- retrieve the relevant orders
- make sure the same order is not processed twice
- map data
- validate SKUs
- apply Business Central rules
- create the relevant ERP data
It is therefore the integration layer that turns Amazon data into business logic.
Listings Items API
The Listings Items API provides access to work programmatically with seller listings and information such as terms of sale, price and inventory. Amazon Developer Docs
That can be relevant if the integration also has to work with product or stock data.
Reports API
The Reports API can retrieve and manage various report types and is used for, among other things, inventory, orders, tax data and returns. Amazon Developer Docs
Reports are particularly interesting when the company needs volumes of data or processes that are not only about individual events.
Finances API
The Finances API provides access to financial events for the Amazon seller’s business. Amazon Developer Docs
That is relevant in connection with:
- reconciliation
- fees
- refunds
- financial reporting
Read more in [Reconciling Amazon sales in Business Central](/en/amazon-reconciliation-business-central/).
Business Central on the other side
Business Central has a set of standard APIs.
If the relevant data is not exposed in the way the integration requires, custom API pages can be developed in AL. Microsoft documents that the API page type is intended for versioned REST web services and supports webhooks. Microsoft Learn
That means an integration project sometimes also involves work in Business Central.
The API connection is only one component
A production-ready setup typically also needs:
Queueing
So that temporary problems do not necessarily stop the whole process.
Retries
So that relevant errors can be attempted again.
Logging
So you can see what actually happened.
Mapping
So that Amazon and Business Central understand each other’s identifiers.
Validation
So that incorrect data is not blindly passed on.
Monitoring
So that errors are detected.
Idempotency and duplicates
If a process fails after Business Central has actually created the order, a retry must not create a second order.
That is why handling unique keys and process status is an important part of the integration design.
API calls are one thing.
Reliable data processing is something else.
API versions change
Amazon maintains both release notes and a deprecation schedule for SP-API. Amazon Developer Docs
That is an important point for companies:
Integrations are not one-off installations.
They are software that has to be maintained.
The key takeaway
An Amazon SP-API integration for Business Central is not just:
API A calls API B.
It consists of all of:
Amazon API
Business Central API
mapping
business rules
error handling
monitoring
security
maintenance
It is the combination that determines whether the integration runs stably after go-live.
Do you have a technical Amazon integration that needs to fit your Business Central architecture?