Logistics & supply chain

Software Development for Logistics and Supply Chain

Peregrine builds software for logistics operators, 3PLs and freight brokerages: live fleet tracking with driver apps and customer ETA alerts, and shipment visibility platforms that normalize tracking data from many carrier APIs into one view.

The two published case studies below cover both sides of that work: a GPS fleet management system for 500+ vehicles, and a visibility platform tracking 2M+ shipments across 12 carriers.

Fit

Is Custom Logistics & Supply Chain Software the Right Fit?

A good fit when

  • Customer service spends its day answering "where is my shipment?" from carrier portals or phone calls to drivers.
  • You work with many carriers or telematics vendors and need one view across them.
  • Drivers work where coverage is unreliable, and paper or messaging apps are the system of record.
  • Your customers ask for a tracking portal or an API under your brand.

Probably not the right fit when

  • You use one or two carriers whose own tracking pages already meet your customers' needs.
  • A commercial TMS or telematics product covers your fleet and carriers, and the gap is configuration or training.
  • You need the hardware itself. Trackers and in-cab devices come from their vendors; this is the software around them.
What we build

What Logistics & Supply Chain Software Includes

Carrier integration layer

One adapter per carrier behind a canonical tracking-event schema, with webhook and polling ingestion, deduplication and a retry queue. The visibility platform in our case study normalizes 12 carrier APIs this way.

Shown in: Supply Chain Visibility for Shipment Tracking & Alerts

Shipper portals and exception alerts

A portal where each shipper sees only its own shipments, with alerts for delays, damage and customs holds. The case study reports 45% fewer customer inquiries.

Shown in: Supply Chain Visibility for Shipment Tracking & Alerts

Live fleet tracking

GPS data streamed from vehicle devices over MQTT, with geofencing, speed alerts and route-deviation detection. Our fleet case study covers 500+ vehicles, with devices from three OBD vendors behind one abstraction layer.

Shown in: Real-Time Fleet Tracking Platform for a Regional Logistics Company

Driver apps that work offline

A React Native driver app that queues delivery confirmations, GPS pings and proof-of-delivery photos on the device and syncs when coverage returns.

Shown in: Real-Time Fleet Tracking Platform for a Regional Logistics Company

Route optimization and ETAs

Route planning that accounts for traffic, vehicle capacity, delivery windows and driver hours, and ETA prediction from historical lane data.

Shown in: Real-Time Fleet Tracking Platform for a Regional Logistics Company; Supply Chain Visibility for Shipment Tracking & Alerts

Scope

What Determines the Scope of Logistics & Supply Chain Software?

These are the inputs that change the effort. None needs a final answer before the first call, but each one you can answer makes the estimate tighter.

Carriers and devices
The number of carriers or telematics vendors, and whether each offers an API, webhooks or only a web portal.
Event volume
Shipments or vehicles tracked, and how often each reports. A position every few seconds is a different storage problem from a few scans per shipment.
Customers and tenancy
Whether shippers log in, how many, and how strictly their data has to be separated.
Offline operation
What drivers must be able to do with no signal, and for how long.
Routing rules
The constraints a route has to respect: capacity, delivery windows, driver hours, vehicle types.
ETAs and alerts
Whether carrier ETAs are enough or you need your own prediction, which depends on having delivery history to learn from.
Regions
Countries of operation, languages, and how good mapping data is in each.
Systems of record
The TMS, WMS, ERP or order system that shipments come from and results return to.

A sensible first phase

A sensible first phase connects two or three carriers, or one device type, end to end and puts the result in front of a small group of real users. Both of our logistics case studies began with discovery in the field: documenting each carrier API in one, riding along with drivers in the other.

What to bring to the scoping call

  • Your carriers or telematics vendors, with the share of volume each handles.
  • Shipments per month, or vehicles and drivers on the road.
  • How tracking questions are answered today, and roughly how many arrive.
  • The systems orders and shipments originate in.
  • A sample of tracking data or a device export.
  • For driver apps: the devices drivers carry and where coverage fails.

Partial answers are fine. Whatever is missing becomes the first item on the call.

Book a discovery call or send a project enquiry

Technical consultation

Building Logistics or Visibility Software?

Tell us which carriers, vehicles or systems you need to connect. An engineer will tell you how we would design the data model and the integration layer.

  • A 30-minute technical discovery call with an engineer, not a salesperson.
  • Fixed-scope projects, monthly retainers, or a combination, agreed after the call.
  • Small, well-defined tasks get a scoped estimate. We reply within 1 business day.

Prefer to pick a time? Book a call on Calendly

Tell us about your project

We'll review your details and reach out within 1 business day.

Book Strategy CallCase Studies