From stamps to systems: reconciling track-and-trace with plant dispatch

02

Three records that should agree

Every dispatch from a regulated plant now leaves three trails:

• The code record: stamps or identifiers issued, applied, damaged and activated, and the counts reported from the packing line.
• The physical record: weighbridge tickets, gate passes, vehicle numbers, loading-bay counts and timestamps.
• The commercial record: sales orders, delivery notes and invoices in the ERP, plus e-invoices where these are required.

03

Where the numbers drift

In most plants these records sit in different systems run by different teams: packing, security, the weighbridge office, sales and finance. They are reconciled, if at all, in spreadsheets at month end. By then the truck is long gone, the shift has changed and the explanation is a guess.

Differences arise for many reasons, and most of them are not fraud:

• Stamps applied by hand when applicators fail, without the count reaching the system.
• Damaged or rejected codes, rework and re-bagging.
• Bags loaded onto the wrong vehicle, or partial loads and split deliveries recorded against one order.
• Repeated weighing, incorrect tare weights or vehicles not fully on the weighbridge platform.
• Time lags between packing, loading and invoicing that move units across shift or day boundaries.
• Returns and transfers between plants and warehouses that follow a different paperwork path.

04

Gate and weighbridge vision

Process noise still matters because, without evidence, an auditor or a regulator cannot tell it apart from leakage. The aim is to make every dispatched unit explainable, and cameras at the gate and weighbridge are a practical, low-disruption way to create that evidence.

Processing runs on edge hardware at the site, so the system keeps working on weak connectivity and only events and evidence travel to the central system. A useful vision layer does a few specific jobs well:

• Reads number plates to bind each vehicle to its weighbridge ticket and gate pass.
• Checks that the vehicle is fully on the platform and that nothing interferes during weighing.
• Counts bags or units on loading lines and conveyors, independently of the packing counters.
• Checks samples for the presence and readability of stamps or codes.
• Stores time-stamped images with each transaction, so every exception comes with evidence.

05

Reconciling with the ERP

Vision on its own produces more data, not fewer problems. The value comes from reconciliation: a common event model that links code counts, gate and weighbridge events and ERP documents by vehicle, time, order and delivery note.

With that model in place, a reconciliation engine matches records per vehicle, per order and per shift, applies tolerances agreed with the compliance and finance teams, and flags anything outside them the same day rather than at month end.

Integration should start read-only, using extracts or APIs from the ERP and weighbridge software. Interfaces to the authority's own devices and systems may be closed or controlled by a licensed operator. That is not a blocker. Start with the weighbridge, gate and ERP data the plant owns, add code-system data when access is available, and never modify regulated equipment.

06

Exception handling is the product

A dashboard that shows a mismatch is not a control. A control needs an exception workflow: each mismatch is raised with its evidence, assigned to an owner, given a reason code and closed with a recorded resolution. Over time the reason codes show where the process breaks, so it can be fixed at the source, and the history forms an audit trail.

Typical exception types include:

• A vehicle left the gate with no matching invoice, or an invoice has no matching gate exit.
• Bag or unit counts at loading differ from the code count beyond tolerance.
• A weighbridge ticket's net weight is inconsistent with the invoiced quantity.
• The same vehicle was weighed more than once within a short window.
• Codes were activated but no corresponding dispatch was recorded.

07

A pilot at one gate

A reconciliation pilot usually covers one gate or weighbridge at one plant and runs for 8 to 12 weeks. The first two weeks map the real process, not the documented one, and secure data access. Cameras and integrations follow, then several weeks of live running to tune tolerances and exception rules with the people who will use them.

In seasonal industries such as sugar, timing matters: the data only exists while the plant is operating, so a pilot should be planned to start early in the season. Agree success measures up front:

• The share of dispatches reconciled automatically across the code, physical and commercial records.
• The number of exceptions detected and confirmed by the plant team.
• The time taken to investigate and close an exception.
• The effort needed to prepare compliance and audit reports.

08

What this does and does not replace

A reconciliation layer does not replace the authority's track-and-trace system, the stamp applicators or the ERP. It makes the plant's own records consistent with them and gives management early warning when they diverge. Any design should be agreed with your compliance team and, where relevant, with the licensed operator of the regulated equipment.

Our gate, weighbridge and compliance vision solution follows this pattern. Where delivery notes and invoices still arrive on paper, intelligent document processing closes the gap between the physical and commercial records.