Taobao, 1688 and Weidian: Reading RizzitGO Spreadsheet Source Data

RizzitGO's goods-detail and QC endpoints both require two identifiers: goodsId and source. The documentation maps 1 to Taobao, 2 to 1688 and 3 to Weidian. Keyword search additionally documents 5 for Xianyu. This design shows that a numeric ID cannot safely be interpreted outside its marketplace namespace.

The returned record preserves goodsSource alongside the title, detail URL, image, price, stock, sales and SKU fields. A directory that drops the source field loses part of the product's identity and makes later refreshes or comparisons less reliable.

Alibaba describes Taobao as China's leading retail e-commerce platform, launched in 2003 and built around a broad assortment of consumer goods and services. Its official profile emphasizes discovery across stores, brands, daily necessities, imported products and idle goods within the wider Alibaba ecosystem.

That retail breadth helps explain why a Taobao-derived row may look consumer-ready: one listing can include variants, promotional pricing, merchant images and sales context. Those fields remain properties of the source listing and can change after an index captures them.

Alibaba calls 1688 China's leading integrated domestic wholesale marketplace and a product source for Chinese e-commerce. Its official profile says the platform brings together wholesale suppliers across industries and has expanded procurement services beyond its original business-to-business role.

A 1688 listing can therefore carry assumptions that differ from a typical retail product page, including supplier-oriented presentation, quantity context or SKU structures. A low displayed unit price should not be detached from the current option, quantity and seller terms.

Weidian's official site presents the service as an online-store and merchant operating platform with storefront, mini-program, live-commerce and distribution tools. That makes a Weidian link another marketplace record—not a mirror of a Taobao or 1688 listing even when images and product names resemble one another.

For an independent RizzitGO-style index, the most honest presentation keeps the source visible, avoids merging rows solely by image similarity and treats price or sales comparisons as source-specific. Similar appearance can support discovery; it cannot prove that two listings share inventory, seller responsibility or fulfillment quality.

The documented goods-detail response can include a skuList and skuSpecInfoList. SKU records carry identifiers, price fields, quantity, an optional image and property names, while the specification list describes dimensions such as color and size. One parent listing can therefore contain several combinations with different availability or price.

This makes cross-source price comparison more difficult than placing two headline numbers side by side. A displayed parent price may represent one option or a starting point, while the selected color and size can carry another amount. 1688 also has a documented specId field, reinforcing that supplier-oriented variations can be represented differently from a simple retail option menu.

A searchable index can help narrow the field, but it should preserve the destination link so the current SKU structure can be checked where the listing is active. An old spreadsheet row cannot guarantee that the same combination still exists.

The keyword-search section documents source code 5 for Xianyu. The goods-detail and QC sections shown in the same guide list Taobao, 1688 and Weidian for their required source field. That difference should be recorded rather than smoothed over.

It would be unsafe to infer from the search source list that every other partner endpoint offers the same Xianyu coverage. Public API documents define capabilities endpoint by endpoint, and the absence of a source from one contract can matter even when another contract recognizes it.

For publishers, this is a reminder to attach claims to the exact feature being discussed. Saying that keyword search recognizes four source values is supported; saying that the entire Open API handles all four sources in the same way is broader than the published specification.