New vs Used vs ASIS vs CPO
Choose by buyer type, proof needs, warranty expectations, and risk tolerance.
Compare condition routesOperational comparisons for Apple-category buying decisions.
Compare condition, version, lock-state, model, and destination routes before asking the LiuDao team for a quote. The goal is cleaner requests, not generic product opinions.
Comparison library
Compare the route the buyer is really choosing.
The page should answer what route fits the buyer, what proof is needed, what risks must stay clear, and where the next action goes.
HK version vs US version vs China version
Frame version choice around destination, buyer preference, packaging, and route confirmation.
Compare version routesLocked vs Unlocked
Separate route language, destination risk, and unsupported claims before a quote discussion.
Compare lock routesiPhone 15 Pro vs 15 Pro Max
Compare demand, storage mix, stock signal, and quote preparation details.
Compare model routesCondition route matrix
The strongest comparison is not specs; it is route fit.
Condition choices should show who the route is for, what proof is expected, and what claims stay confirmation-only.
RouteBest forProof neededBoundaryAction
Brand newWholesalers, channel sellers, selected retail requestsPackage, seal, label, version, carton contextAvoid official-authorization or fixed-availability claimsCheck current stock
UsedRepair stores, resellers, destination-aware buyersCondition photos, screen/body state, batch examplesCondition and warranty wording need clear confirmationRequest condition proof
ASIS / ASIS+Repair buyers and parts-sensitive channelsCondition bucket, visible issue examples, batch notesNo repair outcome or warranty promiseSend repair route
CPO / RefurbishedChannel buyers needing cleaner retail presentationPackage and route wording basisDo not mix with used or unofficial claimsReserve interest
Decision cues
Use comparison pages to qualify the inquiry.
A comparison page should quietly collect the facts the service desk needs: buyer type, destination, quantity, condition route, timing, and contact method.
Buyer type
Retail and reseller buyers need clean package/proof language.
Repair buyers can accept more condition detail and route risk.
Destination
Version and lock-state questions matter more for cross-border routes.
Local or familiar buyers may care more about speed and quantity.
Quantity
Small requests can start with Customer Service and a narrow model target.
Bulk requests should use Request Quote with model mix and timing.
Proof level
High-trust buyers expect package, label, inspection, packing, and dispatch proof.
Repeat buyers may only need same-day stock signal and team confirmation.
Page rule
Comparison content should always end with a service action.
The buyer should never finish a comparison page wondering where to send the exact model, condition, quantity, and destination.