01
FIG 01 · Logistics Software Development
Logistics software built around the rules, the data and your drivers
TMS, WMS, fleet dashboards and driver apps for carriers, 3PLs, brokers and shippers, designed around duty-status records, EDI partners and the telematics you already run.
See how it works
FIG 02 · Quick answer
What does a logistics software development company do?
Elgrith is a logistics software development company that builds transportation and warehouse management systems, fleet dashboards and driver apps. We design around the rules your operation runs on, such as FMCSA ELD records, the EU eFTI regulation and UK tachograph changes, and connect EDI X12, GS1 labels, telematics APIs and route optimization to your ERP.
- EDI 204, 990, 214 and 210 mapped to your trading partners
- X12
- Projects delivered since 2015
- 1,000+
- Clients across the USA, UK and India
- 250+
- Your code, repository and IP
- 100%
FIG 03 · Why it matters
Rules and standards shape a logistics system before the first screen.
From the US Code of Federal Regulations (via Cornell LII), X12 and the European Commission, read on 23 Oct 2026.
01
49 CFR 395.8
ELDs record duty status
US motor carriers “must install and require each of its drivers to use an ELD to record the driver’s duty status”, with narrow exceptions such as vehicles “manufactured before model year 2000”.
Source: 49 CFR 395.8, via Cornell LII (read 23 Oct 2026)(opens in a new tab)02
204 → 214
EDI is how freight talks
X12’s 204 lets shippers “offer (tender) a shipment” to a truckload carrier; the 214 gives shippers and consignees “the status of shipments”. Your partners expect both.
Source: X12, transaction sets (read 23 Oct 2026)(opens in a new tab)03
9 Jul 2027
EU authorities must accept eFTI data
The European Commission: on 9 July 2027 “The eFTI Regulation will apply in full”, and authorities must accept freight information shared through certified eFTI platforms.
Source: European Commission, eFTI Regulation (read 23 Oct 2026)(opens in a new tab)
FIG 04 · Rules and dates
Built around the rules: what changed and when
The rules decide what your software must record, keep and share. This is the dated view we design from, checked on 23 Oct 2026 at the official sources linked on this page.
| Rule | Who it affects | Date | What it means for your software |
|---|---|---|---|
| FMCSA ELD rule (49 CFR 395.8) | US motor carriers and their drivers | In force (original compliance date 18 Dec 2017) | Hours-of-service and duty-status data come from a registered ELD; your TMS and driver app read it through the ELD provider’s API rather than replace it |
| Smart tachograph version 2 (DVSA) | Operators carrying goods between the UK and EU in vehicles over 2.5 tonnes | From 1 Jul 2026 | In-scope vehicles need a smart tachograph v2; plan for tachograph data downloads and driver-hours reporting on those lanes |
| EU eFTI Regulation: preparation | eFTI platforms, service providers and EU authorities | From Jan 2026 | Platforms can prepare for operations, and authorities may start accepting data from certified eFTI platforms |
| EU eFTI Regulation: full application | Operators sharing freight information with EU authorities | 9 Jul 2027 | Authorities must accept electronic freight information shared through certified eFTI platforms; keep consignment data structured and exportable |
General guidance, not legal advice. Sources: 49 CFR 395.8 via law.cornell.edu; DVSA bulletin of 1 Jul 2026; European Commission eFTI page. Your compliance adviser confirms what applies to your fleet.
Tracking devices and sensors? IoT app developmentFIG 05 · What you get
Logistics software we build
Logistics software development for the whole chain, from the tender to the signature at the door. Each system shares one data model, so a load, a pallet and a stop mean the same thing everywhere.

02
Warehouse management (WMS)
03
Fleet management
04
Last-mile and ePOD
05
Carrier, shipper and broker portals
06
Supply chain software development
07
Yard and dock scheduling
08
Control tower dashboards
Deliverables
11
deliverables, in writing
FIG 06 · Integrations
Integrations that make or break a logistics system
Most logistics software fails at the edges: the EDI partner, the label printer, the telematics feed. We design those connections first. We integrate through each vendor’s published API and claim no partner or marketplace status with any of them.
- EDI trading partners
- Telematics and ELDs
- ERP and accounting
- Driver app
- Customer portal
- Maps and routing
EDI X12
- Transactions
- 204 load tender, 990 tender response, 214 shipment status, 210 freight invoice
- How
- Mapped and tested per trading partner, over a VAN, AS2 or an API gateway
GS1 labels and barcodes
- Standards
- SSCC for each logistic unit, printed as GS1-128 barcodes
- Where
- Receiving, packing, shipping and the advance ship notice to your customer
Telematics: Samsara, Motive, Geotab
- Data
- Vehicle location, hours of service, faults and driver events
- How
- Through each provider’s published API (Geotab through MyGeotab), with your account’s access
ERP and accounting
- Data
- Orders, customers, rates, invoices and payments, synced both ways
- Where
- NetSuite, Business Central, SAP Business One, Odoo or a custom ERP
Maps, geocoding and routes
- Data
- Addresses, distances, ETAs and route plans
- Where
- Google Maps Platform, Mapbox or HERE, chosen on coverage and cost
FIG 07 · Routing
Route optimization and AI dispatch
The vehicle routing problem is old; the tools are new. Google’s Route Optimization API “generates optimized route plans for single or multiple vehicles and their stops” (page updated 21 Oct 2026). We add your rules on top: time windows, vehicle capacity, driver hours and customer priorities.
05principles
Route plans with your constraints
Stops, time windows, capacities, breaks and depots fed to a solver, with dispatchers able to override and lock stops.
Demand forecasting
Volume forecasts by lane, customer or warehouse from your order history, so you can plan capacity before the peak.
Exception alerts
Late pickups, missed windows, long dwell times and temperature breaches flagged while there is still time to act.
AI for documents and dispatch
Reading rate confirmations, bills of lading and emails into structured data, with a person approving each change.
AI developmentCost and service dashboards
Cost per stop, on-time rates and carrier scorecards from your own data.
Data visualization
FIG 08 · Apps
Logistics app development for drivers, dispatchers and customers
Drivers work in dead zones, loading docks and cabs with gloves on. Our logistics app development starts from that reality: big targets, offline storage and clear next steps.
06principles
Offline-first driver apps
Stops, documents and scans saved on the device and synced when the signal returns, with no lost proof of delivery.
Scanning, photos and signatures
Barcode and label scans, damage photos, signatures and exception codes captured at each stop.
Dispatcher console
Assign loads, re-sequence stops, message drivers and see every vehicle on one map.
Customer tracking
A tracking page or app with live ETAs and delivery photos, without exposing driver details.
Hours-of-service awareness
Driver hours read from the ELD provider’s API, so dispatch never assigns a load a driver can’t legally finish.
iOS and Android
Native or cross-platform apps, chosen on scanning hardware and background location needs.
App development
FIG 09 · UK and EU
Running UK or EU lanes?
UK and EU operators work to different paperwork. We build the records your organisation needs for tachographs, eFTI and electronic consignment notes, and keep them exportable for inspection.
04principles
Smart tachograph v2
From 1 Jul 2026, DVSA says UK–EU operators of in-scope goods vehicles over 2.5 tonnes need a smart tachograph v2. We plan driver-hours data and downloads around it.
eFTI-ready freight data
Consignment data kept structured, so it can be shared through a certified eFTI platform before the regulation applies in full on 9 Jul 2027.
eCMR consignment notes
Electronic consignment notes with signatures and status history, where your lanes and partners accept them.
Manufacturing and B2B supply chains
Inbound materials, outbound orders and dealer deliveries for manufacturers.
Manufacturing
FIG 10 · Portfolio
From our portfolio: a fleet and logistics command centre
A design concept from our portfolio, not a client case study: a live operations CRM that maps every shipment, flags delays before customers notice and joins dispatch, sales and support in one pipeline. Real case studies are shared on request, without client names.
04principles
Live shipment map
Every load on one route map, coloured by status, with the next action for each.
Delay flags
Loads at risk of missing their window surfaced before the customer calls.
One pipeline
Dispatch, sales and support working from the same shipment record.
FIG 11 · Process · 6 steps
Map the data, pilot one lane, then roll out
A free call, a fixed written quote, then a staged build: discovery, data mapping, a pilot on one lane or one warehouse, and rollout. Weekly demos throughout. You own the code, the data and the IP.
- Step 01
Free call
Tell us how freight moves today: the systems, the spreadsheets, the partners and where things break. We ask about loads, lanes and drivers, not just screens.
- Step 02
Discovery
Your workflows, rules and integrations mapped: EDI partners, telematics, ERP, labels and the reports you can’t live without.
- Step 03
Data mapping and fixed quote
A shared data model for loads, stops, units and documents, plus a written scope and a fixed quote, before any build starts.
- Step 04
Pilot lane
One lane, one customer or one warehouse, built in sprints with a demo every week and tested with real loads and real drivers.
- Step 05
Rollout
More lanes, sites and partners, with data migration, training and a staged switch-over from the old system.
- Step 06
Support and change
New partners, rule changes and features, covered under terms agreed in your written scope.
FIG 12 · What you get
Everything included
Written into your fixed quote, so you know exactly what you are paying for before work starts.
11items
- Written scope and fixed quote
- Process and integration map
- Shared data model for loads, stops, units and documents
- Web platform: TMS, WMS or fleet modules in scope
- Driver app for iOS and Android
- EDI maps and partner testing
- Telematics and ERP integrations
- Dashboards and exception alerts
- Data migration from your current system
- Training and runbooks
- IP assignment: code and data are yours
FIG 13 · Tech & tools
The tools behind the work
Proven, well-supported tools, chosen for your project and set up in accounts your business owns.
- Kotlin
- Swift
- Flutter
- React Native
- Next.js
- Node.js
- Python
- PostgreSQL
- PostGIS
- Redis
- EDI X12
- AS2
- GS1-128
- Google Maps Platform
- Route Optimization API
- Mapbox
- Samsara API
- Motive API
- MyGeotab API
FIG 14 · Who it’s for
Logistics software for the people who move freight.
Carriers, 3PLs, brokers and shippers in the US, UK and Europe, each with different rules and partners.
3 audiences
Carriers
Fleet and dispatch built around your drivers.
Dispatch, driver apps, maintenance and settlements, reading hours and location from the ELDs and telematics your fleet already uses.
- Driver app with ePOD
- ELD and telematics data
- Fleet maintenance
- Driver settlements
3PLs
Warehouses and customers on one system.
WMS, customer portals and billing for third-party logistics providers, with each client’s rules, labels and EDI kept separate.
- Multi-client WMS
- Customer portals
- GS1 labels and ASNs
- Storage and handling billing
Brokers and shippers
Tender, track and audit every load.
TMS features for freight brokers and shippers: carrier onboarding, tenders over EDI, tracking and freight audit against the 210 invoice.
- EDI 204, 990, 214, 210
- Carrier onboarding
- Tracking and alerts
- Freight audit
FIG 15 · Working with us from the USA and UK
Built in New Delhi. Run on your hours.
Every project gets a point of contact in New York or London and an engineering team in New Delhi. Here is how today’s working days line up, live.
New York
North America
--:--ET
New Delhi team Your working day- Shared working time
- ≈ 3 hours today
- New Delhi is
- 10.5 h ahead
- Live calls, your time
- 9 a.m. to 12 p.m. ET
London
UK & Europe
--:--UK
New Delhi team Your working day- Shared working time
- ≈ 4.5 hours today
- New Delhi is
- 5.5 h ahead
- Live calls, your time
- 9 a.m. to 1:30 p.m. UK
Three ways to work together
- 01
Fixed-scope project
A written scope, one fixed price and a dated plan. Suits websites, apps and MVPs.
- 02
Dedicated team
Designers and engineers on your roadmap every month, billed monthly.
- 03
White label
For US and UK agencies: our work, your brand, unbranded deliverables.
Every engagement
- Fixed quote in USD, GBP or INR after a free 30-minute call
- NDA before discovery. You own all code, designs and content
- A working demo every sprint, not status slides
- Reply within one business day, calls inside your hours
Calls on ET or UK hours
FIG 16 · Decide
Buy an off-the-shelf TMS or WMS vs build custom vs extend what you have
Custom isn’t always the answer. This is how we compare the three routes with you, before any quote.
| Buy off the shelf | Build custom | Extend your current system | |
|---|---|---|---|
| Best for | Standard workflows a product already covers | Workflows that are your edge, or that no product fits | A system that works but leaves gaps |
| Integrations | The vendor’s list | Whatever your partners need | Added around the core through its API |
| Code and data | The vendor’s product; your data under their terms | Yours | Your extensions are yours; the core stays the vendor’s |
| Main risk | Bending your process to the software | Scope and time if the first release is too big | Limits of the vendor’s API |
Many teams end up with a mix: a product for the standard parts, custom software and integrations for the rest.
Need a bespoke system? Custom software developmentFAQ
Frequently asked questions
Straight answers about Logistics Software Development with Elgrith.
We don’t publish prices, because cost depends on scope: which modules you need (TMS, WMS, fleet, portals), how many EDI partners and integrations, whether you need driver or customer apps, and how much data must move from your current system. After a free call you get a written scope and a fixed quote.
FIG 17 · Related
Keep exploring
Custom Software Development
Bespoke platforms, tools & SaaSERP Development
Custom ERP & ERP integrationsIoT App Development
Connected devices & wearablesApp Development
iOS, Android & cross-platformAPI Integration
Connect your apps, CRM & paymentsAI Development
LLM apps, AI agents & MCPData Visualization
Dashboards, Power BI & TableauB2B & Enterprise
Free 30-minute call
Build logistics software your drivers and partners can trust.
Tell us how freight moves today and where it breaks. After a free call you get a written scope and a fixed quote, starting with one lane or one warehouse.
Pick a day for your call
OpenPick a day. You'll choose a time in your own time zone on the next step.







