Logistics & Supply Chain engineering, built by people who have shipped logistics & supply chain before
Logistics platforms that survive contact with the real world: bad data, flaky connectivity, and angry drivers.
How Kiebot ships logistics & supply chain
Kiebot has shipped logistics platforms for last-mile, B2B freight, and warehouse ops. The defining characteristic of logistics software is that the input data is always wrong: bad addresses, partial loads, broken scanners, drivers offline for hours. We design for it.
- Driver and field-ops mobile apps with offline-first queues
- TMS and WMS modules that integrate with existing ERPs
- Real-time tracking with map rendering and route optimisation
- POD (proof of delivery) capture with photo, signature, and OCR
- Carrier integrations and rate-shopping engines
Engineering signals you can audit
- Offline-first mobile apps with conflict-resolution on sync
- Spatial queries on PostGIS for distance and zone logic
- Event-sourced state for driver activity and load history
- Map renderer choice tuned for data cost and offline capability
Compliance, in practice
Region-specific labour and rest-time rules for drivers, e-way bill integration in India, customs and last-mile data flows, GDPR for B2C deliveries.
Selected logistics & supply chain work
Frequently asked questions
Mapbox or Google Maps?+
Mapbox by default for predictable cost and offline maps. Google Maps when the customer demands its place data or routing.
How do you handle drivers losing connectivity?+
Offline-first mobile apps with a local queue, optimistic UI, and clear conflict resolution when sync happens. The driver is never blocked by the server.
Can you integrate with our existing TMS or WMS?+
Yes. We have shipped against Oracle WMS, SAP, and several custom systems. The integration layer is its own service, not glue in the front end.