Appearance
Source:
docs/tickets/006-missing-amazon-price-disclosures.md. Edit it there; this page is generated at build time.
006 — Two disclosures Amazon requires beside a displayed price are missing
Size: ~2 hours Found: 2026-09-06, researching the Creators API contract for Phase 2 price ingestion
The problem
The site renders Amazon prices with an "as of {time}" stamp — resources/views/components/ui/buy-button.blade.php:71 and resources/views/rich-content/comparison-table.blade.php:23, both gated on the merchant's requires_price_timestamp. That part is right, and it is the part the product plan anticipated.
The operating agreement asks for two more things that are nowhere in the codebase. Neither string appears in any Blade file:
1. The price-accuracy disclaimer (IP License §2(i)), required verbatim, adjacent to the price or reachable from it by hyperlink or pop-up:
"Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on [relevant Amazon Site(s), as applicable] at the time of purchase will apply to the purchase of this product."
Note the shape of Amazon's own documented example — Amazon.com Price: $ 32.77 (as of 01/07/2008 14:11 PST- Details) — where "Details" is the link to the disclaimer. The stamp we already render is the first half of a two-part requirement, and we ship it without the second half.
2. The "AS IS" content notice (§2(k)), required for any Amazon-sourced content displayed at all, in capitals as given:
"CERTAIN CONTENT THAT APPEARS [IN THIS APPLICATION or ON THIS SITE, as applicable] COMES FROM AMAZON. THIS CONTENT IS PROVIDED 'AS IS' AND IS SUBJECT TO CHANGE OR REMOVAL AT ANY TIME."
Source: the live US operating agreement at affiliate-program.amazon.com/help/operating/policies. The text has already been updated to name "Creators API" alongside "PA API", so it is current rather than a PA-API-era leftover.
What to check before writing any copy
The §2(i) trigger is refresh frequency, and it may not fire at all. The clause requires the stamp "if you call Creators API, PA API or refresh the Product Advertising Content displayed on your application less frequently than hourly." The disclaimer sits inside that same clause, so it plausibly shares that trigger — and Phase 2's ingestion targets an hourly refresh, which is Amazon's own recommended TTL for offers.
So the honest first step is reading §2(i) and deciding whether an hourly-refreshed price owes either the stamp or the disclaimer. It is possible the correct outcome here is fewer strings on the page, not more, plus a comment recording why. Do not skip this and just add copy — that is how a page ends up carrying a disclosure it doesn't need next to one it does.
§2(k) has no such trigger and applies to any displayed Amazon content.
Where it belongs
buy-button.blade.php already owns every price rule (freshness, the stamp, the strike price) and cta-button.blade.php says so in a comment. That is the seam.
The constraint that shapes the design is the same one that shaped the FTC disclosure work in ADR-0005: co-visibility. A disclosure the reader has to scroll away from doesn't do its job. Amazon explicitly permits a hyperlink or pop-up for the §2(i) disclaimer, which the FTC does not permit for an affiliate disclosure (16 CFR §465.1(c)(4) — clicking disqualifies it) — so these two are different obligations with different rules and should not be merged into one component just because they sit near each other.
requires_price_timestamp is already the per-merchant switch for "this merchant imposes price-display terms". Whatever gets added should hang off the same flag rather than hardcoding Amazon, since the wording is Amazon's but the pattern isn't.
While you're in there: price alerting is prohibited too
Standing product rule and plan §4 both record that price-history tracking is prohibited. The clause is broader than that. Participation Requirements ¶(y):
"Unless otherwise agreed by Amazon, your Site must not have price tracking and/or price alerting functionality."
So no price-drop emails and no watch lists either — worth writing into §7 of the plan before someone builds one, because "email me when this drops" is an obvious and otherwise harmless-looking newsletter feature, and Phase 2's roadmap has newsletter work in it.
Two more clauses worth recording while the agreement is open
- §2(e) prohibits, without written approval, using the API "for the purpose of aggregating, analyzing, extracting, or repurposing any Product Advertising Content… or in the direct training or fine-tuning of a machine learning and/or foundational model." Relevant to any plan to generate editorial copy from API responses.
- Image URLs expire too. §2(h) permits storing a link to an image for up to 24 hours — not indefinitely. The plan's §4 row says "Merchant imagery stays a URL", which is right about not re-hosting but implies the URL is durable. It isn't. ASINs are the only datum storable indefinitely.
Done when
- §2(i)'s hourly trigger has been read against Phase 2's actual refresh interval, and the outcome — copy added, or copy deliberately not added — is recorded in a comment or ADR where the next person will find it.
- The §2(k) notice appears wherever Amazon content does.
docs/affiliate-product-plan.md§4 and §7 are corrected on price alerting and on image URL expiry.