Group pricing
Let’s try another scenario.
You want to specialize navigation, products, and pricing for different groups. In this case, you have customers who are part of a loyalty program as well as your employees.
Look at that red t-shirt again, but this time logged in as Alan Jay who is part of the loyalty program.
To increase sales, you want to encourage volume purchases of products from your loyalty program members. What happens when you add a single "Red T-Shirt" to the cart, then add 9 more increasing the quantity to 10.
The individual price of the red t-shirt is reduced to $8.97 or €7.97.
You also have pricing set up for your employees. But their pricing is different.
Try again, but this time log in as Jane Snow from Riders, Inc.
The individual price of the same red t-shirt for employees is $9.55 or €8.55.
Let's look at another product. In order to incentivise sale of jeans, you offer sales pricing. This special pricing is ongoing and so is not running as a promotion.
This time, look at the boyfriend cut jeans when not logged in, as Alan Jay, and as Jane Snow to see how the pricing changes.
Loyalty members receive even further discounts ($105.97 or €95.97); whereas, employees have the same pricing as the public ($158.00 or €143.00).
Why wouldn’t I just use a promotion for special group pricing? A promotion would work if your discount is a set across all products or for only a specific group of products, like 20% off everything or 10% off shirts. Also, promotions generally are run within a date range. But, the power of catalogs gives you the ability using either approach. In this scenario, the employee and loyalty programs prices are long running and the company policy is to have every loyalty program price end with ‘-.97’ whereas employee prices end with -‘.55’. Group specific price books make these kinds of requirements easier.
What if I don’t have group pricing for specific products? With price lists stacked and ranked in the employees catalog, Commerce allows you to leverage new and existing price books, in multiple catalogs, in multiple ways. When looking for a price, Commerce looks for a price in the first price book. Not finding one, it then looks for one in the next price book in the stack, minimizing maintenance. In this scenario, there is no special employee pricing for jeans so these products are not listed in the employee price book.