Key takeaway
Build the renewal calendar from the configured decision and adjustment deadlines. The current term’s end date may leave too little time to change the next one.
Put three dates in the diary
A company plans to review a software subscription two weeks before its December expiry. Its configured renewal election may already be locked by then. The commercial owner needs the deadline for changing the next term, the deadline for its price and the current agreement’s end date on the same calendar.
AWS announced private-offer auto-renewal support on 1 September 2026. Its buyer documentation explains that enabled renewal terms can generate a new offer and agreement when the current term ends. This article uses that specific mechanism, read on 16 October 2026, to explain the scheduling decision. It does not assume every private offer renews automatically.
An illustrative December agreement
Hypothetical example: a company buys an eligible non-ADX private contract offer for software used in an internal data project. Its current annual price is USD 12,000 and its agreement ends on 31 December 2026. Assume both parties accepted enabled renewal terms with a thirty-day lockout period and a sixty-day price-adjustment deadline.
For a price uplift within a stipulated range, the default is 5% if no different permitted value is finalized. The exact timestamps and time zone are deliberately not invented. An operating calendar must obtain them from the actual offer and notifications before deciding when a real action is timely.
| Event under the illustrative terms | Date | What the date controls |
|---|---|---|
| Price adjustment deadline: P60D | 1 November 2026 | Finalize the permitted uplift; default otherwise applies |
| Renewal decision deadline: P30D | 1 December 2026 | Last change to this cycle’s renewal election |
| Current agreement end | 31 December 2026 | Current term ends; enabled renewal creates the next agreement |
Read which decision belongs to whom
The developer documentation gives these relative-date examples: thirty days before a December 31 end is December 1, and sixty days before is November 1. The buyer guide distinguishes the renewal-decision deadline from the range-uplift adjustment deadline. Before using a notification as a task reminder, identify which decision it concerns and who can make it.
Under the documented mechanism, the renewal election cannot be changed for that cycle after the decision deadline. A December 15 review would therefore be late for the assumed December 1 election. That is a consequence of the stipulated configuration, not a legal conclusion that no contractual or statutory remedy could exist in a real dispute.
Calculate one next-term commitment
If the hypothetical default 5% governs, the next annual price is USD 12,000 × 1.05 = USD 12,600. That is a potential next-period commitment, not evidence that an invoice was paid. A range-based uplift should not be projected as 5% forever; future cycles need their actual finalized or default terms.
Suppose the internal data project has already spent USD 1,200 on outside engineering and USD 800 on external review. If no data license produces cash, those USD 2,000 preparation costs remain. If the software renews and the next USD 12,600 is paid, the stated cash outflow across this illustration is USD 14,600, before tax and omitted costs. There is no assumed licensing receipt, other external seller fee or additional recurring service in this calculation.
The older USD 12,000 subscription price is not added to this forward renewal comparison. It describes the current term. Whether future software is still needed, and which cancellation or replacement costs arise, requires the operating owner’s own evidence.
Check the supported offer before copying the calendar
The developer guide lists restrictions on renewal attributes for AWS Data Exchange products. This example therefore expressly uses an eligible non-ADX offer. A data owner should not infer that lockout, maximum-renewal or price-adjustment fields are available for every data-product listing just because the general private-offer feature exists.
Retrieve the applicable accepted offer, renewal settings, notices and agreement identifiers. Confirm the price type, range/default where relevant, election state and who is responsible for reviewing changes. Keep a new agreement distinct from an amendment to the current one, and preserve the version actually accepted.
Schedule the choice while it can still be made
The useful output is a dated internal review before the earliest relevant deadline, with a named commercial owner and a way to verify the resulting election. An internal instruction to avoid renewal is not proof that a permitted account action happened. Reconcile the actual status without assuming that a diary entry executed it.
Nonrenewal of a future term, cancellation of the current term and handling artifacts after expiry are separate questions. This worked calendar answers only the first scheduling problem. No AWS account was accessed, election changed or notice sent, and VOID does not make those decisions on the company’s behalf.