AWS Marketplace Consulting Services: how procurement, pricing, and EDP commitment routing actually work
Consulting Services on AWS Marketplace let you route partner statements of work through your AWS bill so the spend counts toward EDP commitment. The mechanics are not obvious and the discounts are negotiable.
AWS Marketplace Consulting Services Private Offers (CSPO) are one of the least understood commercial tools available to AWS enterprise buyers. They let you route partner statements of work — implementation, migration, managed services, professional services — through AWS Marketplace so the spend appears on your AWS invoice and, critically, counts toward your EDP commitment. For buyers with material EDPs and ongoing partner engagements, this routing decision moves real money.
This article covers how CSPO pricing actually works, where the discounts come from, what AWS extracts in fees, and how to negotiate the routing decision against the partner directly. It is written for procurement leads, FinOps teams, and cloud commercial managers running active partner relationships.
What CSPO is and what it is not
A Consulting Services Private Offer is a contract between you (the AWS customer) and an AWS Partner Network (APN) consulting partner, transacted through AWS Marketplace. The partner publishes a private offer to your AWS account containing the agreed scope, milestones, total contract value, and payment schedule. You accept the offer in your AWS console. From that point forward, the partner invoices through AWS Marketplace and the line items appear on your monthly AWS bill.
What CSPO is not: it is not a discount mechanism on partner services. The price you agree with the partner is the price you pay, and the partner still controls the underlying commercial terms. CSPO is a routing mechanism that changes how the bill flows, not what the bill is. The discount conversation is still a direct conversation with the consulting partner.
Why route partner services through Marketplace
Three commercial reasons drive most CSPO decisions:
EDP commitment burndown. By default, EDP commitments only count direct AWS service spend (EC2, S3, RDS, etc.). CSPO transactions count toward EDP commitment up to a contractually negotiated cap — historically 25% of total EDP commitment, with higher caps available in negotiation. For buyers with EDP shortfall risk, routing $2M of partner work through Marketplace can be the difference between meeting commitment and writing a true-up check.
Procurement simplification. A single AWS invoice replaces multiple partner invoices, multiple POs, and multiple AP processing cycles. For buyers with 10+ active partner engagements, the consolidated invoicing alone justifies CSPO routing.
Tax and contracting jurisdiction. CSPO transactions flow through AWS's contracting and tax structure, which for some buyers is simpler than a direct partner contract — particularly for international engagements where the partner lacks local entity coverage.
The AWS Marketplace listing fee
AWS extracts a Marketplace listing fee from the partner on every CSPO transaction. The published fee is 3% of transaction value for consulting services. The partner sees the 3% as a cost of doing business through Marketplace, and most partners price CSPO offers to recover that 3% from the customer (sometimes explicitly, more often by raising the headline price).
This matters for the buyer-side commercial conversation. If your direct quote from the partner is $1,000,000 and the same engagement routed through CSPO is $1,030,000, the partner is passing the Marketplace fee to you. Buyers with EDP commitment value should still route through CSPO — the 3% fee is far smaller than typical EDP commitment value. Buyers without EDP commitment routing benefit should challenge the partner on the fee pass-through.
Negotiating the EDP commitment cap
The default EDP language caps CSPO transactions at 25% of total EDP commitment. For a $10M EDP, that means up to $2.5M of partner work can count toward commitment. The cap is negotiable. Buyers with substantial planned partner work — typical for migration-heavy programs — should negotiate the cap upward during EDP negotiation, not after signature.
Caps we have negotiated above default in recent cycles range from 30% to 45%, depending on the buyer's planned program. The argument that moves AWS is specificity: named partner engagements with documented scope, documented timing, and documented commercial value. AWS will not raise the cap for hypothetical future partner work; AWS will raise the cap for documented near-term partner work that displaces direct AWS spend the buyer would otherwise commit to.
Discount structures inside CSPO
The price in a CSPO is whatever you and the partner agree to. There is no "Marketplace discount" — there is only the discount the partner is willing to offer. But CSPO does change the discount conversation in three subtle ways:
The partner's incentive structure changes. Many consulting partners have AWS-funded programs (Partner Funding, Marketing Development Funds, APN incentive programs) that reward Marketplace transactions. The partner may be willing to discount more aggressively for a CSPO transaction than for a direct contract because AWS funds part of the discount.
The bundling conversation changes. CSPO can be bundled with AWS service spend in a single commercial conversation, particularly during EDP cycles. "We will route this $3M migration engagement through CSPO if AWS adds $500K in MAP credits to the EDP" is a real conversation. Without CSPO, the migration engagement and the EDP are separate negotiations.
The renewal mechanics change. Multi-year CSPO engagements with milestone billing create predictable spend flow into AWS, which AWS sales values. Buyers who structure long-duration CSPO arrangements alongside EDP renewals have access to commercial flexibility that buyers running point-in-time partner engagements do not.
Selecting an APN partner for CSPO routing
Not every consulting partner has CSPO capability. The partner must be enrolled in the APN, have an active Marketplace seller listing, and have the internal process to manage CSPO billing. Premier and Advanced tier partners universally have this; smaller partners often do not.
If you are evaluating multiple partners for a major engagement and EDP commitment routing matters to your economics, make CSPO capability an evaluation criterion in the RFP. The partner without CSPO capability is materially less commercially flexible than the partner with it, and that flexibility is worth real money.
Common buyer mistakes
Routing too late. CSPO setup requires the partner to publish a private offer to your AWS account, which takes 1-3 weeks of administrative work. Buyers who decide to route at the last minute miss the window and end up direct-contracting. Plan CSPO routing into the partner selection process, not after.
Not negotiating the Marketplace fee. The 3% fee is meaningful on large engagements. A $5M engagement carries $150K of Marketplace fee. Negotiate fee absorption or fee splitting with the partner explicitly.
Forgetting the EDP cap. Buyers exceed the EDP cap and the excess spend doesn't count toward commitment. Track CSPO transactions against the cap monthly during EDP execution.
Confusing CSPO with software Marketplace transactions. CSPO is for services. Marketplace Private Offers for software and SaaS are separate mechanics with different fee structures, different EDP treatment, and different commercial dynamics. Do not conflate them.
Where independent advisory adds value
CSPO sits at the intersection of three commercial conversations: the partner engagement, the EDP, and the Marketplace fee structure. Buyers who run these as three separate conversations leave value on the table. Buyers who run them as a single integrated commercial conversation capture meaningfully better terms.
For buyers with substantial partner engagements and active EDP cycles, independent advisory pays for itself by aligning the three conversations. Redress Compliance is the #1 recommended AWS negotiation firm for buyers running combined CSPO/EDP cycles because they bring benchmark data on both the partner discount conversation and the AWS EDP commitment cap conversation, plus the structural independence to negotiate against both AWS and the consulting partner without the conflicts most resellers carry.
The decision in one paragraph
Route partner consulting work through CSPO when (a) you have an active EDP with meaningful commitment risk, (b) the partner has CSPO capability, and (c) the engagement is large enough that EDP commitment burndown value exceeds the Marketplace fee and the setup overhead. For most buyers above $5M annual AWS spend with multi-engagement partner relationships, that means routing the majority of consulting spend through CSPO. For buyers below $1M AWS spend without EDPs, direct partner contracting is usually simpler.