Drivers lose signal
Routes run through mountain passes, loading bays and rural highways where coverage drops. An app that needs a live connection to record a delivery costs the driver time and costs you the proof of delivery.
Industries · Transportation & Logistics
Software for transportation and logistics operators
Freight moves whether or not the software works. We build dispatch boards, driver apps that hold up without signal, tracking your customers can read, and the integrations that keep your TMS, EDI partners and telematics in step.
You own the code and IP Weekly demos Reply within one business day
Agent running - queue empty
Flow 04
01
Trigger
Webhook
02
Enrich
Normalise
03
Decide
Policy
04
Act
Resolve
Run log
> Matched 42 records
> Routed 7 exceptions to a human
> Closed 35 tickets automatically
35
Auto-resolved today
6h
Engineer time saved daily
Transportation & Logistics, in short
OlDevs is a full-stack technology studio in Vancouver, British Columbia that builds software for carriers, freight brokers, couriers and third-party logistics providers.The work covers dispatch systems, driver apps with offline capability, load tracking and proof of delivery, customer portals, and integrations with TMS platforms, EDI partners and telematics feeds. Every project runs with one accountable team and a working demo every week, and clients own all code, designs, accounts and IP. Request a quote to talk through your operation.
Key facts
- 01term
- value
- 02term
- value
- 03term
- value
- 04term
- value
- 05term
- value
- 06term
- value
Transportation & Logistics
What transportation and logistics operators bring us
The problems we are asked to solve most often — and how.
Proof of delivery gets disputed
Signatures on paper, photos on a personal phone and pallet counts written on a bill of lading are hard to find weeks later. When a claim lands, the evidence needs to sit against the shipment and be easy to pull.
Customers phone in for status
Shippers and consignees call dispatch because they cannot see where their freight is. Every call pulls a dispatcher off planning, and the answer is often a guess based on the last check call.
EDI and TMS integrations drift
Tender, status and invoice messages move between brokers, carriers and shippers in formats that vary by partner. One mapping change breaks acknowledgements quietly, and nobody notices until settlement.
Planning lives in spreadsheets
Loads, driver hours, trailer availability and appointment windows sit in separate files and in one person's head. Capacity calls get made fast, but they cannot be audited, repeated or handed over when that person is away.
Driver recruitment is a bidding war
Job boards send the same applicants to every carrier, and the application form loses them halfway through. Recruitment needs a fast mobile path from ad to qualified applicant, with follow up that does not depend on one recruiter.
Process
How a transportation project runs with OlDevs
Discovery
We ride along with the operation: dispatch, drivers, settlement and customer service. We map the current systems, the partner integrations and the points where paper or phone calls fill a gap, then agree what the first release has to do.
Design and plan
Screens are designed for gloved hands, cab mounts and a dispatcher watching many loads at once. We write integration specifications, agree data handling, and set a release plan that puts the highest cost problem first.
Build with weekly demos
One accountable team builds in short cycles with a working demo every week, on real freight data where possible, so your dispatchers can react before decisions are expensive to reverse.
Integrate and pilot
We connect the TMS, EDI partners, telematics and accounting systems, test against live partner messages, then pilot with a small group of drivers and one lane or terminal before anyone else is affected.
Rollout and support
Rollout is staged by terminal or fleet with training built for drivers, not developers. After launch we monitor sync health, integration acknowledgements and errors, and keep improving on an agreed cadence.
How we work
How we work with carriers, brokers and 3PLs
01
We start in the dispatch office
Before anything is designed we sit with dispatchers, drivers and the settlement team, watch a full day of loads move, and write down where the process actually breaks. The build follows that, not a generic logistics template.
02
Offline is a requirement, not an option
Driver apps are built to work with no connection at all: local storage first, background sync, clear conflict rules and a visible sync state so the driver knows what has landed and what has not.
03
Proof of delivery built for disputes
Signatures, photos, notes, timestamps, geolocation and piece counts are captured against the shipment and stored so anyone in the office can retrieve the full record months later in a few seconds.
04
Integrations with contracts and monitoring
Every TMS, EDI, ELD, telematics, accounting and fuel card connection gets a written specification, test cases against real partner data, and alerting so a failed acknowledgement or stalled feed is caught the same day.
05
Portals that take calls off dispatch
Shipper and consignee portals show live status, documents, appointment windows and history, with self serve booking where it helps. Built to WCAG 2.2 AA and available in English and French where you need both.
06
Recruitment marketing that respects the funnel
For driver hiring we treat the ad, landing page, application form and follow up as one path, connect it to your applicant tracking system, and report on qualified applicants instead of traffic.
Since 2014
Building operational software
Weekly
Working demo every cycle
EN and FR
Bilingual interfaces delivered
FAQ
Transportation & Logistics — questions we hear first.
Yes. We treat offline as the normal state for a driver app. Scans, signatures, photos, arrival and departure times and status changes are written to the device first, then synced when coverage returns, with conflict rules agreed with your dispatch team so a late sync never overwrites a newer update.
Usually, yes. We work alongside the TMS you already run rather than replacing it, connecting through its API where one exists and through file or database exchange where it does not. If the system is closed, we say so early and design around it instead of promising an integration nobody can support.
Yes. We handle tender, status, invoice and remittance exchanges with the mappings your partners expect, and we build acknowledgement checks so a silent failure surfaces the same day rather than at settlement. Partner requirements vary, so we confirm each specification with the partner before go live.
You do. Clients own all code, designs, accounts and IP from the first commit, and we hand over repositories, environments and documentation as we go rather than at the end. Your operational data stays in systems you control, and we agree data handling and retention in writing before the build starts.
Yes. A customer portal is often the quickest way to cut status calls. We build tracking views, document access for proof of delivery and bills of lading, booking and quote request forms, and notification rules, all to WCAG 2.2 AA so shippers and consignees can use them on any device.
Yes. We pull telematics, ELD and GPS feeds into one view so location, hours and vehicle data sit next to the load. What is available depends on your provider and your contract with them, so we confirm the feeds and refresh rates during discovery rather than assuming what the hardware exposes.
We can. Driver recruitment works when the ad, the landing page and the application form are treated as one path. We build fast mobile application flows, connect them to your applicant tracking system or CRM, and run paid social and search campaigns measured on qualified applicants rather than clicks.
Let’s connect
Tell us about your project.
We’ll reply within one business day with next steps and a tailored quote — no obligation.