> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/pro/warehouse.md). # Warehouse overview Warehouse in Equipme Pro: stock warehouse vs. customer warehouses, storage locations, batches, stock statuses, and how goods receipt, reservation and stock withdrawal work together. **Path:** Sidebar → **"Warehouse"** In the warehouse you manage the physical goods you keep on hand for your customers. Equipme Pro distinguishes between two types of warehouse: | | **Stock warehouse** (your own stock) | **Customer warehouse** (supplier warehouse at the customer) | | --------------------- | ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | | What is stored there? | Purchased products (stock items) that are not yet firmly assigned to a customer or are reserved for an order | Services that belong to a specific customer but are still stored with you, e.g. pre-orders or returns | | Level | Individual devices (products) in batches at storage locations | The customer's services (service instances) | | Filled by | [Goods receipt](/pro/warehouse/receiving.md), ["Book inventory"](/pro/warehouse/stock-warehouse.md#book-inventory) | Completed pre-orders, returns, customer orders into your warehouse | | Emptied by | Picking for customer orders, [stock withdrawal](/pro/warehouse/stock-withdrawals.md) | Call-off or delivery to the customer | | Page | ["Warehouse"](/pro/warehouse/stock-warehouse.md) | ["Customer warehouses"](/pro/warehouse/customer-warehouses.md) | ## Pages in the warehouse | Page | Purpose | | -------------------------------------------------------------- | --------------------------------------------------------------------------------------- | | ["Goods receipt"](/pro/warehouse/receiving.md) | Book in delivered stock orders | | ["Warehouse"](/pro/warehouse/stock-warehouse.md) | Stock per batch and storage location, book inventory, change storage location, withdraw | | ["Stock withdrawals"](/pro/warehouse/stock-withdrawals.md) | Log of all withdrawals (picking and manual withdrawals) | | ["Customer warehouses"](/pro/warehouse/customer-warehouses.md) | Your customers' services that are kept ready for them in your warehouse | ## Terms | Term | Meaning | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Warehouse** | Your stock warehouse with an address. You need exactly one. As long as none exists, the warehouse pages show "No warehouse was found for your company. Create one to use warehouse management." with the **"Create warehouse"** button (name and address). | | **"Storage location"** | A freely named place in the warehouse, e.g. "Shelf A3". New storage locations are created automatically when you enter a new name while booking in (max. 50 characters). | | **Batch** | One booking: one product, one quantity, one storage location, one date. Every goods receipt posting and every "Book inventory" creates a batch. | | **"Stored"** | The device is unassigned in the warehouse and available for new orders ("Available"). | | **"Reserved"** | The device is assigned to a customer order and is waiting to be picked. | | **Stock item** | A product marked as "Stock item" in the [product master data](/pro/portfolio/products.md). Only such products are managed through the warehouse. | ## How procurement, warehouse and fulfillment work together 1. A confirmed customer order creates demand. Unassigned goods in the stock warehouse are **reserved automatically**. 2. If goods are missing, an [order proposal](/pro/procurement/order-proposals.md) is created, and from it an [order](/pro/procurement/purchase-orders.md). 3. In [goods receipt](/pro/warehouse/receiving.md) you book in the delivery. Whatever is assigned to an order becomes "Reserved", the rest "Stored". 4. In [picking](/pro/fulfillment/picking-production-shipping.md) you withdraw reserved devices for the order and record, for example, serial numbers. The withdrawal appears under ["Stock withdrawals"](/pro/warehouse/stock-withdrawals.md). ## Who can do what? | Role | Warehouse | | -------------------------- | ---------------------------------------------------------------------------------------- | | **"Warehouse Manager"** | Book goods receipts, book inventory, change storage location, withdraw, create warehouse | | **"Warehouse controller"** | View warehouse and stock only | | **"Administrator"** | Full access | Without read access to the warehouse, the "Warehouse" menu item is not shown. ## Frequently asked questions **Can I create more than one warehouse?** Equipme Pro works with one stock warehouse per provider. Subdivide it using storage locations. Customer warehouses are independent of this and each belongs to one customer. **What is the difference between "Reserved" in the stock warehouse and a service in the customer warehouse?** A reserved device is still your goods, earmarked for an order. A service in the customer warehouse has already been created as a service for the customer and belongs to them, but is still physically with you. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hub.equipme.io/pro/warehouse.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.