# conditional pricing in HB

If I'm using conditional pricing, how will I encode the prices in the "Attribute Information" tab of CBC/HB? I applied proportional intervals across levels, do I need to use linear coding or can be part worth coding? Will this matter if I will interpolate prices later on? Thanks!

+1 vote
Good question.

You may use part-worth coding, and if you have 5 levels of price (in your conditional pricing table), then that will use up 5-1 parameters to estimate the main effect of price.  If you use a linear price, then you will use up just one parameters to estimate for the main effect of price.

Sometimes researchers have enough data and few enough SKUs (brands) in their studies to estimate the interaction between brand and price.  In that case, using linear pricing saves a lot of parameters to estimate, because in the case of 12 SKUs and 5 price points in the conditional pricing table (5x12 cells in the table), estimating interaction effects under part worth specification would lead to (12-1)+(5-1) for the main effects plus (12-1)(5-1) for the interactions or 59 parameters to estimate, whereas with linear coding of price it would require (12-1)+(5-1) for the main effects plus (12-1)(1) or 26 parameters to estimate.

If doing linear estimation and conditional pricing, your % change up and down from average price should have followed the same pattern across all SKUs.  Let's imagine you have 5 price levels, with relative prices of -20%, -10%, AvgPrice, +10%, and +20%.  In CBC/HB software, you select "Linear" for the Coding type for the Price attribute, and then at the right in the "Value" column, you would type the following 0.8, 0.9, 1.0, 1.1, 1.2 to indicate the relative prices used.  During CBC/HB estimation, the software will then give you a message that all values for linear terms have been zero-centered.

Then, when you use SMRT simulator or the Online Simulator, you make it much easier on yourself if you check the option that says to use the original conditional pricing table values in the simulator.  That way, you can simply specify the original price values from the original table (as was seen by respondents), and the software will map those values according to the table to the relative prices (on the 0.8 to 1.2 scale) prior to multiplying by the utility coefficient.  Much more intuitive way to specify prices for products rather than having to convert the prices to 0.8 to 1.2 relative scaling!

Either way, using part-worth estimation (which burns up more parameters to estimate, but has the potential benefit of capturing non-linearity) or using linear price will allow you to interpolate between prices included in the experiment.
answered Feb 27, 2012 by Platinum (148,340 points)
Also, an important sanity check to make sure you get this right is to compare the pseudo-demand curves you get from 2-way counting analysis between SKU and Price to the demand curves you get from sensitivity runs (including all SKUs in the simulation).  The information should be fairly similar between 2-way counts and simulated sensitivity demand curves, though the simulated curves will have less noise and better precision.
Thanks for this Bryan! I'll use part-worth since I only have 3 price levels and I'm interested to capture non-linearity. Thanks again!