> 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/software-management.md). # Software management Use **Software management** to prepare software packages for rollout across the device estate. Software management helps you organize device-specific packages and control which devices receive them. ### When to use this page Use this page when you need to: * prepare a software package before rollout * understand how package compatibility is controlled * decide how reference sets affect device targeting ### Before you start Confirm that: * your role allows you to manage software packages or rollouts * you know which device model the software targets * the package is prepared in a supported format for that device platform If you are scheduling the deployment next, review: * [Rollouts](/verifone-central-device-management/verifone-central/rollouts.md) * [Manage rollouts](/verifone-central-device-management/verifone-central/rollouts/manage-rollouts.md) * [Schedule rollouts](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts.md) ### What software management supports Use software management to: * manage software packages for supported device models * prepare packages before rollout * control package order and compatibility through reference sets * support software deployment across one device or many devices ### Understand software packages A **software package** is a bundle of applications compressed in a supported format. Packages use a predefined structure based on the device platform. Supported package formats include `.tgz` and `.zip`, depending on the device. Software packages are specific to the device model. The model determines which application package can be configured and deployed. ### Package readiness checks Before you move to rollout scheduling, confirm that: * the package matches the intended device model * the package format is supported for that platform * the package version is the one you intend to deploy ### Understand reference sets A **reference set** is a logical container used during software deployment. It defines: * the packages included in the deployment * the order in which those packages are downloaded * the device models that are compatible with the reference set * the matching criteria used to decide which devices qualify Device Management evaluates available reference sets and identifies the best match for each device. ### Choose the right preparation path Use these rules: * prepare the package first when the software payload still needs review * review the reference set when targeting, order, or compatibility is the main question * move to rollout scheduling only after the package and reference set are both ready ### How software management fits into rollouts Software management is the preparation stage of a rollout. Most software deployment work follows this order: 1. prepare the software package 2. assign or organize the package through a reference set 3. schedule the rollout 4. monitor rollout progress and results ### Verify before rollout Before you leave software management, confirm that: * the correct package is available * the correct reference set can match the intended devices * the rollout page you need next is clear ### Related deployment areas Use these pages when you need to manage other rollout content: * [Parameter management](/verifone-central-device-management/verifone-central/rollouts/parameter-management.md) — manage application parameter configuration * [Content management](/verifone-central-device-management/verifone-central/rollouts/content-management.md) — manage static files and media for rollout ### Result Software management prepares the package and compatibility rules needed for a successful software rollout. ### Next steps * [Schedule rollouts](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts.md) * [Managing rollouts](/verifone-central-device-management/verifone-central/rollouts/managing-rollouts.md) * [Parameter management](/verifone-central-device-management/verifone-central/rollouts/parameter-management.md) * [Content management](/verifone-central-device-management/verifone-central/rollouts/content-management.md) --- # 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/software-management.md?ask=&goal= ``` `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.