> 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/orders.md).

# Tracking orders

Tracking orders and their items: order status, delivery status, shipment tracking, PO number and cancellation.

**Path:** sidebar → **"Controlling" → "Orders"** ("My organization" view: **"My organization" → "Orders"**)

Here you see all orders your company has submitted.

## The order list

| Column                            | Content                                                                                                                          |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| "Ordered by"                      | Who placed the order                                                                                                             |
| "ID"                              | Order number in equipme                                                                                                          |
| "Order number (PO)"               | Internal reference number                                                                                                        |
| "Supplier"                        | Offline supplier, if assigned (only visible if you can manage [offline suppliers](/dokumentation/offer-management/suppliers.md)) |
| "Ordered on"                      | Date                                                                                                                             |
| "Services"                        | Number of items                                                                                                                  |
| "One-time costs", "Monthly costs" | Totals                                                                                                                           |
| "Order status"                    | Combined status of all items                                                                                                     |
| "Note"                            | Note on the order                                                                                                                |

### Order status

| Status                | Meaning                                                           |
| --------------------- | ----------------------------------------------------------------- |
| **"Ordered"**         | All items are ordered or confirmed.                               |
| **"In progress"**     | Items are being processed, delivered or canceled.                 |
| **"Action required"** | Intervention is needed, e.g. because a delivery was not possible. |
| **"Completed"**       | All items are done.                                               |

## The order details

A click opens **"Order *****ID*****"**:

* You can edit the **"Order number (PO)"** and **"Note"** afterwards.
* The item table shows for each item: type (order, change, cancellation, call-off), "Name", "Location", "Employee", for add-ons the "Target instance", costs, "Supplier", the item's **"Order status"**, **"Asset status"**, "Requester", "Delivery address", "Preferred delivery" and "Note". Expanding a row shows the options.

### Status of an item

"Ordered", "Confirmed", "In progress", "Ready for delivery", "Delivery requested", "In delivery", "Successfully delivered", "Delivery not possible", "Completed", "Cancelled".

## Tracking a delivery

Click an item. The [service detail page](/dokumentation/assets/inventory/asset-details.md) shows the tracking number, carrier, expected delivery date and a tracking link under **"Shipment details"**. All statuses are explained in [Service status](/dokumentation/assets/inventory/status.md).

## Who is who?

An order distinguishes three roles:

* **"Requester"**: who made the request in the Marketplace,
* **"Ordered by"**: who placed the order in the order requests,
* **Recipient**: who the service is assigned to (employee or location).

## Canceling an order

There is no cancellation of an entire order. Cancel the individual services on their detail page. This creates an order request of type "Cancellation" (see [Lifecycle actions](/dokumentation/assets/inventory/lifecycle-actions.md#terminating-cancelling-or-removing)).

{% hint style="warning" %}
Once the supplier has confirmed an order (status "Ordered (confirmed)"), it can no longer be canceled in equipme. In this case, contact the supplier directly.
{% 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/orders.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.