> 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/import-chain-of-custody-device-details.md).

# Import Chain of Custody device details

Upload a prepared template file to bulk update chain of custody values.

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 %}

Export the current report scope before uploading. Keep that file as the pre-change reference.

Stop if the template contains unknown devices, unexpected rows, or unreviewed values.

### 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="https://1786380399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdzivQyj8aHN5Kvmx8apX%2Fuploads%2F5gpEyMeRjqmS32MOSZQc%2FPicture156.png?alt=media&amp;token=cd002300-c01d-4fc0-94b6-edd07f4e50ad" 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="https://1786380399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdzivQyj8aHN5Kvmx8apX%2Fuploads%2Fx2eNQ9A3cdhoeGuQTl6K%2FPicture157.png?alt=media&amp;token=79ab4b4c-467b-4e8c-9fb2-80580f8ff2a0" 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

Reopen representative updated records and compare their serial numbers and custody values with the reviewed template.

### Common follow-up checks

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

* the wrong records changed — stop further imports and compare the template against the pre-change export
* 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 reviewed custody updates are merged and validated against the target records.

### Next steps

* [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 the updated custody data
* [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 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 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/import-chain-of-custody-device-details.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.