> 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/asset-tracking.md). # Asset tracking Use **Asset tracking** to follow a device from shipment through custody handoffs, inspection, and deployment. Use it before the device enters normal device management. ### When to use this page Use asset tracking when you need to: * confirm where a shipped device is now * identify the current custodian or location * record a handoff, inspection, incident, or status change * verify whether a device is ready for deployment or registration Use [Devices](/verifone-central-device-management/verifone-central/devices.md) after the device is active and you need normal device management. ### Before you start Confirm that you know: * the device **Serial Number** or shipment record * the current or expected custody stage * whether you need to review status, update a record, or manage locations Prepare these details when available: * current custodian * current location * new status or inspection result * any incident notes or supporting evidence ### How asset tracking fits the workflow Asset tracking supports the onboarding path used when shipment and custody data drive device intake. Use this path when **P2PE-Asset Tracking** is the onboarding method for the device. The workflow usually follows this order: 1. The device ships from the Verifone store. 2. Custody and location details are updated at each handoff. 3. Inspection results are recorded during transit, storage, or deployment prep. 4. The device reaches the deployment location and is installed. 5. The device connects to the server and completes registration. {% hint style="info" %} Use asset tracking before or during deployment. Use registration after the device can contact the server. {% endhint %} ### Choose the right task Use this order to find the right page quickly. {% stepper %} {% step %} ### 1. Do you need to review the current custody state? Use [View device status in Chain of Custody](/verifone-central-device-management/verifone-central/asset-tracking/view-device-status-in-chain-of-custody.md) when you need one device record. Use [Chain of Custody report](/verifone-central-device-management/verifone-central/reports/device-management/chain-of-custody-report.md) when you need a broader report view or a filtered record set. {% endstep %} {% step %} ### 2. Do you need to update the custody record? Use [Updating the File Chain of Custody](/verifone-central-device-management/verifone-central/asset-tracking/updating-the-file-chain-of-custody.md) when a custodian must record a new status, location, inspection result, or incident. {% endstep %} {% step %} ### 3. Do you need to manage the location list? Use [Configure locations](/verifone-central-device-management/verifone-central/asset-tracking/configure-locations.md) when the available custody locations need to be added, edited, imported, or reviewed. {% endstep %} {% step %} ### 4. Do you need to confirm deployment progress? Use [Active lifecycle and key indicators](/verifone-central-device-management/verifone-central/devices/active-lifecycle-and-key-indicators.md) when you need to confirm where the device sits between shipment and active use. {% endstep %} {% endstepper %} ### Common custody outcomes Asset tracking records status changes that explain what happened to the device. Common outcomes include: * **In-Transit** — the device is moving between approved locations * **Awaiting deployment** — the device is received and stored securely, but not installed yet * **Deployed** — the device is installed and in operational use * **In Repair**, **Malfunctioning**, **Tampered**, or **Lost or Stolen** — the device needs operational or security follow-up * **Retired** — the device is removed from service and will not return to active use Use the selected status to keep the recorded workflow aligned with the physical device state. ### What to verify during tracking Check these points each time you review or update a device: * the custodian matches the last confirmed handoff * the location matches the device's physical position * the status reflects the current stage of transit, storage, deployment, or exception handling * inspection notes explain any damage, tamper signs, or incidents These checks help prevent registration or deployment from starting with incorrect custody data. ### Related onboarding and registration Asset tracking is one onboarding path. Use [Onboard a Device](/verifone-central-device-management/verifone-central/devices/onboard-a-device.md) when you need to choose between manual add, bulk import, auto-registration, or asset workflows. After deployment, use [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) to understand first contact with the server. {% hint style="warning" %} Do not treat shipment tracking as proof of successful registration. A device still needs to connect to the server before it becomes active in normal device management. {% endhint %} ### Verify the result After you use asset tracking, confirm that: * the device shows the correct custodian, location, and status * the recorded workflow stage matches the physical device state * inspection or incident details are complete when needed * the next action is clear: continue tracking, deploy, or register ### Result You can track devices from shipment to deployment and hand them off to registration and normal device management with the right custody context. ### Next steps * [View device status in Chain of Custody](/verifone-central-device-management/verifone-central/asset-tracking/view-device-status-in-chain-of-custody.md) — review one shipped device * [Chain of Custody report](/verifone-central-device-management/verifone-central/reports/device-management/chain-of-custody-report.md) — review or filter custody records * [Updating the File Chain of Custody](/verifone-central-device-management/verifone-central/asset-tracking/updating-the-file-chain-of-custody.md) — record custody updates * [Configure locations](/verifone-central-device-management/verifone-central/asset-tracking/configure-locations.md) — maintain location values * [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) — continue after deployment --- # 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/asset-tracking.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.