Bluedart HIH Exchange
Bluedart's Hand-in-Hand (HIH) exchange service enables a simultaneous forward delivery and reverse pickup in a single trip to the customer's doorstep. The delivery agent delivers the new product to the customer and picks up the old item — with an optional quality check at the doorstep — in one visit.
Forward Courier Partner ID: 5
Reverse Courier Partner ID: 28
How the Exchange Flow Works
Bluedart's exchange flow requires two separate API calls to Clickpost — one for the reverse pickup and one for the forward order. The two legs are linked via the reverse AWB.
Here is the end-to-end flow:
Step 1 — Customer initiates exchange The client's system receives an exchange request from the customer on their website/app.
Step 2 — Fetch SR Number The client system calls its own API to fetch the Service Request (SR) Number for the exchange request. This SR Number is required in the next step.
Step 3 — Create Reverse Pickup on Clickpost The client calls the Clickpost Reverse Pickup API to create the reverse pickup order. Key points:
- Pass
"EXCHANGE"in theorder_typefield. - Pass the SR Number (from Step 2) in the
reference_numberfield. - Pass the client order ID in the
order_idfield. - The pickup address is the customer's address; the drop address is the client system warehouse address.
- Share all QC fields in the format specified by Clickpost.
- Share the drop details and the address of the client system warehouse location.
This call returns the Reverse AWB.
Step 4 — Create Forward Order on Clickpost The client calls the Clickpost Forward Order Creation API (v3) to create the forward order. Key points:
- Pass the Reverse AWB generated in Step 3 in the
exchange_rvp_awbfield. This links the two legs. - Pass
"COD"or"PREPAID"in theorder_typefield (not"EXCHANGE"). - Use the same
order_idas the reverse pickup created in Step 3 — this is how Clickpost latches the forward and reverse shipments together.
This call returns the Forward AWB.
Step 5 — Store both AWBs The client stores both the Forward AWB and Reverse AWB in their system. Tracking for both AWBs works independently.
Operational Flow (Bluedart Network)
Once both orders are created on Clickpost, the operational sequence on the Bluedart network is as follows:
- Forward pickup: Bluedart picks up the forward shipment from the client warehouse. Tracking activates on the Forward AWB.
- Delivery attempt: At the customer's address, the Bluedart field executive attempts delivery of the forward shipment and simultaneously initiates the reverse pickup.
- Quality Check (QC) at doorstep:
- QC Pass: The forward shipment is delivered (
Delivered— terminal state). The reverse journey begins; tracking updates activate on the Reverse AWB and Bluedart agents carry the reverse shipment to the client system warehouse. - QC Fail: The exchange fails. The forward shipment is returned to the client location (RTO). The reverse pickup does not happen.
- QC Pass: The forward shipment is delivered (
- Reverse shipment delivered: Once the reverse shipment reaches the client system warehouse, it reaches its terminal state of
Delivered— completing the exchange.
Tracking
- Tracking for the Forward AWB and Reverse AWB is available and updated independently.
- To correlate the forward and reverse shipments for a given exchange, use the shared
order_idto look up both shipments together. - Tracking updates for the Reverse AWB only begin after the Forward AWB is delivered successfully (QC Pass).
Technical Notes for Bluedart Exchange
| Parameter | Detail |
|---|---|
| Pickup Type for Forward shipment | E |
| Pickup Type Reverse shipment | OE |
| Exchange Waybill No (Forward) | The Reverse AWB must be mapped under the Exchange Waybill No field on the forward shipment. |
Forward order order_type | COD or PREPAID |
Reverse order order_type | EXCHANGE |
| Order ID | Must be the same for both forward and reverse orders to latch them together. |
| QC Fields | All Dynamic QC array fields must be correctly mapped to the QC questions in the format specified. |
| Forward shipment identifier | An exchange identifier is printed on the physical forward shipment so it can be identified across the network until final delivery. This is verified by the RVP-OPS team. |
| Shipping data | Shipping data for both forward and reverse shipments is shared by the shipper, integrated into Clickpost, and processed further from there. |
Notes
- The reverse pickup request must always be created before the forward order, as the Reverse AWB is required in the forward order payload (
exchange_rvp_awb). - Both orders must share the same
order_id— this is the key linkage between the forward and reverse legs in Clickpost. - QC is performed by the Bluedart delivery agent at the customer's doorstep. Ensure the
dynamic_qcarray in the reverse pickup payload is correctly populated with the right QC questions and format. - If QC fails, the forward shipment will be returned to the client (RTO); no reverse pickup will occur.
- The client system warehouse address must be passed as the drop address in the reverse pickup request.
Updated 5 months ago
