> 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/assets/inventory/status.md).

# Status of a service

All statuses a service can have in equipme and what they mean.

The status is shown in the inventory in the "Status" column and on the detail page in the header.

## Order phase

| Status                                            | Meaning                                                                                          |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| **"to order"** (self-service: "Approval pending") | Requested but not yet ordered. Waiting for approval or ordering.                                 |
| **"Ordered"**                                     | The order has been sent to the supplier or to internal processing. Cancelling is still possible. |
| **"Ordered (confirmed)"**                         | The supplier has confirmed the order.                                                            |
| **"In progress"**                                 | The supplier or internal order processing is preparing the service.                              |

## Warehouse and delivery

| Status                                  | Meaning                                                                                                 |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **"Ready for delivery"**                | The service is in the warehouse (your own warehouse or the supplier's warehouse) and can be called off. |
| **"Delivery requested (outgoing)"**     | The call-off from the warehouse has been requested.                                                     |
| **"In delivery (outgoing)"**            | The service is on its way to the recipient.                                                             |
| **"Successfully delivered (outgoing)"** | The delivery has taken place.                                                                           |
| **"Delivery not possible (outgoing)"**  | The delivery failed. Check the delivery address and availability.                                       |

## Return

| Status                                 | Meaning                                                          |
| -------------------------------------- | ---------------------------------------------------------------- |
| **"Return requested"**                 | A return to the supplier or to the warehouse has been initiated. |
| **"In delivery (return)"**             | The return shipment is on its way.                               |
| **"Successfully delivered (return)"**  | The return shipment has arrived.                                 |
| **"Delivery not possible (returned)"** | The return shipment failed.                                      |

## Operation and end

| Status           | Meaning                                                        |
| ---------------- | -------------------------------------------------------------- |
| **"Active"**     | In operation and billed. All lifecycle actions are possible.   |
| **"Cancelled"**  | Terminated; the service expires at the end of the contract.    |
| **"In removal"** | The service is currently being decommissioned.                 |
| **"Completed"**  | The contract has ended.                                        |
| **"Removed"**    | Permanently written off; no longer visible in the inventory.   |
| **"Cancelled"**  | Cancelled before delivery; no longer visible in the inventory. |

## Open changes ("Type" column)

Regardless of the status, the **"Type"** column shows whether a request for this service is currently open:

| Type               | Meaning                                       |
| ------------------ | --------------------------------------------- |
| **"Order"**        | New order                                     |
| **"Cancellation"** | Termination or cancellation                   |
| **"Call-off"**     | Issue from the warehouse                      |
| **"Change"**       | Option change, add-on, replacement or similar |

You can see the progress of the request under [Order requests](/dokumentation/procurement/order-requests-and-checkout.md) and [Approvals](/dokumentation/procurement/approvals.md).


---

# 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/assets/inventory/status.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.