> 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/asset-lifecycle-overview.md). # Asset Lifecycle Overview The asset lifecycle describes the states an asset or service moves through over time, from the moment it is defined to the moment it leaves the system. It sits one level above the day-to-day work. [How fulfillment works](/documentation/fulfillment/how-fulfillment-works.md) explains what happens to a position while it is being delivered. This page explains what happens to the thing itself across its whole life, including everything after delivery: exchanges, returns, storage and the end of the contract. Use it when you need to know where an asset currently stands and what can reasonably happen to it next. ## The states | Lifecycle State | Description | Typical Next States | | --------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------------------- | | Defined | The asset or service exists in the system but has not yet been ordered or activated. | Ordered, Removed | | Ordered | The asset has been ordered and is entering the fulfillment process. | Provisioning, Removed | | Provisioning | The asset is being prepared, shipped, manufactured, or otherwise fulfilled. | Active, Returned, Removed | | Active | The asset is in use and assigned to a person, location, or organization. | Swap, Successor, Returned, Stored, Unsubscribed | | Swap | The asset is being replaced due to defect, loss, or another reason while maintaining continuity. | Active, Returned | | Successor | A successor asset or service is assigned to replace the current one. | Active, Returned | | Returned | The asset is returned from usage to the provider or warehouse. | Stored, Unsubscribed | | Stored | The asset exists physically but is not actively assigned or in use. | Active, Unsubscribed | | Unsubscribed | The service or asset lifecycle has ended and is no longer active. | None | | Removed | The asset or order was cancelled before activation or usage. | None | Two of these are worth pausing on, because they look similar and are not. **Stored** is a live asset without a user. It is still on contract and still billed, it has simply been parked, usually in a [customer warehouse](/documentation/warehouse/customer-warehouses.md) after somebody left the company. It can go straight back into use. **Unsubscribed** is the end. The contract has run out or been cancelled, and nothing follows. ## What moves an asset from one state to the next | Current State | Action or Trigger | Resulting State | Notes | | ------------- | ------------------------------ | --------------- | ---------------------------------------------------- | | Defined | Order is placed | Ordered | Asset enters the fulfillment flow. | | Defined | Order is cancelled | Removed | Asset never becomes active. | | Ordered | Fulfillment starts | Provisioning | Covers shipping, manufacturing, or provisioning. | | Ordered | Order is cancelled | Removed | Cancellation before activation. | | Provisioning | Fulfillment completed | Active | Asset is assigned and ready for use. | | Provisioning | Fulfillment cancelled or fails | Removed | Asset never reaches active usage. | | Active | Swap initiated | Swap | Replacement due to defect, loss, or similar reasons. | | Active | Successor assigned | Successor | Planned replacement or upgrade. | | Active | Return initiated | Returned | Asset is sent back after usage. | | Active | Service is cancelled | Unsubscribed | Lifecycle ends after being active. | | Swap | Replacement completed | Active | New asset becomes active. | | Swap | Asset is returned | Returned | Defective or replaced asset is returned. | | Successor | Successor activated | Active | New asset replaces the previous one. | | Returned | Asset stored | Stored | Asset is kept for later reuse. | | Returned | Asset is removed | Unsubscribed | Asset is retired after return. | | Stored | Asset reassigned | Active | Stored asset is put back into use. | | Stored | Asset retired | Unsubscribed | Stored asset is permanently removed. | The actions in the left-hand column are the ones you carry out in Fulfillment. An exchange runs through [Changes](/documentation/fulfillment/changes.md), a return through the production steps on its position, and storing happens with the Store action or automatically when a return is completed. --- # 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/documentation/fulfillment/asset-lifecycle-overview.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.