Book Delhivery shipments, check pin code serviceability, print labels and share tracking with your customers, without leaving your order management system.
Delhivery covers surface and express movement across India, and the questions that matter are ordinary ones: does Delhivery deliver to this PIN code, what does it cost at this weight, and when will someone collect the parcel. The Delhivery API Integration answers all three from your order or inventory system, so Delhivery shipping automation happens while an order is being packed rather than at the end of the day.
Domestic shipping in India runs on PIN codes and weight slabs. These are the parts of the Delhivery workflow the API handles for you.
An order already carries the delivery address, the pin code and the weight, and that is what the Delhivery booking is built from. The AWB comes back against the order, along with a label that prints on the paper stock you already use. Nothing is retyped, which removes the most common cause of a failed delivery.
Some orders get cancelled after the label is generated, and a few get cancelled before the parcel is even packed. Both can be handled from the same record while the booking is still open, and the cancellation reference is kept alongside the order.
Delhivery tracking data is brought into Softpal as shipments move, so customers can see where a parcel is without being sent to a carrier portal. The person answering a support call has the same scan history on screen, which matters when most of your calls are delivery-related.
Where Delhivery does not push an update, the status is fetched again after an interval you choose. Polling is easy to set up and easy to overdo: a short interval across a large order book produces a lot of requests for very little new information, so we set it around your daily volume.
Credentials, rate cards and pickup locations are configured per Delhivery account, so each seller or warehouse is billed on its own contract. Serviceability and rates are checked against the account that will actually carry the shipment, not a default one.
Pickups, manifests and multi-piece shipments sit with the order they belong to, and a booking can still be placed by hand where a consignment needs something unusual. Service availability is checked before the order is confirmed, so an unserviceable pin code is caught early rather than at the door.
The fetch rate is how often your system calls the Delhivery API. Every five minutes keeps a busy dispatch board accurate; an hour is enough for orders that go out in batches. Rates can also be fetched on a trigger, such as a new order or a status change, instead of on a clock.
Delhivery accepts pickup requests through its API, so parcels ready at a given address can be flagged for collection from your system rather than by phone. The request stays linked to the consignments it covers, so there is no disagreement about what was in the batch.
The estimated delivery date comes back from Delhivery after the shipment is picked up, not when the label is printed. Distance, the service chosen, the Delhivery network and the time the order took to process all feed into it, which is why the estimate settles once the parcel is moving.
In India, whether a shipment can be booked at all is decided by the pin code, and the same rate request confirms it. Checking serviceability before an order is confirmed means an undeliverable address surfaces while you can still change something, instead of becoming a failed delivery later.
The Delhivery charges recorded in accounts payable are compared against Delhivery's statements, transaction by transaction. Bringing them in through the API rather than re-keying a bill is what makes weight discrepancies and surcharge lines visible while they can still be queried.
Several Delhivery accounts can run at the same time, and the account is selected by rule rather than by hand. Weight slabs are the usual approach, with one account for consignments under 5 kg and another for anything heavier, and accounts can also be split by region, Hyderabad in Telangana and Bangalore in Karnataka for instance, with a default account for the rest of India.
