Learn how to keep integrated products updated with price and inventory level information. Before you start, check out what’s included in the product update flow:
|Prices defined in the VTEX main account||Prices defined in third party sellers or franchise accounts|
|Prices updated directly to the marketplace integration|
|Inventory levels defined in the main account||Inventory levels defined in third party sellers or franchise accounts|
|Inventory levels updated directly to the marketplace integration|
To use this flow, the connector should provide an endpoint according to the standard:
This endpoint should be configured in the VTEX affiliate registration page. Check out our Configuring an Affiliate article.
Whenever the seller updates a product or SKU in VTEX, a notification will be sent through the url configured in the section above. The table below presents the fields sent in this notification’s payload. The connector should use this data to implement the new product registration flow, described in the scenarios that will follow.
|idSKU||SKU ID in VTEX|
|productId||Product ID in VTEX|
|an||Seller’s account name in VTEX, shown in the store’s VTEX Admin url.|
|idAffiliate||Affiliate ID generated automatically in the configuration.|
|DateModified||Date when the item was updated|
|isActive||Identifies whether the product is active or not. In case it is “false”, it means the product was deactivated in VTEX and should be blocked in the marketplace. We recommend that the inventory level is zeroed in the marketplace, and the product is blocked. In case the marketplace doesn’t allow it to be deactivated, the product should be excluded, along with any existing correspondences in the connector.|
|StockModified||Identifies that the inventory level has been altered. Connectors should send an Fulfillment Simulation request to collect updated information.|
|PriceModified||Identifies that the price has been altered. Connectors should send an Fulfillment Simulation request to collect updated information.|
|HasStockKeepingUnitModified||Identifies that the product/SKU registration data has changed, like name, description, weight, etc|
|HasStockKeepingUnitRemovedFromAffiliate||Identifies that the product is no longer associated with the trade policy. In case the marketplace doesn’t allow it to be deactivated, the product should be excluded, along with any existing correspondences in the connector.|
The price update flow begins when the connector receives a VTEX Catalog notification, indicating that changes have been made to the SKU or product. Besides the notification mechanism, we recommend using an independent inventory update mechanism, so stocks are always updated. Diagram 1 illustrates the information flow used to keep prices of seller’s SKUs updated in the marketplace integration.
Diagram 2 illustrates how the price update occurs in the integration
Follow the steps below to maintain prices updated in the marketplace integration:
- Connector validates the VTEX <> Marketplace authentication. In case it has expired, perform the update routine defined in the marketplace’s documentation. Otherwise, connectors should log the error AND put the VTEX notification in a contingency queue.
- After receiving the VTEX notification, connectors should:
a. Check which store the product belongs to, through the “an” parameter.
b. If the
HasStockKeepingUnitModifiedis defined as true, the product should be registered or updated in the marketplace.
c. Collect details from every SKU using the
d. Validate if the product is active through the Get Product by ID endpoint, through the
e. Validate if the product is associated with the trade policy used in the marketplace integration through the
f. Identify whether the SKU conforms to the marketplace’s product registration rules.
g. Validate if the product’s category is mapped in the marketplace.
In case it is not mapped, the marketplace should put the SKU in the approvement’s queue, until the mapping is complete.
h. Use Fulfillment Simulation (without postalCode) to check if price is configured in the selected trade policy.
- To collect the product’s price, use the
- To collect the sales price configured for that trade policy, use the attribute
- Register operation’s Logs. Check out Content of the messages for this step.
If all validations pass, the product or SKU is sent to the marketplace and the operation is logged according to information described in the Logs made available for users section.
If the IDs between VTEX and the marketplace differ, the connector should store both values.
To avoid processing gaps due to the big volume of information of the initial load of products, we recommend:
- Using an async messaging architecture, using individual queues by context and store.
- Creating mechanisms that respect the marketplace API limit rates. We suggest the standard use of the Circuit Breaker integration.
- In case any of the steps listed above presents failures in communication, we suggest using the contingency mechanism of deadLetters.
- Being TotalReader: whenever possible, in the data transformation process, using standard values accepted by the marketplace, in case the information is not filled or sent by VTEX.
- In case the marketplace’s processing is in lots - meaning that the connector assembles a group of SKUs, guaranteeing the the limit of records per lot is respected, according to marketplace riles, and sending them to the marketplace at once - it is fundamental to control the lot’s processing, to avoid sending SKU updates without making sure that the product exists in the marketplace.
- Keeping a states table to know which SKUs have not been integrated with success, attempt date and the response received. This allows the system to use the contingency flow effectively, avoiding infinite loops, and avoiding reaching the request limit.
Make sure to check out our Recommendations for performing the steps above successfully.
Be mindful to make all validations at once, and before the SKU’s publication in the marketplace’s catalog. In case there’s an error detected, the connector presents the seller a list of actions to correct. This way we can avoid the correct - publish - correct cycle.
If products do not apply to steps a, b and c, an error log must be filed, and the connector should collect the next items on the list obtained by step 2.
Use the endpoints described below to get SKU, price and inventory details. It is important to note that when consuming this API, the connector must have a valid VTEX App Key and App Token. You can also download our Postman collection to access the API. The diagram illustrates the endpoints used in the integration:
Request bodies for POST calls
All parameters in the endpoints below must be declared in the request. In case one of the parameters does not have a value, you must still send it as
To consider the integration validated by VTEX, the connector should:
- Follow the step by step of the catalog integration flow.
- Check if flows comply with the scenarios described.
- Validate log messages contained in the table of Log’s Content of the messages.
- Perform the performance test to validate response time, and SKU processing time from a set of 5000 SKUs.
- Create tutorials for the final user (including text, videos and diagrams), including a step by step guide explaining how the connector created works. The documentation should be published in the production environment with easy access and navigation.
- Create a table that shows which data is mandatory and which is recommended when registering products or SKUs, and to improve the offer’s positioning in the marketplace’s storefront.
- Create a table with known error logs and actions that the user can do to solve the problem.
Tables should follow the format below. They will be implemented in the integration according to the connector’s documentation.
|VTEX field||How to fill it in VTEX||VTEX API||Marketplace field||Transformation||Mandatory||BuyBox|
|Name||Catalog page||/api/catalog/pvt/stockkeepingunit||ShortName||Sent to the marketplace only 50 characters||Yes||Yes|
Updated 8 months ago