Reports are the default way to bring Amazon data into Business Central. Tinx Connector requests a report, and Amazon prepares a file to download. You can also import some data through direct API calls. Tinx consultants set up those calls when the report route doesn't work for your data. In the other direction, Tinx Connector sends data to Amazon as a feed. Because each feed takes several calls instead of one, Tinx Connector stores it on the Amazon Feeds page before sending it. This article explains how reports and feeds work in Tinx Amazon Connector and how the Amazon throttling limits affect them.
The way data moves is one more area where Tinx Amazon Connector works differently from the connectors for webshops such as Shopify or Magento. With those webshops, communication is more direct than with Amazon. Tinx Connector sends a request to the webshop API and receives the data in the same call. Data that leaves Business Central goes out in a single call and isn't stored along the way.
Import data from Amazon by using reports
Tinx Connector imports Amazon data in five steps, whether the report carries product listings, settlement data, or FBA returns.
1. Process the message definition
To request an Amazon report, run a message definition. The message definitions that request Amazon reports are included in the AMZ-EU-IN-REPORT synchronization dashboard. The following screenshot shows the dashboard in the default mapping with the messages that let you import product, settlement, and returns data from Amazon.
AMZ-EU-IN-REPORT is the dashboard that you use if you sell in Europe. If you sell in North America or the Far East, your dashboard code starts with AMZ-NA or AMZ-FE instead. For more information, see Amazon synchronization dashboard codes.
Choosing a recurrence for report requests
Each message definition that requests a report can have its own recurrence. The recurrence sets how often Tinx Connector sends the request. No single recurrence fits every report. Decide it per report type, based on how soon you need new data in Business Central and how often Amazon refreshes that data. Amazon refreshes some data rarely, such as settlement data, so frequent requests for it don't bring new data. A recurrence also keeps your report requests within the Amazon throttling limits, because Amazon rejects requests that exceed them. For more information, see Recurrence and Throttling limits.
2. Amazon returns an ID
The message definition sends the request to Amazon, which returns a report ID. Tinx stores the report ID on the Amazon Report List page. The following screenshot shows an example report ID recorded on the Amazon Report List page.
The Amazon Report List page shows the status of Amazon reports downloaded into Business Central, either automatically or on request. Examples include settlement, return, and order reports. Use this page to confirm that scheduled downloads are running correctly and that you've received all expected reports.
3. Download the report
Tinx Connector can download the report from Amazon in two ways.
Execute Report Processing: On the Amazon Report List page, choose the Execute Report Processing action to process the downloaded reports without waiting for the job queue.
-
Job queue: Create a job queue entry for the Amazon Reports Processing report 11205839. The job queue entry processes every downloaded report, and the processed report stays visible in the reports list. For more information, see Use job queues to schedule tasks.
With either method, the Report Status field changes from DONE to COMPLETE, and the report document URL is filled in.
To review the imported report, on the Amazon Report List page, select the relevant report, and then choose the Edit action. On the Amazon Report Card page, on the Report Response FastTab, you can find the raw report data imported from Amazon.
4. Convert the report
Amazon sends the file in its own format, usually a tab-delimited flat file. Tinx Connector converts it into a format that Business Central can read. The conversion runs through a job queue entry. Each Amazon report type has a specific Tinx report to process it. For example, you can schedule report 11205846 to process the Amazon report GET_MERCHANT_LISTINGS_ALL_DATA. This Amazon report contains products. For more information, see All Listings Report. The following screenshot shows the Tinx reports that process the imported Amazon reports.
Step 3 is the same for all report types. One job queue entry, Amazon Reports Processing, downloads every raw Amazon report to the Amazon Report List page. Step 4 is different for each report type. Each type has its own job queue entry, and the converted data goes to a different page in Business Central.
The job queue entry picks up only reports that aren't processed yet and have the Report Status field set to COMPLETE. Processed reports stay on the Amazon Report List page, but they're marked as Is Processed.
5. Review data on the destination page
Where the converted data goes depends on the report. Product listings go to the Webshop Products page, orders go to the Amazon Orders page, and FBA returns go to the Amazon Returns page. Continue processing data from there. For example, if you imported products, the next step is to match the Amazon products with the Business Central items.
Report access and your private application's permissions
Some Amazon reports contain buyer personal data. Tinx Connector can request and process these reports automatically through the Selling Partner API only if your private application has the required permissions. For more information about restricted roles, see Amazon private application.
If your private application doesn't have the restricted roles, or if you use the Tinx public application, Tinx Connector can't import personally identifiable information (PII) from Amazon automatically. You can still get that data into Business Central by downloading the report manually from Amazon Seller Central and then uploading it to Business Central. For more information, see Importing Amazon customer data to Business Central.
Direct API calls
Instead of a report, you can use a direct API call to import data such as products, stock, or fulfillment orders from Amazon. You might need this option when the data available in reports doesn't meet all your needs.
Export data to Amazon with feeds
For most webshops, Tinx Connector sends changes from Business Central to the webshop as soon as they happen, without storing the data first. Nothing is held in a buffer, because you don't review or approve data that leaves Business Central. For more information, see From Business Central to webshop: Publish immediately.
Amazon works differently. Tinx Connector can't send data to Amazon in a single call. Every feed takes several steps.
- Tinx Connector requests Amazon for an upload location for the feed data.
- Amazon returns a URL.
- Tinx Connector uploads the feed data to that URL.
- Tinx Connector creates the feed for a specific marketplace and type of data.
- Tinx Connector checks the processing status of the feed until Amazon finishes processing it. Processing can take up to 8 hours.
To understand the details of Amazon feed processing, review the Amazon Selling Partner API (SP-API) documentation. For more information, see Submit a feed.
Because a feed passes through several calls, Tinx Connector stores it on the Amazon Feeds page. The Amazon Feeds page lists all feed submissions that Business Central has sent to Amazon. Use this page to:
- Check whether Amazon successfully processed the feeds.
- Review any failed updates and their error messages. Reviewing failed updates helps keep your listings and stock levels synchronized.
Tinx Connector uses feeds to publish stock and to send shipment confirmations to Amazon. You can also publish product data through a feed. The default mapping doesn't cover it, so it needs a custom setup. By default, some feed values are fixed, but you can change them.
Throttling limits
Throttling limits are an important aspect of the Tinx Amazon Connector setup. Amazon limits how many requests you can send in a given period. Each type of request has its own limit, so you can't use the same approach for all of them. Requests over the limit fail, so orders, stock updates, or shipment confirmations don't get through on time. For more information, see Usage Plans and Rate Limits.
Message definitions get rejected if you exceed the throttling limits. In that case, you get a Rejected line with the following Fault reason on the Synchronisation Ledger Entries page. For more information, see Synchronization ledger entries.
{
"errors": [
{
"code": "QuotaExceeded",
"message": "You exceeded your quota for the requested resource.",
"details": ""
}
]
}Consider the throttling limits when you set up:
The frequency of job queue entries that are responsible for communication with Amazon. On the Amazon-related job queue entries, don't set the No. of Minutes between Runs field to less than 5 minutes. This limit applies to both inbound and outbound job queues. For more information, see Job queues.
The number of message definitions. If you reach the throttling limits, you can split AMZ-SP-086 into one message definition per marketplace. For more information, see Importing orders from multiple marketplaces.
-
The sleep parameter on the Sales Channel Card page. This parameter defines how often you make a call to Amazon. The parameter applies to all messages of the sales channel. The following screenshot shows an example setup of those fields.
The size of the API call. To better understand the limits in the particular sections, review the Amazon API documentation. For example, if the Rate (requests per second) for orders is 0.0056, you can't make those calls too often. Therefore, each call needs to import a huge number of orders. For more information, see searchOrders.
Related information
Use a private application to connect
Business Central with Amazon
Connect Business Central with
Amazon
Synchronization
dashboards
Recurrence
Key concepts in Tinx
Connector
Troubleshooting
checklist
Get help
from Tinx Support
Last updated on October 12, 2026