Multi-supplier consolidation and order-line routing for merchants: stocked fulfillment vs supplier direct dispatch

Short answer: you keep purchasing from and paying your own suppliers. Every supplier parcel is sent to one receiving point we operate in China, where it is logged, photographed and — when it makes operational sense — consolidated into one outbound batch. Each order line is then routed by rule: SKUs you already hold in the China warehouse ship from stock, while long-tail, made-to-order and low-velocity lines are dispatched by the supplier. Title to the goods stays with you the entire way.

1. Who buys, who pays, who owns the goods

Before routing, get the boundary right — it determines which problems are yours and which are ours.

• You negotiate with your supplier, place the purchase order and pay them directly. Your purchase money never passes through us.
• We provide the China receiving point and the fulfillment layer: receiving records, photo evidence, quality checks, consolidation, repacking, first-mile and international transit, and tracking.
• Title to the goods remains with you at every step, including while goods sit in our warehouse.
• Out of scope: merchant fulfillment is not a purchase-on-your-behalf service. We do not place orders with your suppliers, do not pay them, and never become the buyer of record.

One clarification: the platform also runs a separate buying-agent service for individual shoppers, executed against a confirmed quote and payment. That is a distinct service line and does not change how the merchant workflow described here operates.

2. Consolidation: many supplier parcels, one merchant inbound

Consolidation succeeds or fails on labelling and matching discipline, not on warehouse speed.

Step 1 — standardise the shipping address format

Give every supplier the same address layout. One version per supplier is how parcels go missing. A ready format is available at /tools/china-warehouse-address-template.

Step 2 — require a merchant-side identifier on the label

A workable pattern is merchant account code + purchase order number + carton sequence (for example, carton 2 of 3). Untagged parcels slow down receiving and are difficult to reconcile later.

Step 3 — send an expected inbound list

Share the purchase order numbers, SKUs, quantities and expected arrival window in advance. Receiving then becomes a line-by-line match instead of a memory exercise.

Step 4 — receive, record, photograph

Each parcel is logged on arrival and photographed, with weight and dimensions recorded. Those records serve three purposes: quantity reconciliation, evidence if something is wrong, and input for estimating volumetric weight when parcels are later combined.

Step 5 — consolidate and repack

Received parcels can be combined into a single outbound batch, with supplier outer packaging removed or reduced where appropriate. Be precise about the benefit: consolidation typically reduces the number of cartons and the outer volume, and it may reduce volumetric weight. It does not guarantee a lower billed weight, because carriers bill on the greater of actual and volumetric weight, and the outcome depends on destination, carrier rules and shipment profile. Model it with /tools/volumetric-weight-calculator, then check the billing logic in /pricing/shipping-calculator. The scope of the consolidation service itself is described at /services/consolidation.

3. Order-line routing: stocked fulfillment vs supplier direct dispatch

Routing is a per-line decision, not a per-store one. A single cart can contain one line fulfilled from China stock and another dispatched from the supplier. The signals below are what actually drive the call.

In practice: take your ten to twenty highest-volume SKUs, write an explicit routing rule for each, and let everything else default to supplier direct dispatch. Adjust thresholds after a few months of real receiving and exception data rather than trying to automate everything on day one.

4. How a mixed order actually executes

When one order contains both a stocked line and a direct-dispatch line, execution runs as two parallel actions:

1. The order is evaluated line by line and split into two outbound legs.
2. Stocked leg: picked from China warehouse inventory, checked, packed, labelled and logged as outbound.
3. Direct leg: the supplier ships to our receiving point for inbound logging and inspection, then onward transit. This leg gets its own parcel record and tracking number.
4. Both legs are tracked separately, so your customer may receive two parcels arriving at different times. Saying so on the storefront reduces support tickets.

If you have several direct-dispatch lines that can afford to wait, batching them into one outbound usually reduces the number of separate parcels. Whether it is actually more economical depends on destination, carrier billing rules and how long you can hold the order. Compare options in /pricing/shipping-calculator instead of relying on rules of thumb.

5. Receiving evidence and short-ship handling

With multiple suppliers, three exceptions dominate: short shipment, wrong SKU, and cartons damaged in transit. The handling logic is straightforward.

• The receiving record — photos, weight, dimensions, timestamp — is the objective evidence captured at the moment of arrival. It cannot be reconstructed credibly afterwards.
• Because you purchased from and paid the supplier, the claim is yours to file. What we provide is the complete receiving evidence to attach to that conversation.
• Records stay linked to the purchase order number and SKU, which helps with reconciliation, supplier reviews and future sourcing decisions.

Fixing this chain in advance is far cheaper than reconstructing it from chat history during a dispute.

6. Running routing at scale

Copying rules by hand breaks once order volume grows. The event-driven approach is to let order state changes trigger routing through the Merchant API, scoped API keys and webhooks, rather than having someone maintain a spreadsheet. WooCommerce merchants, note the channel wording precisely: our plugin is currently represented by a listing in the WordPress.org plugin directory, which is a different distribution channel from the WooCommerce Marketplace, and we describe it that way on purpose. For Shopify and Amazon, check the current verified status of each channel on /integrations before planning around it — availability should never be inferred from a roadmap. For agent-driven workflows, see /developers.

7. Pre-rollout checklist

1. Standardise the supplier-facing label format, including merchant account code, purchase order number and carton sequence.
2. Send the warehouse address template to every supplier and confirm they are using the current version.
3. Write routing rules for your top ten to twenty SKUs; default everything else to direct dispatch.
4. Start with one product line instead of migrating every supplier at once.
5. Agree internal exception turnaround times: who reviews receiving exceptions, and who contacts the supplier.
6. Review the first receiving records before scaling, to confirm matching and evidence actually work.

If you are coordinating several suppliers at once and want to know which routing mix fits your order structure, start at /for-merchants, or submit a workflow review and we will map a workable split based on your SKU profile and order distribution.