Connector functions and synchronization specifications

Regarding the synchronization of items (Listing Items), there are three important aspects to keep in mind about what the connector can do:

Create: if the product does not exist in Amazon, the connector will create it.

Update: if the product already exists in Amazon, the connector will update the existing information, with some exceptions*.

Delete: the connector does not delete products. In case you want to delete a product, you will have to do it directly on Amazon.

*There are certain changes that are not supported through the connector such as changing the product category, certain price fields... In those cases, the error log will show whether to update directly from your Amazon panel or request it from Amazon.

It is recommended, whenever possible, to manage all product information from Sales Layer, avoiding doing it from Amazon, except for deleting products. Keep in mind that the connector is unidirectional, so if modifications are made directly in Amazon, they will not be reflected in the Sales Layer catalog and could lead to inconsistencies in the product information.

Regarding synchronizations and API operation, once the connector has been saved with the synchronization mode (i.e. not in test mode), the next synchronization will occur according to the set configuration, but will also follow the rules below:

• Apart from following the status of items, it will sync any item that may have suffered changes in Sales Layer.
• It will synchronize any (modified) items that may be affected or relevant to the modification of any connector (such as updating the product type or synchronization settings, for example).
• It will not synchronize previous elements (that have been synchronized before) and have not had any changes or are not relevant to the modification of a connector.
• in case a synchronization is in progress and a change is introduced (in catalog or connector) that implies a new synchronization, the first synchronization will be canceled and the next synchronization will be queued. 

Note: The change of operation from Test Synchronization to Synchronization will require making a change in the exported items to be included in the next synchronization since the API takes into account the last modifications made to know whether to synchronize those items or not.

A quick option if you do not have more changes planned to continue adding information to these products is to change the status of these and put them back to their original state. For example, if you are exporting only visible items, you could make a visible-draft status change and that would cause them to be included in the next synchronization according to the synchronization period that has been chosen.

Another option that can synchronize the entire catalog would be to use the Force Refresh button in the Connector Parameters tab. We must be aware that this action will imply the synchronization of everything from scratch with the consequent synchronization times.