Amazon Relay frequently adjusts the permissible refresh rate for load board searches. Using the correct speed settings is a MUST for effective Amazon Relay automation. While these settings can seem technical, understanding them offers a significant advantage over competitors who may overlook them. This guide covers best practices and testing methods to find optimal speed settings.
❗️ It’s crucial to note that Amazon Relay sets and enforces the speed limitations on their platform. This means that while our software is optimised to give you the best performance possible, it operates under Amazon's rules ❗️
It’s critical to follow these procedures precisely to ensure accurate results. Unlike some automation tools that hide failed searches, our system provides transparent metrics to help you make informed decisions and understand Amazon’s operational limits. This knowledge is useful for both automated and manual refreshing, as both can trigger restrictions if done too quickly.
In the visual provided, you can see an example of both failed and successful search counts. This indicator may appear differently across various tools, but all our tools display this metric in some form once a search is initiated.
A failed search happens when Amazon Relay does not return any results due to exceeding its speed limits. Instead of successfully retrieving available loads, the request is either ignored or blocked by Amazon. Think of failed searches like knocking on a door too quickly—if you knock too many times in a row, Amazon simply stops answering. It’s important to note that failed searches do not come from our software—they are entirely controlled by Amazon’s system and its restrictions.
This can happen for a few reasons:
Each of these reasons is explained in more detail later in this guide, so keep reading to understand how to optimize your speed settings effectively.
❗️ For specific speed recommendations, refer to the result table at the bottom of this article. However, reading through this guide will help you better understand the concepts❗️
The standard unit for measuring speed is milliseconds (ms). For instance, setting a refresh rate of 500ms means refreshing the load board every half-second. Lower ms values, like 400ms, indicate faster refreshes, while higher values, such as 600ms, slow it down. Although this concept may seem basic, it’s essential for accurate speed configuration—lower ms settings mean faster refreshes, while higher values slow the process.
High speed doesn’t always equal better performance. Just because a system might theoretically allow extremely rapid refresh rates (e.g., every millisecond), that doesn’t mean running it at the maximum speed is effective. Our software offers flexibility in speed settings to accommodate a variety of conditions, but we also provide feedback on failed searches so you can monitor what’s working and adjust as necessary. This approach lets you modify your settings when Amazon’s speed thresholds shift, ensuring that you’re not locked into a single rate. By allowing a range of refresh speeds, we enable you to adapt if Amazon’s constraints loosen, giving you an edge over systems that do not allow you to do it.
Over the years, Amazon’s speed thresholds have slowed (it seems like that it will keep going that way), likely to manage the increasing volume of users without overwhelming their own system. Currently, Amazon enforces these speed limits at the account level. This means that even if multiple users are refreshing the board from separate IPs under the same account, the speed limits will stack at the company level. It is crucial to grasp this concept: