When the Model Was Right and the Decision Was Wrong

May 2026  |  Pricing Strategy  |  Empirical Research Note  |  ← Back to Blog

This analysis draws from a working paper on profit-aware pricing in two-sided marketplaces, examining profit optimization across 110,840 transactions from the Olist Brazilian e-commerce marketplace.


The Finding

In one electronics category from my marketplace pricing research, the revenue-optimal recommendation produced an 82.7% increase in revenue and a 144% reduction in profit at the same time.

The elasticity estimate was directionally correct. Demand responded exactly as the model predicted. The optimization system was working as designed.

Most optimization systems fail long before the modeling fails.

The problem was that the system was optimizing the wrong objective.

"A technically correct recommendation can still be the wrong business decision."


The Mechanics

The electronics category in this analysis had a price elasticity of -2.18, meaning demand is highly responsive to price changes. A revenue-maximizing algorithm correctly identifies that lowering prices will generate substantial volume increases. The 40% price reduction it recommends projects an 82.7% revenue increase, and the demand model is right. That volume increase does materialize.

The issue is what happens on the cost side. With a cost of goods sold structure in the range of 60 to 75%, consistent with industry benchmarks for consumer electronics, the revenue-optimal price falls below the profit-maximizing threshold. At high volumes, each additional unit sold at the discounted price amplifies the loss rather than generating profit. The result is a margin spiral where more sales means more loss. Relative to the original pricing baseline, projected profit turns negative despite the large increase in revenue.

This is not a modeling failure. The demand estimate was accurate. The revenue projection was accurate. The system was behaving exactly as it was instructed to behave. The failure was in what the system was instructed to do.


The Objective Function Problem

Revenue often becomes the default optimization objective in pricing systems because it is easy to measure, easy to communicate, and easy to operationalize. Sales teams report revenue. Dashboards track revenue. Quarterly targets are denominated in revenue. The entire organizational incentive structure points toward topline growth.

Profit maximization requires integrating cost structure into the optimization, which introduces uncertainty, complexity, and the need for cost data that is often harder to validate than demand data. It is technically harder to do and organizationally harder to defend.

So organizations take the path of least resistance. They optimize revenue and assume profit will follow. In inelastic markets with thin cost structures, this assumption often holds. In elastic markets with material costs, it breaks down systematically.

Optimization systems do not understand strategy. They only optimize the incentives they are given. When those incentives are misaligned with the actual business objective, the system will reliably produce the wrong answer, and do so with high confidence.


The Organizational Dimension

The deeper issue is not technical. A profit-aware objective function is not difficult to implement once the cost structure is validated. The harder problem is organizational.

Revenue is visible and immediate. Margin destruction from a flawed objective function is invisible until it compounds. A pricing team that shows an 82.7% revenue increase will be celebrated. The 144% profit reduction will appear in a quarterly review months later, attributed to cost pressures or market conditions, and the connection to the pricing decision will rarely be made explicitly.

This is why the problem persists. It is not that organizations do not understand the revenue-profit distinction in theory. It is that the feedback loop between pricing decisions and profit outcomes is too slow and too noisy to consistently correct misaligned objective functions in practice.


The Practical Implication

The most important question in pricing system design is not "how accurate is the demand model?" It is "what is the system being asked to optimize, and is that the right objective?"

A well-estimated system with the wrong objective function can outperform a poorly-estimated system with the right one for a long time, until the underlying economics eventually assert themselves.

Before investing in model refinement, it is worth asking whether the optimization target itself is correctly specified. In elastic markets with material cost structures, revenue maximization and profit maximization are not equivalent problems. Treating them as equivalent is the most expensive assumption in applied pricing.


Conclusion

The electronics finding from this research is a useful illustration precisely because everything about the modeling was correct. The demand estimate was accurate. The revenue projection was accurate. The system performed exactly as designed.

The failure was upstream of the model. It was in what the model was asked to optimize.

This analysis is part of a broader working paper on profit-aware pricing in two-sided marketplaces, examining demand elasticity estimation, profit optimization under cost uncertainty, customer lifetime value modeling, and implementation frameworks across 110,840 transactions from the Olist Brazilian marketplace. The full paper is available on my research page.


← Back to Blog