Profit-Aware Pricing in Two-Sided Marketplaces

2-minute summary  |  April 2026  |  Full paper available here

Most marketplace pricing systems are designed correctly, and still destroy profits.

They optimize revenue instead of profit. In elastic categories with meaningful cost structures, this leads to systematically bad decisions. This summary covers the key findings and practical implications. The full 105-page paper with methodology, data, and implementation frameworks is available on the research page.

For pricing, strategy, and marketplace teams making production pricing decisions.

The Problem

A revenue-maximizing algorithm recommends a 40% price cut in an electronics category with elastic demand, projecting an 82.7% revenue increase. At a 65% COGS structure that recommendation reduces profit by 144%. The algorithm is technically correct on its own terms and commercially destructive in practice.

A 40% price cut generates +160% revenue and −162% profit simultaneously. It is the dominant failure mode in algorithmic pricing.

Revenue and profit optimization diverge sharply when demand is elastic and costs are material. For Electronics with elasticity η = −2.18 and 65% COGS, the profit-optimal strategy is a 20% price increase, not a decrease. Volume falls, but margin per unit rises more than proportionally, yielding a 5.6% net profit improvement.

What Actually Determines Pricing Decisions

Contrary to standard practice, cost accuracy matters more than demand modeling precision.

20% Elasticity Error

Profitable

All scenarios remain profitable. Direction is preserved. Magnitude changes but the recommendation stays correct.

5-Point COGS Error

−70 to 75% of gains

Forfeits most potential profit. Can reverse the optimal pricing direction entirely in borderline categories.

Every category has a breakeven COGS where marginal revenue equals marginal cost. Electronics has a breakeven of 54%, well below the realistic industry range of 60 to 75%, making its price increase recommendation directionally robust. Watches (66%) and Garden Tools (64%) sit near the boundary. A 2 to 3 point cost miss reverses the optimal decision.

Validate cost structure before deploying demand models. Cost validation takes 2 to 4 weeks. A/B testing for elasticity refinement takes 2 to 3 months. The parameter that destroys more value when wrong takes less time to validate.

What the Data Actually Shows

Applied to 110,840 transactions across 71 product categories from the Olist Brazilian e-commerce marketplace (2016–2018).

Robust Demand Elasticities

Bucket-level aggregation produced null results (β = +0.09, p = 0.648). Disaggregating to the category level recovered four robust negative elasticities:

Category Elasticity R²
Watches / Gifts −2.98 0.89
Garden Tools −2.77 0.72
Electronics −2.18 0.62
Consoles / Games −1.35 0.56

Marketplace Structure

The top 20% of sellers generate 82% of revenue (Gini coefficient 0.75). 96% of products have a single seller. Platform retention strategy should focus disproportionately on a small seller segment.

Customer Behavior

97% of customers purchase once. Same-order co-purchase rate across focus categories is 0%. However, 53% of repeat customers switch categories in their next order with a median return window of 29 days. These patterns invalidate conventional cross-selling strategies.

Freight as a Pricing Variable

Freight and price affect retention probability at approximately equal magnitude (βprice = −0.079, βfreight = −0.076). North region customers pay 51% more in total delivered cost than Southeast customers. Freight is simultaneously an acquisition barrier and a retention penalty.

What Companies Are Getting Wrong

Mistake 1: Optimizing for revenue. In elastic categories with material costs, revenue maximization converts profitable operations into sustained losses. The algorithm is correct. The objective is wrong.
Mistake 2: Investing in same-session cross-selling. With a 0% co-purchase rate across focus categories, bundle recommendation infrastructure has no customers to target.
Mistake 3: Treating freight as fixed. Shipping cost affects retention at the same magnitude as product price and creates structural demand barriers in remote regions.

What Actually Works

Price for profit, not volume. Apply the Lerner Index framework using validated elasticity and cost structure. In some categories the profit-optimal move is a price increase, not a decrease, even when demand is elastic.
Prioritize cost validation. Establish the plausible COGS range before committing to a pricing recommendation. If the range crosses the breakeven threshold, validate costs before acting.
Replace bundling with sequential engagement. Customers do not buy across categories in one session, but 53% return to a different category within 29 days. Time-triggered recommendation campaigns outperform same-session cross-sell widgets.
Use freight strategically. Free shipping thresholds in high-freight regions, regional pricing tiers, and local seller recruitment reduce both acquisition barriers and retention penalties simultaneously.

Expected Impact

With disciplined implementation, including A/B testing with Bonferroni-corrected stopping rules, phased rollout design, pilot thresholds, and rollback criteria, the projected annual gain is approximately 8 to 9% above baseline profit, conditional on cost validation and experimental confirmation. This improvement comes without increasing revenue. In most scenarios it involves decreasing revenue while improving margin.

Bottom Line

The failure mode is consistent. Pricing teams optimize revenue instead of profit in elastic, cost-heavy environments. The fix is straightforward but rarely implemented. Integrate cost into the objective function, validate it before deployment, and test decisions under uncertainty.

This is not a modeling problem. It is a system design problem.

The methodology transfers across industries and data contexts. The point estimates do not. What generalizes is the framework. Identify the profit-optimal price using the Lerner rule, stress-test it against cost uncertainty, validate experimentally before full deployment, and build implementation discipline into the process from the start.