Segmented pricing strategy: test margin and demand

A segmented pricing strategy groups comparable business offers, measures the economics of each group, and tests proposed prices against explicit volume assumptions. Start with actual net prices and variable costs, then keep the observed baseline separate from the demand response you have assumed.

Define segments before looking for a price gap

Consider a US industrial distributor selling the same replacement cartridge through three service offers. Routine orders receive normal fulfillment. Scheduled orders have a committed delivery schedule and consolidated shipments. Rush orders require expedited handling.

These are offer segments with observable business terms. Document eligibility, the service promise, who assigns the segment and the effective dates. Assign each transaction once using the terms of the order. An account can use different offers on different orders, so do not force all its purchases into a single category if that changes the comparison.

Keep product specification, package size, currency and reporting period constant. If these vary, subdivide the analysis before interpreting the price gap. A lower scheduled price may accompany lower fulfillment costs; that is a commercial difference to measure, not evidence of weak pricing.

Set policy boundaries with the responsible commercial and compliance owners before offering different terms. The financial calculation below evaluates contribution; it does not determine whether any particular segmentation policy is appropriate for your business.

Build the observed baseline from exports

Bring invoice lines with customer, order, segment, product, quantity, net sales and transaction date. Attach the product cost assigned to those sales and variable service costs for the same orders. Include discounts, credits and earned rebates consistently in net sales. A pricing dashboard helps reconcile price exceptions before using the baseline.

Here the September 2026 export has no returns and one realized price within each segment. Variable service costs include only costs that change with these orders. Fixed facility and corporate costs are excluded throughout, so contribution is not operating profit. The distinction from other profit measures is explained in gross margin versus contribution margin.

Put this baseline on a sheet named Segments, in A1:E4. All unit amounts are USD.

Add F for revenue, G for variable cost, H for contribution and I for contribution per unit. Enter these Excel formulas and fill down through row 4:

F2 =B2*C2
G2 =B2*(D2+E2)
H2 =F2-G2
I2 =C2-D2-E2

Scheduled orders have the lowest unit contribution but produce the most contribution dollars in this baseline. Rush orders have the highest realized price and contribution per unit, while their service costs are also higher. Neither observation establishes what either group would buy at a different price.

For an underlying transaction sheet named Transactions, with segment in A, units in B and net sales in C, derive the realized price for the segment named in Segments!A2 with:

=SUMIFS(Transactions!$C$2:$C$1000,Transactions!$A$2:$A$1000,A2)/SUMIFS(Transactions!$B$2:$B$1000,Transactions!$A$2:$A$1000,A2)

Expand the ranges to include the whole export. Microsoft documents SUMIFS for sums meeting multiple criteria; add product and period criteria when the sheet includes other populations. Do not average invoice-level unit prices. Covirage is not affiliated with Microsoft.

Test a proposed price with an explicit demand scenario

The pricing team now proposes the prices below. For illustration, it assumes each segment retains 95% of baseline units. This 5% reduction is a scenario input, not an estimated elasticity or a prediction from the observed rows.

Enter proposed price in J and assumed units in K on Segments. Calculate proposed unit contribution in L, scenario revenue in M, scenario contribution in N and the contribution change in O:

L2 =J2-D2-E2
M2 =J2*K2
N2 =L2*K2
O2 =N2-H2

The scenario reduces revenue from $88,000 to $86,070 while increasing contribution from $30,000 to $30,970. That result follows from the stated price, volume and unchanged unit-cost assumptions. It does not establish that the strategy will produce those results.

Test alternative unit assumptions before approving a change. If lower scheduled volume removes shipment consolidation, revise its service cost too. A fixed unit cost is inappropriate when the proposed terms alter the work required per order.

Calculate the volume threshold that preserves contribution

Minimum scenario units = Baseline contribution / Proposed contribution per unit

Add P for the continuous break-even volume and Q for the maximum volume reduction, using the proposed unit contribution in L:

P2 =IF(L2>0,H2/L2,NA())
Q2 =IF(B2>0,1-P2/B2,NA())

Display thresholds to two decimals and calculate with full precision. For whole cartridges, round required units upward: 270, 469 and 92 respectively. Scheduled has the narrowest volume cushion under these assumptions. The assumed 475 units exceed its threshold, but actual demand remains unobserved.

NIST's discussion of scatter plots distinguishes association from proof of cause and effect. Historical segment price differences likewise do not isolate price response. Agree a bounded test with the pricing owner, record which offers changed and when, and assess comparable outcomes before drawing a causal conclusion. Review win rate by segment, source and deal size separately when the question concerns won and lost opportunities.

Reconcile the economics before deciding

Baseline revenue minus variable cost must equal contribution: $88,000 − $58,000 = $30,000. A second check uses units times contribution per unit:

=SUMPRODUCT(B2:B4,I2:I4)-SUM(H2:H4)

This must return zero. Microsoft's SUMPRODUCT reference describes multiplying corresponding arrays and summing their products. The scenario check is =SUMPRODUCT(K2:K4,L2:L4)-SUM(N2:N4), also zero. The contribution changes sum to $970, matching $30,970 − $30,000.

Where it goes wrong

• Segments defined after seeing prices. The classification explains the result by construction and may not correspond to a usable offer.
• Different product mix mistaken for different pricing. Compare like items and terms first.
• Service costs omitted. Higher revenue can hide more expensive fulfillment.
• Assumed demand labeled measured demand. A scenario supplies a decision threshold, not evidence of customer response.
• Fixed costs deducted inconsistently. Keep contribution and operating profit separate throughout the comparison.

Test your own segment economics in Covirage

Bring your transaction export, segment definitions and matching product and service costs. Covirage maps the columns; its tools compute and check the figures, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See customer profitability for the supporting account economics.