Appearance
Source:
docs/tickets/005-lowest-used-price-cannot-be-sourced.md. Edit it there; this page is generated at build time.
005 — lowest_used_price can no longer be sourced, and it's live in the UI
Size: ~1 hour to decide, half a day to remove Found: 2026-09-06, researching the Creators API contract for Phase 2 price ingestion
The problem
docs/affiliate-product-plan.md §4 lists this as a hard design consequence of the Associates operating agreement:
| In any comparison format, must show lowest new and lowest used price | |
lowest_used_priceis a first-class column, not an afterthought |
That premise no longer holds for Amazon. PA-API 5.0 is deprecated in favour of the Creators API, and the Creators API cannot return a lowest used price:
- Amazon's own OffersV1 → OffersV2 field-mapping table marks
Offers.Summaries,Offers.Summaries.LowestPrice,Offers.Summaries.ConditionandOffers.Summaries.OfferCountas "Not Available" — discontinued, not renamed. - The same page states that OffersV2 "provides only featured listings as shown to retail customers on Amazon Detail Page buybox", and reports out of stock when there is no featured offer. There is no offer enumeration to aggregate over.
- The
conditionrequest parameter now accepts onlyAnyandNew. Verified in the official PHP SDK'smodel/Condition.php, which contains exactlyANYand_NEW; PA-API 5'sUsed/Collectible/Refurbishedfilters are gone.
Source: resources/offersV2 and operations/get-items.
What that leaves in the codebase
The column is not dormant — it is wired end to end, and every one of these is now a field only a human can ever fill:
| Where | What it does |
|---|---|
database/migrations/..._154430_add_pricing_and_merchant_to_affiliate_links_table.php:17 | The column, with a comment citing the obligation that has now lapsed |
app/Models/AffiliateLink.php | $fillable + a decimal:2 cast |
resources/views/components/ui/buy-button.blade.php:31 | Formats and renders it beside the new price |
app/Filament/Resources/Products/RelationManagers/AffiliateLinksRelationManager.php:58 | An editable admin field |
database/seeders/DemoContentSeeder.php, database/factories/AffiliateLinkFactory.php | Populate it, so tests and demo content all show a used price |
Phase 2's ingestion pipeline deliberately never writes it, and its offer snapshot distinguishes "this source cannot supply a used price" from "there is no used offer" — specifically so a refresh doesn't null out a figure a human typed in. That's the right behaviour for a column in limbo, but it isn't a resting place.
Why it needs a decision rather than drift
A hand-maintained price is the exact thing the rest of this system is built to prevent. Standing product rule 2 is "never display a price older than its merchant's TTL", and isPriceFresh() enforces it by refusing to print a stale number — but freshness is keyed on price_updated_at, which the new price sets. So a used price typed in once and forgotten will keep rendering, indefinitely, stamped with the refresh time of a different number. That is worse than not showing it.
The licence position — this is not a compliance problem
The obligation was always conditional. Participation Requirements:
"you must display both the lowest 'new' price and, if we provide it to you, the lowest 'used' price."
Amazon no longer provides it, so the clause lapses. Removing the field creates no exposure. Sourcing it from somewhere else would create some: IP License §2(e) prohibits aggregating or repurposing Program Content, and §1(z) forbids using it to promote non-Amazon retailers' products.
Options
Remove it. Migration to drop the column, out of the model, the buy button, the admin form, the seeder and the factory. Honest, and the buy button gets simpler. Cost is a destructive migration — check whether any real row holds a value first.
Keep it, admin-only, and make it expire. Give it its own lowest_used_price_updated_at so freshness is per-figure rather than borrowed, and drop it from the display once stale. Only worth it if someone genuinely intends to maintain used prices by hand for a non-Amazon merchant, which is a question about editorial workflow, not code.
Recommend removing it. Nobody has ever entered one outside a seeder.
Done when
- The column's fate is decided and
docs/affiliate-product-plan.md§4 is corrected — that table currently asserts something untrue about the API, which is how it ends up back in a schema later. - Either the field is gone from all six places above, or it can expire on its own.