What a Private Offer Actually Is
An AWS Marketplace private offer is a negotiated, non-public transaction between an enterprise buyer and an independent software vendor (ISV), transacted through AWS Marketplace rather than on the vendor's paper. The buyer and ISV agree pricing, term, payment schedule, and the end-user licence agreement directly; the ISV then issues a private offer to the specific AWS account IDs the buyer nominates. AWS handles billing and the charge lands on the buyer's consolidated AWS invoice.
The headline discount in a private offer is whatever you negotiate — Marketplace imposes no ceiling, so a well-run private offer matches the discount you would secure buying direct. The reason to route the deal through Marketplace is not the discount itself; it is what the transaction does to your AWS commitment and your invoice. For the wider commercial picture, our AWS enterprise agreement negotiation guide sets out how Marketplace fits alongside your core EDP.
Commitment Drawdown: The 25% Cap
The single biggest reason enterprises use private offers is commitment drawdown. Eligible Marketplace spend retires your Enterprise Discount Program (EDP) or Private Pricing Agreement (PPA) commitment — meaning you can use software budget you were already spending to satisfy a cloud commitment you have already made, rather than asking finance for new money. When a private offer is accepted, the full transaction value counts toward your drawdown, whether it is billed upfront, annually, or by usage.
The constraint is the cap: AWS generally limits Marketplace spend to 25% of your total committed amount, and professional-services line items are normally excluded from the eligible figure. On a $20M three-year EDP, that is up to $5M of third-party software you can run through Marketplace to retire commitment. If your software stack leans heavily on AWS-native ISVs, the 25% ceiling itself becomes a negotiation point — buyers with a documented case have moved it toward 30–35% through their AWS account team. Understanding how this interacts with your headline discount is the heart of the EDP vs Private Pricing Agreement decision.
Model the cap before you sign anything. An enterprise that fills its 25% Marketplace allowance early in year one can find itself unable to retire commitment on a strategic SaaS renewal in year three — and forced to either buy direct or true-up in cash.
The May 2025 Deployed-on-AWS Rule
The rules tightened materially on 1 May 2025. From that date, only SaaS products hosted entirely on AWS qualify for commitment retirement. If any part of a vendor's product runs outside AWS — on Azure, GCP, or the vendor's own data centres — that spend no longer draws down your AWS commitment. Eligible products now carry a "Deployed on AWS" badge in the Marketplace listing.
The trap is in the timing mechanism: eligibility is assessed by invoice date, not signature date. An invoice dated on or after 1 May 2025 for a non-qualifying product will not retire commitment even if the private offer was negotiated and accepted months earlier. Several enterprises discovered mid-term that a multi-year private offer they had treated as commitment-eligible stopped counting — leaving a drawdown gap they had not budgeted for. Before you rely on a private offer to hit your commitment, confirm the specific product carries the Deployed-on-AWS badge and write that eligibility into your internal business case.
The Buyer-Side Negotiation Levers
Because the ISV pays a Marketplace listing fee to AWS, there is margin in the transaction that buyers can target. The fee is tiered and falls as deal size rises — roughly 3% on deals under $1M, 2% from $1M to $10M, and 1.5% above $10M. On a large multi-year deal, that declining fee is real money the ISV keeps, and a prepared buyer can argue for a share of it in the net price.
| Lever | What to ask for | Typical buyer gain |
|---|---|---|
| Payment cadence | Annual or milestone billing instead of full upfront | Protects cash; spreads drawdown across commitment years |
| Multi-year price lock | Fixed unit price for the full term, capped uplift on renewal | 5–15% vs annual repricing |
| Listing-fee share | Net price reflecting the lower 1.5–2% fee on larger deals | 1–3% of contract value |
| Flexible start date | Align offer start to your EDP year boundary | Avoids stranded drawdown |
| EULA substitution | Standardised Marketplace contract or your own paper | Faster legal sign-off, fewer bespoke terms |
These levers compound with the structures covered in our multi-year cloud discount structures guide, which sits above this article as the pillar for AWS, Azure, and Google Cloud commitment design. Pairing a private offer with the right commitment term is where the largest savings sit.
Terms to Lock Before You Accept
A private offer is accepted with a click in the AWS console, and acceptance is binding — there is no cooling-off period. Before anyone in your organisation accepts, confirm four things in writing with the ISV. First, the renewal mechanism: a private offer does not auto-renew at the negotiated rate, so agree how the follow-on offer is priced. Second, account scope: the offer is bound to specific AWS account IDs, so confirm it covers every account that will consume the product. Third, commitment eligibility: written confirmation the product is Deployed-on-AWS and counts toward your drawdown. Fourth, termination and credit: what happens to unused entitlement if you exit early. The AWS team and the ISV manage these conversations separately, and gaps between the two are where buyers get caught.
The Common Mistakes
The most expensive error is treating Marketplace as automatically cheaper than direct. It is not — the discount is identical to what you negotiate, and the only structural advantages are drawdown and invoice consolidation. If a product is not Deployed-on-AWS, or you have already exhausted your 25% allowance, buying direct may net out better. The second mistake is letting the ISV drive the private offer creation before pricing is settled; the offer should be the last step, not the negotiation itself. The third is ignoring the AWS account team, who can adjust the Marketplace cap and confirm eligibility but will not volunteer either. If you want an independent read on whether a private offer or a direct deal serves you better, request a confidential briefing — and review the AWS commercial landscape on our AWS vendor intelligence hub and in the AWS EDP Negotiation Playbook.