In a busy delivery station, small equipment lives a hard life. Tape guns get set down and buried under parcels. Scanners get dropped, kicked and occasionally leave the building in the wrong van. Each loss is a small cost that multiplies across shifts, stations and a continent-wide network — in replacement hardware, in downtime, and in the minutes staff spend hunting for shared kit.
That was the problem a major international logistics operator brought to us: keep tape guns and scanners physically attached to workstations and people, without getting in the way of hundreds of repetitive movements per shift.
Why coiled kevlar was the answer
• Reach without slack — a coiled lanyard extends for the task, then recoils out of the way. There’s no loose cable to tangle in rollers or catch on parcels.
• Survives industrial use — braided kevlar cores shrug off the abrasion and repeated stretch cycles that crack plastic-coated cables within weeks in this environment.
• Fits existing equipment — the right end fittings clip to tape guns, scanner holsters and belt loops without modification.
The rollout
The first batch went into live delivery stations as a working trial: standard KOILED lanyards on tape guns at packing and dispatch points. The result was simple — secured tools stopped going missing — and the programme is now expanding, including a custom extended-stretch variant we’re developing so shared equipment can serve a wider workstation area from a single anchor point.
What any operation can copy
You don’t need a global network to have this problem. If your team shares tools, scanners or keys across a workspace, the same three decisions apply: anchor point (belt, workstation or both), stretch length (enough reach for the task, no more — see our lanyard length guide), and fitting (match the clip to the equipment, not the other way round).
We supply volume orders with custom lengths and fittings, and we’ll confirm feasibility with our manufacturer before you commit. Start with our wholesale & bulk orders page, or contact us with your use case.