Selling on AWS Marketplace takes a registered seller account with tax and banking set up, a listed product with a pricing model buyers can transact, and a motion for private offers, channel resell and co-sell. The listing is the storefront; the private offers, resell and co-sell are what turn it into revenue.
Ask an ISV founder why they’re finally listing on AWS Marketplace and the answer is rarely “distribution.” It’s the buyer’s budget. Enterprise AWS customers sign multi-year committed-spend agreements — Enterprise Discount Programs — and software bought through AWS Marketplace draws down that same commitment. For a buyer with millions already committed to AWS, buying your product on the marketplace is close to free money they’ve already budgeted.
That single fact reorders the sale. Procurement moves faster because the paperwork, security review and payment rails already exist. Deals that stalled for a quarter in vendor onboarding close in a matter of days on a private offer. And the AWS field team has a reason to help you, because marketplace revenue counts toward the numbers they’re measured on.
None of it happens automatically. A listing is table stakes; the revenue lives in the transactional layer most guides skip. Here’s the complete picture, from registration to payout.
What is AWS Marketplace and why sell on it?
AWS Marketplace is a curated digital catalog where AWS customers discover, buy and deploy software, data and professional services, billed through their existing AWS account. For sellers, it’s a transaction channel — not just a directory — that plugs your product into the procurement and billing infrastructure AWS customers already use.
Three things make it worth the listing effort. First, committed spend: purchases count against a buyer’s Enterprise Discount Program, so budget that’s already allocated to AWS can be spent on you — see how AWS EDP committed spend works for why this shortens deals. Second, procurement speed: legal terms, security posture and payment already sit inside the AWS relationship, collapsing the vendor-onboarding cycle. Third, co-sell pull: marketplace revenue is a metric AWS sellers care about, which turns their field team into an ally rather than a bystander.
The catch is that all three benefits require a transactable listing plus the machinery around it. That machinery is the rest of this guide.
Who can sell, and how does seller registration work?
Any company can become an AWS Marketplace seller by completing seller registration in the AWS Marketplace Management Portal: a public seller profile, tax information, and — to receive payouts — banking details, plus acceptance of the seller terms. There’s no gatekeeping on who lists; the gating is on getting your account payout-ready before your first transaction settles.
Two distinctions matter early. A seller lists and sells its own products directly to buyers. A reseller (channel partner) transacts a software vendor’s product on the buyer’s behalf through a Channel Partner Private Offer — a separate motion covered below. You can be both.
Set up tax and banking on day one, not the week a deal is ready to close. Registration also determines your legal seller of record and how disbursements reach you, and both are painful to change mid-deal. If you sell into public sector or specific regions, confirm the tax and entity requirements before you list, because those are the details that hold up a first payout.
What product and listing types can you sell?
AWS Marketplace supports several listing types, and the right one is dictated by how your product is delivered and metered — not by preference. SaaS is the most common path for modern ISVs, but AMI, container and professional-services listings each exist for a reason.
| Listing type | Best for | How buyers consume it |
|---|---|---|
| SaaS contract | Multi-tenant SaaS sold on a term commitment | Buyer subscribes for a fixed term at an agreed price |
| SaaS subscription (metered) | Usage-based SaaS | Buyer pays for what they consume, metered by you |
| AMI / server | Software deployed into the buyer’s own AWS account | Buyer launches a machine image; billed hourly or annually |
| Container | Kubernetes and container-based products | Buyer pulls approved container images |
| Professional services | Implementation, training, managed services | Buyer purchases a scoped engagement |
| Machine learning / data | ML models and data products | Buyer subscribes via the relevant AWS catalog |
Most SaaS ISVs list a SaaS contract, a metered subscription, or both, and integrate their application with AWS so entitlements and usage report back correctly. Services firms and partners increasingly attach a services listing to a software deal — the mechanics of selling professional services on AWS Marketplace differ enough to plan separately.
What pricing models are available?
AWS Marketplace lets you price the way you already sell: fixed-term contracts, usage-based metering, subscriptions, or contracts with additional usage on top. The pricing model you pick should mirror your real commercial motion, because it determines what a buyer can actually transact and what a private offer can override later.
Fixed-term contract pricing suits committed annual or multi-year deals with a known price. Usage-based pricing (metered) suits products where consumption varies and you meter it — seats, API calls, compute, whatever your unit is. Subscription pricing covers recurring flat-rate access. A contract with consumption blends the two: a committed baseline plus metered overage.
The public price on your listing is a starting point, not a ceiling or a floor. Nearly every enterprise deal closes on a private offer at negotiated terms — custom price, custom duration, custom payment schedule — layered on top of the listed pricing model. Get the underlying model right first; the negotiation happens in the offer.
What are the fees, and how do payouts work?
AWS charges a listing fee — a percentage of each transaction it processes — and disburses the remainder to you on a schedule tied to when the buyer pays. The headline number to know is directional, not exact: AWS has reduced its marketplace listing fee over time, and it’s lower for private offers than for public transactions, which is one more reason enterprise deals route through offers.
Payouts follow buyer payment terms, not deal-close dates. When a buyer accepts an annual private offer, you don’t receive a year’s revenue at once; AWS disburses as the buyer pays under the agreed schedule, net of the listing fee. For metered products, usage accrues and disburses in cycles. The practical consequence for finance is that marketplace revenue recognition and cash timing depend on offer structure — a multi-year deal paid annually disburses very differently from one paid upfront.
Because the mechanics are qualitative here and change over time, treat the current fee and disbursement terms as something to confirm in the AWS Marketplace Management Portal at deal time. What’s stable is the shape: a percentage fee, then scheduled disbursement following buyer payment.
How do private offers work?
A private offer is a custom, non-public deal extended to a specific buyer — negotiated price, term, payment schedule and custom EULA — that the buyer accepts to transact. Private offers are where the real money moves on AWS Marketplace, because enterprise buyers rarely purchase at public list price.
There are a few flavors. A standard private offer is the negotiated one-to-one deal a seller builds and sends. An express private offer lets a buyer self-serve an AWS-generated offer from pricing rules you set up in advance — automating the routine, in-policy SaaS deals (see express private offers, explained). The Private Offer API does the reverse for scale, letting you create offers programmatically. A multi-party offer brings a channel partner into the transaction so a reseller can participate in the deal (the CPPO motion below). Each is a variation on the same core idea: move the deal off the public listing and onto agreed terms.
The operational challenge isn’t creating one offer — it’s creating them at volume without errors, tracking which are pending acceptance, and reconciling accepted offers back to your CRM and finance. Managing AWS Marketplace private offers as a repeatable, tracked process is what separates a team closing a handful of marketplace deals from one running marketplace as a primary channel.
How does channel resell with CPPO work?
Channel resell on AWS Marketplace runs through the Channel Partner Private Offer (CPPO): the software vendor authorizes a reseller, sets the wholesale terms, and the reseller extends a marketplace offer to the end customer. The buyer transacts with their preferred partner, on their AWS bill, while the vendor still records a marketplace transaction.
CPPO exists because many enterprises buy software through an incumbent reseller or systems integrator, not direct. Without it, a partner-led deal would fall outside the marketplace and forfeit the committed-spend and procurement benefits above. With it, the reseller’s margin, the vendor’s net, and the buyer’s drawdown all resolve inside one AWS transaction.
For sellers, the discipline is authorizing partners cleanly, setting resale terms once, and tracking which CPPO offers are outstanding — the same reconciliation problem as direct private offers, with a partner added to the record. Multi-party offers are the mechanism that makes the whole thing transact.
How does co-sell and AWS ACE fit in?
Co-sell is the motion where you and AWS work an opportunity together, and the AWS Partner Central / ACE (APN Customer Engagements) pipeline is where that collaboration is registered and tracked. Marketplace and co-sell reinforce each other: a co-sold opportunity that closes as a marketplace private offer gives the AWS field team the revenue credit that motivates them to help.
The loop works like this. You register an opportunity in ACE, share it with AWS, and the field team engages. When the deal is ready, it closes as a private offer on AWS Marketplace, and the marketplace transaction ties back to the co-sell record. Sellers who skip the ACE registration get the marketplace transaction but none of the field alignment — the pull that makes AWS reps bring you into their accounts.
Running this well means keeping ACE opportunities, marketplace offers and your CRM in sync so nothing is registered twice or lost between systems. Our full walkthrough of co-selling through AWS ACE covers the pipeline stages and how they map to marketplace deals.
How do you get listed faster?
The fastest path to a transactable listing is to prepare the account-level requirements before you touch the listing itself, then use tooling that automates the metering, offer creation and reconciliation you’d otherwise build by hand. Most delay isn’t the listing form — it’s the seller registration, tax and banking, and the application integration that reports entitlements and usage.
Do these in parallel: complete seller registration with tax and banking; decide your listing and pricing model against how you actually sell; and stand up the metering/entitlement integration your product needs. Teams that sequence these end to end lose weeks; teams that run them concurrently compress the timeline substantially.
A platform layer removes most of the remaining friction. Suger for AWS Marketplace handles listing setup, private-offer and CPPO creation, metering, and reconciliation back to your CRM and billing — across all major clouds, not just AWS — so a first deal closes on infrastructure you didn’t have to build.
Frequently asked questions
What does it cost to sell on AWS Marketplace? AWS charges a listing fee as a percentage of each transaction it processes, then disburses the rest to you. The fee is lower on private offers than public sales, and AWS has reduced it over time. Seller registration itself has no upfront fee.
How long does it take to list on AWS Marketplace? It depends mostly on your product integration and how ready your account is. The listing form is quick; seller registration, tax and banking setup, and application metering are what set the timeline. Preparing them in parallel compresses it significantly.
What is the difference between a public price and a private offer? The public price is the listed rate any buyer can transact. A private offer is a custom deal — negotiated price, term, payment schedule and EULA — extended to a specific buyer. Nearly all enterprise deals close as private offers, not at public price.
What is a CPPO on AWS Marketplace? A Channel Partner Private Offer lets a reseller transact a software vendor’s product on a buyer’s behalf. The vendor sets wholesale terms, authorizes the partner, and the partner extends the marketplace offer to the end customer, all inside one AWS transaction.
Do I need AWS co-sell to sell on the marketplace? No. You can transact on AWS Marketplace without co-sell. But registering opportunities in ACE aligns the AWS field team, who are motivated by marketplace revenue. Skipping co-sell means you keep the transaction but lose the field pull that fills your pipeline.
When do I get paid for a marketplace deal? AWS disburses as the buyer pays under the agreed terms, net of the listing fee — not all at once on close. A multi-year offer paid annually disburses annually; metered usage disburses in cycles. Offer structure drives your cash timing.
Takeaways
- The listing is table stakes; the revenue lives in private offers, CPPO resell and co-sell. Plan the transactional layer, not just the storefront.
- Buyers come for committed spend and faster procurement — marketplace purchases draw down existing AWS budget and skip vendor onboarding.
- Complete seller registration, tax and banking before your first deal is ready; those details, not the listing form, are what delay payouts.
- Pick the listing and pricing model that mirror how you actually sell, then negotiate real deals on private offers layered on top.
- Register co-sell opportunities in ACE so marketplace revenue gives the AWS field team a reason to bring you into their accounts.
Suger runs AWS Marketplace listings, private offers, CPPO resell and co-sell reconciliation on one platform — the same infrastructure that manages your other cloud marketplaces. See how it works on the Suger for AWS Marketplace page.
Stay Updated
Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.