Automatic Container
Code Recognition

Usage Context and Data Preparation

Container codes contain an owner code, equipment category, serial number and check digit as described in the existing features. Reading the code and validating its check digit address different checks. A valid format does not necessarily mean the container matches the intended shipment.

Prepare images from the actual crane, gate or forklift camera positions, together with sample codes and TOS/WMS reference records. Define what counts as one transaction and how images, times and positions are reviewed when searching for a record or correcting an incomplete code.

ISO 6346 describes container-code structure and supports format checking; mentioning it does not certify this product. Preserve the complete required characters and distinguish the identifier from surrounding text such as weights and other markings on the container wall.

Check digits detect some error patterns, not every OCR error or a match to shipment records. Compare reference records and actual events. Failed or incomplete codes need review; do not alter characters merely to satisfy a checksum without image evidence.

Site images may contain rust, paint damage, vertical text and structural obstructions. Select views from the actual handling sequence. Multiple views must be associated with the same container, not neighboring containers or separate transactions occurring close in time.

TOS/WMS integration needs transaction identity, reading point, time and review ownership. One container appears at several workflow stages, so its code alone cannot deduplicate events. Human corrections should preserve original readings and reasons within the agreed traceability scope.

Evaluate complete-code accuracy and transaction association. Distinguish incomplete visibility from recognition errors, and group results by angle, character condition and layout. Valid format alone is insufficient because a correct-looking code can still be attached to the wrong transaction.

Multiple-side reading, shipment verification and evidence-review workflows require proposal confirmation and trials with actual systems. Container-code reading does not establish internal contents, seal integrity or customs status; those conclusions need separate evidence and responsible procedures.