Hong Kong sellers often ask a reasonable question before they renew a storefront, add a service, or turn on a workflow: “Which fee pays Alibaba.com, which fee pays the local partner, and which fee pays for an optional operating service?” A fast answer is useful only when it separates those destinations. Blending them into one “package” makes budgeting difficult, creates avoidable approval risk, and can leave an owner believing that a service invoice is a platform invoice.

This guide is a practical fee map for sellers using an Alibaba.com Hong Kong channel and considering Accio Work or operational help from a local authorized channel partner such as Corpable. It is not a substitute for the current contract, tax advice, Alibaba.com terms, or a written quote. Prices, taxes, promotions, renewal dates, and eligibility can change. The control to keep is simple: every line item should have a payee, a purpose, a period, a tax treatment, and a document that supports it.

Start with three separate buckets

Bucket one: Alibaba.com platform or membership charges. These are amounts owed to the platform entity named in the seller agreement or renewal notice. A Hong Kong seller should check the legal entity, invoice description, service period, currency, payment method, and whether the charge is recurring or one-off. A reseller or consultant should not describe its own service fee as an Alibaba.com membership fee. If the seller is unsure, ask Alibaba.com through an official account or billing channel and keep the answer with the renewal record.

Bucket two: authorized channel or implementation services. A partner may provide onboarding, account-readiness work, catalog cleanup, training, workflow design, campaign assistance, or local operational support. Those services are not automatically included in platform membership. The partner should issue its own scope and invoice, identify the contracting entity, state what is included, and disclose any pass-through cost. A seller should be able to reject an optional service without losing the ability to pay a platform invoice through the approved platform route, unless the underlying contract clearly says otherwise.

Bucket three: optional tools and operating consumption. Accio Work, translation, content production, lead-handling, CRM, creative, inspection, freight, samples, and other services may have separate pricing or usage conditions. Do not assume that a tool name on a proposal means it is a platform fee. Ask whether the charge is a subscription, per user, per task, per campaign, per lead, or a professional-services retainer. Ask what happens when the seller pauses, exceeds a quota, or cancels.

The point is not that one bucket is good and another is bad. The point is that a seller can approve each bucket knowingly. The pricing reference is a useful public starting point for separating fee categories; the actual amount still belongs in the applicable agreement or quote.

Use a fee register before signing or renewing

A one-page register prevents most confusion. For every line, record:

• Payee and legal entity: who receives the money and whose bank or card account appears on the invoice.
• Commercial purpose: membership, implementation, software, content, training, freight, sample, inspection, or another service.
• Period and trigger: annual renewal, monthly subscription, one-time setup, per-use charge, or a milestone.
• Currency and tax: currency, whether tax is included, and which party issues the tax document.
• Refund or cancellation rule: what happens if onboarding stops, a campaign is paused, or the seller does not use the allocation.
• Deliverable or entitlement: account access, listed service, workflow configuration, report, training hours, or a defined output.
• Approval owner: the person who checked scope, budget, and payment route.

Keep a separate column for “platform charge confirmed?” and attach the source document. If a partner proposal uses words such as “official,” “authorized,” or “required,” ask what requirement it refers to. Authorization to provide channel support does not, by itself, turn every partner service into a mandatory platform charge.

A useful control is to require two independent descriptions for bundled work: one sentence describing the platform entitlement and one sentence describing the partner deliverable. If the salesperson cannot split them, the seller should pause and request an itemized quote. Bundling can be commercially convenient, but it should not make the destination of money opaque.

What a transparent seller-facing explanation sounds like

A good explanation is short but specific: “The Alibaba.com membership charge is paid through the platform-approved billing route under the seller agreement. Our implementation fee is a separate invoice for the listed onboarding and workflow services. Accio Work or other usage charges, if applicable, are shown separately with their billing basis. Samples, freight, inspection, and creative work are not included unless the quote says so.”

That language does not promise a price that is not published. It tells the seller what to verify. It also avoids a common mistake: describing a local service fee as if it were a tax, platform levy, or compulsory renewal. If a charge really is mandatory under a particular agreement, show the clause and the payee. If it is optional, say so. If it is conditional, give the condition.

Sellers should also ask whether a “free” onboarding or sample offer has a later trigger. Free may mean no service fee, but it may not cover freight, duties, inspection, tooling, rush work, or a future subscription. Put those exclusions next to the offer rather than in a footnote that the operator will not see during approval.

Where Accio Work fits

Accio Work is best treated as an operating capability with a defined scope, not as a magical synonym for the platform account. An implementation plan should state what the workflow does: for example, organize RFQs, prepare drafts from approved catalog facts, route exceptions, or support a human review queue. It should also state what it does not do: approve unverified prices, make compliance determinations, change payment instructions, or guarantee leads or sales.

Before enabling an Accio Work workflow, ask four questions:

1. Which account, users, queues, and data are included?
2. Is pricing subscription-based, usage-based, project-based, or covered by a service retainer?
3. Who owns the human approval step and the audit record?
4. What is the stop or handoff process when a catalog fact, sample condition, payment term, or destination is uncertain?

The Accio Work overview can help a seller understand the operating context. It should not be used as evidence of a seller-specific price or a promise that every workflow is included in membership. The written commercial document controls.

Questions to ask before paying any intermediary

A Hong Kong seller can send a short due-diligence checklist before approval:

• What is the exact legal name of each payee?
• Which amount is paid to Alibaba.com, and through which official route?
• Which amounts are partner or vendor fees?
• Is the partner authorized for the stated service, and where can that status be verified?
• What service dates and deliverables apply?
• Are taxes, bank charges, foreign-exchange costs, freight, samples, or inspection excluded?
• Are renewal and cancellation automatic?
• Can the seller receive an official receipt or tax invoice for each bucket?
• What support channel handles billing disputes?
• Does any request ask the seller to pay a personal account, unrelated wallet, or off-platform destination?

The final question is a hard stop. A request to misdescribe a payment, split a fee to hide its purpose, or send money to an unrelated personal account should not be “fixed” by better wording. Escalate it to finance and the platform’s official support route. Speed is not a reason to weaken payment controls.

Build the approval workflow around evidence

The seller’s onboarding file should contain the platform agreement or renewal notice, the itemized partner quote, the tool or services scope, the fee register, and the approval record. The onboarding checklist can be used to assign owners for entity verification, billing, catalog readiness, and operational handoffs. It is better to mark one field “awaiting confirmation” than to approve a blended amount that no one can explain later.

The services page is useful for understanding the types of implementation or support work a partner may discuss. Treat it as service context, not as a substitute for a negotiated statement of work. A statement of work should name the output, acceptance point, support window, assumptions, exclusions, and change process.

A monthly reconciliation can be lightweight. Match every bank or card transaction to an invoice, then tag it as platform, partner, tool, or pass-through. Review unused credits and upcoming renewals. If the ledger shows one recurring “Alibaba fee” but three different services are being delivered, ask for a correction before the next cycle.

A simple decision rule for sellers

Approve a fee only when you can answer five questions without guessing: who gets paid, what the payment buys, when it applies, what document proves it, and who owns the dispute. If one answer is missing, request an itemized explanation. If the route is unusual or off-platform, stop and verify independently.

The aliad.hk home reference can provide context for the authorized-channel and operational conversation, but transparency remains a process owned by the seller and its advisors. Keep Alibaba.com charges, partner services, Accio Work or other tools, and logistics or sample expenses visibly separate. That small discipline makes a Hong Kong seller’s budget easier to approve, audit, renew, and explain to a buyer or finance colleague.

Hong Kong export desks do not lose Alibaba.com deals only on Tuesday mornings. They lose them on Saturday nights in São Paulo, on National Day long weekends, and on Christmas Eve when a serious German buyer finally sends the RFQ they sat on for two weeks. The inquiry lands. Nobody replies for thirty-six hours. By Monday the buyer has three other quotes and your store looks asleep.

Coverage is not “someone checks WeChat.” Coverage is a written weekend and holiday plan: who is on, what they may send, what they must escalate, and how Accio Work or any agent layer is fenced so fluency does not become an unauthorised commitment. This playbook is for Hong Kong and Greater Bay Area desks selling through a Hong Kong Alibaba.com entity. It is an operating note, not a staffing pitch.

Why weekend silence is expensive on Alibaba.com

Alibaba.com RFQs are time-stamped and compared. Buyers — especially in Europe and the Americas — write when their day ends, which is often after HKT close. A first reply that arrives Monday afternoon is not “still responsive.” It is late relative to competitors who acknowledged within four hours with a partial answer and a clear next step.

Three failure modes show up every long weekend:

1. Total silence. The RFQ sits unread. Rank and reply metrics suffer; the buyer moves on.
2. Junior improvisation. Whoever happened to be online invents a price, lead time, or Incoterm to “not lose the lead.”
3. Agent overreach. An always-on draft layer sends (or queues as if ready) a quote outside band, a DDP promise, or soft language on off-platform payment.

Silence loses speed. Improvisation and overreach lose margin and compliance. The playbook has to prevent all three.

If your weekday RFQ chain is still undocumented — classify, catalog check, quote, sample/QC, follow-up — fix that first. Weekend coverage amplifies whatever weekday process you already have. The unglamorous baseline is the same entity, bank, document, and ownership sequence we publish on the seller checklist.

Define coverage windows before you name people

Do not start with “who works Saturday.” Start with clocks.

Window A — Soft coverage (acknowledge + triage). Target: first meaningful acknowledgement within four hours of RFQ arrival on weekends and HK public holidays, 08:00–22:00 HKT. “Meaningful” means: we received it, we understand the SKU family, we will reply with a commercial draft by a named time, and we list the missing specs if any.

Window B — Commercial coverage (quote inside band). Target: draft quote inside published price bands and default Incoterm within one business half-day of the acknowledgement, even if that half-day is Sunday for a priority SKU family. Outside band stays human.

Window C — Dark hours. 22:00–08:00 HKT on weekends/holidays: auto-ack only (Layer 1 facts), no commercial numbers. Morning owner picks up at 08:00 HKT with a sorted queue.

Publish these windows on one page. If the team cannot recite them, you do not have coverage — you have hope.

Hong Kong’s calendar is dense: Lunar New Year, National Day / Mid-Autumn clusters, Christmas–New Year, Easter, Buddha’s Birthday, HKSAR Establishment Day. Map the next twelve months of public holidays into the same three windows. Treat “half-day before a long weekend” as holiday coverage, not as a normal Friday.

RACI for weekend RFQ ownership

Name roles, not vibes. A useful split for a Hong Kong Alibaba.com desk:

R = responsible, A = accountable, C = consulted, I = informed.

Two rules that keep this matrix alive on a Sunday:

• Override is a named act. Whoever clicks past a gate records their name. “The bot sent it” is not a control.
• On-call is a person with a phone, not a group chat. One primary, one backup. Rotate fairly; publish the roster four weeks ahead.

For desks adopting Accio Work, the agent sits in the draft and Layer-1 columns — not in the accountable columns for price exceptions or payment. That is the same fencing we use in weekday Accio Work implementations: catalog-aware drafts and multilingual first replies with human approval on commercial send.

What the on-call may send without waking the director

Write a one-page “Sunday permission list.” If it needs a lawyer, nobody will open it at 21:00.

Allowed auto-send (Layer 1). Receipt acknowledgement; restatement of published catalog attributes; request for missing specs (quantity, destination port, preferred Incoterm, artwork if OEM); link to the live SKU page; public lead-time band; standard packing note.

Allowed draft, human-approve before send (Layer 2). First commercial quote inside coded price bands; default Incoterm (for example FOB Hong Kong or EXW Dongguan) when the buyer did not specify; sample fee and lead time from a published schedule; multilingual rewrite of an already-approved English shell.

Hard-stop — do not draft a workaround (Layer 3). Any number not in the system of record. Any new Incoterm, especially DDP. Any payment path other than the platform’s. Batteries, food-contact, branded OEM, dual-use, or exclusivity language. “We can ship next week” when the factory calendar says otherwise. Any suggestion that membership fees or deposits be paid to a third party.

That last hard-stop is non-negotiable. Hong Kong sellers pay platform membership to ALIBABA.COM HONG KONG LIMITED. An authorised dealer helps with onboarding and implementation; it does not collect or “remit” those fees. Fee-category transparency for the authorised channel sits on aliad.hk/pricing. Weekend pressure is exactly when fraudulent “pay us over the holiday and we’ll sort Alibaba Monday” messages appear. Train the on-call to refuse and log, not to negotiate.

A practical weekend runbook (copy into your desk wiki)

Friday 16:00 HKT — handoff. On-call confirms roster. Sales director freezes price bands for the SKU families in Soft + Commercial coverage. Open RFQs are tagged: waiting-spec / quote-ready / director-hold / done. Factory contacts for emergency QC photos are verified (name + WhatsApp + hours).

Saturday / Sunday / public holiday — every four hours in Window A. On-call or Accio Work clears the acknowledge queue. Classification tags are applied. Anything Layer 3 goes to the director channel with a one-line reason, not a novel.

Once per Window B block. On-call reviews Layer 2 drafts. Edits go into three buckets: fact-fix, tone-fix, policy-kill. Policy-kills page the director even on holiday if the buyer is priority.

Monday 09:30 HKT — wash-up (30 minutes). Count RFQs received, acks sent, quotes sent, policy-kills, and near-misses. Update the permission list if the same kill repeated. If wash-up is skipped twice, you do not have a playbook — you have a story you tell buyers.

Holiday-specific traps for HK Alibaba.com sellers

Lunar New Year. Factories close. Do not let weekend fluency imply production capacity that does not exist. Publish a freeze date for new sample commitments and a restart date for production quotes. Agent templates must carry the freeze language, not hide it.

National Day / Mid-Autumn cluster. Logistics and inspection slots tighten. Lead-time bands widen in writing before the holiday, not after a buyer complains.

Christmas–New Year (buyer side). European and US buyers are slow to reply but sharp when they do. Keep Soft coverage; do not discount into Layer 3 to “catch the year-end PO.”

Typhoon and black rain. HK desks sometimes go dark for safety while overseas buyers keep writing. Pre-write a weather ack: we are under government signal, commercial reply resumes when offices reopen, here is what we already understood from your RFQ. That is Soft coverage, not radio silence.

Metrics that keep coverage honest

Track four numbers, weekly, including weekends:

1. Median time-to-first-meaningful-reply on weekend/holiday RFQs (not bot-ack alone).
2. Policy-kill rate on Layer 2 drafts (want rare and loud).
3. Correction rate after send (fact fixes within 24 hours).
4. Qualified advance rate (sample booked / PO path) for weekend-origin RFQs vs weekday-origin.

If you only optimise (1), the desk will pressure auto-send. Pair speed with (2)–(4). A four-hour correct quote still beats a four-minute wrong FOB — on Sunday as on Wednesday.

Staffing without burning the team

Coverage that relies on the founder forever will collapse. Rotate on-call. Pay it (allowance or time-off-in-lieu). Cap consecutive holiday weekends. Give the on-call authority matching the permission list — responsibility without authority produces either silence or improvisation.

For thin desks (two to three commercial people), Soft coverage plus Layer-1 Accio Work auto-ack is often the honest maximum until catalog truth and price bands are clean. Do not buy 24/7 commercial auto-send to paper over a missing roster.

How this fits Accio Work and the authorised HK channel

Accio Work is Alibaba’s B2B commercial agent layer: RFQ parsing, catalog-aware drafts, buyer context, multilingual first replies. On weekends it is most valuable in Window A and as a Layer 2 drafting engine — not as an unsupervised signatory. Corpable Marketing Limited (企丞) implements that fencing for Hong Kong exporters as an Alibaba.com HK authorised dealer and Accio Work channel partner. Platform membership fees still go to ALIBABA.COM HONG KONG LIMITED, not through us.

Implementation sequence we use: freeze one SKU family for weekend pilot; write the Sunday permission list; name primary and backup on-call; run two consecutive weekends with logged edits; then expand or stop. Training is with the people who will click send on Sunday evening, not a generic prompt workshop. Scope, pricing bands for service work, and what sits where are summarised on aliad.hk/services and the Accio landing at aliad.hk/en/accio.

Start this week — a two-hour setup

1. Write the three coverage windows with HKT clocks.
2. Fill the RACI table with real names (and a backup).
3. Paste the Sunday permission list (Layers 1–3) into one page.
4. Tag open RFQs before Friday 16:00.
5. Schedule Monday wash-up on the calendar as a recurring 30-minute meeting.
6. If you use an agent layer, disable commercial auto-send for Layer 2 until wash-up shows policy-kills are rare.

If you cannot name the on-call and the escalation owner for next Saturday, you are not ready for holiday volume. Speed without permission is how Hong Kong desks earn the wrong kind of weekend story.

For a desk-level working session — weekend roster, permission page, and a scoped Accio Work coverage pilot — write to wz@aliad.hk or start from aliad.hk. Bring last quarter’s weekend RFQs, including the ugly ones. The playbook only works on those.

Liu Wei is Sales Director at Corpable Marketing Limited (企丞), an Alibaba.com Hong Kong authorised dealer. NAP: ROOM 802, 8/F Chevalier House, 45-51 Chatham Road South, Tsim Sha Tsui, Kowloon · +852 6816 3966 · wz@aliad.hk · aliad.hk

Nothing erodes buyer trust faster than two replies that quote different prices, lead times, or Incoterms for the same RFQ. When Accio Work drafts Alibaba.com responses in parallel with a salesperson’s chat and a factory WeChat note, version drift is almost guaranteed unless the desk treats quotes as controlled documents.

This playbook explains how Hong Kong export desks can keep Accio Work helpful without letting draft A, draft B, and a “quick WhatsApp confirmation” contradict each other.

Why version conflicts happen

Typical failure pattern:

1. Buyer asks for 5,000 units of SKU-A on Alibaba.com.
2. Accio Work drafts a reply from last week’s catalog price.
3. Sales edits a chat message using a verbal factory update.
4. Operations uploads a revised pack size but does not bump the catalog revision.
5. Buyer compares both answers and asks which one is real.

The problem is not that automation is fast. The problem is that the desk has no single current quote object, no revision id, and no rule for which channel is authoritative.

Define one quote object per RFQ

Create a desk record keyed by buyer thread id (or inquiry id) with:

• Quote version number (v1, v2, …)
• Catalog revision used
• SKU / variant / packaging
• Quantity band and unit price
• Currency, Incoterm, payment term code
• Lead time window and validity date
• Status: draft / pending review / approved / sent / superseded
• Owner of the next edit

Accio Work may propose v1 from approved sources. Humans may revise. The sent message always cites the version and validity window. If a new fact arrives, supersede—do not silently edit the old reply in another channel.

Channel discipline

Pick one primary reply channel for commercial numbers (usually the Alibaba.com thread). Other channels may acknowledge and point back: “Commercial terms are in quote v3 on the inquiry thread.” Do not let Accio Work publish a different number on email while chat carries yesterday’s number.

For multi-language desks, translate the approved version; do not re-negotiate facts while translating. A German reply that quietly changes MOQ is a new version, not a localization.

What Accio Work may draft vs never invent

May draft from approved fields:

• Restatement of catalog price within band
• Standard payment term codes already on the term sheet
• Lead time ranges tied to the current capacity note
• Clarifying questions for missing quantity or destination

Must never invent:

• A “temporary” discount to win the thread
• A new Incoterm not chosen by the commercial owner
• Certificate or compliance language without document reference
• A promise that a prior quote still holds after catalog change

Use the checklist to mark each commercial field as confirmed, conditional, or escalated before publish.

Supersession rules

When factory capacity changes, FX moves outside policy, or packaging revises:

1. Freeze open drafts tied to the old catalog revision.
2. Create v(n+1) with the new source stamp.
3. Notify the account owner if a prior version was already sent.
4. Tell the buyer clearly if previous numbers are withdrawn.

Do not rely on Accio Work to “notice” a WeChat update. Source of truth is the desk record, not the latest chat screenshot.

Review gates by risk

• Low risk (standard SKU, standard terms): one reviewer may approve Accio Work’s draft.
• Medium risk (custom pack, near-MOQ, non-standard lead time): commercial + ops review.
• High risk (payment exception, exclusive claim, regulated product): finance/compliance before any send.

Accio Work fits best where the version object already exists. Automation without versioning only accelerates contradiction.

Practical KPIs (not vanity)

Track:

• Share of sent quotes with a version id
• Count of buyer messages citing conflicting numbers
• Time from catalog change to freeze of open drafts
• Percent of multi-channel replies that point back to the primary quote

Volume of drafts generated is a weak metric. Consistency of the number the buyer can rely on is the strong one.

Implementation notes for HK desks

Start with a lightweight sheet or CRM field set if you lack a full CPQ. Train the team that “quick confirm” outside the quote object is a process defect. For setup patterns and desk services, see services and pricing. Company context: aliad.hk.

A versioned quote is slower than an unchecked chat reply for about thirty seconds—and far cheaper than a dispute about which promise was binding.

Worked example

Monday 10:00 — Buyer RFQ for SKU-A, 8,000 pcs, FOB Shenzhen, T/T 30%. Accio Work drafts quote v1 from catalog rev 14. Reviewer approves; reply sent on Alibaba.com.

Monday 15:40 — Factory reports carton change that raises freight estimate. Ops updates catalog to rev 15. Desk freezes any open drafts on rev 14. Accio Work prepares quote v2 with the new pack note and a clear line that v1 lead-time assumptions no longer apply. Commercial owner approves; buyer is told v1 is superseded.

Tuesday — Buyer asks on WhatsApp whether Monday’s price still holds. Sales does not invent a third number. Sales points to quote v2 on the inquiry thread and offers to open v3 only if quantity or Incoterm changes.

That sequence looks bureaucratic on paper. In practice it prevents three people from sending three truths.

Anti-patterns to ban

• Editing a sent PDF without bumping the version and notifying the buyer
• Letting Accio Work regenerate from a stale cache after catalog bump
• Using “approx.” or “around” to hide that two owners disagree
• Translating a quote while changing MOQ “for local market habit”
• Mixing sample pricing into a replenishment quote without a separate version

Closing rule

One RFQ, one current version, one authoritative channel. Accio Work drafts inside that rule; humans escalate when the rule cannot hold. Everything else is noise that buyers eventually screenshot back at you.

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:

1. Buyer account and entity name.
2. Source thread and requested response time.
3. Product family, SKU, variant, and revision.
4. Quantity and whether it is sample quantity or production quantity.
5. Destination country, city or port, and Incoterm if known.
6. Required date and whether it means dispatch or arrival.
7. Sample status: first sample, revised sample, approval sample, or no sample requested.
8. Prior order reference, if replenishment is claimed.
9. Price basis, currency, payment route, and quotation validity.
10. 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.

Hong Kong export teams often install Accio Work across the whole store on day one. That usually creates noisy drafts, unclear fee lines, and no baseline. A one-SKU-family pilot is safer.

Day 0 — confirm the channel and the invoice split

Accio Work in Hong Kong is offered through Corpable Marketing Limited (企丞市场策划有限公司), an authorized Alibaba.com HK channel partner. Read the product scope first: aliad.hk/en/accio.

Keep two ledgers:

• Platform membership / ads / store tools billed to the official Alibaba.com entity — see fee categories at aliad.hk/pricing.
• Channel work (onboarding, RFQ-desk design, training) billed separately — aliad.hk/services.

Do not pay a WeChat middleman for “membership upgrades.”

Day 1 — pick one SKU family

Choose a family with stable MOQ, published price bands, and complete English specs. Avoid made-to-order or frequently changing BOM items. Run the pre-pay exporter checklist: aliad.hk/checklist.

Days 2–3 — desk rules, not autopilot

A workable desk is agent draft → human approve → send. Before anyone clicks send, a human should check:

• price band and currency match the published sheet
• Incoterms and lead time are not invented
• buyer country / certification asks are answered or explicitly parked
• no promise of Trade Assurance outcomes the store cannot support

Days 4–5 — measure three numbers only

1. Time-to-first-draft
2. Edit distance (how much the human rewrote)
3. Meetings or samples booked from the piloted family

If edit distance stays high, fix retrieval and price tables before adding languages.

Days 6–7 — decide expand / hold / stop

Expand only if drafts are short to edit and the invoice split is still clean. Hold if English RFQs are stable but other languages are not. Stop if the desk invents commercial terms.

Corpable Marketing Limited · Alibaba.com Hong Kong authorized channel · aliad.hk · wz@aliad.hk · +852 6816 3966