Source and purpose
Where does the product data come from?
The catalogue is generated from a current product feed and converted into a smaller, site-owned research model before it reaches a page. The API credential is used only during a controlled data refresh and is never exposed in browser code.
The current snapshot covers the 14 product categories listed in the category directory, including shoes, clothing, bags, accessories, sets, belts and perfume. A record is included only when it has a stable slug, product title, category, primary image and update timestamp. Duplicate slugs are removed during generation.
What each visible field means
How “popular” homepage picks are selected
The product endpoint currently does not expose sales, view or save counts. Therefore this site does not claim that its homepage cards are a live sales ranking. The editorial selection favours category coverage, recognizable brand search intent, complete pricing data, recent source updates and product variety. Listings reporting QC are placed in a separate evidence section.
If the API later provides a reliable popularity field, the selection rule can change—but the field name, refresh date and meaning will be documented here before it is used publicly.
Refresh and fallback rules
- Request current categories. Only API-confirmed category slugs can enter the generator.
- Pull a bounded product set. Each selected category receives the same maximum number of records.
- Normalize and validate. Prices are converted to numbers, URLs are parsed, required fields are checked and invalid records are excluded.
- Remove duplicate slugs. A stable product slug can appear only once in the snapshot.
- Compare saved snapshots. New, removed, price-changed and QC-changed rows are calculated from stable slugs and decision-useful fields; a timestamp-only change is not presented as a material catalogue update.
- Keep the last valid snapshot on a temporary failure. The site does not replace a usable catalogue with an empty page when the upstream API is briefly unavailable.
- Display the check date. The header, data summaries and update log show when the current snapshot was produced.
Editorial and indexing boundary
Category pages add original comparison guidance, checklists and search intent; they are not simple copies of API descriptions. Product-detail pages are limited to a small editorial set of QC-backed records with a site-written selection reason, product-specific checkpoints, category context and related internal links. The remaining catalogue records stay in browseable lists rather than becoming thin indexable pages.
Known limitations
- A snapshot can become stale after it is generated.
- QC count does not describe image usefulness or product quality.
- Reference prices exclude international shipping, fees, duties and later changes.
- Images and titles originate upstream and can be revised after the snapshot.
- Brand names are discovery labels, not authenticity findings or endorsements.
