• All the synchronization tests done with this connector have been made with the BigCommerce v3 version.
• Modifying the BigCommerce connector configuration does not provoke a whole catalog synchronization. The only way to move this is by refreshing the connector.

Synchronizations are carried out in only one direction. Therefore:

• It is recommended to manage all product information in Sales Layer, not in BigCommerce. Modifications made in BigCommerce are not propagated in the Sales Layer catalog, which could lead to product information inconsistencies.
• Existing items in BigCommerce that do not exist in Sales Layer will not be disabled during synchronization. If an item was already synchronized, it will be deactivated. If the item was never synchronized before from Sales Layer, the item will keep its current state in BigCommerce because the relation between Sales Layer and BigCommerce did not exist before.

Disabled fields will not be included in the synchronizations. Example of a disabled item:

This connector is synchronized within the process manager of Sales Layer called Cron Calls.

• The Cron Calls process manager executes connectors exclusively.
• Cron Calls loops all existing connectors in Sales Layer. When the connector turn arrives, the execution checks for new information and changes made since the last execution.
• If there are changes, it will run the reading process of BigCommerce to avoid possible errors and proceed to data synchronization in blocks of 10 minutes. If the synchronization of one connector requires 50 minutes, the connector will require 5 executions of Cron Calls.
• If there are no changes, the connector does not use its turn.
• As a consequence of this process management system, synchronization of most connectors is periodic and automatic. Its periodicity depends on the length of the queue of all processes in Sales Layer. Connector executions may be launched in a time that varies between 5 minutes and 1 hour.

The BigCommerce connector gets the items that have to be sent to BigCommerce from the Sales Layer API.

• The connector will sync any item that may have suffered changes in Sales Layer, even if the change originated from related categories or variants.
• It will not sync previous items that have already been synchronized and have not had any changes or are not relevant to a connector modification.
• For more information, go to the following link: API introduction.

For example, if we configure a connector to export only visible items and modify the field to export invisible or draft items, the Sales Layer API will return these changes and will deactivate these items in BigCommerce.

Also, if we use label filters and remove the tag from an item that was previously sent to BigCommerce, the Sales Layer API will indicate to the connector that the item has to be deactivated.

Notes

• The BigCommerce connector usually does not delete items in BigCommerce. The only occasion variants will be deleted and created again is when the structure of the configurable attributes changes.
• Errors in categories may affect products. Errors that cause a parent node in the hierarchy of Sales Layer items not to be exported to BigCommerce cause child items below the parent item not to be exported with the expected behavior. For example, if a category does not sync, associated products will omit that category assignment. If a product does not sync, neither will its associated variants.
• The Sales Layer API is configured to send all the changes made in Sales Layer, even if they are not included within the connector filters.