In this step, you will send the current pricing information for all your products to VTEX.

It is common for store owners to delegate price calculations to the ERP. In such scenarios, the ERP is responsible for calculating the price of each SKU and sending this price to VTEX.

As mentioned in the Import products step, Trade Policies are used in VTEX to differentiate the catalog, prices and logistics settings for each sales channel connected to your store. You may use them, for example, if you want the same list of SKUs to have different prices in each marketplace where your store is selling.

It’s also important to understand our Pricing system architecture, based on three basic concepts:

• Prices: the amount of money for which SKUs are listed for sale
• Price Tables: a container that stores prices that should be applied in a given context
• Price Table Context: conditions for application of a price table, such as a trade policy

Also, given a specific Price Table is selected according to the context, there are some definitions that should be known to understand the computed price:

• List price: value displayed as the suggested retail price proposed by the supplier
• Base price: reference value for the computed price of an SKU in all contexts
• Computed price: retail price after applying the price rules of a specific context
• Fixed price: fixed value that overrides the computed price for an SKU in a price table

The computed Price is obtained from the application of price rules on a base price.

A fixed price overrides the computed price for an SKU in a price table.

So if you decide not to use price rules to compute your prices in VTEX, the way to do it is to send a single base price for each SKU sent by your ERP and set multiple fixed prices as needed to differentiate the value charged for each trade policy. If you would like a conceptual overview of our Pricing module, check out the beginner track in our Help Center.

To set the base price for an SKU, you should use the Create/Edit Price endpoint in the Pricing API.

You should set a base price for each SKU. In between steps, you can use the Get Price endpoint or visit the Products > Prices > Price list section of your Admin panel to check on your progress.

In the same Create/Edit Price request, you may optionally set a list price. Additionally, you may set either a cost price or a markup value. By defining either one of them, the other will be calculated to conform to the formula basePrice = costPrice * (1 + markup).

To set a fixed price for a specific context, you should use the Create / Edit Fixed Prices endpoint in the Pricing API. This context is represented by either a Trade Policy or a custom Price Table, which can be associated to a campaign or a customer cluster.

You should set a fixed price for each price table / SKU combination that needs to be priced differently from the base price. In between steps, you can use the Get Fixed Prices endpoint or visit the Products > Prices > Price list section of your Admin panel to check on your progress.

The tradePolicyId parameter should be filled in with the Price Table name if you want to set fixed prices for a custom Price Table that is not associated with a specific Trade Policy.

Keep in mind that price rules might be a better option than fixed prices if you are consistently applying the same criteria for SKUs in the same category, brand or markup range.

If you’ve done things correctly, you should have imported all your prices, including the base prices for your products and the fixed prices that should be applied in specific contexts.