¶ Warehouse - stock, reservations and warehouse operations
Warehouse management in Hummerce runs the store's warehouse operations: stock levels in one or several warehouses, reservations when an order is placed, and warehouse operations that follow the same logic known from ERP systems (receipts, issues, transfers between warehouses, stocktakes). It's what decides whether an item shows as available and whether the customer can buy it.
Last updated: 2026-09-29 (a core platform mechanism, with no release version given in the source).
¶ Benefits and use cases
- Multiple warehouses in one store - separate stock for the main warehouse, a returns warehouse, a branch or a showroom, with a priority order for reservations.
- Automatic reservation on order - the store picks the highest-priority warehouse on its own, and reaches for the next one when that one is short on stock.
- A full history of warehouse operations - every stock change (receipt, issue, stocktake, transfer) is kept as a document, also linked to an order or invoice where relevant.
- ERP integration - a warehouse marked as integrated pulls stock from an external system, without manual warehouse operations in the store.
- Control over selling below stock - both for the whole store and for each item separately, you can decide whether it's possible to order more than what's in stock.
- The basis for a physical store network and multiple views - a separate warehouse per location or per view lets you run several points of sale from one panel (Views, Physical stores).
- The store can run any number of warehouses, each with its own settings: symbol, name (per language), availability, whether it's a returns warehouse, whether it's local (the store's own) or integrated with an external data source (e.g. ERP), availability time, minimum quantities, minimum balance and priority.
- An integrated warehouse doesn't accept manual warehouse operations in the panel - its stock comes from an external system, typically ERP.
An item's stock is always determined per specific warehouse and includes:
- Quantity - the physical quantity of the item in the warehouse, in its unit of measure (Units of measure and sale),
- Reservations - how much of that quantity is already reserved for placed orders,
- Availability time - used on the item page to tell the customer how quickly the item is available (defaults to the warehouse's own setting),
- Minimum quantities and minimum balance - thresholds below which the item stops being counted as available.
Every change to quantity or reservations happens through a warehouse operation - warehouses integrated with an external data source (ERP) don't accept operations manually in the panel. Types of operations:
| Symbol |
Name |
Effect |
| PZ |
External receipt |
Receiving goods into the warehouse - increases quantity |
| WZ |
External issue |
Issuing goods from the warehouse - decreases quantity |
| IN |
Inventory |
Sets a new, verified quantity for the item |
| MM |
Inter-warehouse transfer |
Moves a quantity of the item from one warehouse to another |
| REZ |
Reservation |
Increases the reserved quantity |
| WREZ |
Reservation cancellation |
Decreases the reserved quantity |
| RW |
Internal consumption |
Decreases the item's quantity for use in production |
| PW |
Finished goods receipt |
Increases the item's quantity from a production receipt |
| ZO |
Customer return receipt |
Increases the item's quantity from accepting a return |
- Operations are added manually from the operations list (for several items at once), from the item page (for a single item), or from the order (for an order line); some operations are added automatically by the store (e.g. a reservation once the order is placed).
- An operation can carry extra data - an issue or receipt date, a linked invoice, order, or partner - and can be printed as a document.
¶ Item availability and buyability
- Warehouse availability is calculated as: Quantity - Reservations - Minimum balance (e.g. 10 - 3 - 3 = 4 available), and is checked only for items with the Availability attribute set to yes.
- The store can set an item's Availability attribute on its own based on actual warehouse stock - a task does this once a day for all items and every 2 minutes for items that have changed.
- Item lists show aggregated availability - the sum across all warehouses taken into account, not a breakdown per location.
- Buyability of an item depends on the buyability attribute and actual warehouse availability (taking units of measure and any allowance to order below stock into account).
- Warehouse operations in an order only apply to items for which warehouse management is enabled.
- When an item has no allowance to order below stock, the store enforces quantity <= available: it shows a message in the cart (without changing the quantity), and doesn't allow placing the order until the quantity is corrected.
- Once the order is placed, the store reserves the item (a REZ document) in the highest-priority warehouse; if that one is short, it tries the next warehouses by priority. With an allowance to order below stock, the surplus above the available quantity is reserved in the highest-priority warehouse.
- A reservation can be manually moved to a different warehouse from the order.
- Changing the order status to one meaning "ready to ship" converts reservations into an issue from the warehouse (WREZ -> WZ); this status can't be set without the corresponding quantities in the warehouse.
Warehouse management and warehouse operations are a core mechanism of the Hummerce platform - available in all current versions. Warehouse management through the AI assistant - as part of the MCP server, which has been available since version 2.34 (recommended 2.35.55 or newer).
- Units of measure and sale - the warehouse always keeps stock in the item's stock unit.
- Views - the "Multi-viewable" warehouses setting limits an item's availability in a given view to the warehouses assigned to that view; the basis for a physical store network (Physical stores).
- Purchases and goods receipt - receiving goods into the warehouse (a PZ document) closes a purchase once the received quantity covers the ordered one.
- Stock import - a bulk stock update through an Excel file, via the Inventory operation.
- ERP integration (Comarch ERP XL, Microsoft Dynamics NAV / Navision) - for integrated warehouses whose stock comes from an external system.
- The warehouse works after the update - one primary warehouse is part of the standard configuration. Setting up an additional warehouse or an ERP integration is implementation work.
- Minimum estimated time:
- an additional local warehouse with a priority setting - from 2 h,
- integrating warehouse stock with ERP (an integrated warehouse) - quoted separately after analyzing the ERP system.
- The time for a specific implementation depends on its scope - we quote it individually.
- What the time depends on:
- the number of warehouses and how the reservation priority between them is decided,
- the need for ERP integration and how often stock is synced,
- availability and below-stock ordering rules per item,
- the link to views (a warehouse per view/showroom) - see Physical stores.
- An integrated warehouse doesn't accept manual warehouse operations in the panel - only the external system changes its stock.
- Aggregated availability on the item list and product page is the sum across all warehouses taken into account - a breakdown of availability per location requires additional template work.
- A reservation on order goes to the highest-priority warehouse, not automatically to the warehouse of the chosen pickup location - priorities need to be set deliberately when warehouses correspond to showrooms or views.
- Changing the order status to a shipping status is blocked without the corresponding quantities in the warehouse - this needs to be accounted for in the order handling process.
- We do not verify the warehouse configuration for legal compliance (e.g. warehouse record-keeping requirements in a specific industry).
- Breaking down aggregated availability into individual warehouses/locations directly on the product page, without additional template work.
- Automatically routing reservations to the warehouse linked to the chosen pickup location, without manually setting priorities.
Does Hummerce support multiple warehouses in one store?
Yes, with separate stock, priority and settings for each warehouse.
Can a warehouse pull stock directly from ERP?
Yes - a warehouse marked as integrated doesn't accept manual operations in the panel, only stock from the external system.
Can selling an out-of-stock item be blocked?
Yes, with the allowance-to-order-below-stock setting - by default for the whole store, with the option to override it per item.
Is the availability shown to the customer calculated automatically?
Yes, using the formula quantity minus reservations minus minimum balance, with the option to automatically set the availability attribute through a scheduled task.
How long does setting up an additional warehouse take?
From 2 h for a local warehouse with a priority setting; we quote ERP integration separately after analyzing the system.
Want to see how warehouse management could work in your store? Book a free demo (in Polish).
- Warehouses: Warehouse -> Warehouses - list and details of warehouses (symbol, name, availability, returns warehouse, local, availability time, minimum quantities, minimum balance, priority).
- Item stock: item editor -> Warehouse tab (stock per warehouse for a single item) and Warehouse -> Products in stock (stock for many items at once).
- Warehouse operations: Warehouse -> Operations (for many items), the Warehouse tab on the item page (for a single item), or from the order preview (for an order line).
- General settings: Configuration -> Settings, the Warehouse group - including whether warehouse operations are performed, whether the store sets item availability on its own, the default value of "Manage warehouse stock" and the default value of "Allow ordering below stock"; both of the latter can be overridden per item. The "Multi-viewable" warehouses setting is described under Views.
¶ REST API and MCP
- REST API: reading and writing warehouses, stock and warehouse operations (REST API).
- MCP (AI assistant - MCP server):
ec2_warehouse_list - list of warehouses with a summary (available ones only by default),
ec2_warehouse_create - creates a warehouse (symbol, name, priority, whether local); stock usually comes from ERP - this tool only creates the warehouse it's posted to,
ec2_warehouse_stock_overview - item stock in a specific warehouse,
ec2_inventory_check_stock - warehouse stock for a single item,
ec2_inventory_low_stock_report - items below a given quantity threshold,
ec2_inventory_update_stock - changes an item's warehouse stock (add, subtract or an absolute value),
ec2_inventory_forecast - how many days the current stock will last at the current sales pace; a simple average over a period, without seasonality or trend - treat it as a list to review, not a ready-made purchase order.
An item's warehouse stock is described by: Quantity, Reservations, Availability time, Minimum quantities and Minimum balance (described in How it works). Item availability in the store is controlled by two item attributes, Availability and Buyability, and two settings overridable per item, Manage warehouse stock and Allow ordering below stock.