Warehouse

Definitie

Store → Warehouse → create | balances | movements | transfer

A warehouse is a physical or logical stock location where inventory movements post. Inventory answers how much sellable stock you have; Warehouse answers where it sits; Movements are the audit trail of how it changed. Sellable product stock is what shoppers and POS (Point of Sale) see; warehouse balances are the location ledger behind it.

Compatibility

• Full multi-warehouse UI: Professional+ (confirm Store → Billing).
• Starter/Growth inventory still uses a default warehouse bootstrap without the full multi-warehouse screen.
• Only one default warehouse at a time — marking a new default clears the previous one.
• Branches (Enterprise) can be linked to warehouses — Branch ≠ Warehouse.
• Staff need warehouse / inventory permissions from the store owner.

Mental model

Inventory   → how much sellable stock?
Warehouse   → where is the stock?
Movement    → how did stock change?
Transfer    → relocate between warehouses (company total unchanged when fully received)
Branch      → outlet org structure (Enterprise) — not a stock location

Path & fields

Store → Warehouse
  warehouse: { name, code, address?, isDefault?, branchId? }
  balance(product, warehouse)
  movements(product, warehouse)
  transfer(fromWarehouse, toWarehouse, lines[])
    status: draft → approved → in_transit → received

Behavior

• Purchase GRN (Goods Receipt Note) and bill-without-GRN post to the store’s default warehouse (current purchase UI does not pick a warehouse per GRN).
• Transfer does not create or consume company stock overall: when fully received, source −qty and destination +qty; company total unchanged.
• Successful transfer movements on both sides link to the same StockTransfer document (transfer ID / transferNo).
• Transfer UI is stepwise: create → advance to in_transit (leave source) → received (arrive destination).
• Investigate Movements before “fixing” a balance mismatch.

Create a warehouse

1. Confirm Professional+ (or higher) on Store → Billing.
2. Open Store → Warehouse.
3. Choose Create / New warehouse.
4. Enter a clear name and code (required); add address if ops need it.
5. On Enterprise, optionally assign a Branch.
6. Mark one warehouse as default for single-location or primary receiving (only one default at a time).
7. Save, then verify it appears in the list and transfer pickers.

Transfer stock between warehouses

Warehouse A   −10
      ↓ Transfer (fully received)
Warehouse B   +10
Company total = unchanged

1. Open Store → Warehouse → Transfer (need at least two warehouses).
2. Select from-warehouse and to-warehouse.
3. Add product lines and qty (cannot exceed available balance on the source).
4. Create the transfer, then advance status until received (in_transit leaves source; received credits destination).
5. Confirm balances on both warehouses and the product’s sellable stock after refresh.

Examples

Single shop
  Default warehouse “Main”
  → GRNs and POS sales hit Main

Shop + godown
  Create “Front” and “Godown”; set Godown as default (GRN posts to default)
  Supplier → GRN → Godown +100
  Godown → Transfer 20 → Front (fully received)
  → Godown 80 · Front 20 · Total 100

Mismatch
  Balance looks wrong → open Movements for that product/warehouse before changing anything else

Common errors

• No Warehouse menu — upgrade to Professional+ or ask for warehouse permission.
• Transfer qty too high — reduce to available balance on the source warehouse.
• Stock doubled after purchase — see Purchases / GRN troubleshooting; Warehouse only shows the posted result.
• Confused with Branches — Branch = org outlet (Enterprise); Warehouse = stock location.

Zie ook

• Ops & people overview
• Purchases and inventory
• GRN (Goods Receipt Note)
• Production — turn materials into finished goods
• Projects
• Service jobs (repairs and work orders)
• Fixed assets (equipment you own)
• Branches
• Core concepts (journals, stock, parties)
• Business Suite troubleshooting