In header bar > sync status apart from active and queued synchronization processes it is possible to view if there were any errors during these processes. It is important to check them as there might be some actions required from the user.

One or few error messages during synchronization

Error examples:

  • "An existing connection was forcibly closed by the remote host"

The error means that the server that Linnworks was connecting to and obtaining information from was shut down. It could be caused by issues with the sales channel servers, the network connection on your provider's side, or issues with the Internet connection on the computer that you are using.

  • “Step: Synchronize orders for, Unhandled Error is thrown: Step: Get all Amazon accounts Error: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - Not enough storage is available to complete this operation.)”

The error message means that Linnworks either could not connect to channel server or their server run out of space.

These are normally a "one-time" errors and next syncs run successfully. Such errors do not have a detrimental effect on your account. The synchronization process could have stalled for a bit when a certain error occurred but it would then pick up from where it stopped.

If you received 1 or couple such errors in 100  successful synchronizations there is nothing to worry about.

Many error messages in a row

Many errors in the row prevent Linnworks from synchronization.

Normally in the automation logs, it looks like this:

Error examples:


  • “Authorisation token is hard expired. User needs to generate a new token for this application.”

If a token expires and no new token is generated, Linnworks will be unable to make API calls in that user's name. This has no effect on the user's eBay account, only on Linnworks ability to interact with eBay.

This article explains how to fix: eBay token expiry/generation


  • "Start sync Error: Amazon SubmitInventoryChange: Feed Rejected"

The error means that Amazon is rejecting the feed before even looking at it. This article explains how to fix: Amazon - inventory sync error: SubmitInventoryChange: Feed rejected

Amazon FBA errors during Order Sync

"amazon.SSOFStatefulWorkflow.common.WorkflowPermanentException: SIPS invalid request on fulfillmentOrder='"

This error can appear in the order sync logs when you are submitting an order to FBA. It indicates a temporary connectivity issue or an issue with the shipping address or shipping service. 

To fix it:

  • Check the shipping method and make sure it is used by FBA.
  • Check the address lines and make sure that it doesn't have anything abnormal or unnecessary in it, such as an international province code.
  • Try to submit this order again in a couple of minutes, if it was temporary, the order should submit the second time without any issues.

If the above does not help, please contact Amazon FBA for assistance. 

"ERROR: The field PerUnitDeclaredValue has a value of GBP, was expecting EUR"   - currency may vary.

To resolve this issue would be do disable 'Send Declared Value:' in channel settings and save the changes:

  • Go to Settings > Channel Integration > Edit Channel > FBA and disable 'Send Declared Value' option. 
  • Proceed to the Open Orders Screen > locate the order > right-click on order > Action > Bulk change > clear shipping label info.
  • Check in a while, the order should be submitted to the FBA successfully.