Verify tiered price boundary calculations

Write the cost function before approving the rate card

Stripe’s Set up tiered pricing documentation, checked 7 November 2026, distinguishes volume pricing, which applies the selected tier rate to the whole quantity, from graduated pricing, which adds charges within successive tiers. The resulting totals can differ at the same quantity. This lesson tests arithmetic, not whether either commercial model is appropriate or legally compliant.

Define the charged unit, currency, included quantity range and calculation method in the acceptance brief. Keep taxes, discounts, minimum charges and flat fees outside the first fixture unless they are explicitly specified. They can be added as separate components later. A simple model with stated exclusions is more useful than a realistic-looking total whose components nobody can reproduce.

Calculate a boundary using independent fictional numbers

Consider an invented rate card with units one through eight priced at 15 USD and units nine through twenty priced at 11 USD. There are no other charges in this example. At eight units, both candidate methods produce 120 USD. At nine, the whole-quantity method produces 9 × 11 = 99 USD. The accumulated-tier method produces 8 × 15 + 1 × 11 = 131 USD.

Write both answers beside the same quantity instead of comparing only the two displayed unit rates. The extra unit changes the first total by negative 21 USD and the second by positive 11 USD. That is a consequence of the fictional definitions, not a forecast of customer behavior. If the approved commercial offer expects one result and the quote shows the other, the defect is the calculation method or specification, not necessarily multiplication.

Test a decrease as carefully as an increase

Now reduce the fictional quantity from nine to eight. The whole-quantity total rises from 99 USD to 120 USD, while the accumulated total falls from 131 USD to 120 USD. Record this reversal explicitly. Do not automatically smooth the first result or add a hidden adjustment because it looks counterintuitive. The pricing owner must decide whether the approved model should contain that boundary.

Add quantities seven, ten and twenty to the test sheet. Seven costs 105 USD under either method; ten costs 110 USD under the first and 142 USD under the second; twenty costs 220 USD or 252 USD respectively. Independently recalculate each line and compare it with the supplied quote output. Keep a separate case for zero or out-of-range quantity, with its expected treatment provided by the actual specification rather than guessed from this simplified example.

Reconcile the quotation without changing the offer

The acceptance sheet should show quantity, selected calculation method, tier allocation where needed, line subtotal and any separately approved charges. If the final quote differs, first compare the unit definition and tier endpoints, then the method, then the additional components. Do not force agreement by editing a total manually. A matched amount at eight units would not have revealed the disagreement found at nine.

Have the pricing owner review both the arithmetic and how the customer-facing explanation describes the boundary. A mathematically correct result can still contradict an advertised promise about savings or quantity changes. Keep the two judgments separate. Acceptance means the agreed cost function and its explanation survive the tested increases and decreases; it does not authorize a new price, an invoice correction, a customer charge or any claim that the model will improve sales.

Make the reasoning concrete.

A fictional membership add-on uses the eight-unit boundary above. A sales calculator gives 99 USD for nine units, while the billing specification expects 131 USD. Both teams checked eight units and saw 120 USD, so they initially believed the systems agreed.

The teams hold the calculator release and resolve the intended method. All amounts are fictional calculations, not actual quotes or transactions.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Function

   What exact calculation method does the approved rate card specify?

2. Boundary

   Which adjacent quantities make the competing methods diverge?

3. Allocation

   How does the line total arise from the stated quantities and rates?

4. Decrease

   What happens when quantity moves back across the boundary?

5. Reconciliation

   Which component explains any difference from the supplied quote?

Watch for the wrong conclusion.

• Testing only a quantity where both methods coincide.
• Comparing unit rates without computing the payable total.
• Smoothing a surprising boundary with an undocumented adjustment.

Sources & scope

Workflows, fixtures, worksheets and examples are original editorial analysis. Sources support the narrow attributed statements, not measured business results. Platform guidance is scoped to the documented implementation and date checked. No real account, financial, document or publication action is performed.

• Set up tiered pricing →Primary technical documentation · Supports: Supports the two named calculation models. All rates, quantities, arithmetic and acceptance cases here are independently constructed.