Online Service
Quality / Proof

Operational proof for Apple-category sourcing.

LiuDao should prove stock, condition, packing, and service reliability with clear media, route wording, and team-confirmed commercial terms.

5P0 proof groups
ComingLive media
4Media groups
ProtectedSensitive details
Proof hub

Turn trust into a repeatable proof system.

The Trust page should not be a gallery of random warehouse photos. It should show the product, packing, and service details buyers need to make decisions.

Buyer-facing lineShow buyer-relevant product, route, and service details only.
Can publish

Make real proof visible.

Product, package, warehouse, checking, packing, dispatch, or permissioned social proof that helps buyers understand the route.

package label contextwarehouse overviewpacking workflowpublic social link
Prepare first

Prepare before showing.

Useful proof should focus on the buyer route and avoid private business context.

serial or IMEItracking labelsupplier markcustomer name
Never publish

Keep private.

Customer-private, supplier-private, pricing/cost, staff workflow, raw chat, or identity material.

raw customer chatinvoice valuesupplier sourceinternal checklist
P0 asset checklist

Capture these proof groups before the first serious public launch.

This keeps the site honest: no decorative claims, no private business material, and no route promises the team has not confirmed.

P0Product proof
P0

Packaging front, back, seal, and label detail

Show what the buyer can inspect before quote confirmation.

Capture
  • outer box front/back
  • seal state
  • specification label
  • carton context
Can show
  • package views
  • route and model family
  • condition label context
Keep private
  • full serial/IMEI
  • supplier/channel labels
  • private pricing marks
P0Open-box proof
P0

Device, tray, accessories, and condition examples

Useful for used, ASIS, ASIS+, locked, and CPO/refurbished routes.

Capture
  • device front/back
  • tray/accessories
  • screen/body condition
  • representative issue examples
Can show
  • honest condition examples
  • included accessory state
  • route-safe condition notes
Keep private
  • unique identifiers
  • customer notes
  • private batch IDs
P0Warehouse
P0

Stock organization and checking area

Show operational scale and orderliness without exposing supplier or customer details.

Capture
  • shelves or trays
  • sorting area
  • checking area
  • non-sensitive stock context
Can show
  • organized storage views
  • team workflow context
  • carton handling views
Keep private
  • supplier labels
  • customer names
  • private stock notes
P0Inspection
P0

Condition and specification checking

Show the checking process behind route-specific quote wording.

Capture
  • checking desk
  • condition check
  • label/spec check
  • route-specific check moment
Can show
  • checking process overview
  • condition proof
  • category context
Keep private
  • device identifiers
  • private checklist notes
  • supplier marks
P0Packing
P0

Checking, sorting, carton, and dispatch preparation

This is a core trust signal for cross-border buyers and wholesalers.

Capture
  • sorting
  • carton preparation
  • label area
  • dispatch preparation
Can show
  • packing workflow
  • carton handling
  • non-sensitive route context
Keep private
  • tracking numbers
  • order IDs
  • private destination details
Existing mobile price board screenshot
Current Price Board signal

The price board gives buyers a factual starting point.

The new site should use the same-day stock and price signal as a buyer-facing starting point, then add richer proof around product condition, packing, and order handling.

Product and package proof

Packaging front/back, labels, seal close-ups, open-box and accessory shots.

Packing and dispatch

Checking, sorting, carton, labeling, and dispatch summaries.

Privacy line

Serials, customer names, supplier marks, private deal values, and private labels stay out of buyer-facing pages.

Social proof

Only permissioned customer-visit media and public social accounts belong on the buyer-facing site.

Trust system

Borrow the structure, make the proof operational.

LiuDao should make quality visible by showing product, warehouse, inspection, packing, dispatch, and customer-visit proof in a buyer-ready format.

Route clarity

New, used, ASIS, locked, and CPO are not mixed together.

Each route needs different proof, risk wording, and quote confirmation.

Product condition

Condition claims are backed by clear product media.

Packaging, labels, open-box shots, and condition checks carry more trust than generic product renders.

Packing proof

Buyers can see how orders are prepared.

Sorting, checking, carton preparation, and dispatch proof should focus on buyer-relevant details.

Team confirmation

Final terms stay team-confirmed.

Stock, price, payment, delivery, warranty, and financing terms are confirmed per order.

Route matrix

Every Apple route needs different evidence and different limits.

This keeps the website credible for serious buyers and prevents overpromising around condition, locked devices, CPO wording, warranty, logistics, or financing.

Brand new

Outer box front/back, seal state, label detail, version/region, memory, color, carton context.

Do not imply official authorization unless legally verified.
Used

Open-box device, screen/body condition, battery or check status when available, accessories if included.

Show honest condition evidence; avoid beauty-only photos.
ASIS / ASIS+

Condition bucket, visible issues when safe, repair-buyer notes, batch-level examples.

No warranty outcome or repair success promise.
Locked

Lock-state wording, destination risk notes, condition proof.

No unlock promise, no unsupported compliance claim.
CPO / Refurbished

Package evidence, refurbished/CPO wording basis, open-box proof, after-sales boundary.

Do not blur CPO, refurbished, and used routes together.
Order proof flow

Make the service process visible before the buyer commits.

The site should show how a request becomes a team-confirmed quote and shipment path while sensitive deal details stay out of buyer pages.

01

Request intake

Buyer sends model, condition route, quantity, destination, contact method, and service needs.

02

Stock signal

Price Board rows provide a factual signal before final confirmation.

03

Proof check

Team checks product, label, condition, and packing context before the next buyer step.

04

Packing path

Checking, sorting, carton preparation, and dispatch route are confirmed around the order.

05

Handoff

Logistics, payment, and after-sales wording are handled through team-confirmed follow-up.

Next proof groups

Secondary proof groups can phase in later.

Dispatch, permissioned visit, and public social proof are useful, but the first launch should focus on product, warehouse, inspection, and packing proof.

DispatchProof slot

Carton and forwarding handoff proof

Use category and route context, not private logistics documents.

Buyer-visible materialProduct, package, and handling views
Use: Trust / Services
Customer visitProof slot

Permissioned visit or inquiry moment

Use only if permissioned and privacy-safe. Otherwise keep this for a later phase.

Buyer-visible materialProduct, package, and handling views
Use: Trust / Social proof
Social proofProof slot

Social account and public post proof

Link only to public social channels and permissioned posts.

Buyer-visible materialProduct, package, and handling views
Use: Trust / Footer / Help
Next step

Turn proof into a quote-ready buyer path.