What changed, and when
Changes, most recent first
Two kinds of entry: catalogue refreshes, which change the numbers on every page, and editorial changes, which change what the pages say. Both matter, so both are listed.
- Catalogue refresh. 0 items available at the source, 11,414 recorded across this site's categories and brand indexes. All counts, price ranges and category totals recomputed.
- Three calculators added and tested in-browser. Fee shapes are published as four named service structures rather than as rates, because rates move and shapes do not.
- QC checklists published for shoes, tops and bags. The three lists are category-specific rather than shared, because the failure modes differ.
- Disclosure expanded from a summary to four explicit denials, following a review of what a reader could reasonably infer from the shorter version.
- Brand index published with twelve labels. One label is matched by product name rather than by a brand field; the page for it states this rather than showing an empty grid.
- Category indexes published for all eight categories, each with its own inspection criteria rather than a shared generic list.
- First build. Home page, coupon verification section and points section written; catalogue snapshot wired up so that every figure on the site derives from one reading.
What each kind of change affects
Not every change has the same reach. This table says which pages move when each kind of update happens, so a reader can tell how stale a given page is.
| Change | Pages affected | How to spot it |
|---|---|---|
| Catalogue refresh | Every page carrying counts or prices | The snapshot date in the page footer and beside each figure |
| A new section | The new pages, plus the home page and the sitemap | The dates in this log |
| A correction | Only the page corrected | A dated note on the page itself, and an entry here |
| A disclosure change | Every page, through the footer | The disclosure page and this log |
Why an update log rather than a "last reviewed" badge
Three reasons, each about what a reader can actually do with the information.
- A badge says when, a log says what
"Last reviewed 23 October" tells you nothing about whether the number you are reading changed. A log entry says which figures moved and why.
- A log can be checked against the pages
Each entry names its scope, so a reader can confirm that a category total did in fact change on the date claimed. A badge cannot be checked at all.
- A log makes staleness visible
If the most recent catalogue refresh is three months old, a reader can see that and discount the prices accordingly. That is more useful than a promise of freshness.
The practical consequence: if you need the current figure, the source API is the only live reading. Everything here is a record with a date on it.
Log questions
Three answers about how this log is kept.