Hello,
I’m attempting to reorganzie our pricebooks for 2025, yet instead of inventing the wheel again, I’d like to know what some best practices are for setting these up. We would like to combine two things:
- Use the tag system to include price increases based on beer style, for instance
- Core, seasonal, series, collab etc/
- IPA, DH, DDH, NEIPA, TIPA, etc…
- Barrel Aged
- Have our two pricebooks, one for retail/hospitality and one for wholesalers
- The two books have standard pricing for each product, based on the book,
- The SKU’s are different in price based on the tags that they have. (this on top of the book itself)
If anyone could help me on this, or if anyone wants to work together on this feel free to reach out. ([email protected])
Cheers,
Rémi
Hi Rémi,
Thanks for reaching out in the community! Other users may have more specific advice based on their own experiences, but I’m happy to provide some pointers that might help.
- Using Product Tags in Price Books
You can use product tags to create pricing rules, but it’s important to note that these rules can only be applied within a derived price book. If you’re not familiar with the different types of price books, our guide on Creating Price Books and Managing Product Pricing should provide more clarity.
Within a derived price book, you can set a rule that applies a quantity-based discount or a simple discount (the term “discount” here can also refer to an increase or decrease) to all products with a specific tag. For example, you could set a rule where a derived price book applies a 5% price increase for all ‘seasonal’ products. Currently, beer styles cannot be used as a parameter for pricing rules, but you can create and apply your own tags for styles.
- Setting Up Two Price Books for Retail/Hospitality and Wholesalers
To use tag-based rules, you’ll need at least one base price book. Depending on your pricing structure, you may be able to achieve the rest by creating two derived price books that apply specific rules to the base prices based on product tags. This would require a minimum of three price books: one base price book and two derived price books, each applying different percentage-based price increases based on the tags for Retail/Hospitality and Wholesalers respectively.
If your structure is more complex, you may need more than three price books. For example, you might require a separate base price book for retail/hospitality and wholesalers, which you would need to update manually during price changes. Then, you would create a derived price book for each, applying a percentage-based increase based on the respective tags.
I hope this helps give a bit of an idea, but I would definitely read the above-linked guide on price books. Some other users may be able to add value based on their own experience.
Hey Connor. Thanks for the reply! I’ll adapt the suggestions when building the new structure 
One question that remains is whether I can bulk upload prices from an excel file?
Thanks
Rémi
Hi Rémi, Thanks for your reply. Currently, it isn’t possible to import prices from an Excel file; however, we have an open feature request for Data upload price books (import prices from a spreadsheet) ; it would be great if you could add your vote to this! Cheers.