Actively being built and validated. Not yet generally available.
Shipment tracking
Every consignment with its legs, current status and documents in one record.
SIWOM Logistics
Actively being built and validated. Not yet generally available.Shipments, vehicles and delays in one workspace.
SIWOM Logistics is shipment coordination software for freight forwarders, transporters and warehouse operators in India. It is in development: the demo on this page uses sample data, and we are looking for pilot partners.
The problem
Why coordination breaks down.
A single container can move by vessel, rail and road through three or four organisations in a week. Each keeps its own records, and the people coordinating them fill the gaps by phone.
By the time a delay is visible, the berth window, rail cut-off or unloading slot it affects has often already been missed.
- Status lives in spreadsheets, chat groups and carrier portals
- Port, rail and road legs are tracked separately
- Document deadlines, such as e-way bill validity, are easy to miss
- Exceptions arrive unsorted, so urgent ones wait behind routine ones
What SIWOM Logistics does
Built around the shipment, not the system.
Each feature carries its real status. In development means we are building it now; most of these appear in the demo below.
- Actively being built and validated. Not yet generally available.
Exceptions and delays
Delays sorted by severity, each with its cause, its effect on the ETA and a suggested next step.
- Actively being built and validated. Not yet generally available.
Dispatch
Match waiting loads with available vehicles from one queue. A person confirms every assignment.
- Actively being built and validated. Not yet generally available.
Fleet availability
Which vehicles are free, at which hub, and which are in maintenance.
- Actively being built and validated. Not yet generally available.
Milestones and ETAs
Planned and current ETA for every shipment, with the full timeline from booking to delivery.
- Actively being built and validated. Not yet generally available.
Handoffs and documents
What the next partner needs, and which documents, such as e-way bills, are due or expiring.
- Being explored. Feasibility is not yet proven.
Reporting
On-time performance, dwell times and exception trends across lanes and partners.
- Being explored. Feasibility is not yet proven.
Integrations
Spreadsheet import first. APIs and connectors for TMS, WMS and telematics are planned per pilot.
Interactive demo
Try SIWOM Logistics with sample data.
Filter by status or mode, open a delayed shipment, acknowledge an exception and assign a vehicle. Nothing here is connected to live operations.
Illustrative demo data : not connected to live operations
Today18 Oct 202614:30 ISTSnapshot · demo
Status
Mode
Loading interactive demo…Try Select a delayed shipment in the table, on the map or in Exceptions.
Network map · schematic
14 routesOn timeAt riskDelayedDeliveredRoadRailPort
Schematic, not to scale. Positions are snapshot values, not GPS tracking.
Exceptions
6 open · by severity- Critical+9 h 00 min18 Oct, 11:20 IST
- High+4 h 15 min18 Oct, 12:05 IST
- High+6 h 30 min18 Oct, 09:50 IST
- Medium+2 h 10 min18 Oct, 13:40 IST
- Medium+3 h 40 min18 Oct, 10:15 IST
- Low+2 h 30 min18 Oct, 13:05 IST
Shipments
14 of 14SHP-24-0933
Delayed- Route
- Mundra to Nhava Sheva
- ETA (IST)
- 18 Oct, 21:00+9 h 00 min
SHP-24-0954
Delayed- Route
- Bengaluru to Hyderabad
- ETA (IST)
- 18 Oct, 23:45+4 h 15 min
SHP-24-0918
Delayed- Route
- Nhava Sheva to Nagpur
- ETA (IST)
- 19 Oct, 02:30+6 h 30 min
SHP-24-0927
At risk- Route
- Visakhapatnam to Hyderabad
- ETA (IST)
- 19 Oct, 05:10+2 h 10 min
SHP-24-0921
At risk- Route
- Mundra to ICD Tughlakabad
- ETA (IST)
- 19 Oct, 09:40+3 h 40 min
SHP-24-0945
At risk- Route
- Nagpur to Kolkata
- ETA (IST)
- 19 Oct, 18:30+2 h 30 min
SHP-24-0924
On time- Route
- Chennai to Bengaluru
- ETA (IST)
- 18 Oct, 17:05−10 min
SHP-24-0942
On time- Route
- ICD Tughlakabad to Nhava Sheva
- ETA (IST)
- 18 Oct, 18:40−20 min
SHP-24-0930
On time- Route
- Kolkata to Visakhapatnam
- ETA (IST)
- 18 Oct, 22:15−15 min
SHP-24-0936
On time- Route
- Hyderabad to Nagpur
- ETA (IST)
- 19 Oct, 00:50−10 min
SHP-24-0948
On time- Route
- Chennai to Visakhapatnam
- ETA (IST)
- 19 Oct, 22:00On plan
SHP-24-0957
On time- Route
- Kolkata to ICD Tughlakabad
- ETA (IST)
- 20 Oct, 08:00On plan
SHP-24-0951
Delivered- Route
- Nhava Sheva to Hyderabad
- ETA (IST)
- 18 Oct, 09:35−25 min
SHP-24-0939
Delivered- Route
- Bengaluru to Chennai
- ETA (IST)
- 18 Oct, 11:20−25 min
Dispatch queue
5 trucks freeUnassigned · 5
- DSP-1041Pickup 18 Oct, 16:00
Nhava Sheva to Nagpur · 40 ft container
- DSP-1042Pickup 18 Oct, 17:30
Chennai to Bengaluru · 32 ft closed body
- DSP-1043Pickup 18 Oct, 19:00
Hyderabad to Visakhapatnam · 40 ft container
- DSP-1044Pickup 19 Oct, 06:00
Bengaluru to Chennai · 20 ft container
- DSP-1045Pickup 19 Oct, 08:00
Nagpur to Hyderabad · 32 ft closed body
Assigned · 0
Assigned loads appear here.
About the map
The map is schematic and does not draw national boundaries. Positions are snapshot values, not live GPS. A geographic basemap is planned; it would use a provider that depicts India's official boundaries.
Transport modes
Ocean, air, road and rail in one plan.
The milestones SIWOM Logistics is designed to follow for each mode, so the next partner knows what is coming.
Ocean
- Vessel arrival and berthing
- Container discharge and yard
- Delivery order and gate-out
- CFS or ICD transfer
Air
- Flight arrival
- Cargo terminal acceptance
- Clearance status
- Airport-to-warehouse pickup
Road
- Vehicle assignment
- Pickup and e-way bill
- Halts and delays in transit
- Proof of delivery
Rail
- Rake allocation
- Terminal cut-off
- Departure and arrival
- Rail-to-road transfer
Representative photographs; SIWOM does not own or operate these assets. Connections to carrier, terminal and rail systems are planned per pilot; the demo uses sample data.
Milestones
From booking to delivery.
Every shipment carries one timeline. Each milestone records when it happened and who handled it, and exceptions attach to the milestone they put at risk.
Step 1: Booked
Order and documents created.Step 2: Picked up
Load collected at origin.Step 3: In transit
Moving by road, rail, sea or air.Step 4: At hub
Port, airport, CFS, ICD or warehouse.Step 5: Out for delivery
Final leg to the consignee.Step 6: Delivered
Proof of delivery recorded.
International shipments
Being explored. Feasibility is not yet proven.Planning the handoff at the port or airport.
We are researching how to plan imports and exports end to end: compare ocean and air options, see which local partner takes over, and check documents before each handoff. The workspace below is a concept with fictional data.
SIWOM Logistics / International workspace
Demo data · Interactive product concept
Fictional providers and shipment records. No live tracking, actual quotations or connected AI. Recommendations below are written examples.
DEMO-INT-1042
Palletised machinery parts
Global origin → Local destination
Singapore
Supplier documents prepared
International ocean freight
Demo Ocean Network · sample assignment
Chennai port
Document review & terminal handoff · pending
Bengaluru, India
Local logistics partner · final delivery planned
Documents
Packing list · demo draft
Quotation
Awaiting provider quote
Analysis preview
Compare terminal pickup, inland transport and storage charges together. Confirm the local carrier’s pickup window before committing to the main freight leg.
Scripted example · human decision required
Integrations
Being explored. Feasibility is not yet proven.Work with the systems you already run.
None of these connections is built yet. They describe how we intend SIWOM Logistics to connect, scoped with each pilot partner.
- Being explored. Feasibility is not yet proven.
APIs
Planned REST APIs and webhooks to exchange shipments, events and exceptions.
- Being explored. Feasibility is not yet proven.
Existing TMS and WMS
Planned connectors so orders and inventory movements flow in without re-keying.
- Being explored. Feasibility is not yet proven.
Telematics and tracking
Planned use of the GPS and telematics feeds you already pay for.
- Being explored. Feasibility is not yet proven.
Ports, ICDs and rail
Planned ingestion of terminal and rail milestones where access is available.
FAQ
Questions we hear.
Not as a general product. SIWOM Logistics is in development, and the demo on this page uses sample data. We are looking for logistics companies with a real coordination problem to pilot it with us.
No. The intent is to sit alongside the systems you already run and bring their data into one operational view. Integrations are planned, not built yet.
Our approach is to use the telematics and tracking data you already have where possible. What is feasible depends on your providers and is scoped during a pilot.
No. It suggests next steps, such as reassigning a vehicle or moving an unloading slot. Your operators decide.
We start with one lane, hub or exception type, agree what success means and how it is measured, connect the minimum data needed, and review results with your team before anything expands.