The NDR list
Search by waybill, consignee, or invoice. Filter by seller. Each row shows the courier on the order, origin and destination, rejection reason, remark, and attempt count.
For logistics operations
NDR management for your logistics operation
When a shipment is not delivered, the logistics team needs one place to see it and decide what happens next. ShipRabbit keeps those cases on an NDR list for the business that runs the sellers and the courier accounts.
What an undelivered shipment creates
A delivery attempt can fail. The shipment is still in the network, and someone on the logistics team has to know which one it is, which seller it belongs to, and what the courier recorded as the reason.
Follow-up may mean contacting the seller or the consignee, asking for another attempt, or sending the shipment back. If those cases live in separate courier portals and inboxes, the team loses the thread. A single list is how the operation keeps the decision attached to the waybill.
What the ShipRabbit desk provides
NDR records enter the platform when the aggregator uploads a CSV of waybills, for B2B or B2C. A row is kept only when it matches an order already on that account. The list then sits next to the seller and shipment work the same business already runs.
Re-attempt and RTO requests
On a record, the team records a re-attempt request or an RTO request. The action, the person, and the time stay on that record. The seller is emailed when the aggregator records it, and the aggregator is emailed when the seller records it.
Seller context
Aggregators see NDRs across the sellers they operate and can export the filtered list. A seller sees the undelivered shipments on their own account and can record the same two requests.
Status alongside the shipment
Shipment status and public tracking stay available for follow-up. The NDR record is the operational decision. It does not replace the tracking view, and it does not perform the delivery.
How a case moves through the desk
- 1
The aggregator uploads a CSV of undelivered waybills and chooses B2B or B2C. Rows that match orders on the account become NDR records.
- 2
The team finds the shipment on the list by waybill, consignee, or invoice, and can narrow it to one seller.
- 3
They review the seller, the courier on the order, the rejection reason, the remark, the cities, and the attempt count.
- 4
Where another delivery try is the decision, they record a re-attempt request on that record.
- 5
Where delivery will not be completed, they record an RTO request. The history of actions stays on the shipment.
- 6
Tracking remains available for operational follow-up. Recording the request does not itself run the courier attempt or the return.
Courier partners do not all accept the same follow-up from a platform screen. ShipRabbit stores the request the team made. It does not assume every connected courier will act on that request the same way.
Who this desk is for
The page is for the business that operates the logistics network: courier aggregators, logistics companies, and 3PL or shipping operators who manage sellers and shipments. Sellers are the accounts on that network. They can see and act on their own undelivered shipments. They are not the buyer this page is written for, and this is not a consumer help page.
Tracking
Tracking answers what the current shipment status is. Public lookup for a waybill is on the track page . Website tracking for a seller’s own site is previewed on the tools page .
NDR management
NDR management answers what the logistics team should do about a shipment that could not be delivered: review it, record a re-attempt, or record a return to origin.
One part of the platform
NDR sits inside the same ShipRabbit account as shipments, sellers, rate cards, COD, and tracking. The platform is the technology layer. The logistics business still owns the brand, the courier relationships, and the deliveries.
Frequently Asked Questions
What is NDR management?
NDR means a delivery attempt did not complete. NDR management is the desk where a logistics business lists those shipments, reviews the reason and the seller, and records a re-attempt or return-to-origin request.
What can I manage from ShipRabbit when a shipment is not delivered?
An aggregator uploads a CSV of waybills for B2B or B2C. Rows that match orders already on the account appear on the NDR list, with the seller, courier, consignee, rejection reason, cities, and attempt count. The team can search, filter by seller, export the list, and record a re-attempt or RTO request. The request stays on the record, with who recorded it and when.
Does ShipRabbit handle the physical delivery?
ShipRabbit is the platform the logistics business uses. The business and its courier partners handle pickup and delivery. Recording an NDR action on the desk does not itself send someone out for another attempt.
Can NDR shipments be re-attempted?
The desk can record a re-attempt request, or an RTO request, on an NDR record. That request is stored for the team. Whether the courier then attempts again depends on that courier relationship. The screen does not push the same action to every courier.
How does NDR relate to RTO?
RTO means return to origin. On this desk it is one of the two requests a team can record when delivery will not be completed. Re-attempt is the other. The record keeps the action and who recorded it.
Work the undelivered list from the same platform
Start a 7-day trial or book a demo. The trial uses the existing aggregator registration.