Dedicated vs Shared (Multi-Client) Warehousing

A growing brand signs with a multi-client warehouse because the pallet rate looks cheap, then spends its first peak season queuing for dock appointments behind a larger tenant. Another company signs a five-year dedicated site for control, and two years later is paying for 3,000 empty pallet positions after a channel shift. Both chose an operating model on one number and found out about the rest from the invoice.

The choice between dedicated and shared warehousing turns on a handful of measurable things: the volume at which fixed costs beat unit rates, how far peaks rise above the average, how much process the business needs to own, and which contract terms move risk from one side to the other. Put numbers on each and the decision usually makes itself.

• What this guide covers: how each model is priced and governed, a break-even formula, worked US and Indian sites, the clauses that differ, the bailment and warehouse-receipt law behind both, and India's GST storage rules for shared buildings.
• Who it is for: supply chain managers and founders choosing their first or next operating model, before a request for proposal goes out.

Dedicated and shared warehousing: what each model puts in the contract

In a dedicated arrangement one client has a building or a walled-off section, with its own staff, equipment and often its own WMS configuration, and pays the operator's costs plus a fee. In a shared, or multi-client, arrangement many clients use the same building, people and systems, and each pays unit rates for storage and handling. Neither term has a statutory definition; the contract decides which one you have.

• Dedicated pricing: usually open-book cost-plus or a fixed management fee over pass-through costs, so the client carries the fixed base whether volume arrives or not.
• Shared pricing: per pallet per month for storage, per pallet or per case for receiving and picking, plus value-added services, often with a monthly minimum charge.
• Dedicated control: the client can set shift patterns, process steps and automation, because nobody else's freight competes for them.
• Shared flexibility: space and labour flex across tenants, so a client's peak can borrow capacity from another client's trough, within limits the contract sets.

Hybrids are common: a dedicated zone inside a shared building, or shared labour with dedicated racking. Treat each as a mix of the two cost structures, and price the fixed and variable parts separately. The flow below shows how the decision normally moves from volume data to a signed contract.

Where the cost curves cross: fixed cost, volume and peak sizing

Shared warehousing costs rise almost in step with volume, while dedicated warehousing starts with a large fixed block and then rises more slowly. Below the volume where the two lines cross, shared is cheaper; above it, dedicated usually wins, provided the building is sized for the peak and the peak is not far above the average.

The fixed block in a dedicated site is mainly rent, racking and handling equipment, systems and the management layer. The variable part is mostly labour. A shared operator recovers all of those through its rates, plus its margin and the cost of empty space it carries between tenants. That is why the gap between the two models depends heavily on the labour share of total cost, which differs sharply between the US and India.

Monthly cost, shared model:
  C_S(V) = V × (r_st × P0 + r_h × H0 + r_p × K0)

Monthly cost, dedicated model (cost-plus with fee f):
  C_D(V) = (1 + f) × (F + L0 × V)

Break-even volume multiple:
  V* = (1 + f) × F / [ (r_st × P0 + r_h × H0 + r_p × K0) − (1 + f) × L0 ]

where
  V     = volume multiple of today's base (1.0 = current volume)
  P0    = average pallets stored per month at V = 1
  H0    = pallets received plus shipped per month at V = 1
  K0    = cases picked per month at V = 1
  r_st, r_h, r_p = shared storage, handling and pick rates
  F     = dedicated fixed cost per month (rent, racking, MHE, WMS, utilities)
  L0    = dedicated labour cost per month at V = 1 (assumed to scale with volume)
  f     = management fee as a fraction of cost
Valid only while the dedicated building holds peak volume; size F for peak, not average.

The warehouse operating model decision compares a shared contract's unit-rate cost, which scales with pallets stored, pallets handled and cases picked, against a dedicated contract's cost-plus base of rent, equipment and labour; in the illustrative US case below, dedicated becomes cheaper above roughly 1.64 times current volume, about 6,570 average pallets.

Break-even worked for a US site and an Indian site

With the illustrative rates below, a US client storing 4,000 pallets is about $35,000 a month cheaper in a shared building and would need roughly 64% more volume to justify a dedicated site. An Indian client storing 3,000 pallets is close to break-even already, because labour is a much smaller share of dedicated cost.

The Indian case crosses over at only 10% more volume because labour is 30% of dedicated cost there against 46% in the US case, so the fixed block is the bigger lever. All figures are illustrative rates, not quotes. GST is charged on warehousing invoices in both models, so for a client that can claim the input tax credit it does not change the comparison; check eligibility with your tax team.

Peak changes both answers. If the Indian client's peak is 4,500 pallets, a dedicated site must rent space for 4,500 all year, while the shared site bills peak positions only in peak months. Re-run the formula with F sized to peak before treating any break-even as final, and compare it with a full ownership option using our own warehouse versus 3PL cost comparison.

Control over people, process and the WMS in each model

A dedicated contract gives the client a say over how work is done; a shared contract gives the client a say over what is delivered. That difference shows up in who owns each record and who must approve a change, and it should be written into the contract rather than assumed.

The shared model's weak point is contention. When one tenant surges, the operator rations docks and labour, and the contract decides who waits. The trace below shows how that plays out when the agreement is silent; dates, container and invoice numbers are illustrative.

1. 3 October, 08:00: the operator caps client B at six inbound appointments a day because a larger tenant's festive inventory is arriving; the agreement says nothing about dock priority.
2. 5 October, 14:00: twelve containers for client B, including MSKU7741208, sit at the port past their free days and start accruing detention.
3. 9 October, 10:30: the operator moves 600 of client B's pallets to an overflow site at its own discretion; the agreement does not say who pays the shuttle.
4. 31 October: invoice INV-2611-0457 adds overflow storage at a higher rate plus shuttle charges; client B disputes both and holds payment.
5. 18 November: the dispute closes with a credit and a new clause: guaranteed weekly inbound slots and overflow at the standard storage rate.

Inventory ownership inside a shared building is a separate control problem from space. Our guide on keeping customer-owned stock separate in a shared warehouse covers owner keys in receiving, allocation and adjustments; this article stays with the operating-model decision that comes before it.

Contract clauses that change between dedicated and shared deals

Dedicated contracts shift volume risk to the client and need careful exit terms; shared contracts keep volume risk with the operator and need careful service and capacity terms. Read each draft for the clauses below before comparing prices.

• Term and exit: dedicated terms usually match the building lease and equipment life; set out who takes over the lease, racking and staff at exit, and what a break fee covers.
• Volume commitment: shared deals often carry a monthly minimum charge; dedicated deals put the whole fixed base on the client, so model the low-volume year.
• Cost visibility: open-book dedicated contracts need audit rights, a cost category list and a rule on which overheads may be charged.
• Gainshare: where productivity improves, agree in advance how savings are split and how baselines are reset.
• Capacity guarantee: shared contracts should state reserved positions, dock slots and labour hours for peak weeks, and the rate for overflow.
• Liability limit: both models cap the operator's liability for loss or damage; check the cap per unit against the value of your goods.
• Lease accounting: a dedicated building or zone can make part of the fee a lease under ASC 842 or Ind AS 116, as our embedded lease guide explains.

Duty of care, commingling and liens under UCC Article 7 and Indian law

In both countries the operator holding your goods owes reasonable care, may cap its liability by contract, and can hold goods for unpaid charges. The details differ, and they matter most in shared buildings, where goods of many owners sit side by side.

In the US, UCC section 7-204 sets a reasonable-care standard and lets the storage agreement cap liability, and Indian sections 151 and 152 do much the same; our warehouse legal liability and insurance guide works through caps and claims in detail. What differs between the two operating models is separation of stock, the reach of liens and the notice to end storage, where section 7-206 sets at least 30 days if no period is agreed.

Shared warehouse inventory control in the US rests on UCC section 7-207, which requires a warehouse to keep goods covered by each receipt separate so they can be identified and delivered, unless the receipt allows otherwise; commingled fungible lots become owned in common, with the warehouse severally liable for each owner's share.

Section 7-209 gives the warehouse a lien on the goods for storage, transport, labour and related charges, and extends it to charges on other goods only where the receipt or agreement states that claim. India reaches similar results through bailment law in the Indian Contract Act, 1872, which applies whether or not a warehouse receipt is issued.

GST place of business and owner-wise storage in Indian shared sites

An Indian client storing goods in a third-party warehouse must treat that site as one of its own places of business for GST, and the operator must store and record goods so each owner's stock can be identified. In a shared building those two rules decide how the operator lays out the floor and the WMS.

Section 2(85) of the CGST Act, 2017 defines a place of business to include a warehouse, godown or other place where a taxable person stores goods. The client therefore declares the third-party site in its own registration before stock arrives. Section 35(2) requires every warehouse owner or operator, registered or not, to keep records of the consignor, consignee and other details of goods it holds.

• Enrolment: under Rule 58(1) of the CGST Rules, an operator that is not registered must enrol on the common portal in FORM GST ENR-01 and receive an enrolment number.
• Books for the stay: Rule 58(4)(b) requires books covering the period goods remain in the warehouse, including dispatch, movement, receipt and disposal.
• Owner-wise storage: Rule 58(5) requires goods to be stored so they can be identified item-wise and owner-wise, and the operator to allow physical verification on demand.

Multi-client warehouse operations in India must meet CGST Rule 58(5), which requires goods to be stored so a proper officer can identify them item-wise and owner-wise, and Rule 58(4)(b), which requires books covering the whole period each consignment stays, so a shared WMS needs a mandatory owner field on every location record.

A dedicated site meets owner-wise identification almost by default, since one client owns everything in it. A shared site has to prove it, which favours bin-level owner tagging over mixed bulk zones. The US has no federal counterpart to these GST storage records, so a two-market client should check state tax rules wherever its inventory sits.

Forecasts a model can produce and commitments leadership must sign

Software is useful for the numbers in this decision and much less useful for the commitments. Volume forecasts, break-even runs and clause extraction can be automated; signing a multi-year lease-backed contract stays with named executives.

Choosing an operating model: an evaluation checklist

Score each factor with evidence, not opinion, and let the weight of evidence decide. Where most rows point the same way the choice is clear; where they split, a hybrid of a dedicated zone in a shared building is often the answer.

Whichever model wins, write the rate card, capacity terms and exit plan before signing, and keep a written plan for moving stock to another operator if service fails. More operating-model comparisons sit in the Logistics and Supply Chain library.

If you are preparing a warehousing tender and want the break-even model, capacity clauses and owner-wise stock controls built into your evaluation, share your volume history through our request for proposal form and we will help you compare dedicated, shared and hybrid bids on the same basis.