FreightSync — fleet dispatch & last-mile visibility.

The summary.

FreightSync needed to replace spreadsheet-based dispatch with a unified operations platform as their fleet grew past 500 vehicles. Over 14 months we built a dispatch hub, driver mobile app, customer tracking portal, and ERP integrations — cutting fuel costs and saving dispatchers 15 minutes per route.

About FreightSync

FreightSync is a mid-market logistics carrier operating across North India, specialising in last-mile freight for manufacturing and retail clients. Their fleet handles 2,000+ daily shipments across 500+ vehicles, with dispatch teams coordinating routes from regional hubs.

Before partnering with Techora, operations ran on shared spreadsheets, WhatsApp groups, and a legacy TMS that could not support real-time GPS or proof-of-delivery capture. Growth was outpacing their tooling — on-time delivery had slipped to 70% and fuel costs were rising with inefficient routing.

The challenge.

FreightSync's operations director needed a single source of truth for dispatch, drivers, and customers — without a multi-year ERP replacement project. The platform had to work in low-connectivity zones, support offline proof-of-delivery, and sync with existing SAP and Tally systems their finance team already relied on.

Key constraints included:

• Dispatch at scale: planners needed to assign and re-route 500+ vehicles daily without manual copy-paste between tools.
• Driver adoption: the mobile app had to work offline in rural corridors and require minimal training for contract drivers.
• Customer visibility: B2B shippers expected live tracking links and automated ETA updates — not phone calls to the dispatch desk.
• Finance alignment: POD data and trip costs had to flow into SAP and Tally without duplicate entry.

The solution.

We provided a dedicated pod of eight engineers — two backend, two frontend, two mobile, one DevOps, and one QA — embedded in FreightSync's weekly ceremonies. The engagement followed a fixed-milestone model with phased rollouts per regional hub.

Core functional modules

Workflow overview

1. Dispatch planner uploads daily orders or pulls them from SAP; the system suggests optimised routes by vehicle capacity and SLA.
2. Routes are published to the driver app; drivers accept assignments and receive turn-by-turn navigation with offline fallback.
3. At delivery, drivers capture POD (signature, photo, notes) offline; data syncs when back online.
4. Customers receive automated tracking links with live ETA; shippers can self-serve status without calling dispatch.
5. Trip completion triggers ERP sync — costs to SAP, invoice line items to Tally — with audit logs for finance review.

Architecture & security highlights

• Incremental rollout: component-based architecture allowed hub-by-hub deployment without big-bang cutover.
• Offline-first mobile: local SQLite cache with background sync queue for POD and GPS breadcrumbs.
• Hosted on AWS: ECS for APIs, RDS PostgreSQL, ElastiCache Redis, S3 for POD assets.
• Role-based access: dispatch, driver, customer, and admin roles with scoped API permissions.
• Data encrypted at rest and in transit; audit logs for all ERP sync events.