Inventory Visibility
Part of Retail technology performance reviews
Identifying devices and licences no longer used
Reconcile retail assets and software licences with actual work, confirm dependencies and release disused items safely.
Find apparent disuse by matching asset and licence records to store assignments, system activity and the work people still need to do. Confirm the result with an owner before cancelling a subscription, reclaiming access or removing a device. An idle signal is a lead for investigation, not a removal decision.
Build one working list
Bring together purchase and lease records, asset IDs, serial numbers, assigned store or user, subscription or licence type, renewal date, support contract and named owner. Keep a device's physical location separate from its billing location. Record unknowns rather than treating a missing assignment as proof that it is spare.
For software, distinguish named-user seats, shared or device entitlements and capacity charged by another unit. Check the contract for minimum quantities, reassignment rules and cancellation dates.
Look for use through more than one signal
| Candidate | Signal to investigate | Confirmation needed |
|---|---|---|
| Store device | No recent task record or connection | Physical check, assigned role and any offline use. |
| Named licence | Little recorded user activity | Whether the person needs an infrequent function or access through another route. |
| Spare equipment | No current store assignment | Whether it is an approved replacement or continuity spare. |
| Old integration | No visible front-line users | Whether another system or automated job still depends on it. |
Use each system's reporting period and activity definition. A login may occur without useful work; a missing login may reflect shared equipment, offline work or an incomplete report.
For example, Microsoft 365 usage reports generally offer 7-, 30-, 90- and 180-day views, exclude perpetual licences and can lag. Those are Microsoft 365 limits, not a standard for store systems. Do not apply one inactivity threshold across unlike services.
Walk the store where hardware is concerned. Match the physical label to the record, ask what task it supports and check whether another device now performs that task.
A powered-off unit in a cupboard may still be the only approved fallback for a critical counter. A connected screen may be showing content nobody needs. Retain the unit if it is the only approved fallback; release the screen only after its owner confirms the content is no longer needed.
Check dependencies before releasing anything
Ask the business owner and technical owner what would stop working if the candidate disappeared. Review linked printers, payment or order workflows, scheduled jobs, supplier support access and data held in the account or device. Check what staff would do during an outage if a spare is removed.
For a licence, distinguish removing an assignment from ending a paid subscription. Before either action, check access to records, retention needs, connected automation and the provider's data behaviour for the exact service. For equipment, arrange authorised data removal or sanitisation appropriate to the device before transfer, return or disposal. Update the asset record with what happened.
Turn findings into a controlled action list
Mark each candidate in use, needed as a documented spare, needs further checking or approved for release. Give the release an owner, effective date and evidence: store confirmation, dependency check, contract term and data-handling step. Record the financial effect only after billing or the contract confirms it; a reclaimed seat alone is not a verified saving.
Repeat the reconciliation when stores close, roles change or systems are replaced.
