Skip to content
Treblesys

Logistics & Supply Chain

Dispatch, tracking and warehouse tools for a 24/7 operation.

We build the systems that sit between your planners, drivers, warehouses and customers. Most of the time that means replacing phone calls and spreadsheets with software that shows where things are right now, which sounds simple and rarely is.

Discuss your projectSee related work

Constraints we build around

  • Offline-first mobile apps, because drivers and warehouse staff lose signal
  • Telematics, GPS and scan data arriving in real time and at volume
  • EDI and legacy file formats alongside modern APIs
  • 24/7 operations, which means zero-downtime deployments and rehearsed cut-overs
  • Customer SLAs and audit trails for proof of delivery
A container ship being loaded at a port

What we hear

What people in this sector tell us on a first call.

  1. 01

    Visibility gaps between systems

    The TMS, the WMS, the ERP and each carrier's portal hold part of the picture. Planners reconcile them by hand, and customers ring to ask where their order is.

  2. 02

    Manual dispatch and re-planning

    Routes are built in the morning and broken by lunchtime. Re-planning happens on the phone, and the knowledge of how to do it lives in a few experienced heads.

  3. 03

    Ageing core systems

    Dispatch or warehouse software that is decades old and nobody dares touch. Every new process has to be built around it instead.

  4. 04

    Margin pressure

    Fuel, labour and customer expectations all move against you, so any gain has to come from shaving minutes and miles off thousands of individual movements.

What we build

The kinds of systems this sector tends to need.

  • Dispatch and route planning platforms

    Web-based planning boards with live vehicle positions and constraints, drag-and-drop re-planning, and driver apps that push status back in real time.

  • Shipment tracking and customer portals

    Self-service tracking, proof of delivery, document access and notifications, so customers stop ringing the office to ask.

  • Warehouse and yard tools

    Receiving, put-away, picking and yard management on rugged handhelds, either integrated with your WMS or replacing the parts of it that don't fit how you work.

  • Carrier and partner integrations

    EDI, API and file-based integrations with carriers, 3PLs, customs and marketplaces. Each one is monitored, and a rejected or missing message lands in a queue where someone can fix it and resend it the same morning.

  • Modernising legacy dispatch systems

    Replacing legacy operational systems a piece at a time while the operation carries on running. See our legacy modernisation service for how we go about it.

  • Operational analytics

    On-time performance, cost per delivery, utilisation and exception dashboards, with every figure traceable to the TMS or WMS record it came from.

Related work

A project from this sector.

All case studies
Logistics & Supply ChainSample

Replacing a 15-year-old dispatch system without stopping the trucks

A regional carrier running 180 vehicles depended on a desktop dispatch system built in 2009. Planning was done by hand and driver updates came in by phone. The vendor had stopped supporting the product. We replaced it with a web planning board and a driver app, one workflow at a time, while the operation kept running.

hours of operational downtime during cut-over
0
hours of operational downtime during cut-over
fewer inbound 'where is my delivery' calls
38%
fewer inbound 'where is my delivery' calls
saved per planner, per day
2.5 hrs
saved per planner, per day
Read the case study
Aerial view of lorries parked in neat rows at a distribution depot

Questions

Questions that come up before a first project.

Ask us directly
Can you integrate with our existing TMS or WMS?

Yes. Most of the logistics work we do sits alongside an existing TMS, WMS or ERP. We connect through APIs, EDI or file exchange, whichever the system supports, and put monitoring around every integration, since the older ones tend to fail without saying so.

How do you handle systems that can't go offline?

That constraint shapes the design early on, with incremental roll-outs, parallel running, feature flags and a cut-over plan we've run through in advance. Operational software gets replaced piece by piece, and each piece runs alongside the old one until you're happy to switch it off.

Do you build driver and warehouse mobile apps?

We do. Usually offline-capable apps for iOS, Android and rugged devices, with barcode scanning, signature capture, photos and background sync for when the signal comes back.

Relevant services

Other industries