Skip to content
SVHSoftware

Industries / Logistics devices

Devices that move, managed as if they never left the depot

For makers of scanners, handhelds, vehicle units and depot equipment. Devices that are offline for hours still get their identity verified, their updates applied and their data delivered, in order, when they reconnect. Your customer sees the whole fleet in one console, in your brand.

Check my device Book a demo

A fleet console in the device maker's brand: devices online, an update rolling out in waves and a live heartbeat.

How your devices connect

Two ways in, one fleet. Devices that can run the agent do; everything else connects through the bridge.

SVH Device Agent

Rugged handhelds, vehicle units and terminals on embedded Linux run the SVH Device Agent beside your application.

Hardware-rooted identity, an offline queue, signed updates and a sandbox for your application.

SVH Device Bridge

Depot equipment and devices on closed site networks connect through the SVH Device Bridge, over MQTT today or a custom adapter scoped with you.

No firmware change. The bridge carries their data to the Fleet Server over mutual TLS.

What your customer sees

A console in your brand, on their premises or in your cloud.

  • Every device by customer, depot and route, with last-seen and battery state
  • Scan and event data delivered reliably, even after a long offline shift
  • Updates scheduled for the depot, not the middle of a route
  • Settings inherited from the customer down to one device

What their systems receive

Signed webhooks and documented REST APIs, so device data lands where they already work.

WMS and TMS
Scan events and status changes, in order, as signed webhooks
ERP and billing
Device counts, usage and service events per customer
Your own apps
Documented REST APIs for the whole fleet

What it solves for logistics devices

Three problems every device maker in this industry runs into, and how the platform handles them.

Devices offline for a whole shift

The agent stores events durably and delivers them in order when the device reconnects. Nothing is lost or duplicated.

Updating thousands of handhelds

Rollouts go in waves by depot or customer, pause on failures and roll back on their own. Devices update when docked.

One product, many customers

Each customer's installation runs separately, with its own settings, users and data. Your brand is on every screen.

Questions logistics device makers ask

What happens to scans captured while offline?

They are encrypted and stored on the device, then delivered over mutual TLS in the original order once the device reconnects, and acknowledged end to end.

Can updates wait until a device is docked?

Yes. Rollouts are scheduled per group, and a device applies its update when it meets the conditions you set, with a rollback if it fails.

Can each customer run their own installation?

Yes. One Fleet Server per customer site, on their premises, in your cloud or hosted by SVH, with the same console in your brand.

Making something else? The Connected devices page covers every device the platform runs.

Can SVH connect your devices?

Answer six short questions. Within two business days we reply with the path for your device. Then we book a demo with your engineers.

Tell us about your device.

Check my device

Prefer to talk first? Book a demo