The snapshot is a product-discovery dataset. It supplies searchable titles, categories, images, price estimates and available QC counts, while current listing details remain the responsibility of the destination page.
What is indexed for product discovery
The local dataset gives each catalog entry a stable product slug and combines the available title, brand, category, price information, images, QC-photo count and update timestamp. The interface turns those fields into search results and focused category pages.
- Product title and brand label
- Category and stable page path
- Available catalog images
- Estimated USD price or range
- QC-photo count when supplied
- Destination link for current listing details
Questions the snapshot can answer well
A saved catalog works well for discovery questions: which categories exist, which wording appears in titles, which products have extra images and which listings appear comparable at a glance.
Because the data is saved, the same search can be reviewed again without the result set changing simply because the development server restarted.
The spreadsheet page supports broad search and filters, while category routes create stable landing pages for narrower product intent. Blog notes explain patterns and changes in the dataset; guides explain how to use it. This gives each page type a separate job.
Questions it cannot settle by itself
The snapshot is not a checkout system and is not live inventory. It cannot certify authenticity, guarantee quality, confirm fit or promise that a particular option is still available. A catalog image and QC count are research signals, not product testing.
Planned updates instead of build-time fetching
A normal site build reads the saved local data. Products change only when the separate catalog-fetch command is intentionally run and its output replaces the saved snapshot. This separates publishing from data collection and makes changes easier to review.
Before a refresh is published, titles, images, category coverage, unusual price values and a sample of destination links should be checked. Large differences deserve an explanation rather than being presented as unexplained freshness.
The goal is traceability: readers can identify the snapshot date, repeat a search against the same saved data and understand which details still require live confirmation.
Catalog fields and their research value
| Saved field | Supports | Does not prove |
|---|---|---|
| Title and brand | Keyword and model discovery | Exact version or authenticity |
| Category | Focused browsing and internal linking | That every source label is permanent |
| Image | Visible-shape comparison | Material, fit or condition |
| USD estimate | Rough relative price research | A final checkout total |
| QC-photo count | Finding records with extra images | Quality certification |
How this note was prepared
This article is based on the product fields and navigation available in the locally saved RizzitGO catalog snapshot collected on October 6, 2026. It describes catalog behavior and research methods; it does not claim hands-on product testing, live inventory, quality certification or an official relationship with RizzitGO.
The conclusions are limited to fields visible in the saved dataset. Current options, availability, pricing and complete product information should be checked on the destination listing.