The observed values
Across the publicly visible wrapped addresses collected for the 2026-W39 window, the marketplace marker took exactly one value: WD. Thirty-one records, thirty-one WD. That is the whole observed set, and no second value is described here, because none was seen.
A wrapped address follows a shape: the platform product path, then the item ID, then the source marker, then a short trailing code. Reading it left to right tells you which marketplace to rebuild towards. For WD that marketplace is Weidian.
Sample 2026W39-014 carries item 7577045115 and a WD marker. Sample 2026W39-022 carries 7577064689 with the same marker. Two rows taken from different ends of the set show one pattern, because in this set the pattern does not vary. Pick any other row and the reading is the same.
Where the data comes from
The set was collected from public sheet pages, one address at a time, in the same window as the rest of the weekly snapshot. Hosts were contacted with at most two concurrent requests and a gap between calls, under an 8-second timeout, without cookies or account credentials.
Each address was opened as written, then rebuilt from its marker and opened a second time. The first request failed for all thirty-one records. The rebuilt request came back with a normal response for the same thirty-one records, and requests ran at most two at a time so a slow answer was never mistaken for a failure.
For this marker the rebuild target is a Weidian item page built from the item ID alone: https://weidian.com/item.html?itemID={item ID}. Replace the placeholder with the ID taken from the wrapped address and the address is complete. Nothing else in the wrapped address has to be carried across.
How to read the table
The useful columns are the sample ID, the item ID, the source marketplace and the status. The marker column is the one people skip, and it is the column that decides where a rebuild has to point. Read the marker before you read the status.
A status of RESOLVES means the rebuilt source address answered during that window. It does not mean the item is available, that the seller is reliable, or that the listing will be there next month. The five status words are defined on the checking method page, which is the right place to settle an argument about what a label proves.
For the rebuild itself, use the legacy link resolver. It takes a wrapped address, reads the marker, and hands back the marketplace address that marker points at, which is what you paste into a platform that is accepting orders. Run it on one row before you run it on fifty.
Explaining the gaps
One marker value across thirty-one records is a narrow observation, and narrow is the honest word for it. The set came from sheet pages that were publicly readable, which is not the same thing as a random sample of everything ACBuy ever wrapped.
Other markers could exist. This site has not observed one and does not assume what an unobserved value would point at. If your address carries something other than WD, rebuild it only when the destination of that marker is documented somewhere you can check; otherwise keep it as a record and move on.
Two limits belong next to the table. Addresses that the host stopped accepting are left out of the count rather than written up as failures, and the window describes a single moment. A marker that rebuilds cleanly this period can behave differently in the next one, which is what the weekly snapshots exist to catch.