> 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/documentation/fulfillment/pending-activations.md). # Pending activations Pending activations holds positions that are finished but not yet live. Most of the time it is empty, and that is correct. A service normally becomes active the moment its position is completed. This page exists for the cases where you deliberately separate the two. ## Why you would separate them Because delivery and the start of a contract are different events, and they do not always fall on the same day. Equipment for a new starter is often ready a fortnight early. The device can be prepared, handed over and sitting on a desk, while the contract, and the billing, should only start when the person actually begins. Setting an activation date is what keeps a completed position out of billing until the right day. ## Setting the date The activation date sits on the position and opens a dialog called **Set activation**. The same dialog opens from this page once you select an entry. The rules it states are worth reading once. A date in the past or today stays changeable until tomorrow, or until the order is completed, before the contract is finally activated. After activation it is fixed. A future date means the service is only activated on that day. The date can also be cleared, which lets the service activate as soon as the work is done. Setting it changes nothing immediately. The position runs through purchasing, warehouse, picking and shipping exactly as it would otherwise. It only lands here once the work is finished. **Planned provision is a different field entirely.** That is your own scheduling, when you intend to provide the service. The activation date decides when the contract starts. They have separate dialogs and no effect on each other. ## Two things called active Worth reading carefully, because the same word covers two different states. A position waiting here reads **Completed**, and the service reads **Active** with an information icon. Behind the icon: the service has been provided, but the contract has not been activated, and the planned date is shown. So the work is done and the device is with the customer. The contract has not started. **Nothing is billed until the activation date.** A service waiting here does not appear in the customer's Active services and is not part of any invoice. ## What the customer sees In their portal the service shows a green Active badge with its monthly price, and they are prompted to confirm receipt. The activation date becomes visible once they expand the financial overview. A customer looking at an active service with a price attached may reasonably assume they are being charged for it. If you use future activation dates regularly, it is worth mentioning up front. ## Activating Select one or more entries to enable **Set activation**. The button is only active once something is selected. The dialog opens with the existing date prefilled. Save a new one, or use Delete to clear it so the service activates immediately. ## If the list is fuller than expected Positions sitting here longer than intended usually mean a date was set and then forgotten, or set to the wrong month. That is worth catching, because the service is finished, the customer has the device and is using it, and nothing is being billed for it. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hub.equipme.io/documentation/fulfillment/pending-activations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.