The Hybrid Model: Running Bulk Inventory and Dropship Fulfilment Together

Most scaling sellers eventually hit the same fork. Pure dropshipping keeps capital light but leaves margin and delivery speed on the table. Bulk inventory buys better unit prices and faster delivery, but ties cash into stock that may not move. The hybrid model refuses the choice: stock the SKUs where holding inventory pays for itself, and dropship the long tail. Done well, it is the most capital-efficient structure in ecommerce fulfilment. Done casually, it produces overselling, split shipments and a support queue full of “where is the rest of my order”.

The difference between those outcomes is a small number of rules about which SKUs go where and how orders get routed. This article sets them out.

Choosing What to Stock

The decision is per SKU, not per brand, and it is driven by four numbers: unit cost, units sold per month, gross margin, and the storage cost of one month of cover. The working heuristic:

• Stock it when monthly volume is high and predictable, when unit cost drops materially at bulk pricing, or when delivery speed is a stated purchase driver and the dropship lane cannot match a competitor’s promise.
• Dropship it when volume is low or spiky, when the product is bulky relative to its value, when it is a trial or seasonal experiment, or when the supplier is the only practical source.

A useful first cut: the top 20 percent of SKUs by revenue often justify 80 percent of the storage spend and deliver most of the savings from bulk pricing. Start by stocking those, review monthly, and promote or demote SKUs as their velocity changes. The cash flow mechanics of holding stock versus paying per order are covered in detail in the wholesale inventory cash cycle, which is the companion read for the capital side of this decision.

Routing Orders Between the Two Pools

Once a catalogue has both stocked and dropshipped lines, every order contains a routing question. The rules should be automatic, not ad hoc:

• Single-source orders route entirely to whichever pool holds every line item, which is why the pool assignment should live as an attribute on the SKU, not in someone’s head.
• Mixed orders need a policy. Splitting them into two shipments is faster but doubles the parcel cost; holding the stocked item until the dropshipped line ships is cheaper but slower. A common compromise is to split when the dropshipped leg’s promise exceeds a set number of days, and hold otherwise.
• Stockout fallback routes a stocked SKU’s orders to the dropship lane while replenishment is in transit, which converts a stockout from a lost sale into a slower delivery.

Fallback routing is the quiet advantage of the hybrid model. A pure dropshipper has no faster lane to fall back on; a pure stockist has no fallback at all. The hybrid has two lanes per SKU, and the routing layer picks whichever one is currently credible.

The Sync Problem: One Catalogue, Two Pools of Truth

The hybrid model’s characteristic failure is overselling, and it has one root cause: two pools of inventory that do not talk. The stocked pool decrements in real time as warehouse orders ship; the dropship pool’s availability is whatever the supplier says it is. If your storefront sees a single blended number, it will sell units that exist in neither pool.

Three practices keep the numbers honest:

• Separate buffers. Track warehouse stock and supplier stock as distinct quantities, and expose only the lower credible figure to the storefront. A blended number always overstates availability.
• Real-time decrement on the stocked pool and scheduled polling on the dropship pool. The warehouse pool changes fast and is fully knowable; the supplier pool changes slowly and is only approximately knowable, so treat them differently.
• A safety buffer on the supplier figure sized to the supplier’s sync latency. If supplier stock syncs every 4 hours and you sell 6 units per hour of that SKU, the buffer is at least 24 units.

The technical patterns behind this are the same ones described in inventory forecasting and stock sync with a 3PL, and the general economics of inventory explain why carrying cost, not purchase price, is what the hybrid model optimises.

Technical Background

The hybrid model is an application of supply chain design: the same SKU can be sourced through different fulfilment paths depending on the trade-off being optimised at that moment. The stocking decision is a classic safety stock problem, where buffer size is a function of demand variability and replenishment lead time – which is precisely why stable, fast-moving SKUs are the ones that justify holding stock. Where the stocked pool sits also matters: the maths of US warehouse versus shipping from China decides whether bulk stock earns its keep on speed, cost, or both.

Operating the Model Week to Week

Three routines keep a hybrid operation healthy. First, a monthly SKU review that promotes high-velocity dropshipped items into stock and demotes slow movers back to dropship, using the numbers above rather than sentiment. Second, a weekly reconciliation of the two pools against actual sales, catching the sync drift that accumulates quietly. Third, a quarterly check that bulk pricing still beats the dropship unit price after storage – supplier prices move, and a lane that was right last year can be wrong this year.

Peak season stresses every rule here at once, which is why allocation and capacity planning for Q4 deserves its own pass, covered in holiday season stock allocation and production priority. And when the stocked pool grows to the point of needing more than one location, multi-warehouse distribution extends the routing logic across locations rather than pools.

Perguntas Frequentes