When a Delivery Note is submitted in ERPNext, Quantbit's Shiprocket connector automatically creates a shipment booking, selects the best available courier based on your routing rules — fastest, cheapest, or pincode-specific — and generates an AWB number. The shipping label is available to print directly from ERPNext. Tracking events from Shiprocket are fetched every two hours and written back to the Delivery Note. When the shipment is delivered, the Delivery Note is automatically marked as delivered and a confirmation is sent to the customer via WhatsApp or SMS.
Yes. Quantbit's Logistics Connector supports multiple carrier integrations running simultaneously in ERPNext. You configure routing rules — Blue Dart for metro cities, Delhivery for rest of India, DHL for international, and DTDC for zones where it is more economical. When a Delivery Note is created, the connector applies the routing rules, selects the correct carrier, and books the shipment with that carrier's API. All tracking data from all carriers comes back to the same ERPNext Delivery Note interface — no need to check multiple courier dashboards.
Connect Shiprocket, Delhivery, DHL, and Blue Dart to ERPNext. When a delivery note is submitted, your courier is booked, the AWB is generated, and your customer is notified — in seconds, not twenty minutes.
Each carrier has a different API, a different AWB format, a different tracking event vocabulary. We have already handled all of that so your team just clicks dispatch.
Shiprocket's multi-carrier platform gives access to 17+ couriers from one API. Our connector taps into that, letting ERPNext automatically select and book the best available carrier for each shipment.
Delhivery is the preferred carrier for many B2B and D2C businesses because of their coverage in tier-2 and tier-3 cities. Our direct Delhivery API connector gives you full control over shipment creation and tracking without going through an aggregator.
For businesses shipping internationally — especially those exporting from India to GCC, Europe, or the US — DHL Express is typically the most reliable carrier. Our connector handles the customs documentation complexity.
Blue Dart is the benchmark for time-definite domestic express delivery in India, particularly for high-value goods where delivery proof and reliability matter more than price.
Returns are unavoidable in e-commerce and B2B. Our reverse logistics integration triggers pickup requests from ERPNext return orders and tracks the returned goods journey back to your warehouse.
Using a regional courier, a 3PL warehouse partner, or a company-owned fleet? Our connector framework supports custom carrier integrations using standard REST webhooks so any logistics partner with an API can connect.
Every logistics integration we have done started because someone in operations was spending too many hours on something that should have been automatic. Here are the stories that stand out.
A consumer electronics accessories brand in Pune was dispatching 80 to 120 orders every day through Shiprocket. Every morning, their operations manager would sit with the ERPNext Delivery Notes from the previous day and the Shiprocket dashboard open side by side — copying customer name, address, pincode, weight, and dimensions from ERPNext into Shiprocket's create-shipment form. One order at a time. For 90 to 120 orders. It took between two and three hours every single morning, and that was before he even started picking, packing, or handling customer queries. Errors were frequent — a pincode typed wrong meant a returned shipment two weeks later. After the Shiprocket connector went live, he submits all Delivery Notes in ERPNext in one batch action, and every shipment is booked, AWB-numbered, and label-ready within seconds. His mornings now start with picking and packing — not data entry. He handles four times the volume with half the stress.
A packaging materials supplier in Bhiwandi ships to 50 to 80 business customers per day via Delhivery. Customers — mostly retail stores and manufacturers — would call the office throughout the day asking where their shipment was. The customer service team member would open the Delhivery dashboard, type in the AWB number, find the tracking status, and relay it back. For 20 to 30 calls a day, that was an hour of unproductive work. Some customers did not even know their AWB number, so the service team had to first find the AWB in a spreadsheet, then look it up on Delhivery. After the Delhivery connector brought tracking events into ERPNext, customer service can look up any customer, go to their sales order, and see the live tracking status without leaving ERPNext. They also set up automatic WhatsApp notifications — customers now get dispatched, in-transit, and delivered messages proactively. The "where is my order" calls dropped from 25 per day to fewer than 5.
A machine parts exporter in Mumbai ships to customers in the GCC and Europe via DHL Express. Every international shipment requires a commercial invoice, a packing list, and an airway bill — all with the correct HS codes, declared values, and customs descriptions. Before the DHL integration, their logistics coordinator would prepare these documents manually in Word and Excel — copying item descriptions from ERPNext into the DHL template, looking up HS codes in a separate reference file, and calculating customs values. For a shipment with 8 to 12 line items, this took two to three hours. Errors in customs declarations had led to two shipment holds at Dubai Customs in the previous year, causing costly delays. After ERPNext was connected to DHL, the commercial invoice, packing list, and customs data are generated directly from the ERPNext Sales Invoice and Delivery Note. The coordinator reviews for accuracy, approves, and DHL gets the data through the API. What took two to three hours now takes twenty minutes.
An FMCG distributor in Nashik dispatched a significant portion of their orders as Cash on Delivery through multiple courier partners. The problem was reconciliation — figuring out which delivered COD orders had actually been remitted to their bank account by the courier, and which were still outstanding. Couriers remit COD collections in batches, with their own reference numbers that bear no relation to the original order number. The accounts team was getting COD remittance statements, trying to match them to outstanding Delivery Notes in ERPNext, and updating records manually. At any given time, ₹8 to ₹12 lakhs of COD collections were in various stages of "received by courier but not yet reconciled in ERPNext." After the logistics integration brought COD remittance data directly into ERPNext, every remittance batch is automatically matched to the corresponding Delivery Notes and the payment entries are created. Outstanding COD tracking is now accurate and current — always.
A pharmaceutical distributor in Kolhapur was using Shiprocket for last-mile delivery to retail pharmacies. Every day, Shiprocket would generate NDR (Non-Delivery Reports) — shipments where the delivery attempt failed because the pharmacy was closed, the address was wrong, or the recipient was unavailable. These NDRs sat in the Shiprocket dashboard, waiting for the seller to provide instructions: reattempt, return, or hold. Nobody on the distributor's team was checking the Shiprocket NDR dashboard regularly — it was not part of anyone's daily routine. Shipments would sit undelivered for five to eight days before someone noticed and gave instructions, by which point the pharmacy had already called to complain. After the logistics connector brought NDRs directly into ERPNext as alerts assigned to the relevant sales rep, the rep gets a notification the same day an NDR is raised. Resolution time dropped from five to eight days to under twenty-four hours, and the percentage of NDRs that converted to successful deliveries on re-attempt went from 48 percent to 74 percent.
The plant manager at a sugar equipment manufacturer in Sangli was responsible for 15 to 25 dispatch notes per week to customers across Maharashtra and neighboring states. Confirming delivery was entirely informal — the driver would call the dispatch office when he reached the customer, and the dispatch office would call the plant manager. If the driver forgot to call, or the office missed the call, or the delivery happened after working hours, nobody knew whether the goods had reached until the customer called to raise an invoice discrepancy. After Delhivery integration brought proof-of-delivery photographs and signatures into ERPNext as attachments on the Delivery Note, the plant manager reviews the delivery confirmation report every morning. Disputed deliveries — where a customer claims goods did not arrive — went from being a two-week investigation to a ten-minute conversation with the POD image as evidence.
Most businesses do not use one courier for everything. You might use Blue Dart for metro cities, Delhivery for rural pincodes, and DHL for exports. The connector lets you define those rules once in ERPNext — and the system applies them automatically for every dispatch.
Your warehouse team confirms the order is picked and packed in ERPNext and submits the Delivery Note.
The connector checks the destination pincode, shipment weight, product type, and service level against your routing rules to select the optimal carrier.
The selected carrier's API is called. AWB is generated and attached to the Delivery Note. Shipping label is available to print instantly.
A WhatsApp or SMS message with the tracking link goes to the customer automatically the moment the AWB is confirmed.
Delivery updates sync to ERPNext every 2 hours. On delivery, POD and status update close the Delivery Note automatically.
Indian logistics is not straightforward. Pincodes that are unserviceable on weekends, COD limits that vary by carrier, return policies that differ by channel — our connector accounts for all of it.
Tell us which couriers you use and how many shipments you process per day. We will show you how the Logistics Connector fits into your ERPNext workflow.
Book a Free Logistics Integration Call →