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

# Import locations

Upload a CSV file to create or merge location records in bulk.

Bulk import location records from a CSV file.

### When to use this page

Use this page when many location records need to be created or merged at once.

Use it only after the source file is reviewed and ready for upload.

### Before you start

Confirm that:

* the file is in **CSV** format
* the file contains only the locations you want to process now
* the values are complete and consistent
* you are ready to review the import result after processing

Export the current location list before import. Keep it as the pre-change reference.

### Validate the file

Before you upload, confirm that:

* the file uses the correct location columns for your flow
* duplicate or outdated location rows are removed
* the location names and related values match the records you want in the system

### Import location details

{% stepper %}
{% step %}

### 1. Open the import action

Go to **Device Management** → **Locations** → **Actions** → **Import & Merge File**.

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/dzivQyj8aHN5Kvmx8apX/blobs/HqPmPaP3iv5RjeCy2UGg/image.png" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### 2. Upload the file

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

<figure><img src="https://content.gitbook.com/content/dzivQyj8aHN5Kvmx8apX/blobs/t8CzUi1FbzKunXFG6N5K/image.png" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### Verify the result

After the file is processed, confirm that:

* the expected location records are available
* failed or skipped rows are understood
* the updated location list matches the source data you intended to import

Compare the updated list with the pre-change export. Stop and investigate before another upload when unexpected records appear.

### Result

The reviewed location records are merged and verified for custody workflows.

### Next steps

* [Configure locations](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/configure-locations) — return to the location hub
* [Export locations report](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/asset-tracking/configure-locations/export-locations-report) — download the updated location list


---

# 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/import-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.