A price table is a set of SKU prices that can be applied to specific contexts. These tables store the price information that is displayed on a store's page.

Unlike trade policies, which can also be used to segment prices, there is no limit to the number of Price Tables that can be created. The only limitation is a maximum of 100 fixed prices for the same SKU.

For example, let's say you want customers in São Paulo to see a price different from the price seen by customers in Rio de Janeiro. In this case, you can create two different price lists, and associate the first one to the customers in São Paulo, and the second to those in Rio de Janeiro.

You can define fixed prices or price rules to modify the price of an SKU in a price table.

This gives the retailer more freedom to handle contextual information from their customers.

To set up Price Tables, you need to:

1. Set up the priceTables field in Master Data
2. Define prices in the Prices module

Please follow the instructions detailed below.

To use Price Tables, you must enable the priceTables field in the Client entity in Master Data, which means that each customer in your store will have an attribute that indicates if it is associated with a specific price table.

To do this, follow the steps below.

1. In the VTEX Admin, go to Store Settings > Storefront > Master Data, or type Master Data in the search bar at the top of the page.
2. Click on the gear icon next to Profile System.
3. In the Clientes row, click on the pencil button.
4. Check the box next to priceTables.
5. Now click on the Schemas de Layout tab and drag the priceTables field from the Campos disponíveis section to wherever you want - for example, to the box Campos da coluna 1.
6. Click on Save.

Now let's configure the new field for your Customers entity.

1. In Master Data, click on Advanced settings.
2. Click on Estrutura de dados.
3. Select the Data entities tab.
4. On the CL (Customers) entity row, click on the pencil button.
5. In the priceTables row, click on the gear icon.
6. Check the box next to Is filterable?.
7. In the Domain field, you can enter a domain name for each price table. Press Enter to display additional fields. In the example in the image below, we entered two domains: Gold and Silver. Another way to use Price Tables is by declaring them directly on the customer form. If a new Price Table value is entered for a customer, that Price Table will be automatically created, without having been previously declared in Domains. To create more than one, separate them by commas. For example: gold, silver.
8. When you finish, click on Save.
9. In the row of the entity you have edited, click on the floppy disk icon to publish it.
10. Then, click on the arrows icon to reindex it.

Each customer can have up to 5 Price Tables associated with them. When the customer has more than one Price Table linked to them, the system will follow the order in which the Price Tables were created to determine the price of each SKU. If the SKU does not have a price configured in the first Price Table, the system will look for a price in the second one, and so on. In case there is no price configured in any of the Price Tables, the base price will be applied.

Now your Customers entity has a priceTables attribute, which can be populated directly in the Master Data UI or via API.

Once you have created your price tables, you can see the price of each product in the store separated by price table, in the same way as with trade policies.

In the Admin, go to Prices > Price List.

In the search filter, enter the names of the tables created in Master Data.

Price tables are shown as columns of the price list, as are trade policies.

To update a fixed price in a specific table, on the column corresponding to that table, and then on Define fixed prices.

To enter and update prices from a specific table via API, check out the Pricing API documentation.

The Price Table has priority over the prices from the trade Policy. If a given Price Table applies to a user's context, the price set in it will be used, even if that customer is also within the context of a trade policy with a different price.

When a user is not logged into your store, the default prices set by the trade policy will be displayed.

If the user is logged in, they will see the prices corresponding to the price table with which their email is associated.

For example, these two clients are linked to different price tables:

When Daniel, who is linked to the Silver price table, is logged into the store, he will see the prices set on this table. The backpack in the example above will cost USD 50.00.

Breno, who is linked to the Gold price table, will see the prices set on this table. He would pay USD 60.50 for the same backpack.

The customer must be authenticated — through token, password, Google, or Facebook — to see the prices that apply to them. Otherwise, the price shown will be the default price. Please note that entering the email address at checkout is not enough, since in this process the customer is identified, but not authenticated.