Is a distributed network only for grocery and convenience goods?

Those categories drove it, but any trade where immediacy converts browsers into buyers can justify it. The test is whether customers change their purchasing behaviour in response to speed, not whether they say they value it.

Can third-party providers supply local nodes?

Yes, and it is a common way to test the model without committing to leases. It costs more per order than an owned site at scale, and it lets you learn where demand really is before fixing the network.

How is the range chosen for a local node?

By order frequency and coverage rather than by margin. Work out the smallest set of lines that completes a large share of local orders in full, since a node that regularly forces a split order removes much of the benefit it was built for.

Local nodes or one central site: where should stock sit

Placing stock closer to customers shortens the final leg and lengthens almost everything else. A single site concentrates efficiency and pays for distance; several small ones buy proximity with duplicated inventory and multiplied overhead. The right structure depends on what customers will actually pay for and how much of your range genuinely needs to be near them.

Comparison criteria

Criteria are stated explicitly and neither option is declared a winner: which one fits depends on the constraint that binds hardest in your operation.

Criterion	Distributed micro-fulfilment nodes	Central fulfilment operation
Final leg to the customer	Short and quick, which supports same-day and narrow delivery windows.	Longer, so the promise depends on carrier networks and cut-off times rather than proximity.
Stock efficiency	Range must be duplicated across nodes, raising total inventory for the same service level.	One pool covers all demand, which is the most efficient way to hold a wide range.
Range that can be offered	Constrained to fast lines that justify their space in every node.	Full range available, including slow-moving items no local site could justify stocking.
Fixed overhead	Rent, systems, supervision and equipment repeat at every location.	Concentrated in one place, which is where scale and automation pay for themselves.
Labour	Small teams in many labour markets, with cover for absence hard to arrange at each site.	One large team that can be flexed across shifts and functions.
Replenishment	A continuous internal transport requirement to keep every node in stock.	Inbound arrives once, at one place, and is put away once.
Resilience	Losing one node affects one area, and demand can partly shift to neighbours.	A single point of failure, mitigated only by contingency arrangements elsewhere.
Handling of returns	Returns arrive locally and need either local processing or a further movement.	One process, one location, and a single view of returned stock.

Choose Distributed micro-fulfilment nodes when

Customers buy on immediacy and will pay for it, or a competitor already offers it in your category
A narrow band of lines generates most orders, so local stock can be limited to those
Order density in a city is high enough to keep a small site properly occupied
Delivery cost from a distant site is high enough that proximity pays for the duplication

Choose Central fulfilment operation when

The range is wide and demand is spread thinly across it
Customers accept next-day or standard delivery without a price penalty
Volumes cannot fill more than one site to an efficient level
Investment is better spent on automation and process in one place than on replicating overhead

Duplication is the cost that decides most cases

Holding the same lines in several places raises total stock for a given availability, and the effect grows with the number of nodes. That extra inventory is capital, space and obsolescence risk, and it is the main reason distributed models look attractive in a plan and disappointing in a ledger. The usual compromise is a tiered structure. A short, fast-moving range sits locally to serve immediacy, while the long tail is served from the central site. That preserves most of the customer benefit and confines duplication to lines that actually turn.

Occupancy, not proximity, makes a small node work

A local site earns its fixed cost only if it is busy. Order density within its catchment is therefore the decisive number, and it is the one most often assumed rather than measured. Map where orders actually originate before choosing locations, and be sceptical of a node whose catchment relies on growth that has not happened. Staffing is the second constraint. Small teams cannot absorb absence, holidays or a sudden peak without cover, so either sites must be close enough to share staff or the plan must carry the cost of slack in each one.

Complexity grows faster than the number of sites

Every additional location adds inventory decisions, replenishment movements, a stock accuracy risk and a place where an order can be allocated wrongly. Order routing has to decide which site serves which order, and it has to handle split orders, stock-outs and returns arriving at the wrong location. That overhead is real and it is systems work. Before committing to a distributed network, establish that order management can allocate across sites reliably. Where it cannot, the network will spend its savings on manual intervention and mis-shipments.

Frequently asked questions

Is a distributed network only for grocery and convenience goods?: Those categories drove it, but any trade where immediacy converts browsers into buyers can justify it. The test is whether customers change their purchasing behaviour in response to speed, not whether they say they value it.
Can third-party providers supply local nodes?: Yes, and it is a common way to test the model without committing to leases. It costs more per order than an owned site at scale, and it lets you learn where demand really is before fixing the network.
How is the range chosen for a local node?: By order frequency and coverage rather than by margin. Work out the smallest set of lines that completes a large share of local orders in full, since a node that regularly forces a split order removes much of the benefit it was built for.

Data limitations

Logistics figures are operator-supplied inputs, not market data. GeoBusinessIQ holds no freight rates, transit times, capacity, or throughput data and does not estimate them — every result reflects only the figures you enter.

Explore the graph

Across GeoBusinessIQ

Sources

OECD — OECD — economic and tax statistics (accessed 2026-05-14; reviewed 2026-05-18)
Covers: Comparable corporate tax, statutory rate, and economic indicators across member and partner economies.
Does not cover: Effective tax rates, deductions and incentives, local surtaxes, and personal residency rules.
Why it matters: Used as a cross-country baseline to sanity-check rates against primary tax-authority figures.
Review cadence: Annual, plus on major statutory changes.
Eurostat — Eurostat — official statistics of the European Union (accessed 2026-05-14; reviewed 2026-05-18)
Covers: EU-harmonised VAT rates and economic statistics for EU/EEA member states.
Why it matters: Used for EU VAT and member-state economic figures where an EU-harmonised series is preferable.

Educational and operational information only — not legal, customs, tax, insurance, or financial advice. Requirements vary by jurisdiction, commodity, and contract; confirm with the relevant authority or a qualified adviser before acting.

Last updated: 2026-08-25