On a parcel dock, the label is the truth: if the sorting code is wrong, the parcel goes to the wrong place and everyone loses. Labelly was born from a simple request: “I scan, it prints, and it is right”.
The flow
The operator imports the day’s transport file. The handler scans the barcode — with a gun, a phone or an Android terminal — and the label comes out immediately, compliant with the carrier’s template: sorting code and bay band at the bottom, clearly visible.
The belt printer
The real gain is mobility: a Zebra worn on the belt, driven from the phone’s browser thanks to Zebra Browser Print. No more walking back to the desk. A networked printer (configurable IP) remains possible for fixed stations.
Routing
Every carrier has its routing table. On the first network deployed, the file holds 650,000 rules: we import it into the database, index it, and re-import it with one command when the network changes. It is the invisible part that makes the label right.
Why it works for any carrier
- The label template (dimensions, zones, barcodes) is a setting: one file per carrier.
- The routing table is imported as the carrier provides it; only the column mapping changes.
- Native ZPL generation, no images: crisp at 203 dpi, fast, on any Zebra.
- Google sign-in open to everyone, but each account is approved by an administrator before it can print.
Next
Field tests under way on the first network; adding a carrier boils down to loading its template and routing file. The page in the members area.