Shiprocket NDR Panel: How to Handle NDR

Understand the report before choosing an action

The Shiprocket NDR meaning is the same operational idea as a non-delivery report elsewhere: a courier has reported an unsuccessful delivery attempt. Your task is to establish what the buyer wants and whether the parcel can still follow that instruction. A failed attempt does not automatically mean that the order is cancelled or that a return has arrived.

This is general guidance for sellers taking orders through WhatsApp, Instagram or calls. It is not a fixed screen-by-screen walkthrough. Panel navigation, evidence requirements and courier options can change. Keep the Shiprocket support centre open as the reference for exact steps and windows in your account.

Where NDRs appear and what to check

Use the NDR area in your shipping panel to review reported delivery exceptions. Find the shipment by AWB rather than relying only on a buyer name. Note the courier, reported reason, attempt timestamp and latest tracking state. Check which requests are currently available for that parcel before making a promise to the buyer.

Keep a shared work list beside the panel if different people handle selling and shipping. It should show the order reference, buyer response, intended action, owner and next review time. The panel holds courier information; the chat may contain an address correction or an advance payment that the shipping team has not yet seen.

Contact the buyer before the panel action

Ask a short, neutral question: did the courier contact you, do you still want the parcel, and when can you receive it? If the reported issue is an address, ask for a complete corrected version. If the issue is COD, confirm the balance the buyer expects to pay. Keep the original reply rather than reducing it to an unsupported yes or no.

This conversation helps avoid sending a parcel back out while the same problem remains. An unchanged wrong address can produce another failed attempt. A refusal caused by an incorrect collection amount needs a payment check. Use the NDR reason and buyer-question table to prepare the right question for the remark.

Choose reattempt, correction or RTO

Reattempt: request another delivery when the buyer still wants the item and the shipment is eligible. Include a useful availability window and an active contact number where the provider permits them. Treat the buyer's preferred time as information for the courier, not an appointment you can guarantee.

Address or contact correction: confirm the full proposed change before submitting it through the available request. Save the old and corrected details in the order history. A different destination may require a serviceability check or another workflow. If the panel cannot accept the change, ask support rather than assuming a chat message has updated the label.

RTO: where appropriate and supported, request return to origin after checking the buyer's decision and your operating rules. Track the parcel until receipt and inspect the contents. Choosing a return request does not prove that stock is back or that associated charges have been settled.

The action window needs a live check

Act as soon as you see the exception. Read the current Shiprocket NDR processing-time guidance and check the shipment's available actions. Do not copy a deadline from an old screenshot into your team policy without checking whether it applies to the present service and state.

Set an internal review time that leaves room for contacting the buyer and submitting the request. If nobody replies, assign a person to decide the next step under your policy. Avoid treating silence as consent to an address change or a repeated reattempt. An expired or unavailable action needs support clarification, not an assumed extension.

A manual checklist you can follow today

1. Match the parcel. Open the AWB and compare it with the seller's order record. Capture the reason, timestamp and latest tracking event.
2. Assign the case. Put an owner and review time on the shared list so another team member knows who is following up.
3. Get the buyer's instruction. Retain the WhatsApp reply or accurate call note. Check the destination and COD balance where relevant.
4. Check current instructions. Use the live panel and official help for the supported action, evidence and window. Prepare the useful details before submission.
5. Submit and retain proof. Save the reference, time and acknowledgement. If submission fails, leave the case assigned and use the current support route.
6. Check the outcome. Monitor the next event. Close delivery on a verified outcome, and return handling on physical receipt and inspection.

When the buyer says nobody came

Preserve both accounts. The courier remark is evidence of what was recorded, while the buyer's timestamped reply records their account. Attach useful call logs and attempt details when raising a discrepancy through the available process. The customer-unavailable dispute guide includes messages that ask for facts and a reattempt without accusing a named person.

Keep the logistics case separate from related money checks. Read the COD remittance guide when a delivered order is waiting for settlement, and the weight discrepancy guide when a shipping adjustment needs measurements. Your team can use the Hindi NDR explanation when that makes the handoff clearer.

Where RxFlow fits alongside the courier panel

RxFlow has a Shiprocket adapter. NDR automation for Instagram and WhatsApp sellers connects the courier update with the buyer conversation and team follow-up. Account access, supported requests and approval rules are checked during assisted setup. Keep the courier panel and official support as the authority for provider-specific actions; automation does not guarantee that a request will result in delivery.

Shiprocket NDR questions