Why RizzitGO Spreadsheet Counts, Prices and Availability Change

RizzitGO's documented goods-detail response includes stock quantity, sales count, a base price, original price and SKU-level quantity and pricing. Keyword results also contain discount state and discounted price fields. These values describe a source listing at a particular response time, not a permanent row carved into a spreadsheet.

A color or size SKU can disappear while the parent listing remains available. A promotion can change the displayed price without changing the goods ID. Sales data can increase between refreshes. Any directory that stores those fields necessarily begins aging as soon as the source changes.

The Open API troubleshooting notes say the server uses live prices when creating a purchase and advises partners to quote first, then pass the returned amount promptly. That is strong evidence that a previously captured directory price should be presented as an estimate rather than a guaranteed checkout amount.

The same distinction applies to availability. A product card can help someone discover a listing, but only the current destination and current transaction flow can show the latest option and payable amount.

Independent indexes commonly exclude unusable rows, collapse duplicate slugs, restrict image hosts and require enough information to build a useful page. Another directory may keep every imported record. Two sites can therefore begin from related source material and publish different totals without either count describing the entire marketplace.

A falling count can even reflect cleanup: duplicate links removed, empty products excluded or sold-out records retired. A rising count might reflect a broader source, looser inclusion rules or a newer pull. Without a timestamp and methodology, the number alone says very little about quality or freshness.

The keyword-search response separates base price, original price, discount state and discounted price. That structure allows one goods ID to remain the same while its promotional context changes. A cached card can therefore show a price that was accurate when collected but no longer reflects the current discount state.

The SKU layer adds more variation because individual options can carry their own price and quantity. A directory that stores only one flattened price loses the distinction between a parent listing, a selected variant and a temporary promotion. That does not make the stored number useless, but it does make the word estimate important.

Currency presentation introduces another timing issue for independent sites. If a directory converts a CNY figure for easier comparison, exchange-rate movement can change the displayed estimate even when the source price remains fixed. The conversion method and snapshot date should therefore be separated from the seller's original amount.

RizzitGO's version history shows that the available structure has evolved. Version 2.3 added SKU and specification information to goods detail, version 2.5 added a freight estimate endpoint and version 2.10 added keyword search. An integration built against an earlier contract may hold fewer fields even when it references the same goods ID.

This is another reason two spreadsheet-style sites can disagree. One may refresh only product rows, while another also imports SKU detail or QC completion time. One may rebuild every page after a schema update, while another keeps older cached rows until their next scheduled refresh.

Schema growth should not be confused with retroactive verification. More fields can improve context, but they do not automatically correct old titles, confirm inventory or turn marketplace descriptions into platform guarantees.

This finder builds from a saved catalog snapshot and displays its refresh date. It removes duplicate product slugs and incomplete records before generating category, brand and editorial pages. Its totals should not be described as the official RizzitGO inventory or compared one-for-one with a RizzitGO partner API response.

The SEO value of a directory comes from useful, stable pages and transparent context—not the largest number in a headline. A smaller index with clear sources, canonical URLs and meaningful category coverage can be more trustworthy than a larger set of thin or repeated rows.