> 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/offer-management/order-processing.md).

# Order processing (internal orders)

Order processing: process orders for your own services internally, set statuses and complete them; restricted access per organizational unit.

**Path:** sidebar → **"Offer management" → "Order processing"** (the number shows open items)

This is where the responsible teams, e.g. IT, facility management or HR, process orders for services from your **own** [service portfolio](/dokumentation/offer-management/service-portfolio.md). Internal processes such as storing items in your own warehouse also belong here.

## Who sees which orders?

* Users with access to all services (e.g. administrators) see **all** open items.
* Users with the **"Restricted fulfillment user"** permission only see items for services whose **"Fulfillment"** is assigned to one of their groups. They do not see items without an assigned group. In the "My organization" view, the "Order processing" menu item appears directly for them.

## The "Open positions" list

Columns: "Id", "Service name", "Option", "Location", "Employee", "Target instance" (for add-ons), "Group", "Fulfillment", order date, "Expiration date", order number, **"Process status"**, "Preferred delivery", "Pre-order" and "Note". Clicking an item opens its details.

## Setting the status

1. Select items.
2. Click **"Set status"**.
3. For each current status, choose a **"Target status"**, e.g. "Ordered (confirmed)" → "In progress" → "Ready for delivery" → "Completed".
4. When completing, optionally enter an **"Activation date"**.

Notes:

* Only actual order items can be processed this way; mixed selections are cleaned up.
* Returns cannot be processed in bulk.
* "Cancelled" cannot be selected here.
* If an item depends on a base service that is not ready yet, equipme displays a warning.

**Result:** Completed items become **active services** in the inventory. From the activation date, the term and costs of the selected offer apply.

## Internal storage

If someone chooses **"Store service" → "Internal"** for a service, an item is created here. Complete it as soon as the device has been put into storage. Only then does it appear in [Warehouse management](/dokumentation/assets/warehouse.md).

## Notifications

The status messages "Order is being processed", "… is ready for delivery", "… has been shipped" and "… has arrived" inform requesters and recipients. For internal orders, you can use your own email templates (see [Email notifications](/dokumentation/settings/email-notifications.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/offer-management/order-processing.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.