A Consignee can be defined as the 3rd-party entity or the unit which receives the shipments sent by the Shipper through a Transporter. The Consignee master in Pando helps maintain all the Dealer/Retailers involved in placing Sales orders and act as the receiving location in Secondary movement.
Movements consignee can be part of:
When secondary, a consignee can be the destination
In return movement, a consignee is the source
When a Sales order is created, the consignee is provided as input to the ‘Ship To’ field.
TABLE OF CONTENTS
Accessing Consignees in Pando
To access the list of all consignees in Pando, go to > Data Manager and select Consignees from the drop down. This brings up the list of Consignees that are currently available on your Pando account.
Creating a Consignee in Pando
Pando enables shippers to create Consignees in one of the following ways:
To create a Consignee individually, click the Add button and provide relevant details. Once you’ve added the relevant details, click . This creates the Consignee.
To understand details about all fields that are covered under consignee, check the Field glossary at the end of the article.
You can create consignees in bulk by uploading them in an .xlsx file. Click the UPLOAD dropdown and download the Sample format file. This file contains all the fields— mandatory and optional— in the format that needs to be uploaded. Add the consignee fields values to this file and upload it back to Pando by clicking Bulk Upload and selecting the updated file.
Once the upload is completed, you will be presented with the Success notification that indicates the completion of the operation and the number of consignees that have been created and the ones that have been rejected.
To identify the files that have failed and to understand the reason behind their failure, click . This downloads the rejection list. The rejection list file contains the reason for rejection of a record. Fix the reason behind the import failure and upload the file back to Pando to finish uploading all consignees into Pando.
While Pando allows you to create Consignees both individually and in bulk, the number of Consignees involved in secondary movement tends to be of a very high number. New Dealers also get added to a shipper’s repository as and when new orders are placed. Hence, Shippers also prefer to create New Consignees through an integration between Pando and their ERP.
This can be implemented by setting up an API call between Pando and the ERP.
NOTE: The aforementioned fields are mandatory in Pando. These field values will have to be sent as a part of the API payload to create a record. When a value on any of these fields are missed, record creation will fail.
This means, whenever a new consignee is created in the ERP, if an integration is set in place, the ERP will trigger an API push that will create the same Consignee on Pando as well.
API triggers can also be used to update existing Consignee records on Pando from the Shipper’s ERP.