Separating Wholesale and Direct-to-Consumer Inventory Pools
Published
Separating Wholesale and Direct-to-Consumer Inventory Pools
Separate wholesale and direct-to-consumer inventory logically before deciding whether to split it physically. Give each SKU one trusted on-hand quantity, then subtract holds, wholesale commitments, DTC reservations, safety stock, and unavailable states to calculate channel-specific available-to-sell. Define who may transfer stock between pools, what orders remain protected, and how every movement reconciles to physical inventory.
Choose the right order path
Farm intake fits multi-SKU, recurring, inspection-sensitive, staged, packaged, scanning, reverse-engineering, or otherwise complex work. Instant quote fits clean files and straightforward requirements.
Use one inventory truth with channel-specific promises
Start with physical on-hand by production SKU and revision. Remove quarantine, inspection-pending, damaged, return-pending, obsolete, sample, replacement, and customer-owned quantities. From the remaining usable stock, reserve firm wholesale commitments, DTC orders, and safety stock according to buyer-approved rules. This keeps two storefronts or order systems from promising the same unit.
| Control field | Wholesale definition | DTC definition | Hold condition |
|---|---|---|---|
| Demand commitment | Accepted PO, allocation window, ship date, carton quantity, and cancellation rule | Paid or authorized order, reservation timeout, ship promise, and cancellation rule | Commitment events are ambiguous |
| Available-to-sell | Usable stock less protected DTC demand, holds, and assigned buffers | Usable stock less wholesale commitments, holds, and assigned buffers | Both channels can promise the same unit |
| Product identity | Production SKU/revision mapped to wholesale sellable SKU, pack, label, and customer item | Production SKU/revision mapped to DTC variant, parcel pack, insert, and storefront ID | Channel mapping conflicts |
| Transfer authority | Who may borrow from DTC, minimum protected quantity, and replenishment condition | Who may borrow from wholesale, protected PO dates, and replenishment condition | Transfer is an informal override |
| Reconciliation | Committed, picked, shipped, cancelled, short, and residual quantity | Reserved, picked, shipped, cancelled, returned, and residual quantity | System totals do not equal physical states |
Choose shared, segmented, or hybrid allocation
Shared pool
Use one usable stock pool when both channels consume the same product revision and the order system can protect firm commitments in real time. This reduces stranded inventory but requires reliable reservations, cutoffs, and exception ownership.
Segmented pools
Reserve defined quantities by channel when wholesale dates, account commitments, launch windows, packaging, ownership, or DTC service promises must be protected. Segmentation can clarify responsibility, but static splits can strand stock in one channel while the other runs short.
Hybrid pool
Protect bounded wholesale and DTC commitments, then keep a shared flex quantity governed by transfer thresholds. A hybrid approach needs an explicit priority rule, not a dashboard that merely displays two quantities.
Keep product and packaging identities connected
The same printed part may become different sellable configurations. Map the production SKU and revision to wholesale case packs, customer item numbers, labels, routing instructions, DTC variants, inserts, and parcel packaging. Do not move units between pools until the receiving channel's inspection, packaging, labeling, and data requirements are satisfied.
Define transfer and shortage rules before demand collides
- Freeze the physical on-hand and unusable states for the affected SKU.
- Identify firm wholesale commitments and live DTC reservations by due event.
- Protect the buyer-approved safety stock and customer promises.
- Evaluate replenishment timing and packaging conversion work.
- Authorize a bounded transfer with source, destination, reason, approver, and effective time.
- Recalculate both channel promises and reconcile the physical movement.
Fit, non-fit, and production risks
This workflow fits established brands selling repeat 3D printed products through both wholesale and DTC channels, especially when SKUs, revisions, packaging, order sizes, or service promises differ. A one-time order through one channel may need only order-level reservation.
Risks include double-promising stock, protecting forecasts instead of firm demand, stale reservations, incompatible channel packaging, informal transfers, wholesale orders consuming DTC replacements, DTC promotions consuming committed wholesale stock, and returned units reentering availability without inspection.
Make a multichannel inventory program quote-ready
- Production SKUs, revisions, variants, channel sellable IDs, customer item numbers, and barcode mappings.
- Wholesale accounts, PO events, case packs, routing rules, ship windows, and cancellation terms.
- DTC storefronts, reservation events, parcel configurations, inserts, service promises, and return states.
- Usable, held, committed, reserved, buffer, flex, and transfer quantities by SKU.
- Allocation priorities, transfer thresholds, approval authority, shortage rules, replenishment triggers, and reconciliation fields.
Use the print-on-demand onboarding page for a managed multi-SKU program, the production-runs page for recurring releases, the identifier crosswalk guide for channel mappings, and the routing-guide comparison for wholesale packaging and shipping requirements.
Frequently asked questions
Must wholesale and DTC inventory be stored in separate locations?
No. A brand can hold one physical stock population while maintaining channel-specific commitments and available-to-sell rules in a trusted system. Physical separation may help when packaging, inspection, ownership, or service requirements differ.
Can DTC stock be moved to a wholesale order?
Only under a defined transfer rule that checks existing DTC reservations, customer promises, safety stock, packaging compatibility, and replenishment timing. The transfer should be recorded rather than handled as an informal override.
How should returns affect channel pools?
Returned units should enter a pending state until identity, condition, packaging, and channel eligibility are verified. A return should not automatically increase wholesale or DTC available-to-sell.
Final decision
Choose the pool design only when physical on-hand, unusable states, channel commitments, available-to-sell formulas, product and packaging mappings, transfer authority, replenishment triggers, shortage rules, and reconciliation ownership are explicit.
Choose the right order path
Farm intake fits multi-SKU, recurring, inspection-sensitive, staged, packaged, scanning, reverse-engineering, or otherwise complex work. Instant quote fits clean files and straightforward requirements.