Review your historical shipment data for Return to Origin (RTO), SLA breaches, and Failed, and Stuck shipments. This information is utilized to generate dynamic carrier recommendations if weightage and feedback are enabled in the allocation process.
Following is the screenshot of the default view when you visit the Feedback Ingestion section.
This section will give you visibility of the performance of the courier partner corresponding to which the shipment was stuck, failed, SLA was breached and the shipment got RTO. Briefing the available options below for reference.
- Return To Origin: This section will examine the historical Return to Origin (RTO) percentages for each carrier within specific lanes, where lanes represent unique combinations of pickup and drop locations.
You can filter out the data based on courier partner, drop locations and pick up locations accordingly for richer analytics.
- SLA Breach: This section will help you to analyze the historical percentages of SLA breaches for various carriers within specific lanes, where lanes denote unique combinations of pickup and drop locations.
You can filter out the data based on courier partner, drop locations and pick up locations accordingly for richer analytics.
- Failed Shipments: This section will provide the count of shipments that carriers were unable to deliver. Utilize this information to identify trends across different carriers and geographical locations.
You can filter out the data based on courier partner, drop locations, and pick up locations accordingly for richer analytics.
Stuck Shipments: This indicates the count of shipments that were historically stuck, meaning there were no scans from the carrier for a consecutive number of days. Utilize this data to analyze trends across various carriers and geographical locations.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article