Supported and Unsupported Functionalities

The connector’s scope includes catalog integration features but has some specific considerations to keep in mind, such as the following:

VTEX supports custom fields (characteristics in products and attributes in variants), and this is supported by the channel. However, to make the most of them, each case must be previously analyzed.
Category tree cannot change its relationships after being set by VTEX.
VTEX isn’t limited to having one unique reference in items, but for adequate and coherent synchronization purposes it has been set this way from Sales Layer.
Due to the design of the connector, it is possible that a substantial increase in synchronization times may be detected from approximately 30,000 items onwards. If larger quantities are required, each case should be analyzed on a case-by-case basis.

Collections: These are a type of “categories” with no hierarchy structure, a grouping that VTEX has for specific needs. As mapping is done for categories, collections are not covered.
Attached files uploading: VTEX has a feature for attached files (such as pdf manuals, or digital products). This cannot be synchronized from SL-VTEX channel, at the moment.
Offers: VTEX supports offer management, but at the moment, SL-VTEX channel cannot synchronize this.
API’s not supported: VTEX has many API’s for different features, but the channel only supports the Catalog one.
Fields/Attributes type (radio, check, input, for instance) cannot be indicated by the connector. Only from VTEX. So we recommend having them already created before starting, otherwise, you will have to eliminate, create, and re-synchronize them after the first sync. Default selection prevails and it is respected by the connector after being modified manually.