What is a DHgate spreadsheet?
Direct answer
A DHgate spreadsheet is a shared list of individual DHgate listings, circulated as rows: each row holds a link, a short label, a price and sometimes a size or colour note. It is not a shop and it holds nothing itself. The row is a pointer written on a date, and the page behind it can change, die or resolve to something else entirely. Treat every row as a lead to judge rather than as a product page.
Why
- A row is a copy of a page, not the page. The label and the price were typed by whoever maintained the list, and neither is corrected when the seller edits the listing underneath. Two rows can describe the same listing with different words, and one row can keep resolving to a page that now sells an unrelated item at a similar price point.
- Lists exist for different reasons, and the reason decides what a row can tell you. A community list is built for coverage and breadth. A curated list is often paid for the traffic it sends. A personal list reflects one person's interests and one person's order history. None of these are dishonest, but each one decides which rows get written and how often they are re-checked.
- The page you land on has its own life. Sellers retire listings, relist the same build under a new identifier, and reuse one page as a payment shell for several products at once. Reading that page as though it were the row's own photograph is where most mismatches begin, and the fix is a check on the page rather than a message to the list owner.
- Rows are written at a moment of enthusiasm. A row appears when somebody finds a build worth sharing, which is exactly when a listing is new, the price is at its lowest and the seller is answering messages quickly. Six weeks later the same attributes can describe a later run at a different price, and nothing inside the row changes to announce it. The lag is structural rather than careless, because re-resolving every row costs more time than most lists can spend.
When this answer flips
- The list states who maintains it, when each row was last resolved, and whether the maintainer takes a payment for referrals. A dated, attributed row is a different object from an anonymous one, because the stated date can be tested against the live page in about a minute. It still needs the same verification, but the claim is falsifiable, and a falsifiable claim is what separates a desk from an inbox.
- A row resolves to a storefront page rather than to a single listing, and that storefront carries a stable set of items whose labels match the row's wording. That points at a maintained catalogue rather than at a shell, which moves the question from identity to condition. Read the storefront's own pages before the row, because the storefront is the part that survives relists.
- You have ordered from the same row before and still hold the box label, the size tag and the photographs from that delivery. A recorded earlier delivery turns the row into a repeat-order question, where the comparison is against your own earlier evidence rather than against a seller's description. Compare markers rather than memories, because a recollection of a build fades faster than the photographs of it do.
Three things to do next
Sources and checks
- Public community thread — Threads where a shared row was described as the product itself, with no distinction drawn between the row and the live pagen=42
- Editor analysis — Row anatomy defined from lists in circulation during 2025 and 2026, counting the fields a row usually carriesno sample
- Platform published rule — Listing edit and retirement behaviour as published by the platformno sample
Last checked · next review due · status current.