How to Set Inventory Reserves Across DTC, Amazon and Wholesale
Use one physical inventory ledger with explicit channel reserves, release triggers and expiry dates to prevent double-promising stock.
Direct answer: allocate shared inventory across DTC, Amazon and wholesale by keeping one physical inventory ledger and adding explicit channel reserves with an owner, quantity, release trigger and expiry date. Do not create permanent channel silos by default. Reserve stock only when a real commitment or service risk justifies it, then release unused quantities through a controlled rule.
A shared pool improves flexibility, but it can also let a fast-moving DTC channel consume units needed for an accepted wholesale purchase order or an Amazon replenishment. The solution is not three disconnected spreadsheets. It is a reservation policy that the 3PL's warehouse and order systems can enforce.
Separate physical stock from selling permission
Physical inventory answers where the units are and what status they are in. A channel reserve answers who may promise those units. The same pallet can remain in one warehouse location while the system holds part of its quantity for a retailer order, an FBA replenishment or a scheduled launch.
The 247 Fulfillment inventory-management page describes visibility into available, allocated, inbound and order-level inventory across channels. Buyers should still define the reservation rules that fit their commercial commitments.
Use four quantities for each SKU:
- On hand: physically received units in an eligible status.
- Hard allocated: units committed to released or accepted orders.
- Channel reserve: units protected for a defined future demand or service promise.
- Shared available to promise: the balance other channels may sell.
Choose a trigger for each channel
| Channel | Possible reserve trigger | Release trigger |
|---|---|---|
| DTC | Approved launch forecast inside a defined window | Launch ends or actual demand falls below the review threshold |
| Amazon FBA | Approved replenishment plan and prep capacity | Shipment departs, plan is cancelled or Amazon demand is revised |
| Wholesale | PO passes price, quantity and ship-window validation | PO ships, is reduced or reaches a documented expiry point |
| Safety stock | Policy based on replenishment lead time and demand error | Named operator approves use for a defined exception |
Do not reserve inventory merely because a salesperson expects an order. Tie each hold to evidence and an expiry. Permanent reserves create hidden stockouts in one channel while another sits on idle inventory.
Worked allocation for a shared SKU
This example is hypothetical. One SKU has 12,000 sellable units on hand. The brand sets aside 600 units as safety stock, accepts a wholesale PO for 3,000 units, approves an Amazon FBA replenishment of 2,400 units and protects 1,200 units for a dated DTC launch.
The shared available-to-promise balance is:
12,000 - 600 - 3,000 - 2,400 - 1,200 = 4,800 units.
If ordinary DTC demand averages 160 units per day, the shared balance represents 30 days of that demand:
4,800 ÷ 160 = 30 days.
Now assume the Amazon plan is reduced from 2,400 to 1,800 units before prep begins. A controlled release can return 600 units to the shared pool, increasing it to 5,400 units, or 33.75 days at the same DTC rate. The arithmetic is simple; the control matters. The release should update the channel ledger and storefront availability once, with a timestamp and approver.
The recommendation changes when inventory is lot-controlled, expiry-dated or physically customized for a channel. Units labelled for Amazon, ticketed for a retailer or packed as a finished kit may no longer be freely interchangeable. In that case, the system should reserve by the specific eligible status or finished SKU.
Test the systems before launch
Ask the provider to demonstrate five events: create a reserve, allocate an order against it, reduce the commitment, release the balance and reconcile the resulting availability in each connected channel. Then test an exception such as an inventory adjustment or cancelled PO.
Confirm which system is the source of truth. A storefront, ERP, marketplace and WMS can all calculate availability differently. Write down which system owns physical quantity, which owns reservations and how updates move between them. The Amazon FBA prep page describes inventory moving through received, in-prep, prepared and dispatched states; your reserve logic should recognize those status changes.
Give every reserve an expiry and escalation path
A reserve record should include SKU, quantity, channel, reason, owner, creation time, expected ship or launch date, next review and release authority. Review high-risk holds daily and ordinary holds on a schedule suited to the lead time.
When total demand exceeds supply, use a pre-agreed priority rule. Options include contractual commitment, margin, customer impact, ship window or strategic launch. Do not let the warehouse decide commercial priority from an urgent message. The brand owns the tradeoff; the 3PL executes the approved rule.
The guide to DTC and wholesale fulfillment planning explains why the order workflows should differ. This article addresses the narrower inventory decision: how those workflows share stock without double-promising it.
Channel-reserve worksheet
- Identify SKUs sold through more than one channel.
- Define on-hand, eligible status and shared available-to-promise.
- Choose evidence-based reserve and release triggers by channel.
- Name an owner, expiry and review frequency for every reserve.
- Test creation, allocation, reduction, release and adjustment events.
- Reconcile availability across WMS, ERP, storefront and marketplaces.
- Document the priority rule for constrained inventory.
247 Fulfillment's retail and B2B fulfillment page and Amazon prep services show why channel workflows need different controls even when inventory is shared. For a quote discussion, send 247 Fulfillment your channel mix, reserve rules and a representative SKU forecast.
