Manifest Feature in Intellipack Platform

The Manifest feature in the Intellipack platform allows users to manage shipments efficiently by providing a digital record of the items being transported from the manufacturing vendor to the courier partner. Recent updates have enhanced the mobile usability of this feature, introducing a streamlined mobile user interface.

 

Step 1

In this video, we will introduce the Manifest feature available on the Intellipack platform. The Manifest serves as a document or digital record detailing the shipment or collection of items transported from the manufacturing vendor to the courier partner. While the Manifest feature was already present in the Intellipack platform, this video will cover recent updates made to enhance its functionality.

 

Step 2

A significant update to the Manifest feature is its mobile-friendly interface. This video will focus on the newly launched mobile user interface for the Manifest feature.

 

Step 3

Let's begin with a walkthrough of the mobile-based UI for the Manifest feature. Upon logging into the vendor portal, users need to select the vendor code they are operating under. For this demonstration, the vendor code 2000 is selected.

 

Step 4

Next, users must select the factory code. Once selected, they will arrive at the Manifest page, which features two different tabs.

 

Step 5

The two tabs available are "Pending Manifest" and "Completed Manifest." For manifest generation, users should navigate to the Manifest Generate point located on the right bottom tab. Then, they need to select a suitable delivery or courier partner present at their doorstep to create a manifest.

 

Step 6

Upon selecting a courier partner for manifest generation, the Generate Manifest page will open. At the top, users will see the manifest number and a status indicating that delivery partner verification is pending.

 

Step 7

A vendor point of contact (POC) must complete delivery partner verification before closing the manifest. The list of AWBs eligible for that courier partner is displayed, allowing the vendor POC to scan and manage any issues within the consignment for handover to the specific courier partner.

 

Step 8

In this particular AWB, there are two issues. The scanning process of the available boxes is demonstrated here. Once a box is successfully scanned, a confirmation message will appear, indicated by a green dot in the window.

 

Step 9

Next, scan another box available in the manifest. Once all items are scanned, a respective message will display. If a wrong item is scanned, not present in the manifest, an error message will indicate the absence of such items in the manifest.

 

Step 10

It is observed that only one box among the AWB in the manifest has been scanned. The system will not allow closure of such AWBs unless all issues are scanned before closing the manifest.

 

Step 11

The system will display an error before manifest closure if requirements are not met. Before closure, complete the delivery partner verification process by providing details such as the delivery person's full name, contact number, driving license photo, vehicle RC book photo, and employee ID card.

 

Step 12

Enter the full name of the driver present to collect the shipments, along with their phone number. Capture a photograph of the driver's license.

 

Step 13

Upload a photo of the RC book of the vehicle present to collect the consignment.

 

Step 14

The RC book and driving license uploads are mandatory. Also, upload a photo of the driver's employee ID card. If the ID card is not available, a picture of the vehicle with a clearly visible vehicle number can be provided.

 

Step 15

Proceed to verify the driver's contact number. If the driver does not receive the OTP, it can be resent up to three times.

 

Step 16

In case of an invalid OTP, an error message will be displayed. After verifying the delivery partner details, the manifest can be closed. Only completely scanned AWBs will be included in the manifest upon closure.

 

Step 17

Enter the full name of the vendor POC present to hand over the shipments.

 

Step 18

If incomplete AWBs are present in the manifest, the system will generate an error. To close the manifest, remove all incompletely scanned AWBs. Once removed, these AWBs cannot be added to the same manifest again.

 

Step 19

Create a new manifest for any outstanding AWBs. Once all necessary AWBs are completely scanned, proceed to closure. The completed manifest will then appear under the "Completed Manifest" tab.

 

Step 20

The manifest copy, available for download, will include essential details such as the manifest ID, handover date, vendor name, delivery partner name, delivery person name, contact number, and all AWBs with relevant issue details.