> 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/documentation/warehouse/customer-warehouses.md).

# Customer warehouses

Customer warehouses shows services that are sitting with a customer but assigned to nobody.

Despite the name, this is not a second version of your warehouse, and almost nothing you know about that page applies here.

|                     | Warehouse                     | Customer warehouses               |
| ------------------- | ----------------------------- | --------------------------------- |
| Holds               | articles and batches          | service instances                 |
| Comes from          | goods receipt, manual booking | services the customer handed back |
| Storage locations   | yes                           | no                                |
| Moving stock around | yes                           | no                                |
| Belongs to          | you                           | the customer                      |

The distinction that matters: a service parked here **still belongs to the customer and is still running**. Its term continues, it is still billed. All it has lost is the person it was assigned to.

## How something gets here

Usually through a return. Completing a return moves the service into the customer's warehouse and removes the employee assignment, so the device can be collected and given to somebody else.

The same move can be triggered by hand with **Store** on a position, when you want to park it before the return is formally finished.

The everyday case is somebody leaving. Their notebook comes back, sits here for a few weeks, and is then assigned to their replacement. The service instance never stops: same contract, same term, same monthly cost, new person.

## What this page is good for

Three things, and the second one is the reason to look at it regularly.

**Seeing what is parked.** How much hardware is sitting idle at a customer.

**Spotting idle equipment.** A service that has been here for months is being paid for and used by nobody. That is a conversation worth having, and it only surfaces if someone looks.

**Finding something to reuse.** Before ordering a device for a new starter, check whether one is already parked at that location. Cheaper than buying, and faster than delivering.

## Opening an entry

An entry opens the full service instance, not a warehouse record. Everything you can do with any service is available: booked options, service components, replacing a component, additional information, customer notes, attachments.

What you will not find is anything warehouse-like. No storage location, no shelves, no quantity. That is deliberate. This is a running service that happens to be unassigned, not a piece of stock.

## The customer sees the same thing

What you see here matches the warehouse management view in the customer's own portal for that location, and they can park things there themselves.

So this is a shared view rather than a provider-only list. When you discuss idle equipment with a customer, you are both looking at the same set of devices.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hub.equipme.io/documentation/warehouse/customer-warehouses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.