ScrapVerify Vehicle Traceability

YKK India · Plant 1 & Plant 2

The vehicle that was weighed is the vehicle that arrives.

A one-time encrypted barcode is bonded to the vehicle at the tare weigh and checked at every gate it passes. The chassis number travels sealed inside the code, so a cloned number plate proves nothing and a sticker moved to another vehicle is refused on sight.

Why this exists

A weighbridge measures a vehicle, not an identity.

A vendor weighed an empty vehicle at Plant 1, drove out, and presented a different one at Plant 2 — same colour, same plate. The second vehicle was heavier. The difference was billed as material that never existed.

Nothing in the process was wrong on paper. Both weighbridges worked. The gap was that no unique, tamper-evident identity was tied to the physical vehicle after the tare weigh, and a number plate can be copied in an afternoon.

Weighed at Plant 1

8,240 kg

Tare recorded. Vehicle departs.

in transit →

Presented at Plant 2

8,820 kg

A different vehicle wearing the same plate.

580 kg of phantom material per trip — roughly ₹9,000 a run, invoiced against a weighbridge slip that was itself accurate.

How a trip is checked

Four checks, in order, and the vehicle stops at any of them.

01

Bonded at the tare weigh

The guard reads the chassis number off the vehicle itself. It is sealed into the barcode together with the plate, vendor, driver and tare weight, encrypted with AES-256-GCM and signed. The sticker is printed on void-security stock: lifting it destroys it.

02

Read at the gate, before entry

The scanner asks the guard to type the chassis number they can physically see before it shows what the barcode claims. A guard shown the expected answer first would only ever confirm it — this is the check that actually catches a swapped vehicle.

03

Weighed, and the net is computed

Net weight is derived from the tare sealed inside the barcode, never typed. A net outside tolerance flags the trip and holds it for a supervisor rather than flowing into a challan.

04

Closed, and the code dies

The exit scan closes the trip and invalidates the token. It expires four hours after issue in any case, and a third scan is refused outright. Every scan, photograph, GPS fix and supervisor decision stays on the record.

What a gate refuses

Each of these stops the vehicle and raises an alert.

Chassis mismatch

The barcode names one vehicle and the guard is standing in front of another.

Barcode reused

A code already scanned in and out, presented again on a later trip.

Expired

Transit took longer than the window allows. Held, not waved through.

Altered or unreadable

A reprinted, edited or torn code fails its signature and is refused.

No sticker

A vehicle arriving without one is photographed and referred to a supervisor.

Weight anomaly

Net more than 10% off the expected range flags before any challan is raised.

Ways in

Two consoles, and a certificate check that lives elsewhere.

ScrapVerify

Vehicle traceability for scrap movements between plants. Every trip carries a single-use encrypted identity from the tare weigh to the closing scan.

ScrapVerify · vehicle traceability · part of the ScrapCart platform

Certificates are issued and verified on ScrapAssure.

Every scan and decision is recorded against the person who made it.