> 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/rollouts/schedule-rollouts/create-a-batch-rollout.md).

# Create a batch rollout

Create a rollout for multiple devices.

### Before you start

Confirm that:

* you have the required rollout permissions
* the payload type is ready for deployment
* you know the rollout name, batch name, target devices, and schedule window

### Create the rollout

1. Go to **Verifone Central** → **Device Management** → **Rollouts** → **Create New Rollout**.
2. Enter the rollout details.

   * **Rollout name** is unique.
   * **Batch name** identifies one batch within the rollout.
   * **Batch number** is generated automatically.
   * **Description** is optional.

   <div data-with-frame="true"><figure><img src="/files/2VRN7IGPmEo3SAe9KvjH" alt=""><figcaption></figcaption></figure></div>

   <div data-with-frame="true"><figure><img src="/files/fWXGnp29XrT0hdNrTRwh" alt=""><figcaption></figcaption></figure></div>
3. Select **Continue** to proceed.

The **Save for later** option stores progress so you can return later.

```
<div data-with-frame="true"><figure><img src="/files/4KEoEWUL9QKHqKFB0NEZ" alt=""><figcaption></figcaption></figure></div>
```

4\. Select the rollout type, then select **Continue**.

Use these options:

* **Software & Parameter Templates** — deploy reference sets or parameter templates
* **Parameters Only** — deploy parameter changes without software
* **Use preconfigured Software & Parameters** — use an existing predefined package
* **Content Downloads** — deploy media or content files

  <div data-with-frame="true"><figure><img src="/files/J1hAjHR9UwByjsjDcgkK" alt=""><figcaption></figcaption></figure></div>

5. Open **Device Selection** and choose the target devices.

Use **Remove Conflict** if a selected device already has a conflicting rollout.

When you use reference sets or templates, select the required assignment and edit the selected template if needed.

```
<div data-with-frame="true"><figure><img src="/files/pZL77dxYCgWAwA3Di3Vf" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/TYNS8ze9w7lzwRYZKTEI" alt=""><figcaption></figcaption></figure></div>
```

6\. Choose the download schedule:

* **Download during device maintenance hours**
* **Download immediately on the next contact**
* **Start Download on** a specific date and time

7. Choose the install schedule:

   * **Force installation**
   * **Install immediately after download**
   * **Start install on** a specific date and time

   <div data-with-frame="true"><figure><img src="/files/Zt40Fu8jvMQCdfIP2zkL" alt=""><figcaption></figcaption></figure></div>
8. Review the rollout summary, then select **Continue**.

   <div data-with-frame="true"><figure><img src="/files/8hztXaQt9DCsAYkEJ47N" alt=""><figcaption></figcaption></figure></div>
9. Select **Start Rollout**.

   <div data-with-frame="true"><figure><img src="/files/GxMqkLJ4ag9IG8P83JAI" alt=""><figcaption></figcaption></figure></div>
10. Select **Ok** to confirm.

### Verify the result

Before you start the rollout, confirm that:

* the rollout type matches the payload you want to deploy
* the correct devices or device batch are selected
* any conflict is removed
* the download and install schedule matches the deployment plan

### Result

The rollout is created and scheduled for the selected devices.

### Related pages

* [Create a new batch for rollout](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts/create-a-new-batch-for-rollout.md) — add another batch to an existing rollout
* [Monitor estate-wide rollouts](/verifone-central-device-management/verifone-central/rollouts/monitor-estate-wide-rollouts.md) — monitor rollout progress


---

# 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/rollouts/schedule-rollouts/create-a-batch-rollout.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.