Intellipack Platform: Manifest Feature

This document provides a comprehensive walkthrough of the new Manifest feature on the Intellipack platform. The Manifest feature enables users to manage handovers of final AWBs and handling units to courier partners from vendor locations digitally, eliminating the need for paper-based processes. This guide will take you through a step-by-step process of utilizing this feature effectively.

Step 1

Welcome! Today, we will introduce you to the new Manifest feature we are launching on our Intellipack platform.

Step 2

The Manifest is created whenever final AWBs and handling units are handed over to the courier partner from vendor locations. Previously, the process involved creating, downloading, signing, and re-uploading a manifest on the Intellipack platform as consent.

Step 3

With the introduction of the new feature, we are transitioning to a completely paperless and digital handover process.

Step 4

Previously, there was no mobile-based user interface to create manifests. This new feature introduces such an interface, and I will guide you through the manifest feature walkthrough.

Step 5

I will demonstrate each step of the process to explain how the manifest feature operates. I have logged in as a specific vendor for demonstration purposes.

Step 6

Upon logging in, select a test vendor, such as Vendor 2000. Each vendor can log in using their credentials to access their account.

Step 7

After logging in, access the Intellipack version. Select the appropriate factory location you are currently operating from, which will be required in the manifest creation process.

Step 8

Select the first factory location, and proceed to the manifest. Ensure all handling units (HUs) are packed, and the necessary documents, like invoices and e-way bills, are ready.

Step 9

Ensure the air waybills are created for the delivery partners. Navigate to the 'generate manifest' option located at the top right of the screen.

Step 10

Upon selecting 'generate manifest,' you will see a list of eligible delivery partners. Choose the one ready to collect shipments for the day.

Step 11

Within the manifest feature, manifests have only two statuses: pending and completed. Unclosed manifests will appear as pending.

Step 12

When both parties consent to closing the manifest, it moves to the completed state. As an example, we will use Test Bulk as the delivery partner.

Step 13

For the selected partner, view the list of eligible AWBs on the left-hand side. The manifest number and factory details appear on the top left-hand side.

Step 14

To create a manifest for specific AWBs eligible for the partner, start scanning the relevant HUs.

Step 15

After scanning, a green flag indicates successful addition of an HU to the manifest. Continue scanning the HUs with either a mobile scanner or handheld scanner.

Step 16

If using a mobile device, scan directly; if on a desktop, use a handheld scanner or enter manually on the available box.

Step 17

An error appears for an incorrect box ID that is not part of the manifest or AWB. I will demonstrate the error.

Step 18

The right-hand side shows an error if the HU ID is invalid. Ensure each HU is eligible before proceeding to the next.

Step 19

After scanning the correct HU ID, a green flag confirms both boxes are added. The right-hand side shows scanned AWBs and successful HUs.

Step 20

The next step is closing the manifest. Confirm the delivery person at the doorstep, responsible for collecting shipments.

Step 21

Proceed to the verification page. Capture details from the delivery partner, including name, driving license, RC book, employee ID, and phone number.

Step 22

Input the delivery partner's name, e.g., John, and upload a photo of their driving license.

Step 23

In the absence of a driving license photo, upload a placeholder, such as a bar chart.

Step 24

After uploading necessary documents, save the step, and input the delivery person's phone number.

Step 25

Ensure the system accepts a valid 10-digit phone number. A message will prompt if it's incorrect, and an OTP verification step follows.

Step 26

For phone number validation, enter the received OTP. If not received, two more attempts are permitted.

Step 27

An incorrect OTP results in an error. Upon correct entry, the vendor's Point of Contact (POC) must sign.

Step 28

The vendor POC, responsible for handing over materials, should enter their name and acknowledge receipt by the delivery partner.

Step 29

Only fully scanned AWBs are added to the manifest. Errors occur if partially scanned AWBs are included; either remove them or scan all relevant HUs.

Step 30

Confirm the handover to close the manifest. It transitions from a pending state to completed.

Step 31

In the completed state, download a copy of the manifest. Here’s what the document looks like.

Step 32

The manifest contains the ID, handover date, vendor name, delivery partner, delivery person, contact number, AWB details, and shipment quantities.

Step 33

This concludes the manifest creation process. The document is now complete.