Logistics and distribution

Logistics software development

We build tracking, warehouse and driver systems for carriers, freight forwarders and distributors. Parcels get delayed in every network. What hurts is when the depot only hears about it from an annoyed customer on the phone, so we build systems that tell your team first.

A busy container port seen from above

Tracking that keeps working without signal

Tracking, warehouse and driver systems for carriers, freight forwarders and distributors.

Systems we build

  • Shipment trackingOne record per consignment, always visible
  • Warehouse managementReceiving, picking and dispatch on handhelds
  • Route planningDrops ordered by time and capacity
  • Driver appsWorks offline, syncs when signal returns
  • Customer tracking pagesA link showing the real status
  • Partner and carrier linksConnected to the carriers you use
Discuss your logistics project
  • Reply within one business day
  • You own all code and designs
Depot, road and doorstep

Logistics software from depot to door

Shipment tracking

Each consignment gets one record that updates as it moves. The depot, the driver and the customer all look at the same one.

Warehouse management

Your warehouse team receives, shelves, picks and dispatches stock on a handheld scanner, and the clipboard goes in a drawer.

Route planning

Drops put in order by drive time, van capacity and delivery windows, and replanned when a road closes or a driver calls in sick.

Driver apps

Job lists, directions and proof of delivery that keep working in a tunnel or a basement car park, then sync once there's signal again.

Customer tracking pages

A link the recipient can open without signing up, showing where the parcel really is, based on the latest scan.

Partner and carrier links

Electronic data interchange (EDI) and API links to the partners who carry the freight for part of the way.

What makes logistics software harder

A shipment usually passes through several companies, and each one runs its own system. Every handover is a chance to lose sight of it. So our first job is nearly always to create one consignment record that follows the goods from collection to delivery.

Mobile signal is the other big factor. Drivers spend their day on country roads, in loading bays and in tower block stairwells, and an app that needs a live connection will let them down. Ours work offline and catch up later without creating duplicate records.

Delivery, customs and driver law

Rules every shipment has to follow

  • Proof of delivery. We store the signature, photo and time with the consignment, and keep them as long as your contracts require.
  • Driver working time. Hours and rest breaks are recorded accurately. This record carries legal weight, so it has to be right.
  • Customs paperwork. For goods crossing a border, the system fills in customs documents from the shipment data, so nobody types it all again.
  • Address privacy. Recipient addresses and phone numbers count as personal data, so only the people working on that delivery can see them.
  • Dangerous goods. Where they apply, the classification and paperwork travel with the consignment, and the driver sees them on the app.

Systems we usually connect to

Telematics and vehicle trackingCarrier and partner networksCustoms and border systemsWarehouse hardware and scannersAccounting and invoicing systemsCustomer notification channels

Most operators already run a warehouse system, fleet telematics (the trackers fitted to your vehicles) and a few carrier connections. We plug into those first and fill the gaps between them. If one still moves freight reliably, replacing it is your operations team's call, and a project should never force it on you. If your drivers need a new app, our guide to native or cross platform apps helps you choose how to build it.

Logistics project stages

Rolling out across your network

  1. Follow one consignment

    We trace a single shipment across every system it touches and mark each point where its status stops updating.

    Week 1 to 2
  2. Agree one consignment record

    We agree one reference number and one set of status names that every system uses.

    Week 2 to 4
  3. Build depot and driver together

    We build the office screens and the driver app side by side. If one of them is wrong, both are, so they're tested together.

    Week 4 to 13
  4. Pilot on one lane

    Real drivers use it on one route for a few weeks. Once it works there, the rest of your network follows.

    Week 13 onward

The weeks above are the usual range. Bringing each carrier or partner integration on board, getting test devices to your drivers and working around your busiest shipping weeks are what most often change them. See every stage of our delivery process for the detail.

For depots, drivers and recipients

Earlier warnings and cleaner proof

Delays surface earlier

When a parcel misses a scan, your team gets an alert while there's still time to fix it.

Fewer where is my order calls

When recipients trust the tracking page, far fewer of them pick up the phone to ask.

Cleaner proof

The signature and photo attach to the consignment the moment the driver captures them, so nobody has to chase them later.

Logistics questions

Your driver app and warehouse questions

Yes. The app downloads the day's jobs in advance, records work on the phone and syncs when the connection comes back. We test this on purpose, including the awkward case where a driver marks the same job done twice.

Usually. Most carriers offer an API or EDI, and we build a connector for each one. If a partner offers neither, we fall back to swapping files on a schedule.

Often you don't. If it keeps an accurate count of your stock, we connect to it and add what it's missing, such as a driver app or a customer tracking page.

Show us where shipments go dark

Tell us where you lose sight of your freight, and we'll share how we'd close the gap.