NDR: the last point where a return is still preventable
A non-delivery report means the courier tried and failed. What happens next is usually decided by nobody — the parcel ages out of the attempt window and comes back as an RTO you pay for twice.
One queue, with the reason attached
Couriers report why a delivery failed: the customer did not answer, the address could not be found, the customer asked for a different day, the customer refused. Those reasons demand different responses, and they are useless sitting in a portal nobody opens daily.
Kaarobar collects every NDR into one working queue with the courier's reason, the customer's history and the order's value on the same row — so the decision is made with the two facts that matter: how likely this delivers, and how much it is worth if it does.
Three explicit outcomes
Deciding early is itself the saving. A parcel held in a network for a week costs storage and delay on both sides, and a reattempt on an order the customer has already replaced elsewhere buys nothing.
Why this sits next to the profit page
An NDR queue in isolation is an operations tool. Next to the profit ledger it becomes an economic one: the app already knows the margin on that order, the customer's RTO history and what a reattempt costs. A reattempt on a low-margin order to a customer who has refused twice is not a close call once all three numbers are on the same screen.
See it on your own orders — install freeQuestions merchants actually ask
- What does NDR stand for?
- Non-delivery report — the courier's record that a delivery attempt failed, along with the reason. It is the stage before a parcel becomes an RTO.
- Can reattempts be automated?
- Reattempt, hold and return are actions you take from the queue. Automatic reattempt rules are on the roadmap; they are deliberately not the default, because an automatic reattempt on a refusal is a second freight charge for a parcel that was never going to land.