Please note this is a channel-specific article only applicable to Amazon.
Product latency for my Amazon products is not correct on Amazon even though I have set it correctly in Linnworks config.
Linnworks sends latency information to Amazon with each stock level update for the specific SKU. If no latency information is set up in Linnworks Settings > Channel Integration > Amazon > Edit channel details > Inventory > Default Latency OR Product Based Latency, then no latency information will be submitted to Amazon and Amazon will set it back to default (1-2 days). This is the default Amazon behaviour for stock level updates via API, and there is nothing Linnworks can do to change it.
NB! If you have changed the Default Latency or Product Based Latency for the channel/item, then the update will in most cases be sent to the channel during the next inventory chance for the items, since this data is sent together with inventory updates. If there have been no changes to the stock level, the update will not be sent until there is a change in inventory.
If it is the same Amazon (unified) account - same Merchant ID but different Marketplace IDs - and the SKUs are the same for different marketplaces, then Amazon interprets the latency information as valid for all channels/marketplaces when Linnworks sends it. This way, Amazon sets the latency information to be the same on each marketplace.
Here is an excerpt from the Amazon Marketplace Web Service Feeds API Section Reference:
Quantity is a global value in relationship with a SKU, so changes to stock levels are reflected in all marketplaces that the SKU is active in. If multiple inventory feeds are processed for the same SKU in different marketplaces, then the quantity of the last uploaded inventory feed from the seller reflects the global inventory level. Setting the item inventory level to 0 effectively sets the item quantity to 0 in all marketplaces and makes the item non-buyable. All listing information is still maintained in the system.
As the info on default latency is sent along with the inventory level feed, it gets overwritten as well.
To illustrate this issue, let us take a look at the following example:
A seller has one account on Amazon and sells on three different marketplaces – UK, DE, FR.
There are three integrations in Linnworks – all with the same Merchant ID, but with different Marketplace IDs.
On inventory synchronization, Linnworks syncs these channels independently and in that same order - UK > DE > FR.
Let us assume that there is a latency of 1 set for UK, a latency of 2 set for DE, and a latency of 3 set for FR.
Since Linnworks sends stock level updates for the same SKU for all three different marketplaces in the order specified above, it will send a latency of 3 last (for the FR marketplace). This is the latency which will remain on all Amazon channels for the specified SKUs due to the way Amazon interprets it (see excerpt above for information from the Amazon API documentation).