> 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/view-device-status-in-chain-of-custody.md).

# View device status in Chain of Custody

Search shipped device records and review their current custody status.

Use **View device status in Chain of Custody** to review shipment and custody status for one device or a filtered record set.

### Before you start

Confirm that you know:

* the device **Serial Number**, shipment record, or other search criteria
* whether you need one device record or a broader filtered list
* whether the next action is review, export, import, or file update

### Open Chain of Custody

{% stepper %}
{% step %}

### 1. Open the report

Go to **Device Management** → **Reports** → **Chain of Custody**.
{% endstep %}

{% step %}

### 2. Review the current list

Confirm that the visible records match the shipment or custody scope you expect.
{% endstep %}

{% step %}

### 3. Search or filter the records

Use the available search criteria to find a specific device, shipment, or custody record.
{% endstep %}
{% endstepper %}

The **Chain of Custody** screen shows custody details for devices shipped from the Verifone store.

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/dzivQyj8aHN5Kvmx8apX/blobs/4lTOwErg6iYQyN6fddMa/image.png" alt=""><figcaption></figcaption></figure></div>

### What to review

Use this page to review:

* the current status of a shipped device
* the current custody or location record
* the shipment and handoff progress for a device
* whether the record needs an update, export, or bulk merge action

### When to use this page

Use this view when you need to:

* confirm where a device is in the custody flow
* search for a specific shipped device
* identify records that need import, export, or file updates

### Choose the next action

After you find the right record:

* 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 status change, location change, inspection, or incident
* use [Import Chain of Custody device details](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/view-device-status-in-chain-of-custody/import-chain-of-custody-device-details) when many records need a prepared bulk update
* use [Export Chain of Custody details](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/view-device-status-in-chain-of-custody/export-chain-of-custody-details) when you need the current filtered view as a file

### Verify the result

After you review the report, confirm that:

* the visible record matches the expected device or shipment
* the current status, custodian, and location explain the device's position in the workflow
* the next custody action is now clear

### Result

You can verify a device record before you update or export Chain of Custody data.

### Next steps

* [Import Chain of Custody device details](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/view-device-status-in-chain-of-custody/import-chain-of-custody-device-details) — bulk update prepared custody records
* [Export Chain of Custody details](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/view-device-status-in-chain-of-custody/export-chain-of-custody-details) — export the current report scope
* [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


---

# 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/view-device-status-in-chain-of-custody.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.