ConPDS Tracker · Shipping Container OCR Software

Shipping Container OCR Software

On-premise GPU-powered OCR that reads container codes from any IP camera — and publishes results in open JSON via MQTT. No management system dependency. No proprietary lock-in. Your data, your infrastructure, your integration.

Deployed at container depots, terminals, and logistics facilities across Europe.
No obligations — reply within 1 business day

What Is Shipping Container OCR Software?

Shipping container OCR software connects to IP camera streams at logistics facilities and uses computer vision and optical character recognition to automatically detect, read, and record container codes as they move through the site. Results are published in structured data formats — typically JSON — enabling real-time integration with depot management systems, custom automation workflows, email alerts, database storage, or any other business logic a facility requires. It eliminates the need for manual data entry at gates and checkpoint positions, removes transcription errors, and provides a timestamped digital record of every container movement. Used at container depots, intermodal terminals, Ro-Ro terminals, warehouses, and port facilities of any size.
ConPDS Tracker is on-premise shipping container OCR software built on deep-learning container code recognition and the ConPDS Core OCR engine. It connects simultaneously to multiple IP camera RTSP streams — from a handful of cameras at a single gate to dozens across a large facility — and processes all streams concurrently. Streams can be organised into camera groups representing gate lanes, yard zones, checkpoints, or any logical unit the operation requires. Tracker performs motion detection to trigger processing only when a vehicle is present, reads ISO 6346, BIC, and ISO Tank container codes at up to 99% accuracy with processing times as low as 100ms, and publishes every result as JSON to an MQTT broker — per camera or per camera group. Any subscriber can consume that data and act on it: a depot management system (DMS), terminal operating system (TOS), warehouse management system (WMS), a custom integration, or a direct database write. Tracker has no dependency on any specific management system. It runs entirely on your hardware, on your network, and your team decides what happens with the data it produces.
Reads ISO 6346, BIC, and ISO Tank container codes — horizontal and vertical, single- and double-line
Connects to multiple concurrent IP camera RTSP streams simultaneously — streams grouped into camera groups per lane, zone, or checkpoint
Publishes OCR results as JSON via MQTT per camera or camera group — open format, any subscriber, any downstream system
Integrates with DMS, TOS, WMS, and any logistics platform via MQTT, REST APIs, or direct database integration
Runs on-premise — Windows or Linux, GPU-accelerated, edge architecture, no cloud dependency

The Cost of Manual Container Code Capture at Scale

A facility processing 60 container movements per day requires a gate officer to manually read, type, and verify each container code — creating a compounding error risk and a throughput ceiling. A single transposition error on one container number creates a documentation mismatch that may not surface until a dispute is raised weeks later.

Without Automated Container Monitoring

Container codes entered manually — transcription errors create downstream data mismatches
Gate officer required for every movement — throughput ceiling tied to staff availability
No timestamped record of which truck carried which container at which moment
Data lives in paper logs or spreadsheets — not available to downstream systems in real time
Integration with DMS requires manual re-entry — doubling the error risk

With ConPDS Tracker

Container codes read automatically from camera streams — no manual entry
Up to 99% OCR accuracy — results published as JSON within 100ms of capture
Every read timestamped and attributed to camera and lane — full movement audit trail
Results available to any MQTT subscriber immediately — DMS, custom logic, database, alerts
Gate officer freed from data entry — focus shifts to exception handling

✗ Before: Manual Code Entry

A damage dispute is raised three months after gate-out. The gate register shows a container number — but a transposition error means it doesn't match the container that actually departed. There is no camera evidence, no timestamp, and no way to reconstruct what happened.

✓ After: ConPDS Tracker

The same dispute is raised. Tracker's OCR log shows the exact container code read from the camera at the moment of movement, the camera and lane, and the timestamp. The record is unambiguous and was never touched by a human hand.

How ConPDS Tracker Shipping Container OCR Works

01
Camera Connection
Tracker connects to IP cameras via RTSP
02
Motion Detection
Vehicle presence triggers OCR processing
03
Container OCR
Container codes read in real time
04
Result Selection
Best read selected across frames and camera angles
05
JSON → MQTT
Result published — any subscriber acts on the data
Steps 01–02 — Trigger

Motion-Driven Processing

Tracker monitors all connected camera streams continuously. Processing is triggered by motion detection — OCR runs only when a vehicle is present in the frame, keeping hardware load proportional to actual traffic volume.

Steps 03–04 — Read

OCR & Best-Result Selection

The ConPDS Core OCR engine reads ISO 6346, BIC, and ISO Tank container codes across multiple frames and camera angles. Tracker selects the highest-confidence result — up to 99% accuracy at 100ms processing time.

Step 05 — Output

Open JSON Output via MQTT

Every confirmed read is published as a JSON message to the MQTT broker — container code, camera ID, camera group, timestamp, and confidence score. Any subscribed system receives it instantly: your DMS, a custom integration, a database writer, or ConPDS Autogate.

Three Capabilities That Make ConPDS Tracker an Open Platform

Tracker does not prescribe what happens after a container code is read. It gives you accurate, structured data — and leaves the business logic entirely in your hands.

Capability 01 — Identification

Container Code Recognition

Reads ISO 6346, BIC, and ISO Tank container codes — horizontal and vertical orientation, single- and double-line
ISO container type recognition: size and type codes validated against ISO 6346 standard
Rear camera speed up to 10kph · side camera up to 7kph · angles up to 30° horizontal and vertical
Capability 02 — Output

Open JSON Output via MQTT — Build Any Integration

Every read published as structured JSON to the MQTT broker — no proprietary format, no vendor lock-in
Any MQTT subscriber receives the data instantly: your DMS, TOS, WMS, a custom webhook, or a direct database write
Integration via MQTT, REST APIs, or direct database integration — standard protocols, no middleware required
ConPDS provides custom integration support for non-standard environments on request
Capability 03 — Infrastructure

On-Premise, Any Camera, Any Facility Size

Runs on your hardware — Windows 10+ / Linux Ubuntu 20+ — nothing leaves your network
Connects simultaneously to multiple concurrent IP camera RTSP streams — 5 at a small depot, 50 across a large terminal, same software throughout
Streams organised into camera groups — a group can represent a gate lane, a yard zone, a crane position, or any logical unit the facility defines
GPU-accelerated processing — Nvidia CUDA, AMD Radeon, or Intel HD; processing capacity scales with hardware as camera count grows
Centralised OCR engine — update Tracker once and every connected camera stream benefits immediately, with no manual firmware upload or per-camera reconfiguration required

What Container Facilities Gain With ConPDS Tracker

track_changes
Up to 99% OCR Accuracy

Deep-learning ConPDS Core OCR engine with motion and object detection — container codes read correctly the first time, every time a vehicle passes.

flash_on
100ms Processing Time

From camera frame to JSON result in as little as 100ms — downstream systems receive data before the truck has cleared the lane.

photo_camera
Works With Existing Cameras

Any IP camera supporting RTSP streams — no proprietary hardware required, no ripping out existing infrastructure. Axis, Hikvision, Bosch, Vivotek and others.

lock
No Management System Dependency

Works with any DMS, TOS, or WMS — or none at all. Integrate via MQTT, REST APIs, or direct database integration. You choose what consumes the data.

home
Fully On-Premise

All processing and data storage happens on your hardware. Nothing is sent to ConPDS systems. You own the data and control retention, access, and compliance.

sync
Centralised OCR Engine Updates

Update Tracker once — every connected camera stream benefits instantly. No manual firmware upload per camera, no per-device reconfiguration. Cameras with built-in OCR require individual updates; Tracker doesn't.

visibility
Motion-Triggered Processing

OCR runs only when a vehicle is detected — not continuously across all streams. GPU load stays proportional to actual traffic, reducing hardware requirements and energy use at facilities with variable throughput.

settings_input_antenna
Concurrent Multi-Stream Processing

One Tracker installation processes multiple camera streams simultaneously — 5, 20, or 50+ cameras handled by a single OCR engine. No separate system per camera, no per-stream licensing complexity.

square_foot
Scales to Any Facility

From a single gate camera at a small depot to multi-lane, multi-site terminal deployments — same software platform, same open output format, same central update model throughout.

What Do You Want to Build on Tracker's OCR Output?

Tracker publishes container codes as open JSON via MQTT — what happens next is your choice. Two paths are available.

Open Platform · Any DMS · Any Workflow

Build Your Own Integration

Tracker's MQTT output is your data layer. Subscribe any system to the feed — your DMS, TOS, WMS, a custom webhook, or a direct database write. No ConPDS middleware required. Integration is available via MQTT, REST APIs, or direct database integration.

Any MQTT Subscriber JSON published per camera or camera group — consumed by DMS, TOS, WMS, REST APIs, SQL databases, or any custom application.
No Management System Dependency Works independently of any DMS, TOS, or WMS — DepotMaster, EOS, AEMS, or systems you've built yourself. Integrate with whatever you run, or with nothing at all.
Custom Integration & Workflow Development Tracker's job ends at the MQTT publish — what happens next is business logic built on top of that data. ConPDS's team can help design and build custom integrations, routing rules, and automated workflows as a separate engagement.
Pre-Built Solution · DepotMaster Depots Only

ConPDS Autogate — Ready to Deploy

ConPDS Autogate is the complete, turnkey gate automation solution built on Tracker. It adds the physical installation and the DepotMaster integration layer — cameras, kiosk totem with QR scanner, safety-interlocked barrier, video intercom, and full reservation matching logic. Tracker's OCR output becomes barrier decisions and self-service driver interaction, without a gate officer present.

Requires DepotMaster. Autogate is designed specifically for depots running DepotMaster as their DMS. If your operation uses a different DMS, the open platform path on the left is your starting point.
Complete Physical Installation Cameras, kiosk totem, QR scanner, safety-interlocked barrier with lane sensors, video intercom, network equipment — one integrated system.
Observed at Live Deployments Gate events that previously took several minutes now complete in seconds — from truck approaching cameras to barrier opening, no manual involvement.
See ConPDS Autogate →

The ConPDS Platform: Tracker · Checker · Autogate

Tracker is the OCR core. Checker adds mobile field inspection evidence. Autogate is the complete gate installation built on Tracker for DepotMaster depots. All three share the same container reference — connecting what the camera sees, what the technician photographs, and what the office needs to manage.

ConPDS Tracker

The OCR Core

On-premise shipping container OCR software. Connects to any IP camera, reads container codes via deep-learning container code recognition, publishes results as open JSON via MQTT. Independent of any DMS, TOS, or WMS. The data layer that everything else is built on.

ConPDS Checker

Mobile Field Documentation

The mobile inspection documentation app for iOS and Android. Field technicians capture structured inspection photos linked to ISO 6346-validated container numbers — works online and offline. Complements Tracker by adding visual evidence to container movement records.
ConPDS Autogate

Complete Gate Installation

Turnkey automated gate solution built on Tracker — cameras, kiosk totem, barrier, intercom, and full DepotMaster integration. Tracker's OCR output becomes barrier decisions and self-service driver interaction. Designed for DepotMaster depots.

Tracker produces the data. Checker captures the evidence. Autogate closes the loop at the physical gate. Each product works independently — and together they cover the full container lifecycle from camera read to field inspection to barrier decision.

Architecture, Data Ownership & Integration

Edge / On-Premise Processing No Cloud Dependency Customer Data Ownership Open JSON / MQTT Output Any IP Camera Compatible No Management System Dependency Windows & Linux Support
All processing runs on-premise on your GPU hardware — container codes and video frames never leave your network
You own the data ConPDS Tracker produces — data retention, access controls, and GDPR compliance are your responsibility and under your control
OCR results published via MQTT in standard JSON — integrates with any DMS, TOS, WMS, or logistics platform via MQTT, REST APIs, or direct database integration
Custom integration development and workflow logic built on top of Tracker's output is available as a separate ConPDS engagement — not a built-in software feature
Supports authentication via Certificate, API key, Basic Auth, and URL Auth — integrates with existing access control infrastructure
For inspection photo evidence that complements Tracker's movement records, see how container inspection photo documentation works across the ConPDS platform.

Technical Specifications

Performance
Accuracy
Up to 99%
Processing time
As low as 100ms
Rear camera speed
Up to 10kph
Side camera speed
Up to 7kph
Max angle
Horizontal <30° · Vertical <30°
Code Reading
Standards
ISO 6346 · BIC · ISO Tank
Orientation
Horizontal and vertical
Line formats
Single- and double-line
Type recognition
ISO size and type codes (ISO 6346)
Hazardous logos
Not supported
Camera Requirements
Protocol
RTSP / RTSP-S
Codecs
H.264 · H.265 · MJPEG
Min. resolution
1280 × 960
Min. framerate
12fps
Reading distance
1–5m (resolution and lens dependent)
Hardware Requirements
Camera streams
Multiple concurrent RTSP streams — grouped into camera groups per lane, zone, or checkpoint. Capacity scales with GPU and hardware configuration.
OS
Windows 10/2016+ · Linux Ubuntu/Debian 20+
Processor
x86/x64 or ARM32/ARM64
GPU
Nvidia CUDA · AMD Radeon · Intel HD
RAM
Min. 8GB (16GB+ recommended)
Storage
Min. 500MB per camera (config. dependent)

Frequently Asked Questions — ConPDS Tracker

What is ConPDS Tracker and what does it do? ▲
ConPDS Tracker is on-premise shipping container OCR software. It connects simultaneously to multiple IP camera RTSP streams, uses deep-learning container code recognition to read ISO 6346, BIC, and ISO Tank container codes in real time, and publishes results as JSON via MQTT — per camera or per camera group. Any system that can subscribe to an MQTT topic can consume and act on that data: a DMS, TOS, WMS, a custom integration, or a direct database write. No management system dependency, no cloud requirement, no proprietary lock-in.
Does ConPDS Tracker require DepotMaster or any specific depot management system? ▲
No. ConPDS Tracker is completely independent of any depot management system. It publishes container code data in open JSON format via MQTT — any software that can subscribe to MQTT can integrate with it. If your facility runs DepotMaster and you want a fully automated gate solution with barriers and a driver kiosk, ConPDS Autogate is the pre-built integration designed for that scenario.
What camera hardware does ConPDS Tracker work with? ▲
ConPDS Tracker works with any IP camera that outputs an RTSP or RTSP-S stream using H.264, H.265, or HEVC encoding — minimum resolution 1280×960 at 12fps. Cameras from manufacturers including Axis, Hikvision, Bosch, and Vivotek are compatible under these requirements, as is any other vendor whose cameras support standard RTSP output. In most cases, existing on-site cameras are compatible without replacement. ConPDS provides onsite consultation on camera placement, angles, and configuration to ensure optimal read accuracy for your specific installation.
Who owns the data ConPDS Tracker produces? ▲
You do. ConPDS Tracker runs entirely on your hardware on your network — all OCR results, video frames, and movement records stay on your infrastructure. Nothing is sent to ConPDS cloud systems. You control data retention periods, access rights, and GDPR compliance for your installation.
What is the accuracy and speed of ConPDS Tracker's OCR? ▲
ConPDS Tracker achieves up to 99% container code recognition accuracy using the ConPDS Core OCR engine with motion detection and object detection. Processing time is as low as 100ms from frame capture to JSON result. Rear camera reads support vehicles moving up to 10kph; side camera reads support up to 7kph.
Can I build my own integration on top of ConPDS Tracker? ▲
Yes — that is the design intent. Every OCR result is published as standard JSON to an MQTT broker on topics per camera or camera group. Any MQTT client can subscribe and act on that data: trigger emails, write to a database directly, call a REST API, update your DMS, TOS, or WMS, or build a complete gate automation workflow. Integration is also available via REST APIs or direct database integration. For more complex scenarios — custom routing rules, automated alerts, or bespoke workflow logic — ConPDS's team can help design and build that as a separate engagement on top of Tracker's output data.
What is ConPDS Autogate and how does it relate to Tracker? ▲
ConPDS Autogate is a complete, turnkey automated gate solution built on top of ConPDS Tracker — it adds cameras, a driver-facing kiosk totem with QR scanner, a safety-interlocked barrier, a video intercom, and full DepotMaster integration. Tracker does the OCR and publishes the result; Autogate is the pre-built business logic layer that turns that result into a barrier decision and self-service driver interaction. Autogate is designed specifically for depots running DepotMaster.

Related Resources

ConPDS Autogate — Complete Gate Automation

The turnkey gate solution built on Tracker — cameras, kiosk totem, barrier, intercom, and DepotMaster integration for fully automated gate-in and gate-out. Designed for DepotMaster depots.

see how ConPDS Autogate turns Tracker into a complete gate solution →
Container Inspection Photo Documentation Platform

ConPDS Checker — the mobile field documentation app that links inspection photos to ISO 6346-validated container numbers. Works alongside Tracker to add visual evidence to movement records.

explore the ConPDS container inspection photo documentation platform →
Container Depot Photo Documentation Software

Gate-in, repair, lease return, and EIR photo documentation for depot operations — how ConPDS Checker structures inspection evidence across the full depot lifecycle.

learn how container depot photo documentation works →
How to Maintain an Audit Trail for Container Inspections

Timestamped OCR reads, gate events, and photo records — how a structured audit trail links every container movement to retrievable evidence.

read the container inspection audit trail guide →
Digital Documentation Standards in Modern Container Depots

How modern depots enforce ISO 6346 validation, structure photo evidence, and maintain compliance across gate, M&R, PTI, and lease return workflows.

explore digital documentation standards for container depots →

Start Reading Container Codes Automatically

Manual container code entry creates errors that compound downstream — wrong codes in your DMS, mismatched records, and no camera evidence when disputes arise. ConPDS Tracker eliminates manual entry at the source.

✗ Without Automated OCR
✗
Transcription errors enter your DMSA single transposed digit creates a mismatch that may not surface until a dispute is raised weeks later — with no camera record to correct it.
✗
Gate throughput capped by staffEvery movement requires a gate officer to read, type, and verify — throughput ceiling rises and falls with headcount, not container volume.
✗
No timestamped movement recordThe only evidence of a container movement is a manual log entry — which can be wrong, incomplete, or missing entirely.
✗
Data reaches systems late and incorrectlyManual entry introduces lag and transcription errors before data reaches your DMS, TOS, or WMS.
✓ With ConPDS Tracker
✓
OCR reads published at sourceContainer codes read directly from camera frames — no human transcription in the loop. Up to 99% accuracy, timestamped at the moment of capture.
✓
Gate throughput independent of headcountTracker processes every movement automatically — gate officer attention freed for exception handling, not data entry.
✓
Every read timestamped and camera-attributedContainer code, camera, camera group, and timestamp logged for every movement — unambiguous, unedited, retrievable.
✓
Structured JSON delivered in 100msResults published to MQTT immediately — any subscribed DMS, TOS, WMS, or custom system receives accurate data within 100ms of the read.

Two paths forward — pick the one that fits your operation:

Open Platform

Build Your Own Integration

Deploy Tracker, subscribe to the MQTT feed, and build exactly the business logic your facility needs — any DMS, any workflow, any size.

DepotMaster Depots

ConPDS Autogate — Ready to Deploy

Complete turnkey gate automation with kiosk, barrier, and DepotMaster integration — built on Tracker, delivered as one system.

Get the Full Gate Solution →
No obligations — reply within 1 business day