Title Page
-
Auditor's Name
-
Site conducted
-
Conducted on
-
Location
Inbound
General Process
-
Once damaged package recevied DEX Inform the relevant team of such an incident and hand over the package to the Reverse Sort Team against email receiving.
-
Sorting at inbound is done on the basis of the 3PL partners
-
For DEX packages, fine sorting is done on the basis of weight class and destination of the packages
-
In case of any extra packages received, email is sent at the day end where the team is asked to generate a RS for extra packages
-
Mis-sorted parcels sent to wrong hub are inbounded back to sort center
-
In case of partial shipment received, RS is closed by marking the remaining packages "marked as lost" at the end of the day so that RS can auto check in.
-
If damaged package is found after inbounding, issue is highlighted with PSC and CS team via email, within 24 hours package is processed
-
FIFO is to be followed. All the packages should be stacked and labelled according to their respective receiving dates.
-
All the received packages are inbounded within 24 hours
Re-ship Audit Checklist
-
Are the LCS Packages with prefix issues highlighted to the relevant teams (Product Team) and not reshipped.
-
Are large packages with a Non Bulky Tracking number re-shipped to bulky?
Vendor and Cross Border dropoff
-
For CB, receiving is given on email containing all TN
Receive from FM Station
-
Inbounding is done on package level in the presence of Pickup Hero. However, in case of high backlog, Sort Team will initmate the FM Team within 24 hours and Route/Station will be responsible for the loss.
-
If an inbound team finds any package empty / leakage / broken / improper packaging then these packages are handed over to First Mile by escalating an email and keep in loop to CS and PSC team as well.
Line Haul Shipment
-
Truck seal information is updated on LOP app before offloading the linehaul
-
For LH, receiving is given on system generated manifest and on email to the respective facilities is sent as well
-
For 3PL LH, receiving is given on excel printout and email is sent to their facilities as well
Sort
-
Name plates are used for area wise sorting, for LM hub and 3PL partners
-
Packages are placed by sorters by viewing the port codes on airway bills
-
Flyers are stored in sacks/vertical trollies while semibulky are placed on pallets
-
DEX packages are sorted according to 1) based on same city or different city and 2) Based on last mile hub
-
3PL packages are sorted based on 3PL name irrespective of the destination.
Outbound
Dispatching
-
MUs are not overflowed with packages
-
On DEX and TCS MUs "DEX seal is used" and on LCS MUs "LCS seal is used"
-
Gate pass containing the count of MUs, is handed over to admin by LM/3PL on his departure from SC
-
Are we recording vehicle numbers against runsheets dispatched
-
Are the vehicle numbers against runsheets dispatched recorded in the correct platfom
-
Package status is updated from "TTS" to "Shipped" within 48 hours
-
In case of 3PL, package status is changed to "shipped" when booking is received by 3PL.
Forward Shipment DEX (Same City)
-
Email is dispatched to the relevant hubs containing the TN and MU# of the packages being sent
-
If the LM facility is in the same warehouse, no sealed MUs are created and packages are handed over to LM by creating a virtual linehaul.
-
If LM facility is in same warehouse no trolley from sort is brought inside LM directly and handover is only done at border of sort and LM
-
Once the LM hub receives the package, email receiving is given
Forward Shipment DEX (Differnt City)
-
Manual AWB(excel generated) is created pasted to the MUs containing the count of TN of the packages and destination
-
Email is dispatched to the relevant SC conatining the MUs, and TN of the packages being sent
-
Once the SC receives the shipment, email receiving is given
Line Haul through 3PL (Intercity)
-
System generated manifest are downloaded from 3PL website and pasted to the MUs containing the count of TN of the packages and destination
-
Email is sent to 3PL containing the MUS and TN of the packages being sent
-
Data is maintained on a specified format of all the MUs that are handed over to 3PL
-
Email is dispatched to the relevant Hubs containing the MUs, and TN of the packages being sent
-
Once the 3PL and Hubs receives the shipment, email receiving is given
Forward Shipment 3PL (Intracity)
-
Email is dispatched containing RS and TN of packages to 3PL
-
Once 3PL receives the shipment, email receiving is given
-
Receiving is also taken from 3PL on a printed manifest
-
Sort to keep the record of last 2 months PODs (Printed manifest) on which 3PL receiving is given
Problematic Scenarios at Outbound (3PL)
-
Separate excel file for each 3PL is created for Not Found/Offline/Frozen Packages(which are reshipped to 3PL). Receiving is taken on it as well
-
If shipping provider is not correct as per SOP (i.e. non-bulky (flyer/box) have OLE tracking), they are reshipped
-
If there is a data sync issue hold these packages for 24 Hrs and escalate an email to Transport Team on spot. If issue is till not fixed the package is reshipped
-
If 3PL refuses to pickup the packages due to packing issue, the case is escalated to PSC team with images, in real time
-
Email receiving of the mis-route packages are sent to the SC from the respective hubs
SOP Calculation
