The partner network

Multi-LSP orchestration & the Partner Control Board

Eighty-plus logistics partners behind one shipment lifecycle — chosen automatically, tracked leg by leg, and scored on the same metrics as your own fleet.

Request a Demo →All modules

A shipper with fifteen logistics partners has fifteen tracking portals, fifteen status vocabularies and fifteen invoice formats. The usual answer is a person who logs into all fifteen. That person is the integration layer, and they do not scale.

The platform is the integration layer instead. Partners are onboarded through a configuration console rather than a development project, every partner status is normalised to one lifecycle, and the shipment record is the same whether the leg moved on your truck or someone else’s.

Multi-LSP orchestration

Orchestration

80+ logistics partners, 200+ APIs

Direct integration across express, courier, surface, air, parcel and last-mile partners in India, South-East Asia, the Middle East and Africa, covering the large majority of India’s express cargo movement. Structured EDI and portal fallback where a partner has no API.

No-code integration console

A new partner integration is configured, not coded. Endpoints, authentication, field mapping and status translation are set up in a console, which is what makes eighty partners maintainable rather than merely impressive.

Automatic LSP selection

Allocation by pin-code, city, lane, SLA rank or round-robin. Shippers configure the rules and the platform executes them at booking, so seasonal changes are a rule change rather than a re-engineering exercise.

LSP master and customer contracts

Carriers, services and per-customer contracted terms held as masters, so allocation, tracking and audit all work from the same commercial truth.

Booking, tracking and POD as one worker

One pipeline carries a shipment from booking through tracking to proof of delivery per partner, with scheduled pulls and priority queues so a slow partner does not starve a fast one.

Normalised step-wise tracking

Pickup, first mile, origin hub, line-haul, destination hub, out for delivery, delivered — standardised across every partner, so operations reads one lifecycle rather than eighty.

E-way bill through GSTN

Generate, extend and track Part A and Part B across all partners from one system, through a secure GSTN gateway, without each ERP building its own connection.

Reverse logistics

Store or consumer return request, partner assignment, pickup, warehouse acknowledgement — the reverse flow in the same platform as the forward flow rather than in a spreadsheet beside it.

The Partner Control Board

One list, every partner

A single operational list across all partners, filterable and searchable, replacing the fifteen browser tabs.

Multi-carrier legs with handover detail

Where a shipment moves across more than one carrier, each leg carries its own timeline and the handover between them is explicit. Losses happen at handovers, so the handover is where the record needs to be clearest.

Shipment health

A health state on the shipment itself, so the list can be worked by exception instead of read end to end.

League table with drill-through

Partners ranked on the metrics that matter, with drill-through from the ranking to the shipments that produced it. A scorecard you cannot drill into is a debating position, not a management tool.

Hourly trend snapshots

Performance captured hourly, so a partner degrading through the day is visible during the day rather than in next month’s review.

Automated POD and freight audit

POD documents pulled from partner systems automatically and attached to the shipment. Partner invoices audited against contracted SLA, actual performance and chargeable weight, with an exception workflow for disputes.

Where we draw the line

Partner coverage is demand-led: new partners are added as customers bring them, and a partner with neither API nor structured feed is tracked by portal fallback, which is slower and we say so rather than implying parity.