Sample vs replenishment RFQ routing: how Hong Kong desks split Accio Work queues before the first reply
A Hong Kong Alibaba.com desk can lose time by treating every RFQ as the same kind of work. A buyer asking for a first sample needs identity, specification, freight, payment, and approval questions answered before a unit is promised. A buyer replenishing a known SKU may need a fast confirmation of quantity, destination, current price, and available production window. Both requests may arrive in the same inbox, but they should not enter the same Accio Work queue.
The routing decision should happen before the first substantive reply. That does not mean an automated system should make a commercial commitment. It means the desk should classify the thread, assign an owner, preserve the original facts, and send an approved acknowledgement or clarification while the correct queue does its work. The Accio Work workflow is most useful when it makes that boundary visible rather than hiding it behind a fast paragraph.
The first split: sample, replenishment, or unclear
Use three top-level labels:
- SAMPLE: the buyer wants a first unit, pre-production sample, color or material proof, trial quantity, prototype, or a sample before a larger order.
- REPLENISHMENT: the buyer has an established SKU or prior order and wants more of the same approved item, with no material change stated.
- CLARIFY: the message does not establish whether this is a first purchase or repeat order, or it contains conflicting product, quantity, destination, or timing information.
Do not infer replenishment merely because a buyer says “repeat.” Match the claimed item to a stable SKU, variant, approved specification, and account record. “Same as last time” is not enough if the last order is missing, the seller has changed factory or packaging, or the buyer names a new destination. Conversely, do not force a known repeat buyer into a long sample process when the message clearly references an approved SKU and unchanged requirements.
The labels are risk control: SAMPLE creates new evidence and approval work, while REPLENISHMENT is faster but still becomes an exception when price, lead time, destination, packaging, or payment changes.
Capture the routing fields before drafting
An intake card should hold structured fields before Accio Work generates a reply:
- Buyer account and entity name.
- Source thread and requested response time.
- Product family, SKU, variant, and revision.
- Quantity and whether it is sample quantity or production quantity.
- Destination country, city or port, and Incoterm if known.
- Required date and whether it means dispatch or arrival.
- Sample status: first sample, revised sample, approval sample, or no sample requested.
- Prior order reference, if replenishment is claimed.
- Price basis, currency, payment route, and quotation validity.
- Missing facts, hard-stop signals, and named human owner.
Fields should be marked confirmed, estimated, missing, or escalated. A blank field is not permission to invent a value. The RFQ checklist can serve as the visible record for this state. It also gives a desk a common vocabulary when sales, QC, finance, and production look at the same thread.
The SAMPLE queue needs evidence gates
Route SAMPLE to a queue that can answer questions a catalog cannot. The first pass should identify the exact product and configuration, then ask for the missing use, market, artwork, dimensions, finish, quantity, and destination information. QC or product owners may need to confirm whether an existing sample is representative, whether a new sample is required, and what evidence will be supplied with it.
Keep the commercial stages separate:
S1 — Intake. Confirm that the request is a sample and record the requested purpose. Do not call it “free” unless the approved policy says what free covers.
S2 — Feasibility. Confirm sample lead time, tooling or artwork dependency, available materials, minimum sample quantity, and who pays freight, duties, inspection, and any setup cost.
S3 — Approval. A named commercial owner approves price, waiver, credit, or special terms. QC or engineering approves technical claims and evidence. Finance reviews any unusual payment route or refund promise.
S4 — Dispatch readiness. Verify address, consignee, documents, packaging, and approved payment. The first reply can acknowledge the request while these gates run; it should not promise a dispatch date that has not been confirmed.
A safe first response might say: “We can review a sample for the stated configuration. Please confirm destination, quantity, artwork or specification, and intended use. We will return the sample cost, freight basis, and estimated lead time after the product and logistics checks.” That is useful without pretending the answer is already approved.
The REPLENISHMENT queue is faster, not blind
A replenishment request can use a shorter path when the record is clean. Match the buyer’s item to the last approved order or SKU, compare the current catalog revision, and check whether the requested quantity, destination, packaging, Incoterm, currency, and payment terms remain inside the approved matrix.
Use four quick states:
R1 — Match confirmed. The SKU, revision, buyer account, and prior order match. No material change is stated.
R2 — Capacity and price check. Production, stock, MOQ, current price, quotation validity, and lead time are confirmed for this quantity and destination.
R3 — Exception. The buyer changed artwork, material, packaging, quantity band, destination, Incoterm, payment, or deadline. Move the thread to the relevant human queue rather than calling it a routine reorder.
R4 — Ready to reply. A desk lead reviews the approved facts and sends a concise confirmation with conditions and one clear next action.
Accio Work may assemble R1 and R2 facts from approved records, but it should not silently reuse an old price or lead time. “Repeat order” does not freeze commercial conditions. If the last shipment went to the United States and the new request goes to a different market, duties, documents, and delivery terms may change the route.
What happens when the first message is ambiguous
CLARIFY should be a real queue, not a forgotten label. Send a short holding reply with the minimum questions needed to route the work: “Is this for a first sample or a repeat production order? Please share the SKU or prior order number, requested quantity, destination, and required date.” If the buyer has already supplied some of those fields, ask only for the missing ones.
Do not ask a long questionnaire when one distinction will unlock routing. A photo plus “need 20 pcs urgently” might be a sample, a trial order, or replenishment. Ask what the 20 pieces are for and whether there is a prior approved SKU. Keep the original wording attached to the intake card so later reviewers can see why the classification was made.
If the message contains pressure to bypass an approved payment route, alter origin or value, or promise compliance without evidence, apply a hard stop regardless of SAMPLE or REPLENISHMENT. Classification is not a permission level.
The pre-first-reply handoff model
A practical Hong Kong desk can assign roles like this:
- Desk lead: accountable for the first meaningful reply and queue aging.
- Accio Work: extracts fields, suggests the label, drafts a holding question, and highlights missing or conflicting facts.
- Sales owner: approves price, discounts, quote validity, and customer-specific commitments.
- QC or product owner: approves sample representation, technical details, inspection evidence, and change impact.
- Finance or operations: approves payment exceptions, freight assumptions, credits, and unusual refund language.
The services context is relevant when a partner is helping design the queue or training the desk, but the seller should keep decision ownership inside its own organization. An implementation partner can configure handoffs; it should not become an invisible approver of the seller’s commercial commitments.
Set an aging rule. For example, a SAMPLE card waiting on a technical answer gets an owner and a next-check time; a REPLENISHMENT card waiting on current capacity gets a sales or production owner; a CLARIFY card is measured from the time the question was sent. A queue without an owner is another inbox.
Metrics that show whether routing works
Track a few measures weekly:
- Time from receipt to correct queue.
- Time from receipt to first meaningful reply.
- Percentage of cards reclassified after review.
- SAMPLE requests sent without a clear cost or freight basis.
- REPLENISHMENT replies using stale price, stock, or lead-time data.
- Exception rate by SKU, destination, and owner.
- Number of hard stops resolved without an unsafe workaround.
Do not optimize only for reply speed. A wrong replenishment confirmation is worse than a short holding reply. Review both queues for factual accuracy, approval evidence, and whether the buyer knew the next step.
A small operating rule for desks
Before the first substantive reply, answer three questions: Is this a first sample or a known replenishment? Which approved record supports the classification? Who owns the next decision? If the answer to any question is unknown, route to CLARIFY and send an honest holding message.
For teams documenting the process, the pricing reference can help keep fee and payment language distinct from product quotation language. The aliad.hk overview can provide a public context link without replacing a seller-specific quote or approval record.
The goal is not to make SAMPLE slow or REPLENISHMENT bureaucratic. It is to give each request the shortest safe path. Samples need evidence and technical ownership; replenishment needs a current match and capacity check; unclear requests need one precise question. With those queues in place, Accio Work can accelerate extraction and drafting while Hong Kong desk leads remain accountable for what the buyer hears before the first reply.