How do price lists work?

If a client has a price list assigned, these prices will be prioritized over the general prices defined in the product catalog.

First, you need to create a price list with a code and name that lets you easily identify each. Then, assign the products included in the list with their corresponding price. This can be done one by one or through the client template.

Price lists can be modified to adjust to changes in your pricing policies, or they can be disabled once they have served their purpose and you don't want them to be used by your salespeople anymore.

These are the general steps to follow:

• Create a price list
• Add products and assign them the prices on the list
• Assign a price list to a client

Click here to find a detailed walkthrough on creating price lists.

When creating an order for a client that has an assigned price list, prices are applied automatically.

For clients who don't have an assigned list, if there are price lists available, the seller can either select a price list or use the regular prices.

🗂 Massive import

Price lists can be imported from Excel templates. Importing allows you to create new price lists, as well as edit existing ones.

You can learn more about bulk importation in this article.

⚙️ Create and edit via the API

On this link, you'll find all the information from the API to create and edit price lists.

The API v2 allows you to create a new price list with the HTTP POST method and update it with PUT.

If you wish to make specific changes to price lists, you can include only those that you wish to create or edit; you don't need to always include all elements.

If you send Handy the same prices that you had before, these won't be modified, and their current value will be maintained. When navigating price lists on the web portal, you'll see that the date of the last update hasn't changed.

❌ ** Creating and editing via API v1 (obsolete) **

Before API v2 existed, which is the more robust and manageable version, there used to be another method to update price lists via API v1, which allowed, in one single request, to send thousands of elements to be updated at once, and even different price lists at once.

This API method has been recognized as obsolete, even though it still works for some integrations that are still up and running. It was marked as obsolete because it's very easy to reach the limit of processing of web requests our servers handle, which is 30 seconds per web request.

If you wish to keep using API v1, we recommend sending prices in lots, where it's limited to one price list at a time, and no more than 200 elements per request. This way, you can make sure that your requests are always processed successfully.

Remember, we're always here to help in the chat! 😎

Updated on: 09/29/2025