Understanding How Consumers Actually React to Price Changes
When a price goes up, people buy less. That seems obvious until you try to model it precisely. The problem is that a single price change does two things at once, and most people lump them together when they should be keeping them separate. This separation matters more than you might think if you are pricing anything. Let me start with the mechanism before the definitions. When the price of coffee rises from $3 to $4 a cup, a consumer doesn't just react to the new number. They re-optimize their entire basket. The total change in coffee consumption from that price move is called the price effect. It is the sum of two distinct movements along the indifference curve structure, and you can isolate each one mathematically. The first movement is the substitution effect. This captures what happens when you hold utility constant but change relative prices. Coffee became more expensive relative to tea, so the consumer swaps some coffee for tea. This movement is always negative along the demand curve. If the price of coffee rises, the substitution effect alone reduces coffee consumption. It does not depend on whether the good is normal or inferior. The algebra is clean: you rotate the budget line around the original utility level and read off the new optimal bundle.
The second movement is the income effect. After the price change, the consumer is effectively poorer in real terms even though their nominal income hasn't changed. For a normal good, feeling poorer means buying less. For an inferior good, feeling poorer means buying more because you can no longer afford the better alternative. This is where things get weird. So the price effect equals substitution effect plus income effect. For most goods they reinforce each other. Raise the price, substitution says buy less, income effect for a normal good also says buy less. The quantity demanded falls. But if the good is sufficiently inferior and the income effect is large enough in magnitude relative to the substitution effect, the price effect can become positive. That is a Giffen good. The price rose, real income fell, and the person bought more of it because they had to scrape by on the cheapest caloric option available. I saw this in practice once when advising a regional grocery chain on pricing their private-label pasta. They raised the price of their cheapest pasta by 20 percent expecting a standard demand drop. Instead, sales of that pasta increased slightly. The income effect dominated. Low-income customers who were already eating that pasta couldn't afford the mid-tier brands they would normally substitute toward, so they doubled down on the cheapest option even at the higher price. The substitution effect went one way. The income effect went the other and won. It was a textbook Giffen moment in a supermarket aisle, not a lab experiment.
Here is the counter-intuitive part that beginners miss. The magnitude of the income effect depends on how much of your budget the good consumes. A 10 percent price increase on a good that takes up 2 percent of your income produces a negligible income effect. The same 10 percent increase on housing, which consumes 35 percent of income, produces a large income effect. Budget share matters more than elasticity estimates in many pricing decisions. Most people look at historical elasticity tables and ignore the budget share component entirely. Another thing nobody talks about enough is the difference between the Hicksian and Slutsky decompositions. Both isolate substitution and income effects, but they use different approaches to hold purchasing power constant. Hicks keeps utility constant. Slutsky keeps the original bundle affordable. The numerical results differ slightly. In practice it rarely matters for casual analysis, but if you are doing actual demand estimation for a pricing model, you need to know which one your software uses and whether the difference is material for your price range. I ran into this when building a demand system for a utilities client. The two methods gave elasticity estimates that differed by 0.15 at the margin, which translated into millions in projected revenue across their customer base. We settled on Hicks because it is theoretically cleaner for welfare analysis, but I have seen good reasons to prefer Slutsky in discrete choice contexts where the budget constraint binding at the original bundle is the natural reference point. There is also a practical limitation here that most textbooks skip. These decomposition methods assume stable preferences and continuous demand functions. Real consumers have kinks, habits, and brand loyalties that create discontinuities. A person might not buy a product at any price above a certain threshold regardless of income effects. They simply stop considering it. This makes the substitution-incoome split messy in empirical work. You can estimate it, but the confidence intervals tend to be wide unless you have panel data at the individual transaction level, which most firms do not.
Get the Full Details
If you are trying to apply this framework, start by identifying which goods in your catalog are likely to have large income effects. Look for products with high budget share among your core customer segment and low brand differentiation. Those are the ones where price changes will generate income effects strong enough to distort the standard substitution pattern. For those products, estimate demand separately by income tier instead of using a single aggregate elasticity. You will find that the apparent price elasticity of your whole customer base is actually a weighted average of very different behaviors across segments. The quantity effect is really just the observable outcome of the price effect playing out in the market. When you change a price, the quantity demanded moves by the amount of the total price effect. Revenue moves by price times the new quantity, or the old quantity times the price change plus the price change times the quantity change plus the interaction term. Whether revenue goes up or down when you raise price depends entirely on whether demand is elastic or inelastic at that point. If demand is elastic, the quantity effect dominates and revenue falls. If demand is inelastic, the price effect dominates and revenue rises. This is basic, but the complication comes when elasticity itself changes as you move along the demand curve, which it almost always does. A useful rule of thumb that actually works: if you are pricing a necessity with few substitutes and it consumes a small fraction of income, you are probably in the inelastic region. Raising price there increases revenue. If you are pricing a discretionary good with many substitutes or one that consumes a meaningful share of income, you are likely in the elastic region. Raising price there decreases revenue. The edge case is the middle ground where the elasticity hovers around one and small estimation errors flip your conclusion. That middle ground is where most pricing mistakes happen.
If your situation involves a product that behaves like the pasta case did, standard revenue management tools will mislead you. They assume downward-sloping demand everywhere. When you hit a Giffen-like zone, those tools recommend cutting price to boost volume and revenue, which is the exact wrong move. The workaround is to segment your data by income proxy and check whether the demand curve for your target segment actually slopes upward in any price range. Run a simple regression of quantity on price within each segment with controls for time and promotions. If the coefficient turns positive in a specific range, you have found your Giffen zone. Price accordingly. Do not follow the default algorithm. The broader point is that price changes never produce a single clean response. They produce a decomposition of responses that depend on preference structure, budget shares, and income effects. Getting the decomposition right changes the pricing decision. Getting it wrong costs money. Most of the time the standard model is fine. The times it is not fine are the times that cost the most.
