Container, railcar and truck number recognition straight into your TOS
Cameras at gates and rail tracks read container, railcar and truck numbers. Container codes are validated against the ISO 6346 check digit. Data goes straight into your terminal system together with the frame.
What hurts
Truck and container numbers are written down by hand at the gate. One wrong digit reaches customs or the customer, and the container gets hunted across the yard.
A queue builds at the gate because the clerk copies numbers from every vehicle. At night and in rain there are more errors.
When a dispute arises about damage or arrival time, there is no evidence. Cameras record, but finding the right frame takes too long.
What we build
- Survey of gates and tracks, camera angles and RTSP connection
- Container code OCR with ISO 6346 check digit validation
- Railcar number and truck and trailer plate recognition
- Linking truck, trailer and container into one gate event
- Events sent to your TOS, ERP or database via API
- Manual review queue for numbers that fail the check digit
- Frame archive of every gate event for damage and timing disputes
- On-site analysis server that works offline and syncs later
What you get
- A working system on the agreed gates and tracks
- TOS or ERP integration with API documentation
- Gate event log with frames and search by number
- Accuracy report measured on your terminal
- Access credentials, integration source code and operator training
How we measure the result
- Share of numbers read without manual entry
- Number errors that reached documents
- Truck gate transaction time
- Time to find the frame for a disputed case
Questions
What does it cost and what drives the price?
From $8,000. The price depends on the number of gates and tracks, traffic speed, whether extra cameras and lighting are needed, and the complexity of the TOS or ERP integration. We give a fixed estimate within 2-3 days after a site visit.
Why the ISO 6346 check?
Every container code carries a check digit. If a recognised code fails it, the system does not post it automatically but sends it for manual review with the frame. That keeps OCR errors out of your documents.
What about dirty or damaged codes?
AI sometimes makes mistakes, especially on dirty, worn or partly hidden codes. So we capture from several angles, validate the check digit and route doubtful reads to an operator. Accuracy is measured on your terminal during the pilot.
Which systems do you integrate with?
Your terminal operating system, an ERP such as SAP, Odoo or Microsoft Dynamics, or your own database via API. For trucks we can also connect the barrier and booking check, as in our TruxSpot project. The exchange format is agreed during discovery.
How long does the project take?
Six to ten weeks. Discovery takes 1-2 weeks, then the build with weekly demos. We launch on one gate in parallel with manual recording, compare results, then add the rest. After launch we provide SLA support.
Related services
More in this section
Describe the task. We reply within one business day, the first call is with the founder.
Describe the task. The first call is with the founder.
We reply within one business day. 30 minutes to tell you whether it is worth doing and what it costs.