> 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/pro/fulfillment/activations.md).

# Activations

Pending activations: provided services whose contract is not yet active, and how you set the activation date or schedule it for the future.

**Path:** "Fulfillment" → "Pending activations"

When you complete an order, the service is provided. The **contract** (and with it the term and billing), however, only starts on the **activation date**. This lets you, for example, deliver a device before a new employee's start date and only start the contract on their first working day.

The "Pending activations" page shows all completed positions whose service instance is not yet active: "This view shows you service instances that are pending activation."

## How the activation date is set

* **When completing an order**, Pro enters today's date (or an already scheduled one) in the "Activation date" field. You can change or clear it (see [Open positions](/pro/fulfillment/open-positions.md#set-status-in-the-detail-view)).
* **In advance in the order**, a Fulfillment Manager can schedule a date using the pencil next to "Activation date".
* **Afterwards**, you set the date on this page.

Pre-orders have no activation date: on completion they are only stored. Activation only happens when the customer calls off the device and you complete the delivery call-off.

## Set activation

1. Select one or more positions (or right-click a row).
2. Click **"Set activation"**.
3. Choose the "Activation date" and save.

Pro confirms: "The activation date has been successfully set."

| Date                 | Effect                                                                                                                           |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| In the future        | The service is only activated on that day.                                                                                       |
| Today or in the past | The contract is finally activated overnight. Until the next day (or until the order is completed) you can still change the date. |
| Empty                | The activation remains open until you set a date.                                                                                |

{% hint style="warning" %}
After activation, **the date can no longer be changed**. Check the date carefully, especially when backdating, because it determines the start of the term and billing.
{% endhint %}

In the detail view of a service instance, Pro points out contracts that are not yet active: "The service has been provided, but the associated contract has not yet been activated. Planned activation date: …"

## Permission

The page can be edited by users who are allowed to change service instances: "Fulfillment Operator", "Fulfillment Manager" and "Administrator".

## What the customer sees

Until activation, the service is provided to the customer but not yet listed as an active contract. From the activation date, term and costs count (see customer guide, "Inventory"). How activation feeds into your invoices is described under [Billing](/pro/sales/billing.md).

## Frequently asked questions

**I completed an order, but it isn't in Pending activations. Why?**

The activation date was today or earlier. The contract is then already activated or will be activated overnight, and only shows up here until then.

**Can I schedule activation for many services at once?**

Yes. Select all affected positions and set the date in one step.


---

# 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/pro/fulfillment/activations.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.