> 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/customer-warehouses.md). # Customer warehouses Customer warehouses in Equipme Pro: your customers' services kept ready in the supplier warehouse, e.g. pre-orders and returns. Activation per customer, call-off and delivery. **Path:** **"Warehouse" → "Customer warehouses"** A customer warehouse (on the customer's side it is called the **supplier warehouse**) is a warehouse you run for a specific customer. It holds services that already belong to the customer but are still physically with you, e.g. pre-ordered devices for future employees or returned devices that are to be issued again. The customer calls them off when needed, and you deliver. The **"Customer warehouses"** page shows all services stored in your customers' supplier warehouses, across all customers. {% hint style="info" %} The customer warehouse is not your [stock warehouse](/pro/warehouse/stock-warehouse.md). The stock warehouse holds your own stock items that have not yet been sold. The customer warehouse holds finished services that belong to a customer. {% endhint %} ## Activate the customer warehouse for a customer Every direct customer automatically gets a supplier warehouse with your company name when they are created. Whether it is active is something you set when [creating the customer](/pro/customers/create-and-invite-customers.md) or later in the [customer details](/pro/customers/customer-details.md): | Setting | Effect | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **"Supplier warehouse active"** | "You provide your warehouse to the customer for orders, returns and call-offs." The customer can order into this warehouse, send devices back to it and call them off from it. | | **"Allow pre-orders"** | "The customer can pre-order designated products from you (enables the supplier warehouse)." | Whether a product can be pre-ordered is something you also set on the offer with the **"Allow pre-orders"** switch (see [Offers and pricing](/pro/portfolio/offers-and-pricing.md)). ## The list | Column | Content | | ----------------------------------- | ---------------------------------------------------- | | "Id" | Number of the service | | "Service name" | | | "Customer" | Who the service belongs to | | "Supplier" | Who supplies the service | | "Activation date", "Remaining term" | If the service was already activated (e.g. a return) | | "Additional information" | Further details about the service | | "Status" | Usually "Ready for delivery" | You can show further columns (e.g. "Location", "Employee", costs) via the column selection. Use the export button to download the list as an Excel file. A click opens the service's detail page in [Service instances](/pro/operations/service-instances.md). If the customer provides the service internally themselves or it comes from a partner supplier, you see a notice instead and no details. ## How services get into the customer warehouse | Route | Process from your perspective | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Pre-order** | The customer orders with the "Pre-order" provisioning. You process the position like any order in [open positions](/pro/fulfillment/open-positions.md) (purchasing, goods receipt, picking). On completion the service is **not activated** but set to "Ready for delivery" and then sits in the customer warehouse. | | **Order into the warehouse** | The customer selects the supplier warehouse as the destination of an order. | | **Return** | The customer sends a device back. Once the return is completed, it sits in the customer warehouse with "Ready for delivery". For this, the customer's supplier warehouse must be active. | {% hint style="warning" %} For pre-orders, equipme points this out in the position details: "Since this is a pre-order, the status should only be set to Ready for delivery once the customer has requested delivery. …" {% endhint %} ## Call-off and delivery When the customer needs a device from the customer warehouse, they request it ("Request provision" in warehouse management or "From inventory" in the marketplace). On your side, a position of type **"Delivery call-off"** appears in [open positions](/pro/fulfillment/open-positions.md). **No new order is placed with the supplier**: you deliver the existing device. The service goes through "Delivery requested (outgoing)", "In delivery (outgoing)" and becomes "Active" for the customer. How the customer experiences pre-order and call-off is described in the customer guide ("Stock, pre-order and call-off" and "Warehouse management"). ## Permissions The page is visible to everyone with read access to the warehouse ("Warehouse controller", "Warehouse Manager", "Administrator"). The settings on the customer are changed by roles with write access to customers. You process call-offs with fulfillment permissions. ## Frequently asked questions **The list is empty even though I have pre-orders.** A service only appears in the customer warehouse once the pre-order is completed and the service is "Ready for delivery". You can find ongoing pre-orders in [open positions](/pro/fulfillment/open-positions.md). **The customer can't send a device back or order into my warehouse.** Check in the customer details whether "Supplier warehouse active" is set. **Do goods from the customer warehouse show up in my stock warehouse or in the order proposals?** No. Services in the customer warehouse belong to the customer and don't count towards your stock. --- # 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/customer-warehouses.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.