The following features were introduced in this release:


  • Inbound Integration Dashboard 

The latest update to the Inbound Integration Dashboard addresses the previous lack of visibility for rejection responses within the Integration, offering users a clearer understanding of transaction outcomes. This enhancement introduces configurable features for separate Outbound and Inbound settings, consolidates Inbound Integration rejections alongside Outbound ones, maintains the Excel file format, and displays each transaction as a distinct line item for easier tracking. Additionally, it introduces a Depot Filter, allowing users to streamline data viewing, while enabling enhanced filtering for specific Inbound Transactions like Material Invoice, POD, Direct Dispatch, and Bulk Indent. MITM-related details have been excluded to focus on refining the user experience. These improvements aim to empower users with greater control and comprehension of their inbound integration processes.


  • E-Invoice should be verified with the Pando Invoice

The Transporter follows Pando's invoice process: after shipper approval, the status is "Checked." E-Invoices apply to the Two-Step Approval flow only. The Transporter generates an e-invoice in the GST portal, gets the IRN number from the Government portal, and inputs both in Pando. Pando verifies these details; matching leads to "APPROVED," while discrepancies prompt email notifications for IRN validation-related rejections. The Shipper can accept or reject in Pando UI (configurable roles). Accepted invoices move to "APPROVED"; rejected ones need the Transporter to amend in the government portal and Pando, keeping them interim until revised.

  • Role based access management in dashboard

The dashboard in the product has now been revamped to introduce role-based access to customize access levels based on users' roles and association. This ensures appropriate data visibility and control inside the product and limits access to sensitive information. The following changes have been implemented:

  • Depot users linked to a specific depot can access only the particular depot's data.
  • Regional managers have access only to those depots that fall under their supervision. 
  • Super admins will have access to all depots in the organization.


  • Two-factor authentication for the transporter portal

Transporter portal now has two-factor authentication enabled during login. Upon entering the correct email ID and password, a six-digit OTP (One-Time Password) will be sent to the user's email address. This OTP will only be triggered if the provided email ID and password are accurate; otherwise, the system will display the standard error message. Subsequently, users will encounter a new screen prompting them to input and verify the received OTP. Access to login will only be granted if the entered OTP is successfully validated; otherwise, users will be redirected to the login screen with an error message indicating an OTP mismatch. Additionally, an option will be available on the OTP validation screen to resend the OTP if necessary.


  • User Master Integration

The User Master now has integration support. This means, data related to creation and maintenance of users can be updated via ERP integration. Details such Role, Status, and User Permission can be mapping with the available options in the master list. The API supports the creation and update of user data on Pando. Additionally, it also includes capability to deactivate a user through integration.

{
  "data": [
    {
      "username": "abhijit",
      "status": "active",
      "role": "admin",
      "phone": "9898989892",
      "email": "abhijit@pg.com",
      "user_permission": "inbound"
    },
    {
      "username": "balaje",
      "status": "active",
      "role": "admin",
      "phone": "9898989492",
      "email": "balaje@pg.com",
      "user_permission": "both"
    }
  ]
}


  • Transporter Mobile app

The ability to view the LR attachment and E-LR document has now been extended to the Transporter Mobileapp

  • Carbon Emission Factor

Carbon Emission Factor has now been introduced as a non-mandatory field to the Vehicle master. This field will help capture emission factor details that are captured in the client ERP. It can now been sent to Pando via upload, API, or through UI edits. The field can accommodate both positive integers and decimals, with decimals rounded off to two digits.