Frequently asked questions

iBidLogistics is a logistics procurement and transport management platform. A shipper plans a dispatch, puts the freight out to its transporters as a reverse auction, allots it to the winning bidder, then tracks the vehicle by GPS through to proof of delivery and invoice settlement. It runs on the web and as an Android and iOS app.

The shipper publishes a freight with its route, material, vehicle type and quantity, and invites selected transporters. Transporters bid the price down rather than up, each bid having to beat the current best. When the auction closes the shipper allots the freight, normally to the lowest bid. Auctions can be live, meaning open now, or future, meaning scheduled to open later.

Yes. A direct freight is awarded to one nominated transporter at a price the shipper sets, with no bidding. There is also a counter-offer: on a live auction the shipper can send one transporter a specific price, which that transporter either accepts, awarding the freight immediately at that price, or rejects, leaving the auction running.

Four kinds of user share one platform. Shipping companies plan dispatches and procure freight. Transporters bid, assign vehicles and drivers, and raise invoices. Consignees follow their own inbound deliveries and confirm receipt. Administrators onboard companies and transporters and manage master data. See the who it's for page for detail on each.

Yes. Once a vehicle is allotted, the trip moves through a defined lifecycle: vehicle assigned, reported at gate, loading, in transit, reached destination, proof of delivery, closed. Position is reported from the driver's phone, and arrival at each stop is detected by geofencing the stop's pin code, so a stop can be closed without anyone pressing a button.

Yes. A plan carries as many drop-off stops as the route needs, in visit order, and a stop can be collected from several pick-up locations. Order lines are optional, so a plan can record only that a load moves from A to B when the order detail is not known yet. Plans cover outbound movements from your site, inbound movements from a supplier, and out-to-out movements where neither end is yours.

The driver or the consignee records delivery against the stop from the mobile app, attaching the signed document. Each drop-off on a multi-stop trip carries its own proof, and the trip only closes once every stop is accounted for.

Yes, for Android and iOS, and it is not a cut-down version. Shippers can create plans and freights and watch auctions from it, transporters can bid, assign vehicles and drivers and raise invoices, and consignees get their own delivery view.

Procurement spend and auction savings, a plan-to-delivery conversion funnel, on-time delivery and turnaround, and a per-transporter scorecard covering participation, price and performance — all backed by four exportable registers (plans, freights, trips, invoices). See the analytics page for detail.

Against the price expected when the freight was raised, not against an arbitrary benchmark — so a saving reported on the dashboard is the gap between what you expected to pay and what the auction actually settled at.

Yes. When a transporter adds a vehicle or driver, its registration or licence is checked against Vahan, the government vehicle registry, rather than being taken on trust.