01 / REQUEST DEFINITION
A useful request identifies product type, exact model reference where relevant, quantity range, acceptable condition, destination country and preferred timing. It also records whether original accessories, retail packaging, region-specific plugs or documentation are mandatory. A broad message such as ‘send your phone price list’ transfers too many decisions to the supplier and makes comparison unreliable.
02 / SOURCE REVIEW
Potential supply is reviewed against the request rather than treated as interchangeable stock. Model suffixes, memory, colour, regional configuration, voltage, plug type and packaging can change whether an item is suitable. Availability and pricing remain subject to confirmation because a wholesale enquiry is not a reservation.
03 / VERIFICATION SCOPE
The parties agree what can reasonably be checked before commitment or dispatch: count, external condition, model identity, serial capture, accessory presence, seal status or sample functional checks. Not every batch supports every check. The agreed scope should state sampling levels, evidence format and treatment of exceptions.
04 / CONSOLIDATION
When a request contains several product lines, the consolidation plan should identify how cartons are labelled, separated and reconciled against the packing list. Mixed lots require stronger controls because a quantity mismatch in one line can remain hidden inside a correct overall carton count.
05 / DISPATCH HANDOFF
The final stage confirms packing method, carton count, measured weight and dimensions, destination details, commercial documents and carrier handoff. Estimated windows begin only after the relevant commercial and operational conditions are confirmed.
06 / EXCEPTION RECORD
Damage, substitution, missing accessories, packaging variation or count discrepancy should become an explicit exception. The buyer can then accept, reject or revise the affected line without losing the history of the decision.