AWS Marketplace net payment terms are a private-offer setting that lets the seller choose when an invoice-paying buyer’s payment is due — Net 30, Net 45, Net 60, or Net 90 — instead of leaving it to the buyer’s standard AWS terms. AWS launched the seller-configurable field on August 6, 2026. One term applies to every charge in the offer, the buyer sees it before accepting, and on a channel deal the ISV sets a ceiling the reseller cannot exceed.
Payment terms used to be something the buyer brought to the table. An invoice-paying customer had net terms with AWS, whatever they had negotiated for their account, and every marketplace transaction inherited them — sellers rarely knew the number and never set it. On a deal where days-sales-outstanding mattered, that was a blind spot: you booked the revenue, and when the cash actually cleared was the buyer’s arrangement, not yours.
As of August 6, 2026, the seller can set it. AWS Marketplace now lets you configure Net 30, Net 45, Net 60, or Net 90 as a field on the private offer itself. This is a deal-desk and treasury decision now, not a buyer-side default you find out about after the fact.
Here is what each term controls, exactly what it covers inside an offer, what the buyer sees, and how it behaves on a channel-partner deal.
What are AWS Marketplace net payment terms for private offers?
AWS Marketplace net payment terms are a seller-set field on a private offer that determines when an invoice-paying buyer must pay — Net 30, Net 45, Net 60, or Net 90 from the invoice date. Before this launch, payment timing came from the buyer’s standard AWS payment terms; the seller now chooses it as part of building the offer.
Two boundaries define what the field is and is not. First, it applies to buyers who pay by invoice — a customer paying by credit card is charged on AWS’s normal schedule, and there is nothing to configure. Second, it is a per-offer setting: the term you pick is written into that private offer and travels with it to acceptance, rather than being a standing property of the buyer’s account.
The mechanics of everything else about a private offer — the pricing model, the duration, the flexible payment schedule, the legal terms — are unchanged. This adds one field to the offer that answers a question the seller previously could not: when is the money due after we invoice.
Net 30, 45, 60, 90: what each term covers
Each term sets the number of days from invoice to payment due, and the term you choose applies uniformly to every AWS Marketplace charge in the offer. AWS is explicit that the setting covers “all AWS Marketplace charges within a private offer, including upfront fees, scheduled payments, and usage-based charges.” You are not setting different terms for the upfront and the usage lines — you pick one, and it governs all of them.
That “one term, every charge” rule is the detail a deal desk has to internalize. If an offer has a $120,000 upfront fee, three scheduled payments across the year, and metered overage billed monthly, a Net 60 term means each of those invoices — the upfront, each scheduled payment, and each month’s usage invoice — falls due 60 days after it is issued. There is no mix-and-match within a single offer.
| Term | Payment due (from invoice date) | What it applies to in the offer | Typical use |
|---|---|---|---|
| Net 30 | 30 days | Every charge: upfront, scheduled, and usage | The near-default for buyers who simply need invoice-based billing rather than a card charge |
| Net 45 | 45 days | Every charge: upfront, scheduled, and usage | A middle ground when procurement needs longer than 30 but a quarter is too long |
| Net 60 | 60 days | Every charge: upfront, scheduled, and usage | Common for mid-market and enterprise buyers whose AP cycle runs on 60 |
| Net 90 | 90 days | Every charge: upfront, scheduled, and usage | Large enterprises and public-sector buyers that require a full quarter to pay |
The longer the term, the more of your cash sits as receivable. Net 90 is a concession — it can be the thing that unblocks a procurement team, but it moves the cash roughly two months further out than Net 30 on the same contract value. Treat the term as a negotiable line with a cost, not a checkbox: for the mechanics of how the rest of the offer is assembled around it, see creating private offers without the console.
What the buyer sees, and what happens by default
The buyer sees the configured payment term on the procurement page before they accept the offer — it is disclosed, not silent. AWS states that “buyers see the configured payment terms on the procurement page before accepting a private offer,” so the number you set is part of what the customer reviews and agrees to when they accept. There is no surprise on the first invoice.
Because it is visible pre-acceptance, the term is effectively part of the deal you are proposing. If procurement asked for Net 60 and you configured Net 60, they will see Net 60 and accept against it — the offer is now the paper trail for that commitment, alongside the pricing and duration.
The default matters just as much as the setting. If you do not set a custom term, nothing changes: AWS applies the buyer’s standard AWS payment terms exactly as before. The new field is opt-in per offer, so existing offers and any offer where you leave the term alone behave the way they always have. You reach for this deliberately when a specific deal needs a specific term — not on every offer by reflex.
For a fuller picture of the acceptance experience and where the term appears in it, see what buyers see when you send a private offer.
How the CPPO ceiling works on channel deals
On a Channel Partner Private Offer (CPPO), the ISV sets a maximum payment term and the channel partner can offer terms at or below that ceiling — never longer. AWS describes it directly: “ISVs set maximum payment terms and channel partners can offer terms at or below that ceiling.” The software vendor keeps control of the longest term any reseller can extend to an end customer on its behalf.
This exists because a payment term is a financing decision, and on a channel deal two parties are involved. If an ISV is comfortable financing up to Net 60, it sets Net 60 as the ceiling; a reseller building the end-customer offer can then choose Net 30, Net 45, or Net 60, but the system will not let it grant Net 90. The ISV caps its own receivables exposure without having to police each reseller offer by hand.
For a deal desk, the practical rule is to set the CPPO ceiling as a matter of policy, once, at the term you are willing to underwrite — then let partners work within it. The ceiling is the ISV’s control; the specific term on any given end-customer offer is the partner’s choice beneath it. If you are mapping how these multiparty offers differ in the first place, CPPO vs. multiparty private offers covers the offer structures the ceiling sits on top of.
Comparison: seller-set terms vs. the old buyer-account default
Here is the change stated as a before-and-after, because the shift in who controls the term is the whole point.
| Before (buyer-account terms) | Now (seller-set private-offer terms) | |
|---|---|---|
| Who sets the term | The buyer, via their standing AWS account terms | The seller, as a field on the private offer |
| Where it lives | A property of the buyer’s AWS account | A property of the specific offer |
| Seller visibility | Often unknown to the seller | Chosen by the seller, so known by definition |
| Buyer visibility | The buyer’s own arrangement | Shown on the procurement page before acceptance |
| Granularity | Whatever the account carried | One term across every charge in the offer |
| On a channel deal | The end customer’s account terms | ISV sets a ceiling; the partner offers at or below it |
| If left unset | — | Falls back to the buyer’s standard AWS terms |
The operational consequence is that DSO on a marketplace deal is now partly a seller lever. You can quote a term to match a customer’s AP cycle and know the offer enforces it, or hold the line at Net 30 to keep cash close — a choice you did not previously have. It also means the payment term becomes another attribute your finance systems should capture per transaction, because “when is this due” now has an answer set at offer time rather than one you discover on the invoice.
Frequently asked questions
What payment terms can a seller set on an AWS Marketplace private offer? Net 30, Net 45, Net 60, or Net 90 — the number of days from the invoice date until payment is due. AWS added the seller-configurable field on August 6, 2026. It applies to buyers who pay by invoice; card-paying buyers are billed on AWS’s normal schedule.
Do the net payment terms apply to every charge in the offer? Yes. The term applies uniformly to all AWS Marketplace charges in the private offer — upfront fees, scheduled payments, and usage-based charges alike. You choose one term per offer, and it governs every invoice the offer generates; there is no per-line mix of different terms.
What happens if the seller does not set a payment term? Nothing changes. If no custom payment term is set, the buyer’s standard AWS payment terms continue to apply, exactly as before the feature launched. The field is opt-in per offer, so existing offers and any offer you leave unset behave the way they always have.
Does the buyer see the payment term before accepting? Yes. The buyer sees the configured payment term on the procurement page before accepting the private offer. Because it is disclosed pre-acceptance, the term is part of what the customer reviews and agrees to, so there is no surprise when the first invoice arrives.
How do net payment terms work on a CPPO channel deal? The ISV sets a maximum payment term as a ceiling, and the channel partner can offer terms at or below it — but not longer. So an ISV that will finance up to Net 60 sets that ceiling, and a reseller may grant Net 30, Net 45, or Net 60, but the system prevents Net 90. The ISV keeps control of its receivables exposure.
Does this apply to credit-card buyers? No. Net payment terms apply to buyers who pay by invoice. A buyer paying by credit card is charged on AWS’s standard schedule, so there is no net term to configure for them. The setting is only relevant when the customer is invoiced rather than charged to a card.
Takeaways
- AWS Marketplace now lets the seller set the payment term on a private offer — Net 30, Net 45, Net 60, or Net 90 — as of August 6, 2026, instead of inheriting the buyer’s account default.
- It applies only to buyers who pay by invoice; card-paying buyers are unaffected.
- One term governs every charge in the offer — upfront, scheduled, and usage — with no per-line mixing.
- The buyer sees the term on the procurement page before accepting, and if you set nothing, the buyer’s standard AWS terms still apply.
- On a CPPO deal, the ISV sets a ceiling and the channel partner offers at or below it — the ISV controls the longest term any reseller can extend.
Once the payment term is a seller decision, it becomes one more attribute to track per deal — set at offer time, disclosed to the buyer, and carried onto every invoice. Suger builds and manages AWS Marketplace private offers and reconciles what actually gets invoiced and disbursed through billing and metering, so a deal desk can set a term and finance can see when the cash is due. Suger is a Cloud GTM platform for selling and billing through cloud marketplaces — AWS, Microsoft, Google Cloud, Snowflake, Alibaba Cloud, and Oracle.
Sources
Primary sources for the platform rules cited above. Last verified August 19, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.
- AWS Marketplace now supports net payment terms for private offers — The Net 30/45/60/90 options, the August 6 2026 launch, that it applies to buyers who pay by invoice, that one term applies uniformly to every charge in the offer, that the default is unchanged when no custom term is set, that the buyer sees the term on the procurement page before accepting, and the CPPO ceiling (ISVs set a maximum, channel partners offer at or below it).
Stay Updated
Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.