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
Product workflow
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:
Individually:
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.
In Bulk:
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.
Through Integrations:
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.
COMMAND | POST |
Endpoint URL | https://<domain.name>pando.in/inbound/api/masters/consignee |
Payload |
"name": " Zendex enterprises Stirling Central Scotland", "reference_number": "ZN-10-CTRL", "address": "29, 7th Street, Judyshire, Stirling, Central Scotland", "city": "Stirling", "state": "Central Scotland", "pincode": "411892", "region": "13", "mobile_number": "9023463519", "email": "purchase@zendex.com", "customer_type": "Customer Site" |
|
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.
Field Glossary
Field
(Fields marked * are mandatory) | Purpose | Field Format | Mapped to Module/Field |
Consignee Name* | Add the consignee's name. This is usually the name of the locality or region in which the consignee is situated in. For example: Zendex enterprises Stirling Central Scotland | Alphanumeric | |
Reference ID* | Provide a unique reference code to the Consignee. This ID will be reflected on all the contracts and will need to be a unique value that is used to associate with the Consignee. For example: ZN-10-CTRL | Alphanumeric | |
Address | Provide your consignee's address | Alphanumeric |
|
City* | The city which the consignee is based out of. It has implications for determining the type of movement. For eg, City-State, City-Point, City-Region etc. Provide a valid City name. The validation is carried out based on the list configured in the list | Alphanumeric | |
State* | The state which the consignee is based out of. It has implications for determining the type of movement. For eg, State-City, State-Point, State-Region etc. Provide a valid State name. The validation is carried out based on the list configured in the list | Alphanumeric | |
Region* | Choose between one of 4 regions— North, South, East, West. For consignees that have gates located in different regions, this has implications. Be sure to call out the region of the consignee. | Alphanumeric | |
Country | Add the name of the country. This has implications when determining whether the movement comes under EXIM | Alphanumeric | |
Postal Code | Provide a valid pincode based on your country.
For example, if the consignment location is based out of India, provide a valid 6 digit pincode. The validation is carried out based on the list configured in the masters | Number | |
Group | Payment groups enable agglomeration of multiple consignees under a single group. When several Consignees are aggregated under a single Payment group, this enables creation of consignment charges that are charged to the group as a whole instead of created on the basis of multiple contracts for individual consignees. | Dropdown | |
Category | Consignee Category—Optima |
| |
Logistics SPOC - Email ID | Provide an email address for additional point of contacts at the consignee location in order to provide visibility into shipments and also aid with coordination in case of delays or discrepancies.
| Alphanumeric
|
|
Logistics SPOC - Mobile Number | Provide a mobile number for additional point of contacts at the consignee location in order to keep visibility into shipments and will also serve for coordination.
| Number
|
|
Representative Name | Add the name of the representative who will be receiving the consignment at the consignee destination/location. | Text |
|
Representative Mobile | Provide a mobile number of the representative who will be receiving the consignment at the consignee destination/location. This will help with coordination in case of discrepancy and delays | Number |
|
Representative Email | Add the email address of the representative who will be receiving the consignment at the consignee destination/location. | Text |
|
Exclude Truck Type | Select from the list of trucks to mark whether a particular vehicle should be barred from being assigned orders earmarked for this consignee.
Examples:
a) If a Consignee lacks the capacity to handle large trucks on their premises, the truck types can be excluded for the consignee. Optima will take this constraint into consideration while planning and will never add the excluded truck to an indent earmarked for the consignee
b) If the Shipper has a ‘Tanker’ in their fleet serving Primary movements, and if it needs to be avoided for any shipments planned to the consignee, excluding the vehicle type for the consignee will prevent any indents with the Tanker vehicle being created when earmarked for the respective consignee. | Dropdown | |
Sales Contact Name | Provide the point of contact from the Shipper's sales team. | Text |
|
Sales Contact Mobile | Provide a mobile number of the salesperson from the Shipper's side who will be in charge of sending the shipment. This will help with coordination in case of discrepancy and delays | Number |
|
Sales Contact Email | Add the email address of the salesperson from the Shipper's side. | Text |
|
Customer Logistic Leader | Add the User who is in charges of the logistics operations for the Shipper. This is usually a Logistics operations executive who has been added a user on Pando and has access to the Pando instance. You can select the user from the dropdown. | Dropdown
Select User |
|
Loading Start Time | The earliest time every day when loading operations will be permitted at the consignee location.
Significance: Is used by Optima for scheduling indents. | Time (HH:MM) | Optima |
Loading End Time | The latest time every day by which loading operations will need to be completed at the consignee location.
Significance: Is used by Optima for scheduling indents. | Time (HH:MM) | Optima |
Unloading Start Time | The earliest time every day when loading operations will be permitted at the consignee location.
Significance: Is used by Optima for scheduling indents. | Time (HH:MM) | Optima |
Unloading End Time | The earliest time every day when unloading operations will be permitted at the consignee location.
Significance: Is used by Optima for scheduling indents. | Time (HH:MM) | Optima |
Status* | Select whether the consignee is active or inactive | Dropdown |
|
Ports Associated | Select the nearest or the most relevant ports through which the goods to the consignee can be shipped to and received from. This field holds significance if your consignee will be receiving imports. | Dropdown | Optima |
Display Reference Name | Add a display name that will be used for ease of identification while routing. For example: instead of calling your consignee ZN-10-CTRL, you could simply choose to display the Consignee name as the city, say, Stirling while displaying the route. | Name |
|
EPOD Group | Electronic Proof of Delivery— Group the delivery to multiple delivery locations/warehouses under a single legal entity. This is an EPOD group. So, when a delivery is made to one of the EPOD locations, the sign off can be made from any of the locations
In case a Retailer/ Dealer is involved in Modern trade and has multiple stores opened in different locations managed by a single SPOC, these consignees registered in Pando can be grouped together so that their indents/shipments can be tracked from a single user login for ease of use. | Dropdown | |
Combine | When Combine is turned ON, the delivery orders of different Consignees are clubbed together while creating indents via optima in vendor movement. | Toggle |
|
Delivery Do Not Combine | When this setting is turned ON, the delivery orders of those Consignees will not be combined together, in turn planned in separate shipments/indents by Optima even though the Consignees belong to the same route. | Toggle |
|
Overseas Customer | Helps track whether the consignee is an overseas customer or domestic. This has an impact on Optima configurations. | Toggle | |
