> 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/dokumentation/procurement/stock-pre-orders-and-call-offs.md).

# Stock, pre-order and call-off

Using existing warehouse stock before placing a new order, pre-ordering devices and calling them off later.

## Using existing stock first

Before you place a new order, equipme checks in several places whether matching devices are already in the warehouse:

| Where              | How                                                                                                                                                                      |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Marketplace**    | Product cards show "Stock available"; filter "Only show available stock". On the product detail page, you choose a specific warehouse device under **"From inventory"**. |
| **Templates**      | Option **"Use free inventory first"**                                                                                                                                    |
| **Order requests** | Column **"Exchange for stock items"** with the number of matching devices                                                                                                |

When selecting from stock, you filter by **"Warehouse"** and **"Reservation"** ("Free inventory" or "Reserved for (group)"). Instead of a new order, a **"Call-off"** is created.

Some services can only be ordered from the warehouse: "This product can only be ordered from stock".

## Pre-order

With a **pre-order**, you order devices before it is clear who will receive them, e.g. for planned new hires. The supplier holds them for you, and they are only called off when needed.

**Prerequisites:**

* Your company has agreed on pre-orders with the supplier; for hosted customers, the provider enables this,
* the offer allows pre-orders, and
* the recipient is still open (or it is a cloud product).

**How it works:**

1. Marketplace → product detail page → **"Preferred delivery"** → **"Pre-order"**.
2. Optionally set **"Retrieval by"** (latest call-off date).
3. Optionally reserve for a group, assign, and approve and order as usual.

Pre-ordered goods appear in the stock with the note **"(Pre-order)"**.

## Call-off

When a device is needed:

1. In the Marketplace, choose the pre-ordered device under **"From inventory"** and assign it to the employee or location, **or**
2. in [Warehouse management](/dokumentation/assets/warehouse.md) or on the service detail page, choose **"Request provision"**.

An order request of type **"Call-off"** is created. It is approved and ordered as usual; no new order is placed with the supplier. The service moves through "Delivery requested (outgoing)" and "In delivery (outgoing)" to "Active".

{% hint style="info" %}
For pre-ordered goods, equipme points out that a call-off may incur new costs: "These items are currently only available for pre-order. Your request will incur additional costs."
{% endhint %}


---

# 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/dokumentation/procurement/stock-pre-orders-and-call-offs.md?ask=<question>&goal=<user_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.