AWS Marketplace has transformed how enterprises procure third-party software — but most buyers dramatically underutilise the negotiation opportunities it creates. The AWS Marketplace private offer mechanism allows ISVs to create custom, negotiated pricing for individual customers that differs from the public Marketplace listing.
This guide is part of our AWS enterprise negotiation series. Understanding private offers is essential for any enterprise buying software through Marketplace — and increasingly, for using Marketplace spend to optimise your overall AWS EDP commitment.
For broader context on enterprise software negotiation, see our cloud enterprise discount negotiation guide and our software contract negotiation checklist.
AWS Marketplace private offers can deliver 20–40% discounts below public listing prices for enterprise buyers. Combined with EDP spend applicability and streamlined procurement, Marketplace is often a better purchasing channel than direct ISV contracts — when negotiated properly.
What Are AWS Marketplace Private Offers?
A private offer is a custom pricing arrangement created by an ISV (Independent Software Vendor) specifically for your organisation on AWS Marketplace. It differs from the public listing in:
- Price — custom discounts, volume tiers, or flat pricing
- Contract duration — custom term lengths (not limited to standard 1/2/3 year options)
- Payment terms — custom invoicing schedules, milestone payments
- Entitlements — custom usage limits, seats, API calls, or other metered dimensions
- Service levels — custom SLAs beyond the standard Marketplace terms
Private offers are only visible to the specific AWS account they are targeted at — other customers cannot see your custom pricing. Once accepted, they are fulfilled through the standard Marketplace billing mechanism: charges appear on your AWS bill and count toward your EDP commitment (subject to agreement with AWS).
Standard Offers vs Private Offers vs Reseller Private Offers
| Offer Type | Pricing | Who Creates It | EDP Eligible? | Best For |
|---|---|---|---|---|
| Standard Public Offer | List price | ISV | Yes (if in scope) | Small buyers, quick procurement |
| Private Offer (direct) | Negotiated | ISV for buyer | Yes (if in scope) | Enterprise buyers, volume pricing |
| Reseller Private Offer (CPPO) | Negotiated | AWS Channel Partner | Depends | Existing partner relationships |
The EDP Spend Credit Mechanism
One of the most strategically valuable aspects of Marketplace private offers is the ability to have ISV software spend count toward your AWS EDP commitment — and potentially receive your EDP programme discount on ISV charges.
How it works
Standard Marketplace purchases are processed as AWS charges and do appear on your AWS bill. However, their eligibility for EDP discount and their counting toward your EDP commitment minimum varies:
| Scenario | Counts toward EDP minimum? | Receives EDP discount? | Requires |
|---|---|---|---|
| Standard public listing purchase | Sometimes (ISV-dependent) | Generally No | Check EDP terms |
| Private offer via ISV Accelerate partner | Yes (typically) | Negotiable — sometimes yes | ISV must be in AWS ISV Accelerate programme |
| Private offer — non-Accelerate ISV | May count as AWS consumption | Generally No | Explicit EDP amendment |
| Committed-use Marketplace contract | Yes if structured correctly | Negotiable | Upfront contract via Marketplace |
The key negotiation point: during your EDP negotiation, explicitly request that AWS Marketplace charges from ISV Accelerate programme partners count toward your EDP committed spend. AWS increasingly accepts this, particularly for large enterprise buyers, because it helps both parties use the Marketplace as a strategic procurement channel.
This mechanism can materially reduce your EDP shortfall risk. If you have $2M in annual software spend moving to Marketplace, and it counts toward a $10M EDP commitment, your risk of under-commitment drops significantly.
Negotiating the ISV Private Offer
Private offer negotiation involves two separate negotiations: (1) the pricing discussion with the ISV, and (2) the Marketplace mechanics discussion with AWS. Most buyers focus only on the first and miss significant value from the second.
Negotiating with the ISV
Private offer negotiations with ISVs follow the same dynamics as direct software contract negotiations — see our Salesforce contract negotiation guide and software contract red flags guide for the detailed principles. The Marketplace-specific considerations are:
Marketplace fee impact: AWS charges ISVs a transaction fee (typically 3–15% of contract value, depending on the ISV's status and contract type) for Marketplace sales. ISVs may try to recover this fee by increasing their Marketplace price compared to their direct sales price. Counter this by: researching public listing prices, benchmarking against other customers, and explicitly requesting pricing that matches or beats their direct-channel pricing net of Marketplace fees.
Multi-year committed-use contracts: AWS Marketplace supports multi-year committed-use contracts where the buyer commits to consuming a defined quantity of software entitlements over 1–3 years. ISVs typically offer meaningful discounts for these commitments — 20–35% below standard pricing — because the contract value appears on their revenue immediately and they bear no collection risk.
Custom dimensions: Many SaaS products on Marketplace use metered dimensions (API calls, users, data volume). Private offers can use custom dimensions that better match your actual consumption pattern — e.g., tiered pricing above a base minimum, or bundled dimensions that reduce effective per-unit cost.
Key Contract Terms in Marketplace Private Offers
Marketplace private offers have their own contract structure. Ensure these terms are explicitly addressed:
| Term | What to Negotiate | AWS Marketplace Default |
|---|---|---|
| Auto-renewal | Opt-out or fixed-term only | Often auto-renews at list price |
| Price escalation | Cap at CPI or 3–5% annually | ISV can change on renewal |
| Overage pricing | Fixed overage rates; grace period | Typically list-price overages |
| Data portability | Export rights; format; timeline | ISV EULA terms apply |
| Support level | SLA credits against Marketplace charges | Basic support unless negotiated |
| Cancellation rights | Termination for convenience; wind-down | Generally limited mid-term |
Marketplace vs Direct Contract: The Strategic Decision
For each major ISV, decide deliberately whether to transact through Marketplace or direct contract. The decision matrix:
| Factor | Favours Marketplace | Favours Direct Contract |
|---|---|---|
| Procurement speed | Marketplace is faster (no PO cycle) | Direct may be required for complex terms |
| EDP spend credit | Marketplace counts toward EDP (negotiable) | Direct contracts don't count |
| Contract flexibility | Standard Marketplace EULA | Fully negotiable terms |
| Consolidated billing | Yes — single AWS invoice | Separate ISV invoice management |
| Audit and compliance | AWS handles billing records | Direct contract audit rights easier |
| Negotiation leverage | ISV wants Marketplace revenue | May have more flexibility outside Marketplace |
The emerging best practice for enterprises: use Marketplace as the default transaction channel for cloud-native software, while maintaining direct contracts for on-premises or hybrid deployments where complex licensing terms are required. For strategic SaaS platforms (Salesforce, ServiceNow, Workday), direct contracts still typically offer better negotiation outcomes — see our Salesforce renewal tactics for the reason why.
8 Proven AWS Marketplace Negotiation Tactics
The public listing price on AWS Marketplace is the ISV's walk-in rate for small buyers. Enterprise buyers should never pay list. Request a private offer as a baseline expectation, citing your annual spend commitment, multi-year potential, and the value of Marketplace transaction volume to the ISV's AWS partnership status.
Request the ISV's direct sales pricing for an equivalent commitment. If their direct price is lower than Marketplace (common due to Marketplace transaction fees), use this to negotiate a Marketplace private offer that matches direct pricing. ISVs often value the Marketplace channel for its lower sales cost and faster procurement cycle — they will often match or beat direct pricing to secure Marketplace transactions.
AWS Marketplace supports committed-use contracts where you pre-commit to a spend level or entitlement quantity. ISVs offer their best pricing for these — typically 25–40% below standard annual pricing — because the committed revenue improves their planning and reduces collection risk. Structure commitments carefully with ramp provisions to manage over-commitment risk.
Before finalising any large ISV Marketplace commitment, negotiate with your AWS account team whether the spend counts toward your EDP minimum commitment and whether you receive your EDP programme discount on the charges. This negotiation is with AWS, not the ISV — and it can transform the economics of Marketplace procurement entirely.
Many Marketplace private offers auto-renew at public list prices if you do not take action before the renewal date. This is a significant trap — you can lose your negotiated pricing without realising it. Always negotiate either: (a) an explicit opt-in renewal requirement; or (b) a commitment that renewal pricing will not exceed a capped increase over private offer pricing.
If you already work with an AWS Channel Partner, explore whether they can create a Channel Partner Private Offer (CPPO) on your behalf. Partners often have preferential ISV pricing and can pass through additional discounts. The trade-off is an additional intermediary — evaluate whether the pricing improvement justifies the added complexity.
If your organisation purchases multiple products from the same ISV (common with platform vendors like Datadog, HashiCorp, MongoDB), negotiate all products together in a single private offer discussion. Bundled volume typically unlocks an additional 5–15% over per-product negotiation, and simplifies your procurement and renewal management.
When evaluating new software categories, list Marketplace procurement as a requirement in your RFP. ISVs that are not on Marketplace (or have limited Marketplace presence) are at a disadvantage. This creates competitive pressure that benefits both your negotiation position and your eventual procurement efficiency.
Common Marketplace Procurement Mistakes
Accepting the EULA without legal review
AWS Marketplace purchases typically require acceptance of the ISV's standard EULA. These EULAs often contain unfavourable terms around data rights, liability limits, and audit provisions. For significant software spend, always perform legal review before accepting a Marketplace EULA, and negotiate custom terms through the private offer mechanism where needed. See our software contract red flags guide for the top terms to challenge.
Treating Marketplace as procurement-only
Many procurement teams use Marketplace for its billing convenience but negotiate the actual ISV contract direct. If you negotiate direct but transact through Marketplace, you typically lose the ability to have Marketplace spend count toward EDP — because the Marketplace transaction is structured as a passthrough, not as the primary commercial agreement.
Not tracking Marketplace commitments in your renewal calendar
Marketplace private offers have renewal dates that are separate from your main AWS billing cycle. Add all Marketplace committed-use contracts to your software renewal management calendar with 6-month advance notice for renegotiation. See our vendor contract management calendar guide for the framework.
Negotiate Your AWS Marketplace Strategy
Our ranked AWS negotiation advisors help enterprises optimise Marketplace procurement alongside EDP strategy — with gain-share options available.