Guides

Cloud Marketplace: When Partners Lose Out on Margins

When does a marketplace make sense for system houses and MSPs? Channel fees, commit caps, and who truly bears the cost.

By Alec Chizhik July 17, 2026 7 min read

Cloud Marketplace: When Partners Lose Out on Margins

Marketplace deals can look tempting to partners: the customer pays out of their cloud commit, and procurement runs through existing hyperscaler contracts. The real question is how much actually remains in the margin once fees, caps and the cash flow through the channel are taken into account.

Key Takeaways

Channel fees often range from 3 to 3.5 percent. Microsoft charges a flat 3 percent Store Service Fee. AWS CPPO sits at 3.5 percent with a 0.5 percentage point surcharge below the lowest Private Offer tier. Volume tiers and qualified renewals can fall below that. Server listings on AWS remain at 20 percent.
Private Offers drive revenue. The public listing provides visibility. The relevant sales channel is the individually negotiated Private Offer.
Deal P&L instead of margin rules. Decisions are based on contribution margin in euros after fees, delivery costs, and payout lag, weighed against zero revenue from a lost deal. Commit only counts within cap and eligibility.

Why Customers Buy Through the Marketplace

Anyone working as a system integrator, MSP, or ISV in the DACH region (Germany, Austria, and Switzerland) knows the argument well: customers often have unused commitment budgets they want to spend before the period ends. AWS refers to this as an EDP or Private Pricing Agreement, Microsoft calls it the Azure Consumption Commitment (MACC), and Google uses the term Cloud Commit. Marketplace purchases can count toward these commitments, but not automatically and not without limits. With the MACC, Microsoft counts eligible purchases at the full net amount before tax, provided the offer is marked “Azure benefit eligible” and the purchase is made through the Azure portal using the correct subscription. For AWS EDP/PPA and Google, crediting and eligibility depend on the individual customer contract. The amount credited is typically capped, often between one-fifth and one-quarter of the total commitment-always verify the details in the specific agreement. Before any pitch, clarify the cap, eligible SKUs, purchase path, and crediting timeframe. For procurement teams, this route frequently eliminates the need for new contracts and speeds up approvals. Mid-sized companies without a commitment usually require Co-Sell support or procurement convenience; otherwise, a direct contract often remains the cleaner option.

Private Offers Are the Real Sales Channel

The public listing is rarely where revenue is generated. Visibility helps with search and co-selling, but the actual deal closes through Private Offers: individually negotiated prices, contract terms, and payment schedules. Channel Partner Private Offers (AWS) and Multiparty Private Offers (Microsoft) let a reseller manage the customer contract while the ISV supplies the product. I plan margins and capacity around the Private Offer process. The catalog page is secondary.

What the Platform Keeps from the Deal

The rates depend on the provider and the sales path. AWS charges a 3 percent listing fee on the pre-tax contract value for public SaaS offerings. Private Offers are tiered by TCV in US dollars: 3 percent below one million US dollars TCV, 2 percent up to but below ten million US dollars, and 1.5 percent from that threshold onward as well as for renewals. At the ECB reference rate on 16 July 2026 (1 euro = 1.1467 US dollars), the lower threshold equates to roughly 872,000 euros and the upper threshold to roughly 8.72 million euros. This is an illustration as of the reference date. Tiering is based on the provider’s TCV in US dollars, even for euro-denominated offers. CPPO carries a 0.5 percentage point surcharge at AWS, resulting in 3.5 percent below the lowest tier. Professional Services have been set at 0.5 percent for Private Offers since June 2026. Server listings (AMI, Container, ML) remain expensive at 20 percent. Microsoft charges a flat 3 percent Store Service Fee with no tiering by deal size. Qualified Private Offer customer renewals are eligible for 1.5 percent after self-attestation. Every renewal must complete this attestation. According to its Vendor Net Revenue Schedule, Google pays the vendor 97, 98 or 98.5 percent per US-dollar TCV tier, as well as 98.5 percent for Native Renewals, Channel Shifts and Migrations. In the reseller path, realistic starting values are 3 percent (Microsoft) and 3.5 percent (AWS-CPPO below the lowest tier).

// Metric

3-3.5 %

Realistic starting values in the reseller path: Microsoft charges a flat 3 % Store Service Fee; AWS-CPPO below the lowest Private Offer tier charges 3.5 % – both before tax on the contract value. Tiered pricing and qualified renewals can fall below these rates.

At a 40 percent gross margin, a 3 percent fee equals 7.5 percent of the margin. At 15 percent, which is typical for thin resale, the same fee consumes one fifth of the margin. At 3.5 percent for CPPO the impact is even sharper. Additional costs include setup, legal work, tax handling on the net TCV before tax, and payout cycles that can stretch from days to weeks after the direct invoice.

Who Bears the Fee in the Channel Model

The fee is not distributed the same way with every partner. In a pure ISV listing, the platform keeps its share of gross revenue and pays out the remainder. With AWS CPPO, the ISV sets the wholesale price, the channel partner adds a markup, and AWS bills the end customer directly. The listing fee, including the CPPO surcharge, is tied to the offer structure. The partner earns from the uplift above wholesale. Under Microsoft MPPO, the channel partner manages the customer’s share. The store service fee is typically borne by the software vendor in the transaction model. CSP continues to operate as a separate Microsoft channel with its own billing and margin logic. With Google MCPO, channel partners can structure billing and top-line revenue differently than in a pure vendor listing. For system integrators and MSPs, the key is to define the route first-ISV direct, CPPO, MPPO, MCPO, CSP or ProServ-before calculating fees, wholesale pricing and contribution margins.

Control and the Deal P&L

Billing runs through the hyperscaler, which relieves the partner of collections. The customer remains in the platform’s billing environment. Support for purchasing and invoicing sits with the hyperscaler, while solution support stays with the partner. Reports arrive pre-filtered. My decision framework is a deal P&L. First: TCV and the applicable fee rate (3.5 percent CPPO, 3 percent Microsoft standard, 0.5 percent AWS ProServ, or 20 percent Server). Second: delivery costs and onboarding. Third: payout lag and FX exposure under the USD tiered model. Fourth: win probability with and without the marketplace. A lost deal delivers zero euro margin. When commit pressure meets remaining cap headroom, the marketplace is often the simplest procurement route. Alternatives include CSP, separate software orders alongside the infrastructure commit, renegotiating the credit, or shifting phases into the next fiscal year. Fifth: do I need full control over invoicing and customer data? Then I stay out or use the marketplace only where the customer explicitly requires it.

// carries

Commit with remaining cap headroom and eligibility, private offer, positive contribution margin after fee, delivery and lag, higher win rate that more than offsets the fee, recurring annual contract. AWS ProServ at 0.5 percent listing fee eases the calculation.

// open

Cap exhausted or not eligible, thin resale margin after wholesale and fee, one-off micro project, server listings at 20 percent fee, need for full billing and data control, mid-market customer without commit or co-sell leverage. Direct contract or CSP often calculates more cleanly here.

Procurement speed and available cap headroom frequently outweigh pure percentage math. Conversely, 3.5 percent plus a thin uplift can destroy the margin if wholesale, fee and delivery costs are not recorded accurately. You calculate contribution margin deal by deal.

Frequently Asked Questions

What is a Cloud Marketplace?

A Cloud Marketplace is the digital sales and billing channel of a hyperscaler (AWS Marketplace, Microsoft Marketplace, Google Cloud Marketplace) through which partners sell software and services to cloud customers. The customer pays via their cloud invoice. Payout and margin depend on the model: for ISV listings, typically gross revenue minus the platform fee; in the channel, often an uplift via wholesale.

What is a Private Offer in the Marketplace?

A Private Offer is a custom-negotiated offer made to a specific customer, with its own price, term, and often its own payment schedule. It is the standard route for enterprise deals. The public listing primarily serves as an entry point and for visibility.

Do Marketplace purchases count toward a customer’s cloud commitment?

Not automatically and not without limits. With Microsoft MACC, eligible purchases count at 100 percent of the net amount before tax, provided the purchase path and badge are correct. With AWS EDP/PPA and Google, crediting, cap, and eligibility depend on the customer contract. Crediting is typically capped per contract, often in the range of one-fifth to one-quarter of the commitment. Before pitching, clarify: cap, eligible SKUs, purchase path, and crediting period.

What are the current Marketplace fees?

In the reseller path, typically 3 percent at Microsoft (Store Service Fee, flat) and 3.5 percent at AWS-CPPO under the lowest Private Offer tier. Below that, large deals and renewals (AWS) or qualified Microsoft Customer Renewals after Self-Attestation (1.5 percent). AWS Professional Services Private Offers: 0.5 percent. Server listings at AWS: 20 percent. ISV Private Offers without channel uplift are tiered at AWS and Google by US-dollar TCV between 1.5 and 3 percent.

When should a partner choose a direct contract?

When cap and eligibility do not apply, the margin after fees, delivery, and lag is unattractive, the deal is one-off and small, or full control over billing and customer data is required. In these cases, a direct contract, CSP, or separate order often remains the cleaner choice.