> 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/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/onboarded-device-swap.md). # Onboarded Device Swap Onboarded Device Swap lets a merchant administrator or an authorized VASC technician replace the Commander unit at a site directly from Commander Central, without contacting the helpdesk. This is used for routine hardware replacement, including situations where the existing Commander is physically dead or unreachable. ### Initiating a Swap {% stepper %} {% step %} **Locate the site** Navigate to the site's management area in Commander Central and select Swap Device for the currently onboarded Commander. {% endstep %} {% step %} **Review current device** Commander Central displays the current device's serial number and device type. {% endstep %} {% step %} **Confirm** Read the confirmation prompt carefully: the existing device will be permanently deboarded, and this action cannot be undone or cancelled once confirmed. {% endstep %} {% step %} **Swap begins** Upon confirmation, Commander Central immediately deboards the outgoing device (Delete Device) and opens the Service ID for a replacement device to onboard. This happens whether or not the outgoing device is online — a dead or unresponsive Commander is swapped the same way as a working one. {% endstep %} {% endstepper %} ### Onboarding the Replacement Device {% stepper %} {% step %} **Replacement Commander** Install the replacement Verifone Commander at the site and onboard it via Verifone Commander Configuration Client. {% endstep %} {% step %} **Serial Number** The device self-reports its serial number automatically during onboarding — no manual serial number entry is required. {% endstep %} {% step %} **Validation** Commander Central validates that the reported serial number is not already actively associated with a different Service ID, and rejects onboarding with a clear error if so. {% endstep %} {% step %} **Configuration Restoration** After onboarding succeeds, Commander Central automatically triggers reverse seeding (via the existing MQTT mechanism), restoring the site's configuration to the replacement device. All configuration datasets supported up to the device's base version are restored automatically — no manual configuration steps are needed. {% endstep %} {% endstepper %} ### Entitlement Alignment If the replacement device's serial number does not immediately match Verifone's CRM entitlement record for the site, Commander Central raises an Entitlement Alignment Exception rather than blocking onboarding. This exception clears automatically after CRM entitlement data syncs and confirms the new serial number. (This same exception type also applies to fresh, non-swap site onboarding where a serial number mismatch occurs.) #### Exception Report The Exception Report surfaces two types of exceptions related to device swaps and onboarding, with access scoped by role:

Role	Scope	View
Merchant Admin	Own organization's Service IDs	Hierarchical view — can scope to region, group, or individual site
VASC Technician	Only sites the VASC company is authorized for	Worklist of sites with an open Swap Trigger Exception, indicating a replacement device is still needed
Helpdesk / Operations (incl. Tier 1)	Entire install base	Read-only; optional filter by merchant entity, exception type, date range, or device type

* Swap Trigger Exception — created every time a swap is initiated; records the initiating user, timestamp, and the serial number of the deboarded device. This record is the audit trail for the swap itself. * Entitlement Alignment Exception — created when an onboarded device's serial number does not match CRM entitlement (for both swaps and fresh onboarding); clears automatically on CRM sync. #### Who Can Initiate a Swap

Role	Can Initiate Swap?	Can Onboard New Device?	Exception Report Access
Merchant Admin	Yes	Yes	Own organization, hierarchical scope
Authorized VASC Technician	Yes	Yes	Authorized sites only — worklist view
Helpdesk / Operations (Tier 1 & Ops)	No	No	Full install base, read-only
Unauthorized User	No	No	No access

--- # 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/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/onboarded-device-swap.md?ask=&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.