Consumption revenue is the single most consistently misunderstood metric in AWS Partner tier progression. Partners generally know it matters. Far fewer understand exactly what counts, how it is tracked, and why two partners with comparable overall revenue can be sitting at completely different points in their tier journey. This post breaks down what actually drives the number AWS is looking at.
1. What Actually Counts as Consumption Revenue
Consumption revenue, in the context AWS uses for tier progression, generally refers to revenue that flows through AWS Marketplace and is properly attributed to the partner relationship. This includes public listing purchases, standard Private Offers, and CPPO transactions, as long as each is structured and documented correctly. Revenue that a customer pays directly to an ISV outside of Marketplace, even if that customer was originally sourced through an AWS co-sell relationship, typically does not count the same way, because AWS has no visibility into that transaction.
2. Why Deal Structure Affects Whether Revenue Counts Cleanly
Two deals with identical dollar values can be tracked completely differently depending on how they were structured. A deal run through a properly configured Private Offer counts cleanly. A deal that started as a Marketplace conversation but closed through a separate invoicing process outside Marketplace often does not get credited at all, regardless of the AWS relationship that originated it. This is one of the most common reasons partners feel their consumption numbers do not reflect their actual growth: the growth is real, but a meaningful share of it never got captured in a form AWS can track.
3. The Channel Visibility Gap
As covered in earlier posts in this series, channel-sourced revenue that runs through resellers without CPPO configured falls into this same visibility gap. A partner with a growing, healthy reseller network can still show flat or slow consumption growth if that reseller revenue was never structured to flow through Marketplace in a trackable way. This makes CPPO adoption directly relevant to tier progression, not just to channel program health.
4. Timing and Reporting Windows
Consumption revenue is generally evaluated over specific windows, and a spike in revenue that lands just outside a relevant reporting period does not help tier progression in the period it was needed. Partners planning a tier review or renewal should understand the timing AWS uses to evaluate consumption, rather than assuming that any revenue generated at any point automatically strengthens their standing at the moment they need it to.
5. Consumption Growth Rate Matters as Much as Absolute Revenue
AWS does not only look at total consumption revenue. Growth rate over time is a significant part of the evaluation, meaning a partner with a smaller absolute consumption number but a strong upward trend can be viewed more favorably for progression than a partner with a larger but flat or declining number. This is an important distinction for partners who assume tier progression is purely a function of total revenue size rather than trajectory.
6. How to Build a Consumption Growth Plan Deliberately
Because consumption revenue is trackable and specific, it can be planned around directly rather than treated as a passive byproduct of general sales activity. This means auditing current deal structures to identify revenue that is not being captured correctly, prioritizing Private Offer and CPPO structures for new deals where possible, and setting internal targets for consumption growth tied specifically to the thresholds relevant for the next tier, not just general revenue targets.
Strategic Takeaway
Consumption revenue is not simply a byproduct of overall business growth. It depends heavily on deal structure, channel configuration, and timing, all of which are within a partner’s control. Partners who audit their deal structures for tracking gaps and build a deliberate consumption growth plan make far more predictable progress toward tier advancement than those who assume growth in general will eventually translate into tier movement on its own.
Not sure how much of your revenue is actually being captured as trackable AWS consumption? Marketeering helps AWS partners audit deal structures and close the gaps holding back consumption growth.
