Skip to main content
The Stock Locations page is where the physical layout of your warehouse is described inside CloudHub. Aisles, shelves, bin locations, SKU placement. Without this layer, Goods Received cannot record put-away, Order Picking cannot direct pickers to the right shelf, and the Stock Movement Log cannot trace a unit to a specific location. For single-room operations, the setup is light: one warehouse, a few bins, done. For multi-room or multi-site operations, the same model scales without limit.

​
The page

Path: Home, Locate, Warehouse and Stock Locations. The page opens with a six-tab navigation at the top of the grid:
TabWhat it shows
WarehouseWarehouses and their summary product counts
AisleAisles within a warehouse
ShelfShelves within an aisle
Bin LocationIndividual bin locations within a shelf
Stock TakeStocktake reconciliation entries
SKU LocationsThe SKU-to-bin mapping (which SKUs sit in which bin)
Top-bar actions vary by the active tab: + Add Warehouse, + Add Aisle, + Add Shelf, + Add Bin Locations, - Delete Warehouse, - Clear Warehouse. Destructive actions are colour-coded so they are not pressed by accident. The Warehouse-tab grid columns are:
ColumnWhat it means
ActionEdit
Warehouse IDInternal identifier
Warehouse NameFriendly name (e.g. “London W1”)
Bin Location NameDefault bin (when there is one)
Warehouse LocationAddress line for shipping label routing
No.of ProductsDistinct SKUs held
Product QuantityTotal units held
Last Added OnMost recent put-away timestamp

​
The hierarchy

The location hierarchy goes Warehouse, Aisle, Shelf, Bin. Each parent contains the next child. 
Warehouse "London W1"
  └─ Aisle "A"
       └─ Shelf "A-1"
            └─ Bin "A-1-001"
            └─ Bin "A-1-002"
Most multichannel sellers run a flat structure: every SKU has a bin, and the bin name is the readable address (A-1-001). Larger operators use the full hierarchy for warehouse mapping. The structure is configurable per warehouse. A new warehouse can be flat (just bins, no aisles) or fully nested. The picking workflow walks whatever hierarchy you defined.

​
Setting up a new warehouse

The first-time setup is:
  1. Add Warehouse. Click + Add Warehouse. Name, ID, location address.
  2. Add Aisles (optional, for nested layouts). Inside the warehouse, define each aisle.
  3. Add Shelves (optional). Inside each aisle.
  4. Add Bin Locations. Define each bin. This is the granular address that pickers will read.
  5. Map SKUs to bins. On the SKU Locations tab, assign each SKU to its bin (or leave it for first put-away to set automatically).
For an operational shortcut, many sellers skip aisles and shelves and define bins directly under the warehouse, naming each bin after its physical address (“A-1-001”). This works for small to mid-size operations and keeps the data model lean.

​
SKU Locations tab

The SKU Locations tab is the assignment of SKUs to bins.
ColumnWhat it means
SKUThe internal SKU
Product NameProduct name
WarehouseWhich warehouse
Bin LocationWhich bin
QuantityUnits held in this bin
Last UpdatedMost recent put-away or stocktake adjustment
Many operators allow a SKU to live in more than one bin (different cohorts of received stock). The SKU Locations grid shows one row per SKU-bin combination.

​
Stock Take tab

A stocktake is a periodic recount where physical quantity is reconciled against the system quantity. The Stock Take tab records each stocktake event and the variance found. Use cases:
  1. End-of-year stocktake. A full count of every bin against the system. Variance becomes the stock-provision adjustment in finance.
  2. Cycle counting. A rolling count of one aisle per week. Variance is small, recorded as it happens, and never blows up into a big year-end event.
  3. Investigation count. When the Stock Movement Log shows an unexplained adjustment, a targeted recount confirms the actual.
Stocktake variance updates the Current Quantity in the Products report and sources the audit trail in the Stock Movement Log.

​
Multi-warehouse routing

When you operate two or more warehouses, the order workflow needs to know which warehouse fulfils which order. Configure this under Order Workflow. Common routing rules:
  1. By customer location. UK orders ship from the UK warehouse, EU orders from the EU warehouse.
  2. By channel. Amazon orders from one warehouse (3PL), webstore orders from another (own warehouse).
  3. By SKU. Bulky SKUs stocked at one location, small parcels at another.
The Customer Services console and the Order Stages report both surface the assigned warehouse on each order.
NeedWhere to go
”Which warehouse holds SKU DK001B right now?”Ask Viq, plain-English query
”Show me variance from the last cycle count”Stock Take tab inside this page
”Why is warehouse 2 throughput slower than warehouse 1?”Vortex Mind, operational diagnostics
”Open a fix to relocate slow-mover SKUs to overflow bins”Actions Kanban

​
Common questions

Do I have to use aisles and shelves, or can I just have bins? Just bins is fine. Many operators define bins directly under the warehouse with self-describing names (“A-1-001”) and skip aisles and shelves entirely. Use the full hierarchy only if your warehouse is large enough that aisle-level grouping is useful for picking routes. What happens when I delete a warehouse with stock in it? The system asks for confirmation and refuses to delete a warehouse with non-zero stock. Move stock to another warehouse via stocktake-style adjustments first, then delete. Can I bulk-import bin locations and SKU placements? Yes. The roadmap includes a CSV upload path for bins and SKU-bin mappings. For now, the Vendor Central Inventory Import profile system can be repurposed for SKU location updates if you have a large initial set. Does CloudHub support 3PL warehouses I do not control? Yes. Add the 3PL as a warehouse in CloudHub. The operator at the 3PL either enters putaway and dispatch into CloudHub directly (give them a user account with limited permissions), or your team enters it from a daily file the 3PL sends.

​
Next steps