> 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/devices/alerts-and-notifications/notifications.md).

# Notifications

Review import processing updates and decide the next follow-up action.

Review import-related updates in the **Notifications** panel.

### When to use this page

Use this page after you submit a device, location, or chain of custody file.

Use it to confirm whether processing finished, failed, or needs another correction.

### What notifications show

Notifications are created for recent import activity, including:

* device imports
* location imports
* chain of custody imports

If no notifications were generated in the last 7 days, the panel shows `0`.

### Before you start

Confirm that you know:

* which import or merge job you are checking
* when the upload was submitted
* whether you expect a success, partial result, or failure

### Open notifications

{% stepper %}
{% step %}

### 1. Open Device Management

Sign in to **Device Management**.
{% endstep %}

{% step %}

### 2. Open the alert center

Select the bell icon in the header.
{% endstep %}

{% step %}

### 3. Open Notifications

Select **Notifications** and review the latest entries.
{% endstep %}

{% step %}

### 4. Continue the related task

Select a notification when you need to review or correct the related import flow.
{% endstep %}
{% endstepper %}

### When to check notifications

Check notifications after you:

* upload an import file
* need to confirm that bulk processing finished
* need to decide whether another import or correction is required

### Review the outcome

When you open a notification, check these points:

1. Confirm the notification matches the file or job you submitted.
2. Confirm whether processing completed, partially completed, or failed.
3. Review the affected records before you resubmit anything.

### Choose the next action

* **Completed import** — validate the expected records in the related device, location, or custody view.
* **Partial result** — identify the missing or incorrect records before preparing another file.
* **Failed import** — correct the source file, then repeat the related import workflow.

Do not resubmit an import until you know which records need correction.

### Verify the result

After you review the notification, confirm that:

* the entry matches the file or task you submitted
* you understand whether the result is complete or partial
* you know the next page to use for validation or retry

### Result

You can confirm import activity, validate the affected records, and retry only when a correction is required.

### Next steps

* [Alerts and notifications](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/alerts-and-notifications) — return to the alert center
* [Event Notifications](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/event-notifications) — review outbound event delivery options


---

# 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/devices/alerts-and-notifications/notifications.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.