Preliminary Notes

Important warning

The configuration of the VTEX connector can be influenced by different aspects such as:

  • e-commerce configuration
  • e-commerce customizations (third-party services)
  • the type of service, which was contracted

For these reasons, an additional implementer may be necessary for its use.

On average, the time to complete an implementation can vary from 1 day to 2 months, depending on:

  • the implementer's experience
  • concrete casuistry
  • customization
  • data preparation

Sales Layer as a SaaS service does not implement or support these configurations but can provide specialized partners with extensive knowledge of the tool.

In any of these configurations we strongly recommend the following points:

  • Using a staging environment for testing. We need to verify that the synchronization works with necessary data and, in the case of pre-existing data, that it is not lost. The staging environment must be exactly the same as the production environment for the tests to be effective.
  • The implementer should have access to the production server to perform the final installation (since the configuration may differ from staging).
  • Making initial imports with little data, in order to speed up the process of the first integration tests, so that the client can ensure that the information structure is correct. In the Sales Layer connector, it is possible to establish multiple filters (labels, filters with manual searches, formulas ...).

Warning: For security, we recommend exporting all VTEX items before starting to work on integration with Sales Layer.

 

Other things to take into account

  • Any modification in the Sales Layer channel will send all the product information included in it (with the required time for the process).
  • Once the connection between Sales Layer and the e-commerce channel has been established, all the changes made in Sales Layer will be sent to the e-commerce channel. This means that, for example, if a status is changed to draft, the product will change in the e-commerce channel.
  • The plugin connects with e-commerce simply and generically, taking into account its most vulnerable points and the different personal cases depending on the customers. It is important to know that the plugin may have difficulties when mapping the fields as required. Additionally, it is not possible to map fields created by third parties. Should any difficulties arise, please, contact our support team directly.
  • All the tests done with this connector were made with the VTEX v3 API version. 

Once your e-commerce is set up, it is important to manage the product information in Sales Layer, in order to avoid conflicts that may arise managing it both in Sales Layer and in the e-commerce itself. For proper operation, we recommend that each person working with the product information has a clear understanding of the process.

Very important:

Our 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 we modify invisible or draft products, the API will return these changes and will send the ones related to the invisible and draft items as "Deleted".

As a result:

If our connector is configured to export only visible products and we change the status of a product to invisible, the API will send it to be deactivated.

If we filter by tags in a connector and remove the tag from a product that was previously being sent, the API will send it to be deactivated.