> 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/lifecycle-actions.md). # Lifecycle actions Reassign, store or replace services, order a successor, change options, book add-ons, terminate, cancel or remove. This page describes all actions that can be performed on an existing service: on the [detail page](/dokumentation/assets/inventory/asset-details.md) ("Lifecycle" sidebar and footer) or as a bulk action in the [inventory](/dokumentation/assets/inventory.md). The table at the end shows which action is possible in which status. ## Reassigning a service **Detail page → "Assignment details" → pencil icon** or bulk action **"Move"** 1. Choose the new target: employee, location, the employee's home office or warehouse. 2. Optional: request a receipt confirmation and adopt the target's cost center. 3. Save. The assignment applies **immediately**. Good to know: * A service can only be moved if the product allows a change of employee or location and the target location is within the offer's delivery area. * If you assign an active service to an **internal warehouse**, an internal storage is triggered automatically. * If you assign a service from the warehouse to an employee or location, it is processed as an internal delivery. Typical case: A device moves from a departing employee to a new employee. Assign it to the new employee. For documentation, create a [handover or return document](/dokumentation/organization/employees/onboarding-and-offboarding.md#transfer-and-return-documents) on the employee page. ## Storing a service (return) **Detail page → "Lifecycle" → "Store service"** or bulk action * **"External"**: The service is sent back to the supplier. For this, the supplier's return service is ordered; a provisioning date can be selected. * **"Internal"**: The service is stored in one of your own warehouses. An internal order is created for each service. The detail page then shows **"Storage requested"**. As long as the request is open, you can withdraw it with "Remove storage request". Prerequisite: status **"Active"**, a product with a location reference and no other open change. ## Replacing a service (swap) **Detail page → "Lifecycle" → "Replace service"** For defective devices or devices that need to be replaced, if the supplier offers an exchange service. 1. Describe the problem or the desired options, add "Further details". 2. Choose the **"Delivery address"**: "From the assignment" or "Different delivery address". 3. **"Request replacement"**. The request ends up in the order requests. The page then shows **"Exchange requested"**; you can withdraw it with "Remove exchange request". Prerequisite: status "Active", no open change and an exchange offered by the supplier. ## Defining a successor service **Detail page → "Lifecycle" → "Define successor service"** or bulk action **"Request successor service"**. Employees use the same button under "My equipment"; there, the catalog is titled "Request successor service". For a planned replacement with a new model, e.g. at the end of the term. 1. The catalog opens, pre-filtered to the category of the current service. 2. Choose and configure the new service. 3. Define what happens to the previous service: **"None"**, **"Return"** (internal/external) or **"Cancel"**. The new service is requested with the same assignment (employee, location, group). Not possible for add-ons and workplace devices. ## Requesting provision (issue from the warehouse) **Detail page → "Lifecycle" → "Request provision"** or in [Warehouse management](/dokumentation/assets/warehouse.md) For services with the status **"Ready for delivery"** (e.g. devices in stock in the warehouse or at the supplier). You choose the recipient (employee or location); an order request of the type **"Call-off"** is created. You can withdraw it with "Cancel provisioning request". ## Changing options **Detail page → "Configuration" tab** Choose a variant → **"Save"**. The change is submitted as an order request of the type **"Change"** and only takes effect after approval and ordering. In the status "Ordered", options cannot be changed yet. ## Booking add-ons and linked services **Detail page → "Services & extras" tab** or bulk action **"Assign add-on"** Add-ons complement a main service, e.g. warranty extension, accessories or setup service. Linked services are standalone services that are requested and approved together with a main service. Booked entries end up as an order request in the cart. ## Terminating, cancelling or removing | Action | When | What happens | | -------------------- | ----------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Cancel** | The service has been ordered but not yet delivered (status "Ordered"). | A cancellation request is created. | | **"Cancel service"** | The service is active. | An order request of the type **"Cancellation"** is created, which is approved and passed on to the supplier. The service expires at the end of the contract (status "Cancelled"). | | **"Remove"** | Only for **self-provided** services (own portfolio or recorded inventory) with the status "Active" or in the warehouse. | The service is written off from inventory and cost calculation **immediately and irrevocably** as of the selected "Deactivation date", without approval. Requires a special permission. | An open cancellation can be withdrawn: employees with "Remove cancellation request", administrators with "Reject cancellation request". **When is a cancellation not possible?** * Rent, mobile contract or leasing **without term extension** cannot be cancelled after activation until the end of the term. * The service still has add-ons that are not completed; these must first be cancelled or completed. * A cancellation or another change is already in progress. * The service is in an intermediate status (e.g. "In progress" or "In delivery"). * Basic services from the service catalog cannot be cancelled from the inventory list. {% hint style="warning" %} **Basic services:** If you cancel a basic service (e.g. a tenant), all services that depend on it are cancelled as well. {% endhint %} ## Receipt confirmation If [receipt confirmation](/dokumentation/settings/portal-settings.md#general) is active, the employee or a responsible manager confirms receipt of a service. On the detail page, the card on the right contains the **"Confirmation of receipt"** block: a check mark for "Receipt confirmed" (name and time in the tooltip), **"Pending confirmation"** with the check mark **"Confirm"**, or the button **"Request confirmation of receipt"**. Administrators can additionally cancel a pending request via the ✗. Employees confirm receipt on the detail page under "My equipment" or in their profile. You set up email reminders under [Email notifications](/dokumentation/settings/email-notifications.md). ## Which action is possible in which status? | Status | Reassign | Change options | Cancel | Store / Replace | | -------------------------------------------------------------- | -------- | -------------- | ----------------------- | --------------- | | "Ordered" | ✓ | – | ✓ (cancellation) | – | | "Ordered (confirmed)", "In progress", "In delivery (outgoing)" | – | – | – | – | | "Ready for delivery", "Delivery requested (outgoing)" | ✓ | – | – | – | | **"Active"** | ✓ | ✓ | ✓ (subject to the term) | ✓ | | "Cancelled", "In removal" | – | – | – | – | In addition: as long as a change is open (the "Type" column in the inventory is filled), storing and replacing are locked. --- # 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/lifecycle-actions.md?ask=&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.