The five dimensions used here
The first field is whether a platform is accepting orders. This ledger records that from the platform page or a directory object page, with a checked date, and treats silence as silence rather than as a yes. Rows marked as not verified stay that way until something readable turns up, which is why the count of platforms you can act on today is smaller than the count of names you will meet. Each field also carries a different kind of evidence, and mixing them is what makes a platform table look more decisive than it is.
The second field is whether the thing you hand over is a wrapped address or the marketplace listing behind it. The rebuild from a wrapped address to that listing is arithmetic, not a platform service, so every platform accepting marketplace addresses accepts the result. The wrapped form itself is a different question, and the honest answer for most platforms is that this ledger has not tested it. The distinction sounds academic until a row refuses to rebuild.
The third field is the photo set, recorded here as whether photos are included, partly included, or not verified. That field matters because warehouse photos are the only point in the chain where you see your own item before it ships. A platform that includes them changes what you can decide; a platform that charges for them changes when you decide it. Either way the photos are about your item and not about the platform, which is worth remembering when a comparison turns them into a score.
The fourth and fifth fields are the two this ledger refuses to fill from secondhand sources: fee terms and storage terms. Public comparisons describe storage of 100 days at one platform and 90 at another, and a fee of nothing at two more, and those descriptions stay descriptions here. Both settings are per account and move without notice, so the figure that applies to you is the one on your own account page rather than the one in somebody else's table. Reading a description is still worth doing, as long as you read it as a description.
The full grid
Two distinctions are worth carrying out of this grid. The first separates a platform that is closed from one that is unverified: the first has a recorded end, the second has a gap where a record should be. The second distinguishes a platform this ledger could read from one it could only place on a list. A closed platform ends the conversation, while an unverified one asks you to check a page before you plan around it.
Nine names come out of the directory with order-taking stated: Kakobuy, Sugargoo, Superbuy, Joyagoo, Oopbuy, Litbuy, Loongbuy, Eastmallbuy and Lovegobuy. All nine are recorded as accepting a rebuilt marketplace address, which is uniform for a structural reason rather than a flattering one. The rebuild happens before any platform sees the address, so this column says nothing about how well a platform handles an order once it has one. It says only that a rebuilt row will not be turned away at the door.
Two of the directory names need care. ACBuy and AllChinaBuy are one operation under two spellings, and both are closed: purchasing stopped on 12 June 2026, a planned restart on 1 July did not bring ordering back, and by August the storefront was down. A grid listing them as two rows counts one closed entry twice, which is how a platform list grows without gaining anything. The platform ledger keeps both spellings so that people searching either one land somewhere accurate.
Outside the directory sit CNFans and Hoobuy, carried here as accepting orders but flagged as still needing verification. Their photo and storage fields mix recorded descriptions with unverified gaps, which is the honest shape for a platform whose terms this ledger has not read directly. PandaBuy and Mulebuy complete the picture, and they are not listed as history for its own sake: sheets compiled over a long period mix wrappers from platforms that stopped accepting orders at different times, and the rebuild is the same job whichever wrapper a row carries.
Reading each dimension
Order-taking is the only field that decides whether anything else matters. A platform with excellent storage terms and no purchasing is a page, not an option. This is also the field that ages fastest, so read it as a dated observation rather than a property: the row says what was true on the day it was checked, and the ledger carries that date beside every row for exactly this reason. A row with no date is a rumour with a table around it.
Address handling reads as uniform across the nine, and the practical question hides inside it. Since the rebuild happens before the address ever reaches a platform, the thing worth checking is not whether the platform speaks the wrapper format but whether the rebuilt listing it points at still answers. That check happens on your side, with the legacy link resolver, and its result is the only one that speaks about your sheet. Platforms cannot report on rows you have not handed them yet.
Photos divide the group in a way that no comparison table can settle for you. The ledger records one platform as partly including photo sets and several as unverified, and the difference between those two labels is not quality but evidence. Open the order page you are about to use and read what the photo set covers there, because that text governs your order and an article does not. Photo terms are also the field most likely to differ between two accounts on the same platform, which is why the order page beats every summary.
The group nobody can describe is the last thing to keep in view. Hipobuy, Orientdig, HubbuyCN, OOTDBuy, BaseTao, CSSBuy and Ponybuy are recorded here without an operating claim, because the names appear in comparisons while their terms do not. An empty field is a fact about the checker rather than about the platform. A reader who wants terms for any of these has to make the trip this ledger declined to skip, and that trip is two minutes long.
Which combination fits your case
Start from the constraint rather than the platform. If your sheet is mostly one marketplace, filter on whether that marketplace is accepted today, since support has changed during 2026 and a comparison written in spring may describe a set that no longer exists. If your sheet mixes wrappers from two closed platforms, filter on nothing: the rebuild is identical throughout.
For a small first parcel, the photo set outweighs almost everything else. Warehouse photos are the point where you can still accept or reject an item while sending it back is cheap. The ledger records several platforms as accepting orders with photos included, and reading that field against your own order page beats reading it in a table. A first parcel is also the one where a rejected item costs the least to fix, which is why the photo field matters more here than anywhere else in this grid.
For items you already own and cannot decide about, storage is the constraint that decides. A rebuilt item tends to be something you have been considering for months, so it arrives at a warehouse and sits. This is where a description of long free storage becomes relevant, and where reading the terms on your own account beats reading them anywhere else, because the clock that applies is the one your account was opened under. That clock is also the field most often quoted and least often true for a given reader.
For a mixed haul, the deciding field is none of the five on its own but the sequencing. Rebuild the whole sheet, confirm the results, and only then open an order. Carry the rebuilt addresses in plain text beside the original wrapped ones, so a later change of platform costs you an afternoon. Read the grid as five observations, which is less satisfying and more useful.