License plate and container number recognition at the gate means letting cameras read the plate, container, seal and trailer numbers of every vehicle that enters or leaves your site, and matching them with appointment and shipment records automatically. When a truck has no appointment or carries the wrong container, the gate guard and the shipping supervisor are told immediately, and every entry and exit is logged with its time.
At many logistics and production sites the gate is still run with a clipboard. A guard writes down the plate, maybe the container number, and nobody knows exactly how long each truck stayed. That works until the wrong container is loaded or leaves the yard, which is an expensive mistake to undo. The License Plate & Container OCR scenario on TIM INSPECT is built for exactly this gap: reading numbers is only half the job; matching them with the shipment record is the other half.
A handwritten or manually typed vehicle log creates three recurring problems:
Container numbers follow the ISO 6346 structure: an owner code, a serial number and a check digit. Owner codes are registered by BIC, and the check digit exists precisely because manual transcription goes wrong. A camera that reads the number directly avoids the copying step altogether.
Automatic license plate recognition is a common product, and many sites already have a barrier that opens for known plates. The limit is that a plate reader knows the vehicle, not the load. It cannot tell you whether container number and seal number match the shipment, or whether a trailer is leaving with the wrong box.
The difference in this scenario is that number reading and shipment verification live in the same system. The number read at the gate is matched with the shipment record in one workflow, and mismatches reach the right people directly.
On the TIM INSPECT platform, the gate workflow runs in four steps:
| Situation | Response at the gate | System decision |
|---|---|---|
| No appointment | The guard holds the vehicle while the shipping supervisor checks the appointment. | No entry record is opened; the notification stays open until an appointment matches. |
| Container mismatch | There is an appointment, but the container number read does not match the shipment record. Both roles are notified, and the shipping supervisor compares the record with the container. | The mismatch is recorded. No entry record is opened until the number matches. |
| Mismatch at exit | One of the containers read at the exit gate is not in the expected record. The guard holds the vehicle while the shipping supervisor compares the loaded containers with the record. | The wrong container is caught before it leaves the site. The exit record closes once the numbers match. |
Notifying two roles together matters. The guard can stop the vehicle physically, while the shipping supervisor is the one who can fix or confirm the record. Neither has to wait for the other to find out.
Plates are on the front and rear of the vehicle, container numbers on the container doors and sides, seal numbers on the locking bars. Which number is read by which camera is agreed before installation, based on how vehicles approach and stop at your gate.
The numbers read are matched with records in the appointment and shipment system. Where needed, the workflow also connects to barrier control. The integration scope is planned around the systems already used on site.
This scenario reads vehicle and container numbers; it does not assess who a person is. Where people appear in view, images are filtered and only the event moment is stored. Privacy is designed in from the start in line with GDPR and KVKK requirements.
The solution page describes a scenario, not proven figures. Agree on pilot metrics at the start, for example registration time at the gate, mismatches caught before loading or exit, and average time on site.
Once a truck is inside, the next question is what happens at the door. The Dock Door Monitoring scenario follows door occupancy and loading activity on the other side of the yard.
License plates, container numbers, seal numbers and trailer numbers, along with vehicle entry and exit times.
A plate reader identifies the vehicle. Here, plate and container reading is combined with shipment verification in the same system, and mismatches reach the gate guard and the shipping supervisor through AXION.
Where needed, the workflow connects to barrier control. The scope depends on the gate equipment on site.
No. The scenario reads vehicle and container numbers only. Images with people are filtered and only the event moment is stored.
If you want your gate log and shipment record to become one workflow, review the License Plate & Container OCR scenario or request a demo to discuss your gate layout.