Number of Nodes, Echelons & Service Coverage
More warehouses look like better service - until every warehouse starts carrying slow-moving stock, labour sits idle, and inventory quietly explodes. The real question is not “how many locations do we need?” but “which customer promise deserves which network?”
- Nodes are physical or logical points in a supply chain - factories, warehouses, stores, dark stores, hubs, cross-docks or pickup points.
- Echelons are layers in the network - supplier, plant, national DC, regional DC, local fulfilment node, retailer or customer.
- Service coverage means the share of demand that can be served within a promised time, distance, availability or cost boundary.
- Adding nodes usually improves proximity and speed, but increases fixed cost, inventory duplication and coordination complexity.
- Fewer echelons reduce handling and inventory buffers, but may weaken local responsiveness if demand is dispersed.
- The best network is not the fastest network; it is the lowest total-cost network that reliably meets the chosen service promise.
- Interview answers should connect three things: customer promise, demand geography and total landed cost.
Big Picture: Network Design Is a Service-Cost Trade-Off
Think of a supply chain network as a map of promises. Every node you add changes three things at once - how close you are to the customer, how much inventory you must hold, and how complex the operating system becomes.
Core Explanation: Nodes, Echelons and Coverage in One Mental Model
Number of nodes answers: how many locations should exist in the network? A node may be a plant, port, warehouse, sortation centre, fulfilment centre, store, dark store, service centre or pickup point.
Number of echelons answers: how many layers should product pass through before reaching the customer? A two-echelon network may move from central warehouse to customer. A four-echelon network may move from plant to national distribution centre to regional warehouse to retail store.
Service coverage answers: which demand points are covered by the network under a defined service promise - for example same-day delivery, 24-hour replenishment, 95% product availability, or service within a certain radius.
The three decisions are inseparable. A company may add regional nodes to improve coverage, but that creates more inventory stocking points. It may remove an echelon to cut cost, but then last-mile distance can increase. The art is to design the network around demand density and willingness to pay for service.
The Three Design Questions Interviewers Expect You to Ask
A shallow answer says “more warehouses improve delivery speed.” A strong answer says “more nodes improve proximity where demand density and service premium justify the extra fixed cost and inventory duplication.”
Centralised vs Decentralised Networks
A centralised network uses fewer nodes and fewer inventory pools. It usually improves inventory efficiency and control, but may increase delivery distance. A decentralised network uses more nodes closer to customers. It usually improves responsiveness, but raises fixed cost and makes inventory balancing harder.
Key Metrics to Evaluate Nodes, Echelons and Service Coverage
Network decisions should never be judged only by the number of warehouses. Track service, cost, asset use and inventory together.
Notice the tension: service coverage and OTIF push you toward more responsive networks; cost to serve and inventory turns stop you from overbuilding.
Worked Example: Should a Company Add One Regional Node?
Assume a consumer electronics company currently serves South India from one national warehouse. Management is considering one regional warehouse near Bengaluru. The numbers below are hypothetical for interview practice.
Step 1 - Transport saving: ₹120 - ₹80 = ₹40 saving per order. For 100,000 orders, annual saving = ₹40,00,000.
Step 2 - Added cost: Fixed facility cost ₹25,00,000 + inventory holding cost ₹8,00,000 = ₹33,00,000.
Step 3 - Net impact: ₹40,00,000 - ₹33,00,000 = ₹7,00,000 annual cost benefit, plus faster delivery.
Decision: The regional node is worth considering if service improvement also protects sales, improves repeat purchase or supports a premium channel. If demand falls below expectation, the same node can become a cost burden.
Definitions You Can Say in One Breath
- Node: A point in the supply chain where inventory is stored, processed, transferred or served.
- Echelon: A distinct layer of facilities through which product flows from source to customer.
- Service coverage: The portion of demand that can be served within a defined service promise.
- Network optimisation: Choosing facility locations, flows and capacities to meet service at minimum total cost.
If you are weak on the inventory side of this topic, revise setting inventory policy for a multi-product business because every additional node changes safety stock, reorder points and availability.
Case Study: Lenskart and Omnichannel Service Coverage in India
Lenskart shows how service coverage is not only about warehouses - it is about designing nodes for trust, fitting, fulfilment and repeat service.
Eyewear has a difficult service problem. Customers do not only want a product delivered; they need prescription accuracy, frame trial, lens fit, returns support and confidence that the glasses will work. A purely centralised e-commerce model can reduce inventory complexity, but it may struggle with trust and fit in a category where touch-and-try matters.
Lenskart’s move has been to build an omnichannel network in India: online demand capture, physical stores for discovery and service, eye-test touchpoints, and backend fulfilment and lens processing. In network terms, stores act as customer-facing service nodes, while backend facilities handle specialised operations that do not need to sit in every neighbourhood.
The primary driver is service coverage through omnichannel nodes - customers get local access for trial and support without every store needing to behave like a full manufacturing site. Supporting drivers include category focus, standardised operating processes, customer data across channels, and centralised expertise in lens fulfilment.
The strategic lesson: in high-involvement categories, service coverage includes customer confidence. The winning network is not simply the one with the most delivery points; it is the one that places the right type of node at the right customer friction point.
How AI Changes Number of Nodes, Echelons & Service Coverage
1. AI improves demand heat-mapping. Machine learning can cluster demand by pin code, order frequency, basket type, SKU velocity and seasonality. This helps decide whether a city needs a full warehouse, a cross-dock, a pickup point or no local node at all.
2. AI makes dynamic coverage decisions possible. Instead of fixed service zones, companies can estimate real-time feasibility using inventory position, traffic, carrier capacity and order priority. This is especially useful in grocery, spare parts and same-day delivery networks.
3. AI exposes hidden cost-to-serve differences. Two customers with equal revenue can have very different service economics if one requires urgent delivery, fragmented orders and high returns. AI helps segment customers by profitability and operational burden.
Student workflow: Load a company’s annual report, fulfilment notes and your network assumptions into NotebookLM. Ask it to generate: “What network design questions should I ask for this company, and which nodes or echelons create the biggest service-cost trade-off?” For deeper inventory linkage, revise using AI for inventory optimisation and replenishment.
Interview Relevance
“A D2C brand is expanding from metro cities to Tier 2 India. How would you decide the number of warehouses and service coverage?”
Use the phrase “service-cost frontier.” It signals that you understand network design as an optimisation problem, not a warehouse-counting exercise.
Common Mistake
Mistake: Saying “add more warehouses to improve service.” This ignores inventory duplication, utilisation, fixed cost and demand density. Fix: say “add nodes only where the incremental service benefit exceeds the incremental total cost.”