Why the iTaoBuy Spreadsheet Stays Fixed Between Updates

Random results make a spreadsheet harder to trust

A product API is useful for collecting current catalog fields, but an automatically changing response is a poor editorial surface. When products move every time the page reloads, a visitor cannot return to the same shortlist, compare notes with someone else or tell whether a result disappeared because of a filter or a new API order.

The problem is not that a catalog changes. Product records should change when the underlying data is reviewed. The problem is changing without a visible editorial event. A refreshed page should not silently replace the evidence a visitor was comparing a few seconds earlier.

What the current snapshot records

This edition selects products during the Astro site build and keeps that order fixed until the next build. The visible record can include the product title, category, image, approximate USD value and any QC-photo or AI try-on signal currently supplied by the catalog source.

Those fields create a research reference, not live inventory. A stable card does not promise that the seller still offers the same color, size or price. The destination result remains the current reference whenever a visitor is ready to act.

• Product identity and category
• A stable image for comparison
• Approximate USD catalog value
• QC or try-on signals only when supplied

A fixed edit makes site errors reproducible

Stability helps with quality control. Category covers can be checked against the products behind them, brand exclusions can be tested across every generated page and a broken filter can be reproduced against the same set of records. If the selection shuffled on every refresh, the same bug could appear and disappear without a code change.

The goal is not to make the catalog look larger or more active. It is to make the current edition understandable and auditable. The About page records this project’s editorial review date. The spreadsheet also shows the latest update timestamp supplied by a catalog record; that source timestamp is not a claim that we inspected every listing.

When the spreadsheet should change

A new build is appropriate when the category mix changes, data errors are corrected, destination records materially change or a seasonal edition is deliberately replaced. A new build alone does not prove that every item was manually reviewed. Material editorial changes should be documented in a dated note rather than implied by a newer source timestamp.

Between those reviews, visitors get a consistent product-research surface. At the moment of purchase or parcel planning, they should leave the snapshot and verify the current destination information instead of treating the fixed page as a live checkout.