> 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/devices/add-devices.md).

# Add devices

Use **Add devices** to create device records before the devices contact the server.

This page helps you choose the right onboarding method and verify the result.

### Use this page when

Use **Add devices** when:

* the device record must exist before first contact
* you need to add one device or many devices
* you already know the target placement for the new records

Use [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) instead when the device should create its own record during first contact.

### Decide before you add anything

Choose the creation flow that matches the operational need:

* use manual add when accuracy for one device matters more than speed
* use bulk import when the device data is already prepared in a file
* use registration instead when the device should create the record itself

### Choose the right method

Use the method that matches your task:

* [Add a single device](/verifone-central-device-management/verifone-central/devices/add-devices/add-a-single-device.md) — add one device when you want to review each value before saving
* [Bulk import devices](/verifone-central-device-management/verifone-central/devices/add-devices/bulk-import-devices.md) — add many devices from one **CSV** or **XML** file

Use manual add when the device count is small or each device needs individual review.

Use bulk import when the device data is already prepared and the same workflow applies to many devices.

### Before you start

Confirm that:

* your role allows device creation
* the device does not already exist in Device Management
* you know whether you are adding one record or many
* you know the target hierarchy and reference set

Prepare these details for any add flow:

* **Serial Number**
* **Device ID**
* **Model**
* target **Hierarchy**
* target **Reference set**

If you are importing many devices, also prepare a supported **CSV** or **XML** file.

{% hint style="warning" %}
Do not add a device manually or by import if it should auto-register on first contact.
{% endhint %}

### Required values

Every new device record needs enough data to identify the device and place it correctly.

At minimum, prepare:

* **Serial Number**
* **Device ID**
* **Model**
* **Hierarchy**
* **Reference set**

If any of these values are wrong, registration or later management can fail.

### Validate your inputs first

Before you continue, check these items:

* each device has a unique identifier set
* the model matches the device you plan to deploy
* the hierarchy exists and you can place devices there
* the reference set is ready for the target device
* the import file only includes devices you want to create now

For bulk import, also confirm that the file uses the required import structure for your flow.

### Understand the result you want

Use these outcome checks before you start:

* the device record should exist before first contact
* the device should appear in the correct hierarchy
* the selected reference set should match the device you plan to deploy

### Add devices flow

{% stepper %}
{% step %}

### 1. Open **Add Devices**

Go to **Verifone Central** → **Device Management** → **Devices** → **Add Devices**.
{% endstep %}

{% step %}

### 2. Choose the onboarding method

Select the single-device flow when you need to enter one record manually.

Select the bulk import flow when you need to upload a device file.
{% endstep %}

{% step %}

### 3. Complete the selected flow

Continue with one of these pages:

* [Add a single device](/verifone-central-device-management/verifone-central/devices/add-devices/add-a-single-device.md)
* [Bulk import devices](/verifone-central-device-management/verifone-central/devices/add-devices/bulk-import-devices.md)
  {% endstep %}

{% step %}

### 4. Verify the new records

Confirm that:

* the expected device records now exist
* identifiers and model values are correct
* the records are placed in the intended hierarchy
* bulk imports completed without unexpected rejects
  {% endstep %}
  {% endstepper %}

### What happens next

After the records are created:

* manually added devices are ready for first-time registration
* imported devices appear after import processing completes
* both flows continue into the same registration and management workflow

### Choose the next step after creation

After the record exists:

* use [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) when the device is ready for first contact
* use [View devices](/verifone-central-device-management/verifone-central/devices/view-devices.md) when you need to verify the saved record
* use [Device details](/verifone-central-device-management/verifone-central/devices/view-devices/device-details.md) when you need a field-level review

### Troubleshooting

Check these common outcomes first:

* **A device record already exists** — review the device list before you create or import the record again
* **The device appears in the wrong hierarchy** — review the placement values used during add or import
* **The import result is incomplete** — review the file format, required values, and completion status in [Notifications](/verifone-central-device-management/verifone-central/devices/alerts-and-notifications/notifications.md)
* **The record exists but the device still does not connect** — continue to [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) and [Device heartbeats](/verifone-central-device-management/verifone-central/devices/registering-the-device/device-heartbeats.md)

### Result

The required device records are created and ready for registration, review, and later device management.

### Next steps

* [Add a single device](/verifone-central-device-management/verifone-central/devices/add-devices/add-a-single-device.md) — add one device manually
* [Bulk import devices](/verifone-central-device-management/verifone-central/devices/add-devices/bulk-import-devices.md) — upload many devices from one file
* [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) — complete first-time device contact
* [View devices](/verifone-central-device-management/verifone-central/devices/view-devices.md) — verify the new records


---

# 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/devices/add-devices.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.