Warehouse settings

Stockly → Warehouses → warehouse → General. A building’s settings decide what the module may do there and what it will never propose.

The basics

Name, Code — the building’s name and unique code.
Description — a helper note.
Priority — how early this warehouse is reached for; a lower number means earlier.
Active — an inactive warehouse drops out of fulfilment while keeping its data.
Default warehouse — the module’s default.

Storage strategy

Storage strategy decides how many products may sit on one location:

Shared (multiple products per bin) — one location, many products.
Dedicated (one product per bin) — one location, one product.

The dedicated strategy keeps one product per location, but it blocks manual stock changes on locations that would end up holding several products. For that reason location mapping, when it finds such locations, offers to switch to the shared strategy.

What this building can do

Four switches describe the building’s role in the network. They affect allocation: the module never proposes work a building cannot carry out.

Ships to customers — parcels leave this building. Switch it off for a place that never dispatches: a shop that hands goods over at the counter, or a pure storage site. Orders requiring shipping will not be allocated here.
Hands goods over on site — goods can be handed to a customer in person: counter sales, personal pickup. Switch it off for a place customers never visit.
Can send stock to other warehouses — the building may give up stock in an internal transfer. Switching it off stops new transfers being created from here; those already on the road complete.
Can receive stock from other warehouses — the building may receive transfers. Switching it off stops new transfers towards it; those under way still arrive, because goods in transit must always have a destination.

→ Making a warehouse fulfil orders — these switches and the channel assignment, in the order allocation asks about them.

Receiving and carriers

Default receiving mode sets how goods are received by default:

Loose (piece / lot level) — goods counted in pieces and lots,
License plate (pallet / container) — goods grouped onto a scannable carrier at receipt.

The choice can be changed per line while receiving.

License plate (LP) mode decides whether put-away must use a carrier:

Off (no license plates) — no carriers,
Optional (LP allowed, loose is fine) — carriers allowed, loose is fine,
Required (put-away must scan an LP) — put-away must scan a carrier.

This is a policy, not a technical limit: loose stock is always permitted. → Handling units

Handling somebody else’s goods

Owner bin sharing matters in warehouses serving several owners:

Shared (unowned bins are open to all) — bins with no owner accept any client’s goods, while racks and bins with an owner stay exclusive,
Strict (only matching-owner bins) — goods only go to their owner’s bins, which requires every rack to have an owner assigned.

→ Owners

Location profile

Default location profile is a capacity and storage template inherited by every floor, rack and bin in the building. Exceptions are set lower down — on a floor or a rack. → Location profiles

Sales channels

Assigned sales channels names the channels this building serves. Below it, Priority per sales channel overrides the warehouse priority for a single channel, where a lower number means an earlier choice. An empty field inherits the building’s priority.

A building with no assignment is a candidate only for a channel to which no warehouse at all is assigned. → Sales channels and warehouses

Shelf floor

Shelf floor mode decides what happens to stock protected on the shelf. The floor always applies to the network: transfers and fulfilment from other buildings never draw below it. The difference concerns local sales:

Reserved — not for sale — the protected units disappear from published availability,
Protected, still for sale here — they stay sellable in this building.

Pick progress

Pick progress selects where a picking wave keeps its progress:

On the server, scan by scan — every scan goes to the server immediately, so a refresh loses nothing and a second device can work the same wave,
In the browser session — the older behaviour: progress is stored in the session, and a closed tab loses the last seconds of work.

The setting applies to waves created from now on; a wave already under way keeps its own. Put-away, transfers and stocktakes have their own model and are unaffected.