Oracle has raised the share of a customer's cloud credits that can pay for third-party software. Microsoft and Google already count eligible marketplace purchases in full. For anyone selling software into those accounts, the fee has stopped being the interesting number. The commitment rules now shape the close date, the discount and the buying group.
On 23 October, at its AI World event in Las Vegas, Oracle said it had increased the portion of a customer's eligible Universal Credits commitment that can be applied to qualifying Oracle Marketplace purchases. It also added top-ups, so customers can replenish credit for those purchases. It did not say by how much. The same announcement brought Multi-Party Private Offers, which put an authorised reseller on one transaction with the software vendor and the customer, to the US, Spain and Brazil, with more EU countries planned by the end of 2026.
It reads like partner-programme housekeeping. For a revenue team it is the fourth large cloud provider saying the same thing: money a customer has already committed to its cloud can be spent on your product. That changes what a marketplace deal is. A buyer paying from new budget weighs your price against everything else that budget could fund. A buyer paying from a commitment it might otherwise fail to consume weighs your price against losing the money.
The fee is converging. The commitment rules are not.
Marketplace fees have narrowed to a band that rarely decides a deal. AWS takes 3% on a new private offer under $1m of contract value, 2% up to $10m and 1.5% above that, with renewals at 1.5%. Google Cloud's schedule, in force since April 2025, uses the same three tiers. Microsoft's standard store service fee is 3%, and qualifying private-offer renewals can take a 50% discount on it. Oracle's announcement did not mention fees at all.
What differs, and what deal desks tend to check last, is whether a particular purchase will actually count against the buyer's commitment. Microsoft counts 100% of the pre-tax amount for offers carrying its "Azure benefit eligible" badge, but only for licences used exclusively in Azure. Purchases paid from Azure prepayment do not count, and nor do card purchases made on the Marketplace website rather than through the Azure portal. Google Cloud counts 100% of Marketplace spend, minus a list of exclusions that includes services not running on Google Cloud and purchases made through a reseller where the vendor has not opted into Google's resale programme. Google updated that page on 22 October. AWS publishes no general rule. Its commitment terms are negotiated account by account, and advisers who negotiate them describe an annual cap on how much marketplace spend can retire, commonly a quarter of the commitment.
Figure 1
Provider | Eligible spend counted towards commitment | What most often disqualifies a deal | Fee, new private offer under $1m | Reseller route |
|---|---|---|---|---|
AWS | Not published; set in each customer's agreement. Advisers report an annual cap, commonly 25% of the commitment | Terms of the customer's agreement; advisers report that SaaS must run on AWS to qualify | 3% (2% from $1m; 1.5% from $10m and on renewals) | Channel partner private offers, with a 0.5% listing-fee uplift |
Microsoft | 100% of the pre-tax amount for "Azure benefit eligible" offers | Licence not used exclusively in Azure; paid from Azure prepayment; bought by card on the Marketplace website; some older agreements excluded | 3% store service fee (50% discount on qualifying private-offer renewals) | Multiparty private offers; 30 European countries from 27 May 2026, Australia, Japan and South Africa from 15 July |
Google Cloud | 100% of Marketplace spend, less listed exclusions | Not running on Google Cloud; bought through a reseller where the vendor has not opted into resale; professional services; listings owned by the buyer or its reseller | 3% (2% from $1m; 1.5% from $10m and on qualifying renewals) | Marketplace resale programme, vendor opt-in required for commitment credit |
Oracle | Increased on 23 October 2026; new share not disclosed | "Qualifying" purchases; detailed terms not yet published | Not stated in the announcement | Multi-Party Private Offers in the US, Spain and Brazil; more EU countries by end of 2026 |
Compared by the commitment, not the fee. Compiled from AWS, Microsoft and Google Cloud seller and buyer documentation and Oracle's 23 October announcement. AWS commitment terms are contract-specific; the cap shown is adviser-reported, not an AWS figure. Rules change often; check the provider's current documentation and the customer's own agreement.
Close dates start following someone else's calendar
Cloud commitments run over fixed terms. A customer approaching the end of one, with spend still short of target, has a deadline that has nothing to do with your quarter. Deals sold against that shortfall tend to arrive together and late, and they can be pulled forward or pushed out by a conversation between the customer and its cloud provider that your rep is not part of.
That makes the commitment end date a forecasting field. A pipeline review that asks only about the buyer's evaluation misses a more reliable driver of timing: how much the customer has left to consume, and by when. Teams that sell heavily through marketplaces can capture it at the opportunity stage, alongside the route (direct private offer or multiparty) and whether eligibility has been confirmed for this specific purchase rather than assumed from the listing.
The discount often runs the wrong way
Deal desks commonly treat a marketplace route as a cost to offset: a few points of fee, so a few points off. When the buyer is drawing down a commitment, that logic inverts. The purchase can be worth more to the customer through the marketplace than on paper, because it retires an obligation the customer is already carrying. The leverage sits with the seller, at least until the customer's procurement team works that out.
A deal that retires a commitment the buyer would otherwise lose does not need a marketplace discount to close.
The reverse also holds. A deal approved on the assumption that it counts towards the commitment, which then turns out not to, loses its main reason to close. The causes are mundane: a hybrid deployment on Azure, a reseller route on Google Cloud where the vendor never opted in, a cap already reached on an AWS agreement. They tend to surface after verbal agreement, when the customer's cloud finance owner checks the purchase. An approval workflow that records eligibility as a condition, rather than a note in the opportunity, catches the problem before the forecast does.
The buying group gains a member
Whoever owns the cloud commitment, often a FinOps lead or a cloud procurement manager, now has a view on your deal. That person did not evaluate your product and may never speak to your rep, but can decide whether the purchase goes through the marketplace at all, and in which quarter. SalesHub has covered the places a CRM data model breaks as buying groups grow. This is one more seat in that group, and it is rarely mapped.
Multiparty offers add a second name to the paper. Microsoft extended its multiparty private offers to 30 European countries from 27 May 2026 and to Australia, Japan and South Africa from 15 July. AWS adds 0.5% to the listing fee on channel partner private offers, calculated on the vendor's discounted price to the partner. With a reseller on the transaction, partner margin, deal registration and quota credit all have to be settled before the offer is published, not after the customer accepts it. Partner teams and deal desks that run separate approval paths will discover each other's terms at the worst possible moment.
What revenue leaders can settle now
None of this argues for or against selling through a marketplace. It argues for treating the commitment, rather than the fee, as the variable that matters, and for building it into the systems that run the number.
Fields and rules for marketplace deals
The buyer's commitment end date and remaining drawdown, captured on the opportunity and reviewed in forecast calls.
Eligibility confirmed for this purchase (badge, deployment model, purchase path, resale opt-in), recorded as an approval condition.
The named owner of the buyer's cloud commitment, added to the buying group.
The route (direct private offer or multiparty) chosen before pricing, with partner margin and quota credit agreed at that point.
A discount policy that separates fee recovery from commitment value, so the desk does not concede points the buyer would have paid.
Oracle did not publish its new percentage. Customers will hear it from their account teams, and sellers will hear it from customers. The revenue teams that already track commitment dates will know what to do with the number when it arrives.
Sources and notes. Oracle, "Oracle Expands Marketplace to Unlock New Partner Growth Opportunities", announced at Oracle AI World, Las Vegas, 23 October 2026 (PR Newswire, via Yahoo Finance): increased share of eligible Universal Credits commitment applicable to qualifying Marketplace purchases; UC top-ups; Private Offers, Private Offers Co-Sell, metered billing; Multi-Party Private Offers in the US, Spain and Brazil, more EU countries planned by end of 2026; no fee terms given. AWS Marketplace Seller Guide, "Understanding listing fees", fees effective 5 January 2024, read 24 October 2026. Google Cloud, Vendor Net Revenue Schedule, effective 21 April 2025, and "Google Cloud Marketplace commitment drawdown rates", last updated 22 October 2026, both read 24 October 2026. Microsoft Learn, "Azure consumption commitment benefit" (last updated 25 September 2025) and "Commercial marketplace transaction capabilities and considerations" (last updated 23 July 2026), read 24 October 2026. Microsoft multiparty private offer expansion as reported by Channel Insider, 25 May 2026. The AWS commitment cap and qualification criteria are reported by Redress Compliance, an AWS contract adviser; AWS does not publish general commitment terms. SalesHubMedia has no commercial relationship with any provider named. Journalism, not legal or procurement advice. Corrections welcome.
