AWS Marketplace Renewals: An Operating Playbook

An AWS Marketplace renewal is the continuation of a SaaS contract at the end of its term. Buyers can agree to automatic renewal at purchase, and they can change quantity, duration, or cancel the renewal themselves — from the AWS console, without telling you.

---

Direct renewals are a conversation. Marketplace renewals are a scheduled event with a default value.

That is the whole difference, and it is the reason marketplace renewals go wrong in a way direct renewals rarely do. Nobody misses a direct renewal, because the customer has to actively sign something. On a marketplace, the customer can do nothing at all — and either keep paying you or stop paying you, depending on a setting they chose months ago in a console you can’t see.

This is the operating process for that, on AWS first, with the differences on Microsoft and Google Cloud after.

---

How do renewals work on AWS Marketplace?

AWS Marketplace SaaS contracts can renew automatically, and the buyer controls the setting. In AWS’s words: “When a customer purchases your product through AWS Marketplace using SaaS contracts, they can agree to automatic renewal of the contract terms. The customer continues to pay for the entitlements every month or for 1, 2, or 3 years.”

Then the sentence that defines the risk: “The customer always has the option to modify the renewal settings. They can cancel the renewal or renew the contract for different quantities and durations.”

Three consequences follow.

On a SaaS contract, auto-renewal is a buyer setting. You do not turn it on, you do not turn it off, and you find out what it is by looking at the agreement data. AWS’s wording is that the customer “can agree to automatic renewal of the contract terms” and “always has the option to modify the renewal settings.”

On a direct private offer with contract pricing, the seller now shapes it too. Since 1 September 2026 AWS Marketplace supports auto-renewals on those offers, generally available in all commercial AWS Regions with “no additional setup or onboarding.” The seller sets the renewal pricing when the offer is created — “renewal with no price change, renewal with a fixed price change, or a price change within a defined range.” The enabling side stays with the buyer: AWS’s renewals documentation states that “customers can enable auto-renewal for contract-based offers, public or private.” Before a renewal fires, “AWS Marketplace notifies both parties and provides a comparison of the current and upcoming terms, including any pricing changes,” and “either party can opt out of an upcoming renewal before the renewal decision deadline.”

These are two different mechanisms on two different objects, and the distinction is the whole operating difference: the public-offer default is something you discover, while the private-offer renewal is something you negotiate up front. Check which one an agreement is running on before you plan the motion.

A silent downgrade is possible. A customer cannot shrink a contract mid-term — AWS is explicit that “customers can’t decrease the size of their existing contract. They can only decrease the size at renewal, or cancel their renewal.” Renewal is therefore the only moment a contract can get smaller, which makes it the moment that deserves attention, not the moment to relax.

Expiry is abrupt. When a contract ends, “your SaaS product receives an entitlement-updated notification indicating the buyer’s entitlement has changed. The AWS Marketplace Entitlement Service returns an empty response,” and you have one hour to meter any remaining overage. An empty entitlement response is not an error — software that retries it will keep serving a customer who no longer has a contract.

---

The renewal timeline, and the decision at each stage

When	What is happening	The decision it forces
T-120 days	Renewal enters the forecast	Is this a flat renewal, an expansion, or a rescue? Set the motion now — a renewal private offer takes longer to agree than a settings change
T-90 days	Confirm the buyer’s renewal setting and current entitlement	If auto-renewal is off, you have a new sale, not a renewal. Staff it accordingly
T-90 to T-60	Check consumption against entitlement	Under-consumption predicts a downgrade at renewal — the only moment a shrink is possible. Over-consumption is an expansion conversation
T-60 days	Decide the commercial shape	Three options now: same terms and let it auto-renew, a renewal private offer with new quantity, duration, or price, or — on a direct private offer with contract pricing — an auto-renewing offer with the price change agreed in advance
T-45 days	If a private offer is needed, issue it	Enterprise procurement needs runway. A renewal offer landing at T-7 gets processed at T+20
T-30 days	Confirm acceptance status	Not “did we send it” — did the buyer’s procurement actually accept it
T-0	Term ends	If nothing was accepted and auto-renewal is off, entitlements go empty. Your product must handle it
T+1 hour	Metering window closes	Any unbilled overage must already be sent

The stage most teams skip is T-90: confirming the renewal setting. It is the cheapest check on the list and the only one that tells you whether you are managing a renewal or running a sale.

---

Renewal private offers: what changes

A renewal on AWS Marketplace is usually issued as a new private offer against the existing agreement, and two things make it commercially different from the original sale.

Renewals are cheaper to transact. AWS’s published listing fee schedule prices all private offer renewals at 1.5%, regardless of the tier the original contract fell into. A $2M agreement that cost 2% to transact renews at 1.5%. Marketplace revenue gets less expensive as it ages — the full arithmetic is in what a marketplace dollar actually costs you.

The buyer’s committed spend position may have moved. The customer who bought against a committed-spend agreement last year may be over-committed, under-committed, or in a renegotiation of their own. That changes the shape of the offer they can accept, and it is worth asking before you price.

The mechanics of building the offer itself — durations, dimensions, flexible payment schedules — are covered in private offers in Suger.

---

How Microsoft and Google Cloud differ

The concept is the same everywhere. The defaults are not.

Microsoft Marketplace structures the term explicitly: contract durations of 1-month, 1-year, 2-year, 3-year, 4-year, and 5-year, each with a billing frequency of one-time upfront, monthly equal, annual equal, or a flexible schedule available with a private offer. Two rules shape renewals:

• “For contract durations with equal payments, payment collection is enforced for the entire term” — a customer on monthly-equal billing has committed to the full term, not to a monthly rolling arrangement.
• “Subscriptions with multiyear contract durations and pending payments aren’t eligible for cancelation by customers.” Multi-year Microsoft terms are materially harder for a buyer to walk away from mid-term than an AWS contract.

Free trials on Microsoft convert by default: “the trial subscription automatically converts to a paid subscription unless the customer cancels before the trial period ends or disables auto-renew for the subscription.”

Google Cloud Marketplace subscription pricing is “a flat monthly rate. For partial months, the price is prorated.” Price changes have their own timetable — after 30 days of publication you can update pricing, with decreases effective immediately upon approval and increases taking an additional 45 days. Plan a renewal uplift a quarter ahead, not a fortnight.

---

What actually breaks

Four failure modes account for most lost marketplace renewals, and none of them are commercial.

Nobody owned the date. The renewal sat in the marketplace console, not in the CRM, so it never appeared on a forecast and no human was assigned to it.

The entitlement change was invisible. A customer reduced quantity at renewal. Revenue dropped. Finance found out at month-end close, and the account team found out from finance.

The product treated an empty entitlement as an outage. Access continued after expiry. That is unbilled service — and an awkward conversation when it is discovered.

The renewal offer arrived too late for procurement. The commercial terms were agreed on time; the acceptance was not. The agreement lapsed while everyone believed the deal was done.

Every one of these is a data problem before it is a sales problem. The fix is the same in each case: agreement state, entitlement quantity, renewal setting, and expiry date sitting in the system your revenue team already works in, with an owner and a date attached. That is what agreements in Suger is for.

---

Frequently asked questions

Do AWS Marketplace contracts renew automatically? They can, in two ways. On a SaaS contract the buyer agrees to automatic renewal at purchase and controls the setting. Since 1 September 2026, a seller can also set renewal pricing on a direct private offer with contract pricing; the customer enables the renewal, and either party may opt out before the renewal decision deadline.

Can a customer reduce their contract at renewal? Yes. Renewal is the only point at which a contract can shrink — AWS allows mid-term upgrades with a prorated credit, but customers can only decrease size at renewal or cancel the renewal.

What happens if an AWS Marketplace contract is not renewed? Your product receives an entitlement-updated notification and the Entitlement Service returns an empty response. You then have one hour to send any remaining metering records for that customer.

Are AWS Marketplace renewals cheaper than new deals? Yes. AWS’s published fee schedule charges all private offer renewals at 1.5%, regardless of which tier the original contract fell into.

How do I renew a marketplace agreement with new terms? Issue a renewal private offer against the existing agreement with the new quantity, duration, or price, and allow enough runway for the buyer’s procurement to accept it before the current term ends.

Can a Microsoft Marketplace customer cancel mid-term? Not always. Microsoft states that subscriptions with multiyear contract durations and pending payments aren’t eligible for cancelation by customers; those cases go through Marketplace support.

---

Takeaways

• Auto-renewal is a buyer-controlled setting. Confirm it at T-90 or you may be running a new sale without knowing it.
• Renewal is the only moment an AWS contract can shrink. Treat under-consumption as an early warning.
• Expiry returns an empty entitlement, not an error. Build for that or you will serve customers for free.
• Private offer renewals transact at 1.5% on AWS — marketplace revenue gets cheaper as it ages.
• Microsoft enforces payment collection across equal-payment terms and blocks buyer cancellation on multiyear subscriptions with pending payments.
• Most lost renewals are data failures: the date, the entitlement, and the renewal setting were not where the revenue team could see them.

---

Renewals are only manageable if the agreement is visible before it expires. See how agreement management in Suger surfaces entitlements, renewal settings, and expiry dates across every marketplace — in the CRM your team already uses.