Flower Freight’s scanner upgrade is aimed at retail-grade capture: fast 1D and 2D recognition, repeated scans, duplicate suppression, snapshot fallback, and a clean handoff from the decoded identifier to the transport verification API.
Decoding and verification are different layers
The scanner’s job is to capture an identifier accurately. The verification API’s job is to decide whether that identifier belongs on this load and satisfies the required checks.
Keeping those concerns separate allows the capture engine to improve without rewriting the Metrc or transport logic.
Support the labels operators actually encounter
Warehouse environments include Code 128, QR codes, damaged labels, glare, small print, and varying camera distances. A production scanner needs to handle more than one ideal sample.
Flower Freight’s evaluation favored the capture engine that performed better on both barcode and QR examples during real device testing.
Re-arm is a core requirement
A scanner that works once and stalls is not operational. Continuous warehouse scanning needs immediate readiness for the next package while preventing accidental duplicate counts.
That is why scan state, duplicate suppression, and camera lifecycle deserve the same attention as raw decode accuracy.
Fallback should stay in the same workflow
Snap & Read or manual entry should be recovery paths inside the same verification experience. They should not send the worker to a different app or bypass the manifest checks.
The goal is resilient capture, not alternative truth.
Frequently asked questions
Does reading a QR code automatically verify a package?
No. Decoding only produces the value; the verification layer still checks it against the correct transport context.
Why keep Snap & Read if live scanning is strong?
Camera focus, damaged labels, glare, and device differences make a still-image fallback useful in real warehouse conditions.
Should scanning call AeroPay?
No. Scanning should feed transport verification. Payment actions belong at their defined booking/delivery workflow boundaries, not inside the barcode decoder.
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.