> 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/configure-locations.md).

# Configure locations

Create, edit, import, and export the location records used in chain of custody.

Manage the location records used in Chain of Custody.

The **Select Location** list in **Chain of Custody** uses these location records.

### When to use this page

Use this page when you need to maintain the location records that device custody workflows rely on.

Use it to create one record, update an existing record, or manage locations in bulk.

### Before you start

Confirm that you know:

* whether the change affects one location or many
* whether you need manual entry or file-based import
* which locations should be available in chain of custody workflows

Search the current list before creating a location. This prevents duplicate values in custody selection lists.

### Open locations

{% stepper %}
{% step %}

### 1. Open Locations

Go to **Device Management** → **Locations**.
{% endstep %}

{% step %}

### 2. Review the current records

Review the configured location list before you add, edit, import, or export records.
{% endstep %}
{% endstepper %}

### Available actions

From **Locations**, you can:

* [Add a location](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/configure-locations/add-a-location) — create one location record
* [Edit a location](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/configure-locations/edit-a-location) — update one existing location
* [Import locations](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/configure-locations/import-locations) — merge location records from a file
* [Export locations report](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/configure-locations/export-locations-report) — download the current location list

### Choose the right path

Use these quick rules:

* use **Add a location** when you need one new record
* use **Edit a location** when a current record needs correction
* use **Import locations** when many records need to be added or merged
* use **Export locations report** when you need the current list outside the UI

### Protect active custody workflows

Edit a location when its existing record needs correction.

Create a new location when the change represents a different physical place.

Export the current list before a bulk import. Use it to compare the result after processing.

### Verify the result

After you manage location records, confirm that:

* the location list shows the intended records
* the records are available where chain of custody needs them
* the next import, export, or custody workflow uses the correct locations
* active custody records still reference the intended location

### Result

You can keep the location list accurate for chain of custody and related reporting.


---

# 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/configure-locations.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.