Direct Answer
Logistics systems are state machines with money attached. We build order intake, dispatch, tracking, proof of delivery and settlement so every shipment has one authoritative status and every charge traces back to a recorded event.
Suitable For
- Freight forwarders and 3PLs replacing spreadsheet dispatch and manual billing
- Distribution and cold-chain operations needing route, driver and temperature records
- Warehouse operators needing inbound, storage, picking and outbound tracking
Not Suitable For
- Large-scale route optimisation research projects rather than an operational system
- Requests to resell carrier capacity without an operating entity behind it
Core modules and the data each one owns
| Module | Scope, data and rules it owns |
|---|---|
| Order intake | Consignment data, service type, pickup and delivery windows, special handling flags and the pricing basis for the order. |
| Dispatch & routing | Vehicle and driver assignment, load planning, stop sequence, and the rules for reassignment when a job fails. |
| Tracking & events | Timestamped status events with location and operator; the event log is the source of truth, and displayed status is derived from it rather than stored separately. |
| Proof of delivery | Signature, photo, scan and exception reason capture from the driver app, retained as the evidence for billing disputes. |
| Warehouse | Inbound receipt, location assignment, picking task, stocktake and outbound handover. |
| Settlement | Charge calculation from recorded events, customer invoicing, driver or carrier payables, and the reconciliation report. |
Step-by-step Process
- Send the current workflow, the roles involved and where the process breaks down today
- We map the data model, the modules needed at launch and what can wait for a later phase
- Confirm scope, integrations, acceptance criteria, source-code ownership and deployment responsibility
- Iterative build with demos at each milestone, then functional, compatibility and performance testing
- Deployment, source-code and documentation handover, then an agreed maintenance path
Buyer Checklist
- One primary user workflow and one admin workflow defined for the first release
- Role and permission matrix agreed before development, enforced in the backend
- Integration accounts and API credentials confirmed as available
- Data migration source, format and volume reviewed
- Acceptance criteria written per module, not per screen
- Source-code ownership, deployment responsibility and maintenance scope stated in the contract
Information Needed for Quotation
- The workflow you want to replace or build, and who performs each step
- User roles and what each role may see and edit
- Platforms required at launch (web, mini program, iOS, Android, desktop)
- Systems to integrate: payment, ERP, WMS, hardware, accounting, third-party APIs
- Existing data to migrate, its current format and rough volume
- Whether source-code handover and self-hosting are required
Frequently Asked Questions
How does the driver app behave with no signal?
Scans, photos, signatures and status updates are queued locally with their capture timestamp and uploaded when the connection returns. The server keeps both capture time and receipt time so the timeline stays accurate for dispute handling.
Can billing be generated automatically?
Yes, when the pricing basis is expressible as rules over recorded events — weight, volume, distance, waiting time, surcharges. Rules that still need human judgement stay as a review step rather than being forced into automation.
Which platforms do you build for this industry?
Web system for operations and finance, Android and iOS driver app with offline capture and background location, WeChat mini program for customer self-service tracking, plus an admin panel.
What can you integrate with?
Map and geocoding APIs for address resolution and distance; carrier tracking APIs; electronic waybill platforms; accounting export; SMS and message notifications; temperature and GPS device data where the device vendor exposes an API.
Will we own the source code?
Source-code handover, repository access, deployment notes and database documentation can be included in the agreed scope. State it in the brief so it is priced in rather than added later.
Can you take over an existing system instead of rebuilding?
Yes. We start with a code and environment review, then propose a scoped plan for bug fixes, refactoring, UI rework or new features. Rebuilding is only recommended when the review shows the existing codebase cannot carry the roadmap.
Related Pages
Request a Quotation
Include the fields listed above so the response can focus on model, material, fitment or service scope instead of generic claims.
Request a Project Estimate
Tell us about the product goal, current workflow, target platform, constraints and decision timeline. We will review the scope and recommend a practical next step.