Consumption-based pricing flips the traditional subscription script. Instead of locking customers into a fixed monthly fee whether they use the product heavily or not at all, the meter ticks with their actual usage. AWS, Twilio, and Stripe popularized the model, and it has been steadily moving into broader software and even some commerce categories.
How the meter works
Three pieces have to line up for consumption pricing to function:
- A unit of consumption — gigabyte, API call, message sent, transaction processed. The unit must be measurable, attributable to one customer, and meaningful to them.
- A metering pipeline — the engineering plumbing that captures usage in near real time and rolls it up for billing. This is where consumption pricing often breaks down for younger companies.
- A pricing curve — flat rate per unit, tiered with volume discounts, or hybrid with a platform fee plus overage. The curve shapes who finds the model attractive.
Where it works and where it does not
Consumption pricing thrives where usage genuinely correlates with value (cloud compute, payment processing, SMS) and where customers can predict their volume. It struggles when usage is unpredictable, when the unit is hard to explain, or when buyers want budget certainty. Most large enterprises prefer at least a committed minimum to avoid surprise invoices.
Why subscription merchants should care
Even if your Shopify store sells boxes and not API calls, the underlying idea — pay for what you use — is making its way into commerce through pay-per-shipment models, build-your-own-box pricing, and surge-priced add-ons. The discipline of measuring a meaningful unit and charging against it is the part to borrow. See usage-based pricing for the broader category and subscription pricing models for how it compares to flat fees.