The EDP Marketplace Offset Mechanism

The AWS Enterprise Discount Program allows enterprises to count qualified Marketplace purchases toward their annual commit draw-down. Specifically, up to 25% of your annual EDP commitment can be retired through AWS Marketplace transactions. This mechanism serves two strategic purposes simultaneously: it consolidates SaaS procurement onto a single AWS invoice, and it accelerates commit draw-down for organisations that might otherwise face shortfall risk.

The commercial logic is straightforward. AWS earns a percentage of every Marketplace transaction — typically 3–5% for SaaS products. By allowing Marketplace spend to count against EDP commits, AWS incentivises enterprises to route ISV procurement through Marketplace rather than direct vendor channels. For enterprises, the benefit is twofold: EDP commit retirement and simplified procurement through consolidated billing. Our broader AWS EDP negotiation enterprise playbook covers Marketplace offset as one of several commit management tools.

The May 2025 Policy Change: What Changed and Why It Matters

Before May 2025, any SaaS product purchased through AWS Marketplace could count toward EDP commitment retirement, regardless of where the product's underlying infrastructure ran. This allowed enterprises to route software that ran on Azure, GCP, or on-premises infrastructure through Marketplace and have it credited toward their AWS commit.

AWS changed this policy effective May 2025. Under the new rules, only SaaS products fully deployed on AWS infrastructure qualify for EDP commitment retirement. Products running on non-AWS infrastructure, hybrid architectures, or multi-cloud deployments are explicitly excluded. AWS added an eligibility tag in Marketplace to help buyers validate qualifying products before transacting.

The practical impact for enterprises is significant. Many organisations had built their Marketplace procurement strategy around the offset mechanism using software that no longer qualifies. If your organisation has not audited its Marketplace portfolio against the new eligibility rules since May 2025, you are at risk of a shortfall position that your Marketplace procurement will not resolve. This eligibility audit is the first action item from this guide.

"Enterprises that built EDP shortfall coverage around Marketplace spend before May 2025 may be significantly exposed — their offset strategy now qualifies for less than they think."

Which Marketplace Products Qualify After May 2025

The post-2025 eligibility framework requires that the SaaS product's infrastructure run entirely within AWS. The following categories broadly qualify under the new rules:

  • AWS-native SaaS tools: Products built natively on AWS infrastructure, where the ISV uses AWS services as the underlying compute, storage, and database layer. These are identifiable by the AWS hosting tag in Marketplace listings.
  • AWS partner-built applications: ISV products listed as AWS Partner Network Advanced or Premier Tier partners that have verified their AWS infrastructure deployment through AWS's qualification process.
  • AWS managed service add-ons: Professional services and managed configurations sold through Marketplace that are delivered on AWS infrastructure.

Products that typically do not qualify post-2025 include: SaaS tools with multi-cloud deployment models, products that run primarily on the ISV's own data centres and simply distribute through Marketplace, and products that explicitly list Azure or GCP as their infrastructure foundation. AWS's eligibility tag in Marketplace is the definitive reference — always validate before transacting if EDP offset is part of your procurement rationale.

Need to audit your Marketplace portfolio for EDP eligibility?

We map your existing SaaS stack against post-2025 EDP offset qualification rules.
Speak to AWS Procurement Specialists →

Building a Marketplace Procurement Strategy for EDP Offset

A Marketplace procurement strategy designed to maximise EDP offset has three phases: audit, pipeline, and negotiate.

Phase 1: Audit Your Existing SaaS Stack

Map every SaaS tool in your current stack against the post-2025 eligibility criteria. For each tool, determine: is it already procured through Marketplace? If not, does a Marketplace listing exist? Does the listing carry the AWS-hosted eligibility tag? What is the annual contract value? The output of this audit is a prioritised list of SaaS tools that could be transitioned to Marketplace procurement while qualifying for EDP offset.

Phase 2: Build the Eligible Pipeline

From your audit, identify which eligible tools have upcoming renewals in the next 12 months. These represent your highest-priority Marketplace transition opportunities — you can route the renewal through Marketplace without disrupting an existing commitment. Tools with 2+ years remaining on direct vendor contracts require a different approach: evaluate whether early termination and Marketplace re-procurement makes economic sense given the EDP offset benefit.

The 25% offset cap must be modelled explicitly. If your annual EDP commit is $5M, the maximum EDP draw-down from Marketplace is $1.25M annually. Prioritise tools with the highest annual contract value to maximise offset utilisation within the cap. Spreading the Marketplace portfolio across many small tools provides less offset value than concentrating on your largest eligible SaaS contracts. See our full AWS Marketplace procurement strategy guide for detailed pipeline prioritisation methodology.

Phase 3: Negotiate Marketplace Pricing

Transacting through Marketplace does not mean accepting Marketplace list pricing. AWS's Private Offer mechanism allows ISVs to create customised pricing for Marketplace transactions — including the discounts you would have negotiated in a direct procurement. Private Offers are the standard for enterprise Marketplace transactions and should be the default expectation for any significant contract.

In some cases, the Marketplace Private Offer process creates an opportunity to negotiate improved pricing relative to existing direct contracts. AWS Marketplace gives ISVs a closed, simplified transaction environment — some vendors offer Marketplace-specific pricing that is not available through direct procurement channels. Always benchmark the Marketplace Private Offer against your direct vendor rate before transacting.

Marketplace Offset and Shortfall Risk Management

AWS Marketplace spend is one of the fastest mechanisms for closing EDP shortfall gaps, subject to the eligibility constraints described above. Unlike Reserved Instance purchases — which require technical configuration to deploy — Marketplace SaaS transactions are typically commercial decisions that can be executed quickly.

For enterprises tracking against a Q4 shortfall, Marketplace procurement of upcoming SaaS renewals is the fastest legitimate path to closing the gap. The offset applies in the period the transaction occurs, so a Q4 Marketplace purchase directly reduces Q4 EDP shortfall exposure.

However, this tactic has a hard ceiling: the 25% annual cap. If you have already deployed the maximum Marketplace offset through earlier transactions in the year, additional Marketplace purchases will not contribute to shortfall closure. Model your offset utilisation across the full year to ensure Marketplace is available as a Q4 tool when you may need it most. Our AWS EDP shortfall risk management guide covers the full shortfall remediation toolkit, including how Marketplace fits within the broader approach.

AWS Procurement Intelligence — Monthly

Marketplace policy changes, EDP offset strategies, and procurement tactics for enterprise AWS buyers.

Subscribe →

Integrating Marketplace into Your EDP Negotiation

Marketplace procurement volume is commercially valuable to AWS, which creates a negotiation lever most enterprises underuse. If you can credibly commit to routing a defined volume of SaaS procurement through Marketplace as part of your EDP renewal, AWS may offer improved base discount rates in exchange. The logic: AWS earns Marketplace transaction fees on software procurement that would otherwise occur outside their ecosystem.

This exchange — committed Marketplace volume for improved EDP discount rates — is most effective when you can demonstrate genuine pipeline. A list of SaaS contracts due for renewal in the next 12 months, with confirmed Marketplace eligibility and estimated total contract value, is the evidence that makes this lever credible. Without that documentation, the commitment is vague enough that AWS account teams will not translate it into measurable commercial concessions.

Incorporating Marketplace volume commitments into your EDP renewal structure is a differentiated approach that most competitors in your spend tier are not deploying. Combined with the broader renewal strategy in our EDP renewal negotiation guide, it represents meaningful incremental value.

Governance and Tracking

Once Marketplace procurement is established as an EDP management tool, governance becomes critical. Key requirements include: maintaining a real-time register of Marketplace transactions and their offset contribution, tracking the 25% annual cap utilisation, validating eligibility of new tools before procurement decisions are finalised, and aligning Marketplace transaction timing with EDP commit tracking to maximise shortfall protection windows.

Many enterprises lack dedicated governance for Marketplace procurement and discover offset cap utilisation or eligibility issues only when reviewing year-end EDP draw-down. Building Marketplace tracking into your FinOps practice — alongside RI and Savings Plan utilisation — is the appropriate operating model. For practical guidance on optimising commit management tools including RI/SP, see our AWS RI and Savings Plan optimisation guide.

Real-world outcome: In one engagement, a financial services firm faced $890K exposure from Marketplace-dependent EDP shortfall coverage that no longer qualified post-May 2025. Redress restructured their SaaS portfolio, identified $520K in qualifying AWS-native tools, and negotiated improved Marketplace Private Offer pricing that reduced their shortfall exposure to $185K. The engagement fee was $42K — saving the enterprise $305K net against exposure reduction alone.

If you are building or reviewing your Marketplace procurement strategy and want independent benchmarking of your EDP offset utilisation, contact our AWS commercial advisory team for a structured assessment.