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

# Rollouts

Prepare, schedule, and monitor controlled device deployments.

Use **Rollouts** to deploy software, parameters, or content to one device or many devices.

Rollouts help you manage changes across the estate without updating devices one by one.

Use this page to choose a deployment path, validate readiness, and monitor the result.

### Before you start

Confirm that:

* your role allows you to create or manage rollouts
* the target devices are already onboarded and available in Device Management
* the software, parameter set, or content package is ready to deploy

Review access and rollout readiness:

* [Prerequisites](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/manage-rollouts/prerequisites)
* [User privileges](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/manage-rollouts/user-privileges)

Do not schedule a rollout until you have confirmed the target scope and package.

### Choose a rollout path

* **One device** — create a [single-device rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-rollout-for-a-single-device).
* **Many devices** — create a [batch rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-batch-rollout).
* **An existing rollout** — [add a batch](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-new-batch-for-rollout) or [modify it](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/modify-existing-rollout).

### What rollouts support

Use rollouts to:

* deploy software updates remotely
* apply parameter changes to devices
* distribute content packages across the estate
* schedule downloads and installs by time or maintenance window
* monitor rollout progress and results

### Rollout workflow

Most rollout work follows this flow:

1. Prepare the software, parameters, or content.
2. Create the rollout for one device or many devices.
3. Schedule the download and install.
4. Monitor progress and resolve any issues.

Record the deployment scope and intended schedule before starting. Compare them with the rollout summary before launch.

### Choose what to deploy

#### Software

Use software rollouts when you need to install or update application packages on devices.

Start with [Software management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/software-management).

#### Parameters

Use parameter rollouts when you need to update device configuration values.

Start with [Parameter management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/parameter-management).

#### Content

Use content rollouts when you need to distribute files or media used by the device estate.

Start with [Content management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/content-management).

### Common rollout tasks

#### Prepare rollout content

Before scheduling a rollout, make sure the package or configuration is available in Device Management.

Use:

* [Software management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/software-management)
* [Parameter management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/parameter-management)
* [Content management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/content-management)

#### Schedule a rollout

Use the scheduling pages to target one device, a batch of devices, or an existing rollout.

Use:

* [Schedule rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts)
* [Create a batch rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-batch-rollout)
* [Create rollout for a single device](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-rollout-for-a-single-device)
* [Create a new batch for rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-new-batch-for-rollout)
* [Modify existing rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/modify-existing-rollout)

#### Monitor rollout progress

Track rollout status after submission. Confirm progress, completion, or failure before closing the deployment task.

Use:

* [Managing rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/managing-rollouts)
* [Monitor estate-wide rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/monitor-estate-wide-rollouts)

### Result

Rollouts let you prepare, schedule, and track device changes from one workflow. A completed rollout has the expected package, target scope, and outcome.

### Next steps

* [Manage rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/manage-rollouts)
* [Schedule rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts)
* [Software management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/software-management)
* [Parameter management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/parameter-management)
* [Content management](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/content-management)


---

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