A robust dock workflow scans the physical packages being loaded, compares them with the package set expected for the bound Metrc transfer, blocks mismatches, and only allows driver custody after the load verifies.
Bind first, scan second
Package scanning is only meaningful when the system already knows which transfer and load are being verified. Otherwise, a successful barcode read proves only that the camera decoded something.
Flower Freight’s verification API is designed to compare the package identifier against the package list for the specific bound transport.
Warehouse scans; driver accepts custody
The shipper or warehouse team controls loading, so package scanning belongs with that team. The driver should not be asked to repeat warehouse verification from inside the vehicle.
Once the scan set matches, the driver can accept custody of a load that has already passed the departure gate.
Mismatches should fail closed
If the system cannot load the expected package list, it should not silently approve any scanned code. If the scanned package is not on the manifest, that should be visible and actionable.
Failing closed protects the integrity of the record. A green check should mean something.
High-speed scanning still needs workflow discipline
A retail-grade scanner should read Code 128, QR and other common symbologies quickly, re-arm immediately, suppress accidental duplicates, and preserve manual or snapshot fallback when the camera struggles.
But scanning speed is only useful if every accepted identifier flows into the correct transport verification logic.
Frequently asked questions
Should the scanner approve any 24-character string?
No. Format recognition is not the same as manifest verification. The identifier still has to be checked against the expected transport context.
Why not let the driver scan?
Flower Freight’s operating model keeps loading verification with the shipper/warehouse team and gives the driver custody after verification.
What happens if the package list is unavailable?
The safer workflow is to fail closed and explain that the load cannot be verified rather than create a false successful record.
Run the 10-minute transport audit.
Test what your operation can actually produce today: vehicle, driver, GPS, package, custody, receiving and historical transport evidence. No signup required to see your score.