Amazon's Operating Agreement and Program Policies, Which One Controls

Twelve articles on this site carry the date April 14, 2026. Five of them hang it on the Operating Agreement, two of those on the Agreement alone. On August 21, 2026 I opened both pages. The Agreement stamps its own header Updated: October 15, 2025. The Program Policies page stamps Updated: April 14, 2026. Two documents, two dates, and a run of my own writing treating them as one.

The merge is easy to fall into, because the two are named in the same breath. They are not siblings. One is the contract. The other is a page of annexes the contract absorbs, and not a single document at all. Which of the two a rule sits in decides what breaking it costs.

So this piece stays on architecture: what each document is, which one wins a contradiction, what each breach costs, and how much warning Amazon owes before any of it moves. The rules themselves have owners, starting with the complete guide to the Associates rules.

The contract swallows the policies in its opening line

You are bound to the Program Policies before you have read the phrase. The Agreement's first paragraph says that by registering for or using the Associates Site you agree to this Agreement, including the Program Policies, defined in Section 12, which are incorporated by reference. It names four as examples: the Participation Requirements, the IP License, the Commission Income Statement and the Trademark Guidelines, all binding at sign-up.

Section 12 widens the mouth. It incorporates the most up-to-date version of all policies, appendices, specifications, guidelines, schedules and other rules referenced in the Agreement, including any updates of those policies from time to time. Consent is being collected in advance for text nobody has written yet.

Program Policies is a page, not a document

On August 21, 2026 I counted the headings on the Program Policies page. Eight separately named documents live inside it, plus an Appendix:

• Associates Program Commission Income Statement
• Associates Program Participation Requirements
• Associates Program Products Statement
• Associates Program Mobile Application Policy
• Associates Program Trademark Guidelines
• Associates Program IP License and Usage Requirements
• Amazon Influencer Program Policy
• Amazon Creator Ads Boost Program Policy

Take that as what the page displays, not as a closed set. Section 12 reaches every policy, appendix, specification, guideline and schedule referenced anywhere in the Agreement, a wider net than one page can show.

Why a section number on its own is not an address

Each of those eight begins again at its own Section 1. Reading down the page, the numbering resets at least five times. A citation shaped like Program Policies Section 2 therefore locates nothing: it is a coordinate on a map with eight origins.

This site has been citing that way for a while, numbers right and document name wrong. The two rules it cites as Program Policies 2(b) and Program Policies 4 both sit inside the Participation Requirements. Below is the correction, plus two lines that were already right, because an audit reporting only faults is not an audit.

The Participation Requirements has an internal shape worth learning once, because most of what an affiliate is told to do sits somewhere inside it:

• Section 1, Enrollment and Eligibility
• Section 2, Links on Your Site, split into (a) Special Links and (b) General Requirements Applicable to All Special Links
• Section 3, Responsibility for Your Site
• Section 4, Promotional Limitations
• Section 5, Distribution of Special Links Through Software and Devices
• Section 6, Content on your Site

Two placements catch people out. Special Links, the term everything else rests on, is defined at 2(a); producing one is the mechanical job covered in the walk-through on building Amazon affiliate links. And the original content requirement is not in Section 6, Content on your Site, where the heading points. It sits in Section 1, Enrollment and Eligibility, which reframes it as a condition of admission. What it asks of a site belongs to the approval requirements, what it means for machine-assisted drafts to the generated-content piece.

Which document wins when they disagree

The Agreement settles this about itself, in Section 12, in one line: in the event of any conflict between this Agreement and any Program Policy, this Agreement will control. The contract outranks its own annexes, and it says so inside the same section that pulled them in.

That is a tie-breaker for real contradictions, not a licence to skip detail. A policy cannot hand you what the contract withholds, but a stricter-reading policy is not thereby void: most policy text fills ground the Agreement left open.

Breaking one is not the same as breaking the other

Section 6, Term and Termination, is where the two documents stop being equal. A material breach lets Amazon suspend or close an account straight away. Anything else, and the clause spells out including any Program Policy, gets notice and seven days to cure. Then the section narrows the gap: any violation of Section 5, and anything the policies designate as such, is deemed material.

The seven-day cure window appears nowhere in this archive. What the archive says instead is accurate but partial: a material breach carries no obligation to warn you first, which leaves the reader assuming every breach works that way. Behaviour that really does end an account on the spot stays in the catalogue of account-ending mistakes.

The penalty that leaves your account open

The Commission Income Statement introduces a third umbrella term, and it appears nowhere in this archive. Program Documents, as that statement defines it, covers the statement itself, the other terms, specifications, statements and policies Amazon publishes from time to time, and the most current version of the Agreement. The Trademark Guidelines point back at it.

The reason to care is a cost the account-closure framing hides. The same statement says qualifying purchases are disqualified whenever they occur in connection with a violation of it or of any other Program Documents. A breach can strip the earnings off transactions without touching the login. What gets paid, and at which rate, is the commission rates page.

Two business days is the entire warning

Section 13, Modification, is a short clause that sets the pace of every other one. Amazon may change any term by posting a change notice, a revised Agreement or a revised Program Policy, and the change takes effect no less than two business days from the date the notice is provided. Carrying on in the program counts as acceptance. Whether Amazon in practice gives more warning than that floor is not something I can check from outside.

That is the whole distance between a rule you comply with and a rule you are breaking. Reciting Amazon's terms from memory a year later is not wrong on purpose, it is stale, and staleness here has a two-day fuse.

One rule can sit in two documents at once

The offline and messaging limit is in the Participation Requirements at Section 4. It is also in the Trademark Guidelines at clause 3(iv), which separately bars putting Amazon's marks in offline material or email, then itemises printed material, mailings, SMS, MMS, email attachments and oral solicitation. Two documents, one behaviour, and clearing yourself under the one you happened to read does not clear you under the other. Which surfaces are open to you is mapped separately.

One contract, four schedules, a different regime per market

The Agreement does not stop at its numbered sections. It closes with four schedules, each keyed to the marketplace: the Amazon entity and site by location, governing law and disputes, the tax provision, and the privacy notice. Counterparty, governing law and tax treatment all move with the marketplace. Running the United States, the United Kingdom and Germany is not one agreement in three languages.

Now the honest limit of everything above. Every section number here comes from the amazon.com version, read on August 21, 2026. I did not pull the British or German versions, so I do not know whether their numbering, their dates or the eight-document layout match. Do not carry these numbers into another marketplace without opening its own copy. A handful of clauses in the American text did not render with legible numbers, so none are cited.

What neither page settles

Some of what affiliates treat as contract is in neither document. The condition about three qualifying sales within 180 days is the clearest case: Amazon publishes it on an Associates Central help page, not as a numbered clause. It also shares a number with something unrelated, the shipping and payment window in the Commission Income Statement. The piece on the 3 sales rule keeps them apart.

One more blank is worth naming. The eight documents share a single Updated stamp and carry no individual effective dates, so nothing on the page reveals when the Trademark Guidelines last moved.

The working version of all this is short. Never cite a Program Policy without naming which of the eight it is. Check the date printed on the page in front of you, not the date you remember. When a policy and the contract pull in different directions, Section 12 has decided it already. Both texts are public, the contract itself and the policies page, with a change log.