What should I send first?
Send model, storage if known, condition route, quantity, destination, timing, and contact method.
Find the right LiuDao path before sending a request.
Use help topics to understand stock signals, quote details, product conditions, logistics, payment discussion, and after-sales boundaries before contacting the service desk.
Search topics such as ASIS, locked, CPO, logistics, payment, reserve...
Help topics
Topic cards should answer the next action, not just explain terms.
Each card routes the buyer into Price Board, Guides, Compare, Customer Service, or Request Quote.
Current stock and price
How to read stock signals and when to request team confirmation.
Open Price BoardQuote request
What to send: customer type, product, model, condition, quantity, destination, and contact method.
Request QuoteCondition and grading
New, used, ASIS, ASIS+, locked, CPO, and refurbished routes need different proof and wording.
Read guidesLogistics and forwarding
Destination, timing, packaging, carton, and forwarding details are confirmed per request.
Ask service deskPayment discussion
Payment path and related service needs are handled after quote and order details are confirmed.
Start serviceWarranty and after-sales
Warranty, return, and after-sales wording depends on route, condition, and order agreement.
Compare routesASIS / locked / repair routes
Repair and locked-device requests need careful route framing and no unsupported claim.
Read comparisonSold out, reserve, preorder
Unavailable products can still become reserve interest or alternative matching requests.
Send requestSupply and partnerships
Bulk stock, mixed-condition batches, ASIS routes, logistics, or channel cooperation can start with a concise request packet.
Open SupplyTop questions
Set expectations before the service desk takes over.
Are public prices final?
They are stock signals. Send quantity and destination so the team can reply with the current quote and service terms.
Can I ask about ASIS or locked stock?
Yes. The request should include buyer route and destination so the team can confirm wording and risk.
Where does my request go?
The website should prepare a structured request packet for the service desk and later human follow-up.
Response promise
The public site should be fast and careful at the same time.
The experience should feel responsive, but the wording must still leave commercial terms for team confirmation.
Freshness first
Show update date and route to confirmation when the signal is stale, sold out, or unclear.
Quote clarity
Collect the fields needed for a useful quote instead of forcing a generic contact form.
Proof before claims
Use product, packing, inspection, and dispatch evidence that matches the buyer route.