Dynamic Courier Allocation
The serviceability of a courier changes dynamically and very frequently. It is not possible to update the serviceability of all couriers in our system on a daily basis. Thus it is recommended that the next priority courier be allocated in case the AWB allocation fails due to ‘serviceability issues’
Step 1- UC provides a set of rules for deciding serviceability (Separate rules for forward & reverse serviceability)
Step 2- There are two steps in courier allocation:
-
-
Selection of Courier (based on Allocation rules). This factors in the serviceability also (visible at couriers page with 3 possible options – Any Facility to Any place, any facility to Selected Pincodes, This facility to selected pincodes)
-
AWB Number generation (4 methods – List, Global List, Manual, API)
-
Step 3- Currently, if Step 2 fails due to any reason after the success of step 1, there is no means to switch to the next courier basis the rules. This is primarily done because of cost concerns. For instance, if Courier C1 was the 1st priority due to other cost concerns, allocation of Courier C2 would mean additional cost
Step 4- Some of the reasons why Step 2 may fail are:
-
-
API Failure due to Serviceability error
-
API failure due to other reasons
-
Exhaustion of the AWB pool in the system
-
For Forward Courier Allocation/ Reverse Courier Allocation
-
The next priority courier be allocated in case the AWB allocation fails due to ‘Serviceability Error’
-
The Application layer of Uniware will read the error codes sent by courier and throw “Serviceability Error”
Note: No change for Exchange Courier Allocation
Note: You need to get in touch with us through Chat Support or KAM to check the feasibility of this in current UC account.