What does "current" mean here?
Current means "answering when you last looked", and nothing more. A status in this ledger records a response at a recorded time. It is not a stock notice, not an authenticity check and not a promise about next week. The 2026-W39 table was checked on 29 September 2026, and that date is part of the answer.
So a current listing has three parts: the marketplace address, the date you confirmed it, and the item identifier. Anything a sheet adds beyond those three, such as a price, a batch label or a note that photos exist, is a memory of how the page looked on the day somebody typed it.
Does a dead wrapper mean a dead item?
No, and the latest snapshot is the cleanest demonstration of that. Thirty-one wrapped addresses were requested and every one of them failed at the network level. Rebuild the same thirty-one from the source marker inside each one, and all thirty-one answered normally. The layer in front died while the listing behind it stayed up.
Treat a dead wrapper as a routing problem rather than as a verdict on the goods. The identifier inside the address is the part that survives, and it is the piece a marketplace still recognises long after the wrapper around it stops answering.
Which address should I paste?
Paste the marketplace address. Sample 2026W39-014 carried item 7577045115, and its rebuilt form is an ordinary weidian.com listing address. Platform order boxes take marketplace addresses; a wrapped ACBuy address fails before any platform ever sees it. If a rebuilt address refuses to open for you, run it again an hour later before you change anything in the row.
Keep both addresses in the row. The wrapped one is your trail back to where the row came from, and the rebuilt one is what you act on. The legacy link resolver turns a whole pasted block of the first into the second, and it shows you the output before you use any of it.
Can I search by image instead?
Reverse-image search is a normal move and worth using, but it answers a different question. It finds goods that look like the goods in your picture. It does not tell you whether the address in your sheet still opens, and it cannot confirm that the page you are about to paste is the page the row was written from.
Use it as a second route to an item, then close the loop yourself: take whatever listing the image search surfaces, read the identifier on it, and compare that number with the one stored in your row. Same number, same listing. A different number means you have found a lookalike, which is a new row rather than a repair of the old one.
What if the seller changed the listing?
Sellers relist, split one product into several, and retire items without notice. When that happens the identifier usually stops working while the seller keeps trading. The rebuilt address then returns 404 or 410, or it answers and lands somewhere else, which this ledger records as gone or as moved.
Neither reading is a fault in your sheet. A stored row describes a listing as it was, and a seller editing it is ordinary commerce. What you can do is search the identifier on the marketplace, read the brand and title you stored against what comes back, and decide whether a replacement is worth a new row.
What the six add up to
Six questions, one habit: rebuild, confirm, date it. The wrapper was a routing layer that stopped working. The identifier inside it still points at a listing. Whether that listing is current is something only your own request can tell you, and the answer starts ageing the moment you stop looking.
Two assets in this site cover the whole loop. The legacy link resolver rebuilds a block of addresses, and the platform ledger says which platforms are listed as taking orders at all. Everything else in the row is context. Keep it, date it, and never let it outrank a check you ran yourself.