AWS Marketplace Future-Dated Agreements: Renew Early

An AWS Marketplace future-dated agreement (FDA) is an agreement a buyer signs now that starts on a later date the seller sets. For a SaaS contract renewal, it lets the buyer accept the next term while the current one is still running, and the new term begins after the current one ends.

---

Initech’s AWS Marketplace contract ends on January 31. Their procurement team has the budget in December, and your account executive wants the renewal booked this quarter. What nobody wants is to start the new term in December, which would mean replacing an agreement that still has weeks to run.

AWS Marketplace has handled this since January 2024. The seller puts a future start date on the renewal private offer, the buyer accepts it in December, and the new agreement starts on February 1. One precondition catches teams late: auto-renewal on the current agreement has to be off before the buyer accepts, and AWS says it “cannot be re-enabled” afterwards.

It matters more since September 1, 2026, when AWS announced auto-renewal for direct private offers with contract pricing, generally available that day. Signing a renewal early and letting an agreed renewal run now compete for the same deal. This post is AWS-only; the AWS Marketplace renewals playbook covers the full renewal calendar and how Microsoft and Google Cloud differ.

What is a future-dated agreement on AWS Marketplace?

A future-dated agreement is an AWS Marketplace agreement that starts on a date after the buyer signs it. In a typical transaction the buyer gets the license or entitlement as soon as they accept; with an FDA, AWS says, “the buyer receives the product license or entitlement on a predetermined future date.” The seller of record sets that date on the private offer, and buyers “can’t change the start date,” though they can review it before accepting.

It separates three dates that a normal agreement collapses into one:

Date	AWS’s definition	What it means for your team
Sign date	”The date when the buyer accepts the offer and when the agreement is created.”	The deal is booked and the agreement ID exists. The buyer can’t use the new term yet.
Start date	”The date when the buyer’s license or entitlement to the product is activated and the buyer can begin using the product.”	Provisioning, metering and your integration’s notifications begin.
End date	”The date when the agreement ends. The agreement and the buyer’s license or entitlement expire on this date.”	The next renewal decision.

FDA works on SaaS products with contract or contract-with-consumption pricing, “with and without flexible payments.” For a renewal, what matters most is what acceptance does not do. AWS’s API guide puts it plainly: “Accepting a private offer with a start date in the future does not replace the current agreement. Instead, it creates a renewal agreement that begins immediately after the previous agreement ends.” The current term runs to its end, with its own payment schedule intact.

Which renewal path fits the deal?

A future-dated agreement, unless one of four things is true: the agreement has already ended, it already renews on terms both sides accept, the product isn’t a SaaS contract, or the new terms should apply today. AWS offers four ways to renew, and asked in this order, the questions put each deal on exactly one. Stop at the first yes:

#	Question	First yes	Why this path
1	Has the current agreement already ended?	A new private offer	Agreement-based offers “only target active agreements,” and there is no running term for a future start to follow.
2	Is it set to auto-renew, on terms both sides still accept?	Let it auto-renew on the terms already agreed	Pre-authorized renewal terms, or the buyer’s own auto-renewal setting, already cover it. Nothing needs signing and nothing needs switching off.
3	Is the product anything other than a SaaS contract or SaaS contract with consumption?	A new private offer	Future start dates and amendments are SaaS contract features. For AMI hourly, AMI annual and SaaS pay-as-you-go products, AWS’s renewal route is a new private offer “that can be accepted anytime to renew an existing agreement.”
4	Should the new terms apply now?	An agreement-based offer	It replaces the current agreement the moment the buyer accepts.
—	None of the above: the new terms start when the current term ends	A future-dated agreement	The buyer signs now, and the current agreement runs to its end untouched.

The future-dated agreement is the only one of the four that lets a buyer sign new terms while the current term is still running and start them when it ends, which is why it suits a buyer whose budget and contract calendars don’t line up. Its conditions are in the checklist below; the other three paths work like this.

Agreement-based offer: replace the agreement now

An agreement-based offer is a private offer built on the buyer’s existing agreement that replaces it when accepted. AWS is explicit that it can’t be future-dated: amended offers “only target active agreements, and once accepted, the amended agreements immediately become active making future dating impossible.” Use one when the new terms should apply today, such as an expansion that also moves the end date. The cost of starting now is that “any remaining scheduled payments from previous agreements are cancelled,” so the new schedule has to carry them. What an amendment replaces, and how to price the remainder covers the arithmetic.

Pre-authorized renewal terms: let the agreed renewal run

Pre-authorized renewal terms are renewal rules the buyer accepts with the original private offer: the same price, a fixed uplift, or an uplift within a range. AWS calls them renewal terms, and “agreements created from a private offer with renewal terms renew automatically at their end date unless the seller or buyer opts out.” Buyers can also enable auto-renewal on contract-based public offers. If the renewal already agreed is still the renewal both sides want, this path needs the least work: on a range, you finalize the uplift before the adjustment deadline, and the agreement renews.

A new private offer: expired or unsupported

When the agreement has already ended, there is nothing to amend and no term to follow, so the renewal is an ordinary private offer. The same goes for products outside the SaaS contract family. On AMI hourly and annual products, the new terms override the old ones on acceptance, but AWS warns that “pending charges from the previous offer’s payment schedule will continue unless cancelled.” On AMI contract and professional services products, AWS requires the buyer’s current subscription to be cancelled before they accept a new private offer.

What has to be true before the buyer accepts?

Six conditions, all set by AWS, and all worth checking before the offer goes out, because the start date can’t be changed once it has.

1. The product is a SaaS contract or SaaS contract with consumption. FDA is supported on both, with or without an installment plan.
2. The start date is at least one day after the current agreement ends. AWS’s example: an agreement ending 12/31/2024 renews with a service start date of 1/1/2025. The start date can be up to three years out.
3. The offer expires before the start date. AWS rejects an agreement start date that isn’t after the offer’s availability end date, the last day the offer can be accepted.
4. Auto-renewal on the current agreement is off. A buyer can accept an FDA while the current agreement is active only if “auto-renewal is disabled before accepting the FDA.”
5. The dates don’t overlap another accepted FDA. AWS’s condition is that “the service dates don’t overlap with any other accepted FDAs,” so two pre-booked renewals can’t cover the same period.
6. The start date is right the first time. Buyers can’t change it, and AWS rejects a change to it once the offer is released. A wrong date means a new offer.

On a Channel Partner Private Offer, one more control sits with you: the resale authorization can set a maximum allowed service start date. Without one, AWS says the partner “can specify any future service date up to 3 years in the future.”

What happens to the buyer’s auto-renewal?

It has to be off before the buyer accepts the future-dated offer, and it stays off: AWS says that once an FDA is accepted, “auto-renewal cannot be re-enabled.” The renewal the buyer signed takes the place of the one that would have fired.

On an agreement with renewal terms, two rules decide the timing:

• The renewal decision deadline closes the window. AWS defines it as “the last day a buyer or seller can change their auto-renewal decision before the next cycle is guaranteed.” After it, auto-renewal can no longer be switched off, and an FDA can’t be accepted while it is on. Finish the renewal conversation before that date, not after.
• Who switches it off matters. Buyers “can opt in and out until the renewal decision deadline,” so a buyer who switches it off and then doesn’t sign can switch it back on before the deadline. A seller opt-out is “a one-time action that can’t be reversed,” and the buyer then “must request a new offer.” If you opt out, neither side can undo it.

When does each date land?

On four different kinds of day, each owned by a different team. An illustrative example with a fictional customer: Initech’s SaaS contract ends January 31, 2027. The renewal offer expires December 31, 2026, starts February 1, 2027, ends January 31, 2028, and bills in two installments.

Date (UTC)	Event	What happens
December 10, 2026	Initech switches off auto-renewal on the current agreement	The precondition for accepting. Nothing else about the current agreement changes.
December 14, 2026	Sign date: Initech accepts	AWS creates the new agreement and emails your root account. No SNS notification reaches your product yet.
January 15, 2027, 00:00	First invoice, before the start	Allowed: installments can fall anywhere from the sign date to the end date, “before and after the agreement start date.”
January 31, 2027	The current agreement’s last day	The old term runs to its end, on its own schedule.
February 1, 2027, 00:00	Start date: the entitlement activates	Both SNS topics start now, not at signature. AWS emails you on activation. Provision and meter from here.
July 15, 2027, 00:00	Second invoice	Billed on the date you set.
90, 60 and 30 days before the end	Expiry reminders	AWS emails reminders ahead of the end date.
January 31, 2028, 23:59:59.999	End date	The agreement and the entitlement expire.

Three consequences follow. Book the deal on the sign date, with the start date beside it in the CRM. Treat an invoice before the start date as normal: AWS invoices at 00:00 UTC on each date once the offer is accepted, allows only one invoice date before the acceptance date, and bills a first invoice date that has already passed as soon as the buyer accepts. And key provisioning to the start date: for FDAs, AWS initiates both SNS topics “on the agreement start date (and not agreement sign date),” so anything your team does by hand at signature happens weeks early.

How do you set up a future-dated renewal in Suger?

In the Suger Console, turn on Enable future start date on an AWS contract offer, including contract with consumption, and set the Start date. It has to fall after the offer’s expiry date, the same rule AWS applies: an offer that expires June 30 can start on July 1 at the earliest. The other paths:

• Agreement-based offer. Open the buyer’s entitlement and choose Upsell / Renew. The form sets a new end date rather than a start date, and the entitlement updates as soon as the buyer accepts.
• Renewal terms. Eligible offers show Configure renewal terms; after acceptance, the entitlement’s Renewal section is where you finalize a range uplift or opt out. Suger doesn’t offer renewal terms on agreement-based offers or resale authorizations. The fields and deadlines are in pre-authorized auto-renewal in Suger.
• Container and AMI offers. AWS accepts no start date on these, so if one is set, Suger removes it before submitting and records a warning on the offer. The contract starts when the buyer accepts.
• Resale authorizations. For a Channel Partner Private Offer, Maximum allowed service start date on the resale authorization caps how far out the partner can start the deal.

Frequently asked questions

Can a buyer accept an AWS Marketplace renewal before the current contract ends?

Yes, with a future-dated agreement on a SaaS contract or contract-with-consumption product. The renewal’s start date must fall at least one day after the current agreement ends, auto-renewal must be off first, and the new term begins on that start date, not at signature.

What happens to auto-renewal when a buyer accepts a future-dated agreement?

Auto-renewal on the current agreement must be off before the buyer accepts, and AWS says it cannot be re-enabled once the future-dated agreement is accepted. On an agreement with renewal terms, it can be switched off only until the renewal decision deadline.

Can an agreement-based offer have a future start date?

No. AWS says amended offers cannot have a future agreement start date: they only target active agreements and take effect as soon as the buyer accepts. To start new terms after the current term ends, use a private offer with a future start date.

When do SNS notifications arrive for a future-dated agreement?

On the agreement start date, not the sign date. AWS initiates both SaaS SNS topics when the entitlement activates, so provisioning should key off the start date. AWS still emails the seller’s root account when the buyer accepts.

Can the buyer be invoiced before a future-dated agreement starts?

Yes. With an installment plan, payments can fall any time between the sign date and the end date, including before the start date. AWS invoices at 00:00 UTC on each invoice date once the offer is accepted.

How far ahead can a future-dated agreement start?

Up to three years. For a renewal, the start date must also be at least one day after the current agreement ends, and AWS requires it to fall after the offer’s expiry date.

Takeaways

• A future-dated agreement lets a buyer sign a SaaS contract renewal now and start it after the current term ends, without replacing the current agreement.
• One path per deal: a new offer if the agreement has ended or the product isn’t a SaaS contract, the agreed auto-renewal if its terms still hold, an agreement-based offer for terms that start now, an FDA for terms that start at the end of the term.
• Auto-renewal must be off before the buyer accepts an FDA and can’t be re-enabled afterwards. With renewal terms, that choice closes at the renewal decision deadline.
• Sign, invoice, start and end are separate dates, and SNS notifications follow the start date.
• The start date must follow both the current agreement’s end and the offer’s expiry, and it can’t be changed after release.

A renewal is decided on the offer: its start date, the agreement it builds on, and the renewal terms it carries. See how Suger creates AWS private offers and tracks them to acceptance, future start dates included, from the same console as the entitlements they renew.