Direct answer: A 3PL that supports both wholesale distribution and DTC ecommerce from one inventory pool holds stock under a single warehouse management system (WMS) and allocates it to either channel at the point of order, rather than splitting physical stock into separate wholesale and DTC locations. U-Freight’s fulfilment centres operate this way for brands that sell through both models, using a cloud-based WMS with API connectivity, inventory visibility that updates as transactions are processed, and warehouse operations that include QC, labelling, repacking and kitting.
This single setup is really three things working together, and brands evaluating a 3PL usually ask about them separately:
- One inventory pool — a single, shared stock record that both wholesale and DTC orders draw from.
- WMS and API visibility — a system that lets a brand see and connect to that stock in close to real time.
- Value-added services (VAS) — the QC, labelling, repacking and kitting work that turns raw inbound stock into channel-ready orders.
The sections below walk through how each part works, and what to confirm with a 3PL before relying on it.
What one inventory pool actually means
“One inventory pool” means the WMS tracks a single quantity of each SKU, rather than a wholesale-only quantity and a DTC-only quantity sitting in separate systems or separate physical zones. When a wholesale carton order and a DTC unit order both draw from the same SKU, the WMS deducts from one shared number, so stock is not double-counted or artificially split before it is needed.
This does not mean every unit is interchangeable in practice. A brand may still reserve stock for a specific wholesale account, a promotional campaign or a minimum DTC safety level. Those reservations are rules applied on top of the pool — allocation logic decides which order type gets priority when stock is tight — rather than a reason to physically separate the inventory into different pools from the outset.
Two practical benefits follow from this approach: brands avoid holding duplicate safety stock for each channel, and a single stock-take or cycle count reflects the true available quantity across both business models.
Receiving, QC and stock allocation
Before stock enters the shared pool, it goes through receiving and quality checking. Typical inbound steps include:
- Verifying carton and unit counts against the advance shipping notice or purchase order.
- A visual or sample-based quality check appropriate to the product and agreed SOP.
- Recording batch, lot or expiry information where relevant.
- Putaway into the location structure the WMS uses to track availability.
Only after these steps is stock marked available in the shared pool, which is what allows both wholesale and DTC orders to draw from it with confidence. The scope of QC at receiving is agreed with each brand — it typically covers count and condition checks rather than full product testing (see the FAQ below).
Allocation rules are set up alongside receiving. A brand can specify how stock should be split or prioritised between wholesale and DTC when available quantity is limited, and the WMS applies that logic automatically as orders come in, rather than requiring a manual decision on every order.
Wholesale and DTC pick/pack differences
Wholesale and DTC orders draw from the same pool but are picked, packed and priced differently because the underlying work is different:
| Wholesale | DTC | |
|---|---|---|
| Typical order unit | Carton, case or pallet | Individual unit |
| Picking method | Full-carton or case-level picking | Piece-level picking across SKUs |
| Packing | Bulk packing, often to a retailer’s routing guide | Branded packaging, inserts, gift-ready packing |
| Labelling | Carton or pallet labels, retailer compliance labels | Platform or shipping labels per parcel |
| Typical charging basis | Per carton, case or pallet | Per unit or per order |
Because the labour and materials differ, a fulfilment quotation should show wholesale and DTC activity as separate line items even when both are served from the same warehouse and the same inventory pool. Combining them into a single blended rate makes it harder to see what is actually driving cost as channel mix shifts.
Labelling, repacking and kitting
Value-added services (VAS) sit between receiving and outbound dispatch, and are usually where wholesale and DTC requirements diverge most. Common VAS work includes:
- Labelling — SKU labels, platform-specific labels (for marketplaces or retailers), compliance or country-of-origin labels.
- Repacking — moving stock from a bulk inbound format into retail-ready or channel-specific packaging.
- Kitting — combining multiple SKUs into a single sellable unit, such as a bundle or gift set.
- Quality re-checks — inspection carried out as part of a specific VAS task, distinct from general receiving QC.
A 3PL offering VAS should be able to state, for each service, the unit it is charged by (per unit, per carton, per hour), the SOP it follows, and how exceptions (such as damaged stock found during repacking) are reported back to the brand. These details are confirmed during solution design, since scope and quality expectations vary by product and by brand.
API, inventory updates and exceptions
A cloud-based WMS is only useful to a brand if it can be connected to the systems the brand already runs — typically an ecommerce platform, a marketplace, or an ERP. This connection is usually made through an API, which allows:
- Inventory levels to sync from the WMS to the brand’s sales channels.
- Orders to flow from sales channels into the WMS for picking.
- Tracking and status updates to flow back out once an order ships.
“Real-time” in this context generally means inventory and order status update automatically as transactions are processed in the WMS, rather than through a scheduled batch upload run every few hours. The actual sync frequency and method still depend on which systems are being connected and how those platforms’ own APIs behave (see the FAQ below).
Exceptions — a short pick, a damaged unit, a mismatched carton count — are flagged in the WMS and should be visible to the brand rather than only resolved internally. Ask a 3PL how exceptions are surfaced (a dashboard, a report, an alert) as part of confirming the integration.
Onboarding information and responsibilities
Setting up a shared inventory pool, WMS integration and VAS scope works best when both sides are clear on what information is needed and who is responsible for providing it. A typical onboarding split looks like this:
From the brand:
- SKU list, dimensions and weights.
- Wholesale account requirements (routing guides, retailer compliance rules).
- DTC packaging and branding requirements.
- Sales channel and ERP details for API connection.
- Any product-specific handling, storage or labelling rules.
From the 3PL:
- WMS onboarding and API documentation.
- Confirmation of allocation logic between wholesale and DTC.
- Agreed SOPs for receiving QC, labelling, repacking and kitting.
- A clear point of contact for exceptions during go-live.
Confirming this scope before the first inbound shipment reduces the chance of stock arriving without an agreed allocation rule, labelling spec or integration in place — which is the same reasoning that applies to special-goods shipments reviewed through U-Freight’s Special Goods Air Cargo Pre-Check before booking or warehouse inbound.
How U-Freight supports this
U-Freight’s eCommerce fulfilment operations are built to serve wholesale and DTC orders from a shared inventory pool, with a cloud-based WMS, API connectivity and value-added services including QC, labelling, repacking and kitting. Inbound air freight into the fulfilment network is arranged through U-Freight’s Air Freight service, and brands estimating warehouse costs for a Hong Kong-based operation can start with the Hong Kong Fulfilment Pricing Guide. The exact allocation logic, integration scope and VAS pricing are confirmed during solution design against the brand’s actual SKUs, order volumes and channel mix.
Frequently Asked Questions
Is the inventory pool physical or virtual?
It is typically virtual at the WMS level — a single stock record — rather than a physical requirement to store wholesale and DTC stock in one undivided area. Physically, stock may still sit in different pick faces, bins or zones for operational reasons (bulk carton storage versus piece-pick shelving, for example), but the WMS tracks it as one available quantity and allocates it to either channel according to the agreed rules.
Which integrations are native?
This depends on the specific ecommerce platform, marketplace or ERP involved. A “native” integration generally means a pre-built connector that requires configuration rather than custom development, while other systems may need a custom API integration. Confirm the specific platforms in use so U-Freight can advise which connections are already supported and which would need to be built.
What does real time mean?
In practice, “real time” means inventory and order updates are pushed automatically as transactions occur in the WMS, rather than on a fixed batch schedule. The actual latency a brand experiences also depends on how the connected platform (the ecommerce store, marketplace or ERP) processes and displays updates on its own side, so end-to-end timing is confirmed as part of the integration setup rather than guaranteed as an instant, zero-delay feed.
Does receiving QC include product testing?
Not by default. Standard receiving QC typically covers count verification and a visual or sample-based condition check against the packing list. Functional or technical product testing is a separate, specifically agreed service — relevant for categories such as electronics — and would be scoped and priced independently of standard receiving QC.
Share your SKU list, expected order volumes by channel, and the sales platforms you need connected, and U-Freight’s fulfilment team can confirm how a shared inventory pool, WMS integration and value-added services would apply to your operation.
Request a Formal Fulfilment Solution
