Container gate automation: OCR at the depot gate

Every shipping container carries an ISO 6346 code — four letters, six digits, and one more digit that most people never think about. That last digit is a checksum, computed from the other ten characters. It exists because container numbers get mis-read and mis-keyed constantly, and it is the single most useful fact in gate automation.

The check digit is your quality gate

When a gate camera OCRs "MSKU 830421" and proposes check digit 7, the mathematics either agrees or it does not. A failed check means a bad read — wrong character, mud on the door, glare — and the system can retry or flag the lane instead of writing a wrong number into your yard system. Manual clerking has no equivalent safety net: a clerk's typo travels downstream until it becomes a dispute with a shipping line.

What the gate cycle actually contains

A properly built CNR lane does five things in a few seconds: reads the container code (often front and rear), validates the checksum, matches the number against expected movements — a gate-in booking, a delivery order — decides, and actuates: barrier, lane light, driver display. Then the part that pays for everything: the movement lands in the yard system or ERP in real time, with photos attached.

Malaysian-weather engineering notes

Depot gates run at dawn, at dusk, and in monsoon rain. Camera positioning must handle low sun angles down the lane; housings must survive heat and water; lighting must lift the container door without blinding drivers. This is why we treat CNR as an engineering exercise with a survey, not a product in a box.

When you don't need CNR

A yard handling a handful of boxes a week can live with a clipboard. CNR pays when trucks queue, when demurrage arguments cost real money, or when your customers ask for gate-time evidence. Start from the dispute file, not the technology.

See the animated gate walkthrough on our CNR capability page.