Skip to content

Reservations and availability

Three numbers that are easy to confuse:

  • stock — how many units physically lie there,
  • reservation — how many of them are already promised to somebody,
  • availability — how many are left to sell.

The shop displays the third figure to customers, and the warehouse works with the first. The reservation links the two.

An order declares demand, and the module looks for cover: it picks a building and, within it, specific goods. From that moment those units are promised: they still lie on the shelf, but nobody else will buy them.

A reservation is released when the order is picked, cancelled or returned. Each of those shows in movement history as Reserve and Release.

An order with no cover becomes a backorder: it waits for goods instead of taking units reserved for another order.

A reservation is not limited to building level; it can name a specific bin location. Picking then knows which location to go to, and two waves do not send two operators for the same unit.

This is also the point at which a reservation is most often misread.

A warehouse can protect part of its stock from the network: transfers and fulfilment from other buildings never draw below the floor. The Shelf floor mode setting decides whether the protected units remain sellable in that building or disappear from published availability. → Warehouse settings

  • The Reserved column on the stock list.
  • The Reserved figure on the product page, where clicking shows the orders holding the goods. → Stock on the product page
  • The integrity check, where reservations are suspected of having drifted from stock: it has dedicated checks for it, such as a reservation without an order, a reservation on an empty location, and over-reserved values.

For developers: reservations are readable per order or per location, as described under reading stock.