> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/asset-tracking/chain-of-custody.md). # Chain of custody Understand how devices move through shipment, custody handoffs, inspections, and deployment. Use **Chain of custody** to track a device from shipment to deployment. It records who handled the device, where it moved, and what inspection data was captured along the way. ### When to use this page Use chain of custody when you need to: * confirm where a shipped device is now * identify the last custodian or location * review inspection history before deployment * understand which users can update custody records ### Before you start Confirm that you know: * the device **Serial Number**, shipment record, or other search criteria * whether you need to review a record, update a record, or manage locations * which custody stage or exception you expect to see Prepare these details when available: * current custodian * current location * expected device status * any inspection or incident notes you need to verify ### How chain of custody works The workflow usually follows this path: 1. The device is prepared in the Verifone store. 2. The device record becomes visible in **Device Management**. 3. Shipment updates the device to **In-Transit**. 4. Each custodian updates location, status, and inspection details. 5. The device is deployed, repaired, retired, or otherwise resolved. Some merchant flows include multiple logistical stops before the device reaches the merchant site. ### Protect record integrity Match the device serial number to the physical device before recording a handoff or inspection. Record the observed custody state. Do not infer a status from an expected shipment plan. Stop and investigate when the recorded custodian, location, or status conflicts with physical evidence. ### What chain of custody records Chain of custody can include: * shipment and handoff events * current and prior custodians * current and prior locations * inspection findings and evidence * deployment or incident status Use these records to verify that the physical device state matches the recorded workflow stage. ### Choose the right task Use the task that matches the action you need: * use [View device status in Chain of Custody](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/view-device-status-in-chain-of-custody) to review one shipped device or search the current custody list * use [Updating the File Chain of Custody](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/updating-the-file-chain-of-custody) to record a handoff, status change, inspection, or incident * use [Configure locations](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/configure-locations) to maintain the location values used in custody workflows * use [Active Lifecycle](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/active-lifecycle) to review one device's progress through the custody stages ### Permissions by workflow area #### Shipment receipt and change of custodian These roles have **Create**, **Read**, **Update**, and **Delete** access: * **Field Service Supervisor** * **Field Service User** * **Merchant Solution Owner** * **Merchant Supervisor** * **Merchant User** * **Reseller Manager** * **Verifone Admin** These roles have **Read** access: * **Partner HelpDesk** * **Verifone HelpDesk** #### Device inspections These roles have **Create**, **Read**, **Update**, and **Delete** access: * **Merchant Supervisor** * **Merchant User** * **Verifone Admin** These roles have **Read** access: * **Field Service Supervisor** * **Field Service User** * **Merchant Solution Owner** * **Partner HelpDesk** * **Reseller Manager** * **Verifone HelpDesk** #### Locations These roles have **Create**, **Read**, **Update**, and **Delete** access: * **Merchant Solution Owner** * **Partner HelpDesk** * **Verifone Admin** * **Verifone HelpDesk** These roles have **Read** access: * **Field Service Supervisor** * **Field Service User** * **Merchant Supervisor** * **Merchant User** * **Reseller Manager** #### Asset tracking reports All listed roles have **Read** access to asset tracking reports. ### Verify the result After you review or update custody data, confirm that: * the current custodian matches the latest handoff * the location matches the physical device position * the recorded status matches the actual shipment, storage, deployment, or exception state * the next action is clear: continue tracking, update the record, deploy the device, or register it For a custody update, reopen the record and confirm the event appears against the correct device. ### Result You can use chain of custody to understand where a device moved, who handled it, and whether the recorded workflow matches the physical device state. ### Related tasks * [View device status in Chain of Custody](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/view-device-status-in-chain-of-custody) — review shipped device records * [Updating the File Chain of Custody](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/updating-the-file-chain-of-custody) — update one device's custody details * [Configure locations](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/configure-locations) — maintain location values used in custody workflows * [Active Lifecycle](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/active-lifecycle) — review one device's progress through the custody flow --- # 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://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/asset-tracking/chain-of-custody.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.