What to weigh before naming anyone
Begin with the field that decides whether a platform is even usable: does it take a rebuilt source address. A wrapped address is not a shop, and a platform that rejects rebuilt marketplace addresses cannot open anything in your sheet. In the ledger that field is printed per object.
Then read the four fields that carry a value rather than a promise: whether the platform is taking orders, whether it accepts rebuilt addresses, what its QC photo row says, and the date the row was checked. Everything else in the ledger — fee, storage, payment — reads as not verified, for every object in it.
Bring one line of your own before you read anything: the constraint you are actually shopping under. It might be photos you can read before consolidating, a destination, a category, or simply someone who will accept thirty rebuilt rows without a fight. A candidate that ignores your constraint is not a candidate.
Three candidates, three profiles
Kakobuy carries the fullest row of the three: accepting orders, accepting rebuilt addresses, and free QC photos recorded as yes. Its fee, storage and payment notes are all not verified, and no figure for them appears here. More filled fields is not the same as a better service, only a row that can be read further.
Sugargoo shows the same two yes answers and a different storage row: it carries a figure taken from a public comparison page, with a note saying this ledger has not verified it. That is a claim with an owner, not a measurement, and it should be read that way.
Superbuy differs on one printed field: QC photos read as partial rather than yes, so the photo question is one to confirm per item instead of assume. Fee, storage and payment are unverified there too. Three rows, three profiles, one shared limit — almost everything a comparison page would rank them on is missing.
The trade-offs in plain terms
Say the awkward part plainly: this site has not verified the fee terms or the storage terms of most platforms, including all three above. So the usual comparison — cheapest service fee, longest free storage, best payment options — cannot be made here from evidence. Anything you read on those lines elsewhere is a claim you are borrowing.
What can be compared is narrower but real. A yes on QC photos means a photo set exists to read; a partial means the answer depends on the item, so your checklist has to carry the uncertainty. A row with an unverified status cannot even confirm that ordering works today.
Two trade-offs survive that thinning. The first is time: a platform that answers a pasted rebuilt address immediately is worth more to a long sheet than one you have to test row by row. The second is reviewability: a row with a printed check date can be re-read later, and a ranking without one cannot.
Matching a candidate to your constraint
Write the constraint as one sentence, then eliminate. If photos before consolidation are the constraint, partial and unverified photo rows are out until you confirm them. If your sheet is long, test acceptance on three rebuilt addresses before committing the other twenty-seven.
Test in the order the money moves. Rebuild three addresses, open each one to see the listing answer, then paste one into the candidate’s order box short of paying. A row that takes it has answered the first question; the rest of the ledger row tells you what remains unknown.
Revisit the pick on the date, not on a feeling. Ledger rows carry a checked date because a platform that accepted rebuilt addresses in September can change its handling later, and the checking method explains what a status word does and does not prove. Two candidates is enough; three is a hobby.