Features
Yard Access Control (QRGOBox)
The driver holds up the QR from their check-in, the platform runs eight checks in one round trip, and a relay pulses the barrier open — with the reply in the driver's language and the ramp to drive to.
Open the yard barrier from a validated check-in
The driver holds up the QR from their check-in, the platform runs eight checks in one round trip, and a relay pulses the barrier open — with the reply in the driver's language and the ramp to drive to.
From QR to barrier, in one round trip
Every step below is what the code does. The terminal decides nothing and the box decides nothing — all authorisation lives in the validate route.
- 1
The driver shows the QR
The check-in status page renders the check-in ID as a QR code on the driver's phone. That UUID is the whole payload — no name, no plate, no cargo.
- 2
The gate terminal reads it
A mounted terminal facing the truck decodes the UUID, debounces for three seconds, and turns orange: Validating check-in.
- 3
Eight checks, one call
POST /api/gate/validate, behind a rate limit: required fields, check-in found, gate found, organisation key matched in constant time, gate active, same organisation, not deleted, status allowed.
- 4
The open command goes out
On a pass, the platform publishes command: open to qrgo/gate/{id}/command at QoS 1 while writing the access log and the driver's timeline in parallel.
- 5
The relay pulses for one second
The ESP32 subscribed to that topic drives its open pin high for 1,000 ms and the barrier rises. Optional auto-close follows after a delay of at least five seconds.
What the box actually is
A relay controller sitting on your yard's WiFi. It has no camera and reads nothing — it pulses a contact when the platform tells it to.
- Controller
- ESP32 Dev Module, Arduino/PlatformIO firmware v1.0.30
- Relay output
- 5V module (SRD-05VDC-SL-C), sharing a common ground with the ESP32
- Gates per box
- Up to 18 per box — the firmware's own cap — assigned across 18 selectable GPIO pins; dual-pin wiring spends two
- Open pulse
- 1,000 ms contact; optional auto-close, minimum 5 s delay
- Wiring modes
- Open + Close (two pins), Close same pin, or Open only
- Connectivity
- WiFi; outbound MQTT session, 30 s HTTPS heartbeat, OTA firmware
It never phones in. It only phones out.
Gate hardware usually dies in the IT review, because it wants a static IP and a hole in the firewall. This box asks for neither. The ESP32 opens every connection itself: an outbound MQTT session to the broker, and an HTTPS heartbeat to the dashboard every thirty seconds carrying its firmware version, IP, signal strength and the state of each gate. The open command travels back down a socket that is already open, so there is no port forwarding, no inbound rule and no VPN to negotiate. The trade is worth stating plainly: the box keeps no cached list of valid check-ins, so a WiFi or broker outage means nothing opens remotely. There is no offline mode. The only fallback is a person pressing OPEN on the box's own admin page from the yard network.
pilot
This is pilot hardware, and we will not pretend otherwise
QRGOBox is self-built: an ESP32, a relay module, firmware, and a gate terminal that is sideloaded onto a mounted device rather than published to an app store. The whole chain works end to end, and the validation, logging and timeline are production code in the same platform that runs your check-ins. The hardware is not: it has only ever run on one demo yard with two gates, Poarta Principală and Poartă Ieșire, and there is no enclosure spec, no certification, no price list and no lead time. If you want a barrier on your yard wired to your check-ins, talk to us about a pilot and we will scope it with you honestly.
Questions worth asking before you wire a barrier
No. The box has no camera and reads nothing at all. A separate terminal mounted at the gate reads the driver's QR and sends it to the platform; the platform runs the checks and publishes an open command over MQTT. The box subscribes to that topic and pulses a relay contact. Every decision happens in the cloud route, never on the box.
The gate stops working, and the screen will not soften it. There is no offline mode, no cached list of valid check-ins and no retry queue. If the terminal cannot reach the platform it shows a red ACCESS DENIED that looks identical to a genuine refusal. The only fallback is a person pressing OPEN on the box's own admin page from the yard network.
Only those with a status of confirmed, assigned or in progress. A driver still waiting for a dispatcher to confirm is turned away at the barrier, and the refusal is stored with its reason. There is no time-window or slot check in the route: the check-in's status is the only gate on timing, so confirmation is the control your dispatchers really hold.
Every attempt, allowed or denied, QR or manual, writes a row to the gate access log with its reason. From the gate-active check onward the driver's own status timeline also gains a line such as Entry: Poarta Principală, visible to them live. One caveat we would rather state than hide: the log records that access was granted, not that the barrier physically lifted — nothing reads back from the relay.
Everything you need for an efficient warehouse
Digital Check-in
On arrival, the driver scans the QR code or accesses the warehouse in the QRGO Driver app. Fills in the data and receives confirmation. No papers, no queues.
Dock Management
Operators allocate, release and optimize truck flow from a single dashboard.
Real-time Chat & Notifications
Instant chat between operator and driver, push notifications on phone, and SMS options. Clear communication, regardless of the platform used by the driver.
Ready to transform warehouse operations?
Join hundreds of warehouses that chose efficiency. Free demo, quick setup, no obligations.