INDUSTRY // SUPPLY CHAIN & LOGISTICS
Logistics software know-how, stated honestly: industry background and strong adjacents, no logistics logo yet.
No Wavect logistics client yet, and this page will not pretend otherwise. The know-how is still first-hand: our managing director built WMS, TMS, freight-rate engines, and customs integrations at a supply chain and logistics software company before founding Wavect, and Wavect has shipped the hard substrate logistics software is made of: years of engineering inside a city-scale IoT sensor network, real-time geolocation that survives hostile mobile operating systems, and fulfilment automation that measurably cut delivery errors.
Book a thirty-minute call“Logistics software is IoT telemetry, real-time geo, and process automation under one roof. We have shipped all three. Just not yet under that roof.”
What we build in this industry
Asset & condition tracking systems
Sensor fleets, telemetry pipelines, and dashboards built on the same LoRaWAN and IoT engineering we spent four years on at city scale.
Driver & field mobile apps
Real-time location, offline tolerance, and background reliability on iOS and Android, the platform fight we have already won once.
Fulfilment & process automation
Finding the manual steps and recurring errors in an operation and engineering them away, measured against your error rate and throughput.
WMS, TMS & freight systems
Warehouse management, transport management, freight-rate engines, customs integration: our managing director built these systems before founding Wavect. First Wavect client build in this lane gets that knowledge plus senior engineering.
What makes this industry hard
Mobile OSes fight background tracking
iOS and Android kill background location to save battery. Logistics apps that need continuous tracking have to be engineered around the OS, with motion triggers, deferral, and graceful degradation.
Telemetry at fleet scale is its own discipline
A hundred trackers behave nothing like ten. Radio coverage, battery life, and data volume cross thresholds where the architecture has to change, and we have crossed them at city scale.
Integration debt rules the industry
Carriers, ERPs, scanners, and customs systems all speak different dialects. Most logistics software effort is integration engineering, which rewards senior generalists over framework specialists.
Where our experience actually comes from
Where this know-how actually comes from, named and checkable:
Industry background first. Kevin Riedl, our managing director, worked at a supply chain and logistics software company before founding Wavect, on the systems this industry actually runs on: WMS, TMS, freight-rate engines, customs integration. The domain vocabulary, the integration mess, and the operational reality of logistics software are first-hand, not researched for this page.
IKB is the Smart City build of Innsbruck’s municipal utility, where we spent four years on the LoRaWAN infrastructure, multi-vendor device integration, and per-device codecs. Tracking assets and conditions across a supply chain is the same engineering class: constrained radio, battery budgets, device fleets at scale, multi-vendor integration.
Offlinery required continuous, accurate location from locked phones while iOS and Android actively killed the background processes. Fleet tracking, driver apps, and proof-of-delivery face the exact same OS hostility.
MyMerch was fulfilment-process automation on a live commerce operation: delivery errors reduced, roughly 50% efficiency gain reported by the client. Small-scale logistics, by any honest definition, inside an e-commerce engagement.
The honest gap: Wavect as a company has not shipped a WMS, TMS, freight-rate engine, or customs integration for a client yet. Kevin built exactly these systems before Wavect, so the domain knowledge is in the room; the Wavect client reference is the part that is still missing.
Adjacent work, honestly labeled
Adjacent work, not logistics clients. These are the projects the claims above come from.
