AWS Marketplace Agreement Status and Renewal Chains

AWS Marketplace agreement status is the value AWS reports for each agreement: ACTIVE while its terms are in force, then one of five endings. Two of them, RENEWED and REPLACED, mean a new agreement with its own ID has taken over, so one customer’s contract becomes a chain of agreements your systems have to keep together.

---

Acme’s CRM picks up a new AWS Marketplace customer on the first of the month: Umbrella, under an agreement ID nobody has seen. Umbrella isn’t new. Its private offer carried renewal terms, and AWS renewed the agreement at its end date, which on AWS means a new agreement rather than a later end date. The old agreement now reads RENEWED. A sync that opens a customer for every new agreement ID shows one new logo and one ended contract for a customer who never left.

Private offers are where this now starts. On September 1, 2026, AWS announced auto-renewals for private offers, generally available to sellers creating direct private offers with contract pricing.

AWS documents what keeps the contract in one piece: the statuses, a preview of each end date, a renewal event that names the agreement it renewed, and a chain ID that stays the same across renewals. This guide reads each from AWS’s own pages, then shows what Fours does with them. Running the renewal itself is covered in the AWS Marketplace renewals playbook.

What does AWS Marketplace agreement status tell you?

AWS Marketplace agreement status tells you whether an agreement’s terms are still in force and, once they aren’t, how the agreement ended. DescribeAgreement returns one of six values, the Status filter on SearchAgreements takes the same six, and the AWS Marketplace Management Portal shows them as Active, Expired, Renewed, Cancelled, Replaced and Terminated. The middle column is the DescribeAgreement definition, word for word; the right column is our reading.

Status	AWS’s definition	What it means for your records
ACTIVE	”The terms of the agreement are active.”	The current term. Bill and provision against it.
EXPIRED	”The agreement ended on the defined end date.”	The term ran out. A renewal signed separately is a different agreement, so check the buyer before recording churn.
RENEWED	”The agreement was renewed into a new agreement (for example, an auto-renewal).”	Not churn. Attach the new agreement to the same contract.
REPLACED	”The agreement was replaced using an agreement replacement offer.”	Not churn. The new agreement comes from a different offer, on that offer’s terms.
CANCELLED	”The acceptor ended the agreement before the defined end date.”	The buyer ended it early: a real early end.
TERMINATED	”The agreement ended before the defined end date because of an AWS termination (for example, a payment failure).”	AWS ended it, so treat it as a billing problem before you call it churn.

While an agreement is in force, what happens at its end date sits in endTimeBehavior; once it isn’t, which agreement took over sits in the chain keys.

What are ARCHIVED, ROLLED_BACK and SUPERSEDED?

They are three more values that AWS’s agreements data feed defines, and only ARCHIVED is an ending. AWS marks the other two “Only applicable to inactive agreement revisions”: they describe a revision that is no longer active, not how an agreement ended.

Value	AWS’s definition, from the data feed	Treat it as
ARCHIVED	”The agreement has ended; The exact reason for its ending, Terminated, Canceled, or Expired, is not specified.”	An ending with no stated reason. AWS names only termination, cancellation and expiry as possible reasons, so don’t read it as a renewal.
ROLLED_BACK	”The agreement revision has been rolled back because of an error. An earlier revision is now active. Only applicable to inactive agreement revisions.”	Not an ending. An earlier revision is in force.
SUPERSEDED	”The agreement revision is no longer active and another agreement revision is now active. Only applicable to inactive agreement revisions.”	Not an ending. Use the active revision.

The feed, which AWS refreshes every 24 hours, spells the last one “Superceded”. Search results can carry these values too: AgreementViewSummary, the object SearchAgreements returns, allows all nine, while DescribeAgreement and the Status filter name only six, so a parser built for six can meet values it doesn’t know.

What happens when an active agreement reaches its end date?

AWS previews it in endTimeBehavior: a type that says whether the agreement renews, is replaced or expires, and a reason code when it won’t renew. DescribeAgreement returns it “for every active agreement that has an end date,” but not for pay-as-you-go agreements or “an agreement that is no longer active,” so store the last value you read if a churn report will need the reason. SearchAgreements returns and filters on the same values.

type	AWS’s definition
RENEW	”A new agreement is created from the accepted terms of this agreement.”
REPLACE	”A new agreement is created from a different offer than the one this agreement was created from. This happens, for example, when a private offer reaches its end date and the acceptor transitions to the public offer for the product.”
EXPIRE	”The agreement ends and isn’t renewed or replaced.”

reasonCode (null when the agreement renews)	AWS’s definition
PROPOSER_RENEW_OPTED_OUT	”The proposer opted out of renewing the agreement.”
ACCEPTOR_RENEW_OPTED_OUT	”The acceptor opted out of renewing the agreement.”
NO_RENEWAL_TERM	”The accepted terms of the agreement don’t include a renewal term, which is required for an agreement to renew.”
RENEWAL_LIMIT_EXHAUSTED	”The agreement reached the maximum number of renewals allowed by its renewal term.”

Two rules keep a forecast honest. When several reasons apply, AWS returns one, and PROPOSER_RENEW_OPTED_OUT “takes precedence over all others.” And EnableAutoRenew “reflects only the acceptor’s preference,” so read the type, not the flag. A REPLACE preview on a private-offer agreement is worth a note to the account team, because the next agreement comes from a different offer, such as the public one.

The portal shows a matching preview in words: the Agreements page’s At expiration column reads Auto-renews, Converts to public offer, or Access ends, and its Renewal status column reads Auto-renewing, Opted out, Buyer opted out, No renewal terms, or Renewal limit reached.

How does a renewal arrive from AWS?

As a new agreement. AWS documents a Purchase Agreement Created - Proposer event with intent set to RENEW; the new agreement is ACTIVE, and the agreement it renewed now has the status RENEWED. AWS’s example body, trimmed to the agreement:

{
  "detail-type": "Purchase Agreement Created - Proposer",
  "source": "aws.agreement-marketplace",
  "detail": {
    "agreement": {
      "id": "agmt-newrenewalagreementid",
      "intent": "RENEW",
      "status": "ACTIVE",
      "previousAgreementId": "agmt-4mwg1nevbokzw95eca5797ixs"
    }
  }
}

In AWS’s example, previousAgreementId is the ID of the agreement that was renewed. A new purchase uses the same detail type, which is how a renewal reaches the CRM as a new customer. The events a sync has to tell apart:

What happened	AWS event	In AWS’s example
A customer subscribes	Purchase Agreement Created - Proposer	intent: NEW, no previousAgreementId
An agreement auto-renews	Purchase Agreement Created - Proposer	intent: RENEW, with previousAgreementId
An agreement is amended	Purchase Agreement Amended - Proposer	intent: AMEND, the same agreement ID
A customer cancels	Purchase Agreement Ended - Proposer	status: CANCELLED

Amended covers more than it sounds: “Seller opt-out is processed as an amendment and surfaces through this event.”

A replacement offer, also called an agreement-based offer, is the other route. Once the buyer accepts, “their current agreement will be replaced with a new agreement that can extend beyond the previous end date,” the old one reads REPLACED, and AWS cancels “any remaining scheduled payments from previous agreements.” AWS gives no event example for a replacement, so find it through the chain.

How do you follow an agreement chain?

By initialAgreementId, the ID of “the very first agreement in a chain of related agreements, such as renewals or replacements,” which AWS says “stays the same across all agreements in that chain.” An agreement that isn’t derived from another carries its own ID there.

Key	Where AWS documents it	What it gives you
initialAgreementId	DescribeAgreement and SearchAgreements responses	The chain an agreement belongs to
InitialAgreementId filter	SearchAgreements	”every agreement in the same chain”
previousAgreementId	The renewal event	The agreement just renewed
preceding_agreement_id	The agreements data feed	”The agreement ID of the previous agreement.”

The chain has two limits. AWS’s definition names renewals and replacements. A renewal signed early as a future-dated agreement is “a renewal agreement that begins immediately after the previous agreement ends,” and a new private offer can renew AMI hourly, AMI annual and SaaS pay-as-you-go subscriptions, but AWS doesn’t say whether either joins the chain, so read the new agreement’s initialAgreementId rather than assume. And a seller’s search must include the AgreementType filter, “which is required.” In the portal, an agreement’s Renewal history tab “traces every offer and agreement in the renewal chain.”

With those keys, three levels keep a renewal from looking like a new customer. This is our reading, not an AWS rule:

Level	Key	What hangs off it
Customer	The buyer’s AWS account ID, mapped to your account	The CRM account and logo counts
Contract	initialAgreementId	The opportunity, renewal history and retention
Term	agreementId	The term’s dates, invoices, usage and entitlement

Which of these records belong in the CRM at all is covered in connecting your CRM to cloud marketplace data.

What should your sync do when a new agreement ID appears?

Work out whether it continues a contract you already have before you create anything. In order:

1. Read intent first. On Purchase Agreement Created - Proposer, RENEW means the contract continues: attach the new agreement to the contract of the one in previousAgreementId.
2. Resolve the chain. Call DescribeAgreement on the new agreement. If its initialAgreementId differs from its own ID, attach it to that chain; if the two match, it starts one.
3. Close the term, not the contract. End a RENEWED or REPLACED agreement’s term record, and point invoices and the next renewal date at the new agreement.
4. Check the buyer before you record churn. For EXPIRED, CANCELLED, TERMINATED or ARCHIVED, search with the AcceptorAccountId filter for a newer agreement first: a future-dated renewal or a new private offer can carry the customer on.
5. Keep revisions out of churn. Handle all nine values, and drop ROLLED_BACK and SUPERSEDED rows from anything that counts endings.
6. Backfill with a search. The AfterLastUpdateTime filter returns agreements updated since your last run, and AWS counts “Amendments, renewals, and a party changing whether the agreement renews” as updates.
7. Mind the purchase order. AWS lets buyers “map a purchase order to any renewal,” so ask procurement to map theirs to the new agreement.

How does Fours show a renewed or ended AWS agreement?

Fours mirrors AWS: an auto-renewal gets a new entitlement with its own agreement ID and dates, and the entitlement that ended says how, in AWS’s own words. This is Fours behaviour, as Fours’ documentation describes it:

• Status chips. Every ended AWS entitlement has the status CANCELLED in Fours’ shared status set, and its chip uses AWS’s status to say how it ended: Expired for EXPIRED, Renewed for RENEWED, and Replaced for REPLACED or SUPERSEDED. Other endings, such as TERMINATED, stay a red Cancelled. The Status filter offers the same labels, and hovering a chip shows AWS’s own status as Partner status when the two differ.
• A new entitlement per renewal. When AWS auto-renews an agreement, Fours creates an entitlement for the renewal term and cancels the previous one, whose chip then reads Renewed. On Fours’ side that is a created entitlement and a cancelled one, so Fours’ docs say to “Key off the buyer or the agreement rather than the entitlement row.”
• Final usage. The old entitlement is cancelled through the same pending-cancel path as any ending agreement, keeping the grace period for reporting final metered usage. A notice on an Expired, Renewed or Replaced entitlement with usage dimensions says usage reported before it ended is still billed there, and a fractional remainder moves to the renewed entitlement once the old one’s final usage report is done. Terms fixed on the original offer, including the buyer net payment term, don’t carry across automatically.
• The chain on the entitlement. On an AWS entitlement whose agreement carries pre-authorized renewal terms, the Renewal history tab lists every agreement in the renewal chain, oldest first, as Original agreement, then Renewal 1 of 2 and so on, with the one you’re viewing marked Current. A replacement shows its dates without a label and isn’t counted, and a closing line says what follows the latest agreement, such as “No further renewals: the buyer opted out.” On a fixed-percentage or no-uplift term, Renewal details also shows the Next renewal total: the agreement’s total carried forward one cycle at the agreed uplift.

Frequently asked questions

What does RENEWED mean on an AWS Marketplace agreement?

It means the agreement was renewed into a new agreement, for example by auto-renewal. A new agreement with its own ID now carries the contract on, and both share the same initialAgreementId, so the contract hasn’t churned.

Does an AWS Marketplace renewal keep the same agreement ID?

No. AWS creates a new agreement and documents a Purchase Agreement Created - Proposer event with intent RENEW, whose previousAgreementId is the ID of the agreement it renewed. That earlier agreement’s status becomes RENEWED.

How do you find every agreement in an AWS Marketplace renewal chain?

Read any agreement’s initialAgreementId, which stays the same across its chain, then call SearchAgreements with the InitialAgreementId filter and the required AgreementType filter. AWS’s definition covers renewals and replacements, so check a future-dated renewal rather than assume.

What do ARCHIVED, ROLLED_BACK and SUPERSEDED mean?

They’re values from AWS’s agreements data feed. ARCHIVED is an agreement that ended by termination, cancellation or expiry, without saying which. ROLLED_BACK and SUPERSEDED apply only to inactive agreement revisions, so neither is an ending.

Why does a renewed AWS customer look new in the CRM?

Because the renewal arrives as a new agreement ID, on the same event type as a new purchase. A sync that opens a customer per agreement, without reading intent or initialAgreementId, records a new logo and an ended contract for one customer.

How does Fours show an AWS agreement that renewed?

Fours creates a new entitlement for the renewal term, with its own agreement ID and dates, and the previous entitlement’s status chip reads Renewed. Expired and Replaced chips mark those AWS endings; any other ending, such as TERMINATED, stays a red Cancelled.

Takeaways

• AWS reports six agreement statuses. RENEWED and REPLACED mean a new agreement with its own ID carries the contract on, so neither is churn.
• ARCHIVED, ROLLED_BACK and SUPERSEDED come from the data feed and search results, and only ARCHIVED is an ending.
• AWS documents a renewal as Purchase Agreement Created - Proposer with intent: RENEW and previousAgreementId, the same detail type as a new purchase, so read intent before you create anything.
• Key the customer on the buyer, the contract on initialAgreementId and each term on its agreement ID, and store endTimeBehavior while the agreement is active.

Fours syncs each AWS agreement as its own entitlement, marks expired, renewed and replaced ones with AWS’s own status, and lists the renewal chain on agreements with pre-authorized renewal terms. See how it fits your contract operations in Fours’ marketplace agreement management.