Define compartments
Confirm lock count, relay channel, voltage, and door sensor requirements.
Locker unlock control
Smart locker relay unlock controller for API and QR workflows.
Use QuLink when a locker, cabinet, access door, or compartment device needs server-controlled unlock, QR payment trigger, relay output, and door/status upload.
Relay unlockDoor statusAPI commandQR optional
Project fit
For lockers, cabinets, and access devices
Buyer signals
- Smart lockers, charging lockers, storage cabinets, and access doors.
- Projects that need unlock after payment, booking, app approval, or operator command.
- Devices needing door open/close status or fault alerts.
- OEM projects with custom compartment count or wiring harness.
What to send first
- Machine photo or existing board photo
- Interface or wiring note if available
- Target action after API command or payment
- Whether telemetry or data upload is required
Not the right fit if
- You only need a pure payment acquiring account and no machine-side control.
- There is no physical machine action after payment, booking, or API approval.
- The project has no machine photo, board photo, wiring note, or interface clue yet.
Integration model
API approval becomes a relay unlock action
QuLink receives the unlock command, controls the relay output, and can upload door state or operation result to your server.
- Machine interface
- relay unlock, dry contact, door sensor, multi-channel wiring
- Trigger source
- QR payment, booking system, app approval, operator panel, API command
- Data returned
- unlock.accepted, door.opened, door.closed, timeout, fault
- Project mode
- locker retrofit, access control board, OEM cabinet controller
Workflow
From machine interface to API-controlled result.
Map permission
Your platform decides payment, booking, identity, or operator approval.
Unlock device
QuLink triggers the correct relay or lock channel.
Upload state
Door status and operation result are sent back to your backend.
API example
A clear server command or webhook for the machine-side action.
The exact command fields depend on machine interface, firmware profile, and whether payment or your own app triggers the action.
POST /v1/devices/LOCKER-22/commands
{
"command": "unlock",
"source": "booking_approved",
"machine_action": {
"type": "relay",
"channel": 7,
"duration_ms": 800
}
}
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send the locker/cabinet photo, lock voltage, channel count, door sensor needs, and app/payment workflow.
A good first message
If you are unsure about the exact interface, send what you have. Photos often answer more than a long spec.
- Machine type and target country
- Machine photo, board photo, or wiring photo
- Action after payment or API command
- Need data upload? expected quantity?
Fastest first step
- Send a machine photo
- Describe the action after API or payment
- Tell us if data upload is needed
FAQ
Questions buyers usually ask before a sample test.
Can QuLink control multiple locker doors?
Yes, multi-channel relay or OEM board options can be evaluated based on lock count and wiring.
Can QR payment unlock a door?
Yes. QuLink QR payment or your own payment callback can trigger the unlock command.
Can door status be uploaded?
Yes. Door sensors can be mapped to status and event callbacks when the hardware supports it.
Related use cases