How Do Smart Lockers Work? A Guide to Velocity Smart Technology

If you have been asked to explain how smart lockers work, you have probably found that most of the available answers describe what they are for rather than what they actually do. That is a problem when you are the person who has to sign off the integration, the security model and the support burden. This guide walks through the full sequence, from the moment someone raises a request to the moment the asset register agrees with reality.

The short answer

A smart locker is a bank of individually controlled compartments connected to your service management platform. When an employee requests a device, the platform allocates a specific compartment, tells the employee where it is and issues a single-use credential. The employee authenticates at the locker, one door releases, and the act of opening that door is what closes the request and updates the asset record. Nobody from IT needs to be present, and the audit trail is created by the collection itself rather than typed in afterwards.

Everything below is the detail behind those four sentences.

The handover sequence, step by step

1. The request

The sequence starts in your service catalogue, not at the locker. An employee raises a request for a laptop, a headset, a replacement charger or a swap for a failed device. Nothing about the locker is visible to them yet. This matters more than it sounds, because a locker that requires its own separate portal has just added a system for your team to administer rather than removing one.

2. Allocation and stocking

The platform checks what is physically in the locker bank and reserves a compartment holding the right item. Good implementations hold stock against a model rather than a serial number, then bind the specific serial at the point of collection. That distinction is what allows one compartment to serve whoever arrives first instead of sitting reserved for a named person who is working from home that day.

If stock is not present, the request queues and a restocking task is raised against whoever owns replenishment. The locker becomes another stocking location in your existing inventory process rather than a separate store to reconcile.

3. Notification and credential

The employee receives a notification telling them which locker bank to go to and how to open it. The credential is typically a one-time code, a QR code, a badge tap or an identity check through your existing single sign-on. The important property is that it is scoped to one compartment and expires, so a code that leaks is worth nothing after collection or after its window closes.

4. Authentication at the door

At the locker, the employee presents the credential. The locker controller validates it against the platform and confirms the compartment. Where the network is unavailable, a well-designed controller holds a short-lived local cache so collections still work during an outage and reconcile when the connection returns. Ask about this specifically, because it is the difference between a locker that fails safe and one that becomes a wall of locked doors during a network incident.

5. Door release and asset capture

One door opens. Only one. The compartment reports its own state through a door sensor, so the system knows the difference between a door that was released and a door that was actually opened. Depending on the configuration, the asset is identified by a barcode or asset tag scan at the locker, or by the serial already bound to that compartment at stocking.

This step is where a smart locker earns its keep. The physical act of taking the device is the data capture event. There is no separate form to complete and no engineer transcribing a serial number into a ticket later that afternoon.

6. Write-back to the record

The platform closes the request, assigns the asset to the employee, and updates the configuration management database. Your asset register now reflects who holds which device, where they collected it and when. If that write-back is missing or delayed, you have automated the handover but kept the reconciliation problem, which is the most common disappointment we see in estates that bought lockers as standalone hardware.

7. Returns, swaps and failed devices

The reverse path matters as much as the outbound one. An employee returning a device is issued a credential for an empty compartment, drops the device, and the compartment is marked as holding an asset pending collection. From there it routes to reissue, to a repair vendor or to secure disposal. Swaps run both legs in one visit, with the employee collecting the replacement and depositing the failed unit in the same trip.

What is physically inside one

Underneath the software, a smart locker bank is a fairly simple piece of equipment. There is a steel enclosure divided into compartments of varying sizes, because a laptop and a mouse should not consume the same volume. Each compartment has an electromechanical lock, a door sensor and, in some designs, a presence sensor that detects whether anything is inside. A controller unit handles power distribution, network connectivity and lock actuation, usually with a touchscreen or scanner mounted on the bank. Compartments intended for laptops can be powered, so devices charge while they wait and are usable when collected.

None of that is exotic, and it is worth being clear that the hardware is rarely the differentiator. Velocity Smart Lockers are built on six locker manufacturers and three vending manufacturers, with one vendor building both, so eight distinct hardware partners in total. We are deliberately hardware agnostic, because the enclosure is a commodity and the integration is not.

The three integration models, and why it decides everything

This is the question that determines whether a locker programme reduces work or creates it, and it is the one most buying processes skip.

Standalone locker software. The locker comes with its own management application. Your team administers users, stock and reporting in a system that knows nothing about your service desk. Requests are raised in one place and fulfilled in another, and somebody reconciles the two. This is the cheapest option to buy and the most expensive to run.

Middleware and integration layers. The locker platform connects to your service management tool through an API or connector. Better, but you now own an integration. When your platform updates, someone has to care. When a request fails silently between the two systems, the diagnosis crosses a vendor boundary.

Native to the platform. The locker is driven from inside your service management tool, using its catalogue, its workflows, its approvals and its CMDB. There is no second system and no integration to maintain. Velocity Smart Collect is built natively on ServiceNow for this reason, so the locker appears as fulfilment capability inside the platform your team already runs.

If you take one thing from this guide, make it this. Ask any locker vendor where the request lives, where the asset record is written, and what happens to both when your service management platform is upgraded.

How this compares with a tech bar or a vending machine

A staffed tech bar handles ambiguity well. Somebody can diagnose an unclear fault, calm an unhappy executive and make a judgement call. It also costs a salary per location per day, keeps office hours and does not scale to sites too small to justify a person.

A smart vending machine suits high-volume, low-value consumables where the transaction is a straightforward dispense. Cables, adapters, headsets and mice fit this pattern well.

A smart locker sits between the two. It handles items that are valuable, individually tracked and often need to travel in both directions. Most large estates end up running a combination, with lockers for devices, vending for consumables and a reduced tech bar presence at the largest sites for the cases that genuinely need a human.

What actually changes operationally

The obvious gain is that collections stop being appointments. Employees pick up devices at whatever hour suits them, including outside the hours any tech bar could justify staffing, and multi-site estates get the same service level at a small office as at headquarters.

The less obvious gain is data quality. When the handover creates the record, your CMDB stops drifting. Teams that have run this for a while tend to describe the audit position as the thing they would struggle to give up, more than the time saved. Roche, BAE Systems and Centrica all run Velocity lockers in production, and in regulated environments the ability to evidence who held which asset and when is not a reporting nicety.

If you want the arithmetic for your own estate rather than a general claim, the ROI Challenge models it against your device volumes and support costs in a couple of minutes.

What smart lockers do not solve

They do not diagnose faults. An employee whose laptop is behaving oddly still needs a human or a remote session, and a locker only helps once the decision to swap has been made.

They do not fix a broken stock process. If your spares are unreliable, a locker will simply be empty more visibly than a cupboard was.

They do not remove the need for change management. Adoption is a real workstream, and the estates that struggle are usually the ones that installed hardware without telling anyone how the new route was supposed to work.

They are also not the cheapest way to hand over one device. The economics come from volume and from the labour you stop spending on scheduled handovers, so a single site with low churn is rarely the right place to start.

Frequently asked questions

How do employees open a smart locker?

They authenticate with a single-use credential issued when their request is ready. That is usually a one-time code or QR code sent by email or chat, a badge tap, or an identity check through your existing single sign-on. The credential opens one specific compartment and expires after collection or after a set window.

Do smart lockers work if the network goes down?

A well-designed locker controller caches active collection credentials locally, so employees can still collect during a short outage and the system reconciles when connectivity returns. This varies by vendor and is worth confirming before purchase, because some designs simply stop releasing doors.

Do smart lockers integrate with ServiceNow?

Some do, and the manner matters. Many connect through middleware or an API layer that you then maintain. Velocity Smart Collect is built natively on ServiceNow, so requests, approvals, fulfilment and CMDB updates all happen inside the platform without a second system to administer.

How does a smart locker update the asset register?

The collection event triggers the update. When the compartment door opens and the asset is confirmed, the platform assigns that serial number to the employee and writes the change to the configuration management database. The record is created by the handover rather than entered manually afterwards.

What is the difference between a smart locker and a smart vending machine?

Lockers hold individually tracked, higher-value items such as laptops and support returns as well as collections. Vending machines dispense high-volume consumables such as cables, adapters and headsets, where items are interchangeable and rarely come back. Large estates commonly run both.

Can smart lockers handle device returns and swaps?

Yes, and returns are often where most of the value sits. The employee is issued a credential for an empty compartment, deposits the device, and the system routes it to reissue, repair or disposal. A swap runs both legs in a single visit.

Where to go next

If you are working out whether this fits your estate, the practical next step is to put your own numbers against it rather than ours. Model the position with the ROI Challenge, or read how the pieces fit together across devices and consumables in our complete guide to smart locker technology. If you would rather pressure-test the assumptions with someone who has deployed this in regulated estates, book a workshop and we will go through it against your own support data.