How often is a DHgate spreadsheet actually updated?
Direct answer
Update frequency varies by list, and the honest answer is that the price column ages faster than the link column. A working link can point at a repriced listing within days, while a dead link may sit untouched in a row for weeks. Measure the list rather than trusting a stated cadence: sample ten rows at random, re-resolve each one, and count how many prices have moved.
Why
- Prices drift on their own. Sellers reprice when a quantity tier changes, when freight is renegotiated, or when a coupon window opens and closes, which is why the desk reviews coupon parameters on a thirty-day window while weight parameters are reviewed on a hundred-and-eighty-day window. Two figures inside one row can therefore have very different shelf lives.
- A stated cadence describes intention rather than practice. A list that says it is checked weekly usually means new rows are added weekly and old rows are re-resolved rarely, because new rows are what bring readers back. The way to test the claim is a sample drawn across the list's own order, not across its most prominent rows.
- Link health and price health decay at different rates, so they need separate counts. Counting dead links measures maintenance. Counting price moves measures freshness. A list can score well on the first and badly on the second, and only the second number decides whether a row's cost can be used in a budget without re-checking it yourself.
- A reader can measure a list at almost no cost. Ten rows sampled at random across the list's own order, re-resolved one at a time, produce two counts: how many links still resolve, and how many prices have moved. Those two figures describe the list better than any statement about its update schedule, and the same sample can be repeated a month later for a decay curve.
When this answer flips
- The row carries its own check date and that date sits inside the current review window for a cost parameter. A dated row is falsifiable, which makes it more useful than a fresher row that carries no date at all, because you can decide for yourself whether the figure is still inside its window. A row dated this month, inside a thirty-day cost window, is doing exactly what this desk does with its own parameters.
- The price that matters to you is a quantity-tier price rather than a single-unit price, since tier prices move less often than single-unit prices. The figure you actually pay on a multi-unit order can be the more stable number on the page, even while the headline figure beside it moves every few weeks. Multi-unit pricing is usually agreed per parcel rather than per listing revision, which makes it slower to move than a single-unit figure.
- You are reading the list for identity rather than for cost, using it to find a build and then pricing that build yourself through the cost waterfall. Freshness matters far less when the row is a pointer to a factory output rather than to a number you intend to pay. What then has to be current is the build itself, not the figure printed beside it.
Three things to do next
Sources and checks
- Public community thread — Rows re-resolved by readers at intervals of one week to one month, with the outcome of each attempt notedn=36
- Editor analysis — Sampling method of ten rows set so a reader can repeat it without tooling and compare two countsno sample
- Platform published rule — Quantity-tier and coupon behaviour as published by the platformno sample
Last checked · next review due · status current.