G
Glossary
Graduated Pricing
Graduated pricing is a usage-based rate structure that splits quantity into bands and charges each band at its own rate. A customer who crosses a threshold keeps paying the earlier rate on the earlier units, so one bill blends several rates instead of applying a single price to the whole quantity.
Key Takeaways
Graduated pricing bills every band separately, so 600 TB of Amazon S3 Standard storage costs $0.023 per GB on the first 50 TB and $0.021 per GB only above 500 TB.
That 600 TB costs $13,465.60 on AWS graduated rates against $12,902.40 if the whole quantity repriced at the top band, a $563.20 gap.
Graduated and volume are the two modes under the umbrella label "tiered pricing", and vendors use the words loosely enough that you have to read the math.
Falling rates aren't part of the definition. Bands can rise, which is how penalty overage rates get modelled.
Graduated counters reset each billing period unless the contract says otherwise, and that rule causes more invoice disputes than the rates do.
How does graduated pricing calculate a bill?
Graduated pricing walks the quantity up through the bands and charges the units that fall inside each one. The engine never reprices units it already charged.
Amazon publishes a graduated table for S3 Standard storage in US East (N. Virginia):
Band | Rate per GB-month |
|---|---|
First 50 TB per month | $0.023 |
Next 450 TB per month | $0.022 |
Over 500 TB per month | $0.021 |
Storing 600 TB for a month works out like this, in the binary GB AWS bills in, where 1 TB is 1,024 GB:
First 50 TB, 51,200 GB at $0.023, gives $1,177.60
Next 450 TB, 460,800 GB at $0.022, gives $10,137.60
Remaining 100 TB, 102,400 GB at $0.021, gives $2,150.40
Total $13,465.60, a blended rate near $0.0219 per GB
Price the same 600 TB under volume pricing and all 614,400 GB land at the top band's $0.021, for $12,902.40. The $563.20 difference is the whole practical argument between the two modes, and we cover the choice itself in tiered vs volume pricing.
Where does graduated pricing show up in real pricing pages?
Graduated pricing shows up wherever a vendor wants heavy users on a better marginal rate without handing them a retroactive refund on everything they already bought.
Patterns you'll recognise on published pages:
Cloud storage and egress. AWS and its competitors publish storage bands that only discount the bytes above each threshold.
API and message volume. Per-call and per-message rates drop as monthly counts climb, each band billed on its own.
Overage schedules. A committed plan bills included quantity at zero and puts graduated bands above the commitment, which is how overage charges usually get structured.
Seats past a headcount threshold. The first block of seats carries list price and later seats step down band by band.
Rising bands. Penalty rates for uncommitted usage climb across bands instead of falling, which the "bulk discount" framing misses.
What goes wrong with graduated pricing?
Most graduated pricing failures trace back to a band rule nobody wrote down, not to the rates.
Things that break in production:
Undefined reset behaviour. If the contract doesn't say whether the counter restarts monthly, annually, or never, finance and the customer read it differently and the invoice lands in dispute.
Mid-period plan changes. When a customer upgrades mid-period, the engine has to decide whether the band counter carries over or restarts, and the two answers produce different totals.
Late-arriving usage. Events that land after the period closes can push a customer into a higher band retroactively, forcing a re-rate downstream. Correct rating depends on the engine replaying that cleanly.
Quoting the top rate in sales. A rep who quotes $0.021 per GB on a 600 TB deal is off by $563.20 a month, because graduated pricing never delivers the headline marginal rate as an effective rate.
Manual tier maintenance. Teams that hand-code band boundaries into application logic redeploy to change a price, and the bands drift out of sync with the published page.
Related terms
These sit next to graduated pricing in the rate-structure family:
Volume pricing charges every unit at the single rate the total quantity qualifies for.
Tiered vs volume pricing covers which of the two modes to pick.
Block pricing sells units in fixed-size blocks, rounding partial blocks up.
Rating (billing) turns metered quantities into priced line items.
Overage charges are what a customer pays past an included allowance, often on graduated bands.
FAQ
Is graduated pricing the same as tiered pricing?
No, graduated pricing is one of two modes inside tiered pricing. Tiered pricing is the umbrella for any structure with quantity bands, and graduated and volume are the two ways of applying them. Stripe's billing docs use that hierarchy.
Does graduated pricing always mean a discount?
No, graduated pricing only means each band carries its own rate. Rates fall in most published examples because vendors reward scale, but rising bands are equally valid and get used for penalty overage rates and progressive surcharges.
Do graduated tiers reset every billing period?
Usually yes, and the contract has to say so explicitly. Monthly reset is the common default, so a customer's band counter starts at zero each month. Annual and never-reset variants exist in committed contracts, and leaving the rule unstated reliably generates disputes.
What does a customer actually pay per unit under graduated pricing?
They pay a blended rate between the first band and the last. On the AWS S3 table, 600 TB works out to roughly $0.0219 per GB against a top marginal rate of $0.021. The effective rate moves as usage changes, so quoting the lowest band overstates the discount.
Back to glossary
