★★★★★Bespoke software for B2B·One-off build fee, low monthly retainer·You own the software

Sector

Stock control software for businesses with more than one location

Stock control software for a single warehouse just needs to count what's on the shelf. Add a second location and it has to track stock in transit between them, separate what's allocated from what's actually available, and stay accurate without a full annual stocktake.

Haystak · 11 August 2026 · Updated 11 August 2026 · 7 min read

A warehouse worker using a handheld scanner as part of a stock control software system

Stock control software tracks what you hold, where, and what's still free to sell. Single-site, that's a straightforward count. Once stock sits across multiple warehouses or depots, the system also has to handle stock moving between them, orders reserving stock that hasn't shipped yet, and counts that stay accurate without shutting the warehouse for a weekend.

Most of the stock control problems we see in multi-location businesses aren't caused by bad software. They're caused by a system built for one location being stretched across several without anyone rethinking what 'available' actually means.

Why multi-location changes the problem

With one location, stock control answers one question: how much do we have. With more than one, it has to answer several at once - how much is at each site, how much is moving between sites right now, and how much of that total can actually be promised to a customer today.

ConceptSingle locationMulti-location
Stock countOne number per SKUNumber per SKU per location, plus a total
TransfersNot applicableStock in transit, owned by neither location until received
AllocationReserved vs free to sellReserved vs free, per location, with transfer rules between them
Cycle countingFull stocktake, occasionallyRolling counts by location so no site ever fully closes

Stock in transit is where most systems fall down

When stock is despatched from one location to another, it should stop being counted as available at the sending site and not yet be available at the receiving one, until it's actually booked in. A surprising number of systems either drop it from both counts or leave it counted at the sending site until someone remembers to move it manually.

Getting this wrong shows up as stock that's 'in the system' but nowhere a picker can actually find it - one of the most common causes of failed order promises in multi-site distribution businesses.

Allocation vs availability

Allocated stock is stock already committed to an order, even if it hasn't shipped. Available stock is what's left to promise to a new customer. Confusing the two is how businesses oversell - showing stock as available because it's physically on the shelf, while it's actually earmarked for someone else's order.

  • On hand - physically present at a location, allocated or not.
  • Allocated - committed to a specific order, whether or not it's picked yet.
  • Available to promise - on hand, minus allocated, minus anything held back for a reason (quality hold, minimum stock policy).

A system that only shows on-hand quantity will look accurate and still cause overselling, because it's answering the wrong question at the point of sale.

Cycle counting instead of an annual stocktake

A full stocktake across several sites is disruptive and, in practice, often less accurate than a well-run cycle count - because closing the warehouse for a weekend doesn't stop errors creeping back in the other 51 weeks. Cycle counting spreads counts across the year, prioritising high-value or fast-moving lines more often.

  1. 01Classify stock by value and movement (a simple ABC split is enough to start).
  2. 02Set a counting frequency per class - weekly for the highest-value lines, quarterly for the slowest.
  3. 03Investigate variances immediately rather than batching them for a quarterly review.
  4. 04Feed corrected counts straight back into available-to-promise, not just a separate stocktake record.

Barcode and handheld working

Multi-location stock control depends on accurate, timely data entry at goods-in, transfer and despatch - and that's only realistic with barcode scanning on handhelds rather than paper sheets typed up later. The delay between a physical movement and its record in the system is exactly the window where stock figures go wrong.

This matters more, not less, as you add locations, because errors at one site now affect availability promises made from every other site drawing on the same total.

Off-the-shelf vs bespoke for multi-location stock

Established stock control and distribution products handle standard multi-location transfers, allocation and cycle counting well, and are worth trying before building anything. Where they struggle is unusual allocation rules, integration with a bespoke sales process, or a warehouse layout that doesn't map to the product's model of a location - which is where our distribution and wholesale software work usually starts.

If you're weighing that decision generally rather than for stock specifically, see our guide to custom software vs off-the-shelf. For a view on your own setup, get in touch with how many locations you run and what currently goes wrong.

✦ Where this fits

More on this from us: our work in distribution and wholesale software.

Questions we get asked

Common questions

What's the difference between allocated and available stock?

Allocated stock is already committed to an order, even before it ships. Available stock is what's left after allocations, and it's the figure that should be shown when quoting a new order.

How should stock in transit between locations be recorded?

It should leave the sending location's available figure the moment it's despatched and only join the receiving location's figure once it's actually booked in - never counted twice or dropped from both.

Is cycle counting better than an annual stocktake?

For most multi-location businesses, yes. It spreads counting effort across the year, avoids full site closures, and catches errors closer to when they happen.

Do we need handheld scanners for stock control?

If accuracy matters and you're running more than one location, yes in practice - the delay between a paper record and a system update is where stock figures drift.

Can our current single-site stock system be extended to multiple locations?

Sometimes, if it was built with a location concept from the start. If 'location' was bolted on later, it's worth testing transfers and availability carefully before committing, rather than assuming it will scale.

Running stock across more than one site We'll tell you what we'd build.

Tell us how transfers and allocation currently work and we'll tell you whether your system needs configuring properly or replacing.

No pitch deck · We map your process · You own the software