> 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-device-management/verifone-central/asset-tracking/view-device-status-in-chain-of-custody/import-chain-of-custody-device-details.md).

# Import Chain of Custody device details

Bulk update Chain of Custody values from a prepared template file.

Use this action when many custody records need the same update flow.

### Before you start

Confirm that:

* the template file contains only the records you want to update
* the values are reviewed before upload
* you are ready to verify the merged result after processing

{% hint style="warning" %}
Confirm the template values before upload. A merge updates custody data in bulk.
{% endhint %}

### Import and merge device details

{% stepper %}
{% step %}

### 1. Open the report

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

{% step %}

### 2. Open the import action

Select **Actions** → **Import & Merge File**.

<div data-with-frame="true"><figure><img src="/files/8vg7shqgItciuwa61sW9" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### 3. Open the upload screen

The **Drag and Drop Template File here** screen appears.
{% endstep %}

{% step %}

### 4. Upload the prepared file

Upload the file by browsing for it or dragging it into the upload area.

<div data-with-frame="true"><figure><img src="/files/Jo38krP0IhFOYYckgjys" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

### What to validate after import

Check these points after the merge completes:

* the upload finished without unexpected failures
* the intended custody records were updated
* the updated values appear correctly in the report
* any exceptions are reviewed before you continue

### Common follow-up checks

Use these checks if the result is not what you expected:

* the wrong records changed — confirm the template only included the intended rows
* the values do not match — compare the uploaded values with the visible report output
* you need a shareable result file — export the updated report view after validation

### Verify the result

After the file is processed, confirm that:

* the upload completed without unexpected failures
* the intended custody records were updated
* the updated values appear correctly in the report

### Result

The uploaded file is processed and the device details are updated in bulk.

### Next steps

* [View device status in Chain of Custody](/verifone-central-device-management/verifone-central/asset-tracking/view-device-status-in-chain-of-custody.md) — review the updated custody data
* [Export Chain of Custody details](/verifone-central-device-management/verifone-central/asset-tracking/view-device-status-in-chain-of-custody/export-chain-of-custody-details.md) — export the updated result if needed


---

# 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://docs.verifone.com/verifone-central-device-management/verifone-central/asset-tracking/view-device-status-in-chain-of-custody/import-chain-of-custody-device-details.md?ask=<question>&goal=<endgoal>
```

`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.