Initial Considerations

• All the synchronization tests done with this connector have been made with the BigCommerce v3 version.
• Modifying the BigCommerce connector’s configuration doesn’t provoke a whole catalogue synchronization. The only way to move this is by refreshing the connector.

Warning: BigCommerce connector usually doesn’t delete items in BigCommerce. The only occasion variants will be deleted and created again is when the structure of the configurable attributes changes.

Remember that synchronizations are carried out in only one direction. Therefore:

• It is recommended to manage all product information in Sales Layer, not in BigCommerce. Consider that the modifications made on BigCommerce are not propagated in the Sales Layer catalog. Therefore, this could lead to product information inconsistencies.
• Existing items in BigCommerce that do not exist in Sales Layer will not be disabled during the synchronization.
  • If an item was already synchronized, it will be deactivated,
  • But 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 didn’t exist before.

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

Warning: Errors in categories may affect products. Errors that provoke that a parent node in the hierarchy of Sales Layer items is not exported to BigCommerce, cause that child items below the parent item will not be exported with the expected behaviour. For example: if a category doesn't sync, associated products will omit that category assignation, if a product doesn’t sync, neither will its associated variants.

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

• The process manager Cron calls executes exclusively connectors.
• Cron calls loop all the existing connectors in Sales Layer and when the connector’s turn arrives:
  • The execution will check for new information and changes done since the last execution.
  • If there are changes, it will run the reading process of BigCommerce to avoid possible errors and proceed to its data synchronization in blocks of 10 minutes. This means that if the synchronization of one specific connector requires 50 minutes, the connector will require 5 executions of the cron calls.
  • If there aren’t changes the connector doesn’t use his turn.
• As a consequence of this process management system:
  • Synchronization of most of the connectors is periodic and automatic.
  • Its periodicity depends on the length of the queue of all processes in Sales Layer.
  • The executions of connectors 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 it originated from related categories or variants).
• It will not sync previous items (that have been synchronized before) and haven’t had any changes or aren’t relevant to a connector’s modification.
• For more information on this, you can go to the following link in our Support Center: https://support.saleslayer.com/es/api/introduccion.

Warning: 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.

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 the labels 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.