Operations not shown here can be built for your own needs
The use cases we list are simply the most common patterns. KEYVOX lockers run on top of UnlockOS, where everything from checking availability to booking, confirmation, lookup, and return is published as a workflow. Even operations we don't list can be built by recombining the same parts.
Choose the depth to start from
You don't suddenly need development. From top to bottom, we've arranged everything from no-code approaches to embedding into your own service.
Start with just the dashboard
From day one, with no code
Set box access rights from the web dashboard and issue QR codes or PINs. You can switch between two modes — handover and delivery — so many uses run on this alone.
- Grant and revoke access rights from the screen
- Send QR codes / PINs by email or SMS
- Check unlock history in real time
Use the ready-made app as-is
Skip building a user-facing screen
UnlockOS comes with a locker-reservation app for users. It has the full set — size selection, time slot, confirmation, completion, a My Page, and usage history — so you can start hourly rentals or a membership model right away.
- Book by choosing a size and time slot
- Check the box in use and history from My Page
- Booking, membership, and payment are handled by UnlockOS
Embed it in your own site
Keep everything within your existing site
Place the embeddable widget on your own site, and everything from the process to receiving the key completes on that page. Payment is supported too, so there's no need to send users to a different domain.
- Just place a script on your existing site
- Complete through payment on the same screen
- Show the issued key on the spot
Integrate via the workflow API
Make it part of your own business systems
The locker workflow is published as OpenAPI. Checking availability, looking up a reservation, and returning are defined as endpoints you can call directly from your own app or core systems. It uses the same scheme as the smart-lock API, so you can handle access control and lockers together.
- Check availability (public endpoint)
- Look up a reservation (with OTP authentication)
- Execute a return
- Authentication by API key; the same scheme as the lock API
Locker operations are built in this flow
Whichever level you start from, the same workflow runs underneath. When you build it yourself, you'll follow this same order.
- 01
Check availability
Retrieve availability by size and time slot. A timezone-aware availability engine handles it.
- 02
Book
The user books by specifying the size and time they want to use.
- 03
Confirm (assign box, issue PIN)
Assign an actual box and issue a PIN for unlocking.
- 04
Look up
The user checks their own reservation, referenced after OTP authentication.
- 05
Return
Record the end of use and revoke the issued PIN.
For example, you can build operations like these
Each is an application of the same workflow: check availability, assign a box, hand over the key conditionally, and revoke it on return. We just don't list them among the use cases — that doesn't mean they can't be built.
In-house lending of tools and equipment
Issue access rights in step with take-out request approval, and track through return with history.
Equipment lending for member spaces
Vary which boxes are usable by membership tier. Combine with UnlockOS member management.
Inventory transfer between stores
Activate access rights to match the delivery staff's arrival time and make handover unattended.
Time-limited handover of documents and keys
Issue a QR code with an expiry, and automatically disable opening once it passes.
Handover of cleaning and repair items
Do drop-off and hand-back at different times, and send the completion notice from your own system.
Unlocking from your own app
Embed it into the facility's official app and complete everything from payment to unlocking in-app. The form adopted at Nagasaki Stadium City.
The above are examples of combinations. Not all have a track record, and feasibility depends on requirements. Tell us the specifics of your operation and we'll answer which level (dashboard / ready-made app / embed / API) it can be built at.
The enclosure can be built to fit the operation too
Beyond the software side, you can design the box dimensions, compartment count, and door specifications. "There's no size that fits this equipment, so we give up" doesn't happen. Changing the size itself carries no surcharge.
Talk to us about whether your operation is possible
Tell us your current operation and what you want to do with the locker. We'll propose whether the dashboard is enough, whether to use the ready-made app, or whether API integration is needed.