What’s new in Pando?


Pando works constantly to improve the experience across all our Product suites. For the month of March ‘23, here’s a summary of all the changes we are rolling out:


  • Introducing for new details to be captured for courier booking and tracking

    For shippers catering to  eCommerce through direct shipment to customers, there is a need to capture the consignee in Lorry Receipt logic as the volume of distributors or customers placing orders is substantial. To aid this, Pando now allows users to capture sold-to in the LR logic. The end recipient, or whoever the material is being "sold-to", can now be captured. This is now applicable for Courier booking and Courier tracking. 

  • New API for ERP integration 

    To make the process of placing courier smoother,  we've introduced new APIs for SafeXpress.  
    • For tracking and proof of delivery:
      API Type: Restful Service (Open API – No authentication required)
      Method: POST 

    • For creating booking:.  
      API Type: Restful Service (Open API – No authentication required)
      Method: POST  
       

      API Name

      Method

      Media-Type

      Token Generation API

      POST

      JSON

      Consignor/Consignee Creation API

      POST

      JSON

      Create LR/Waybill

      POST

      JSON



  • Revamped interfaces for payment capability for Exports and Imports

    The Freight Audits and Payments module has now been revamped to provide a better user experience for Export Import payments. The following changes have been introduced: 
    • Segregation of clean and non-clean invoices 
    • Bulk approval or auto approval for clean invoices 
    • UI indication in invoice details page for price mismatch to decrease invoice approval time 
    • Bill to entity support at the gate level, since their gates are tagged to different legal entities in the depot master.
    • The status “MISMATCHED“ has been introduced for charges that don't match in the invoice listing page. 

The bill of entry functionality under EXIM now allows shippers to approve/reject ocean and air indents. If rejected, the customs house agent or the freight forwarder is expected to revisit the bill of entry and get it approved by the shipper before it can be proceeded. 

 

  • Improved filters on the exception dashboard for the web app 

    We've now introduced vendor and SKU-based search/filter in the exception dashboard to filter out indents of a particular SKU/ vendor as on a daily basis. This is aimed at improving the experience of searching and finding the relevant indent instead of filtering it down to a list. 

 

  • Introducing newer fields in Freight Provision Payload

    With this release, source depot and gate reference ID are now included in the freight provision payload. This does away with the need for a source code without which purchase orders could earlier not be mapped in the ERP. This prevents the instances of Freight Provision Posting  getting rejected on the shipper's ERP, thereby ensuring that the Transporter's payment process is seamless. 

 

  • Providing limited access to deactivated transporters

    For transporters who have been deactivated while active indents have been assigned, Pando provides limited access to complete the indent. The transporter will have access to login, and mark the ePOD when the consignment is delivered. Similarly, they will have access to raise the invoice, deliberate on charges and receive payment for the final indent. 

 

  • Field changes in the destination charge master

    The following fields are getting modified in the destination charge master: 
    • Source field has been removed from the destination charge master.
    • A new field Remarks has been introduced. Users can now make remarks to the destination charge master. Users can also search for remarks. 

  • Freight Calculation for FTL per Ton basis

    For Full truck load shipments—both multi-pick and multidrop—calculation for per ton contracts will now be done by choosing the minimum of the base-freight of the contracts in Optima and Pay. This means, the computation will not done on the basis of the total weight of the freight, but on the basis of the slab rate that has been decided upon as a part of the contract. This is to set a minimum base freight that will be deemed acceptable by the transporter.  
     
    This logic is applicable for 4 contract types: 
    • Per trip
    • Per km
    • Per kg
    • Per ton 

  • Text changes in Invoices

    For invoices, new text changes have been introduced. If a discount has been applied on the freight cost, then the cost is represented as Total Base Value ( in words ) as opposed to Total taxable value ( in words ).

    This change will now be implemented in the following places:
    • Transporter summary slider (Invoice and Ready for billing)
    • Shipper summary slider (Invoice)
    • Changes to be reflected for both static and dynamic bill discounting
    • Invoice preview copy for both shipper and transporter
    • Client settings for static discount
    • Needs to be applicable for both static and Bill discount

      Normal invoice

      Invoice with discount on total base amount

      Total Taxable Value(Freight + Other charges)

      Total Base Value(Freight + other charges)

      Total Invoice value(Total taxable value + tax)

      Discount


      Total Taxable value(Total Base Value - Discount)


      Total Invoice value(Total taxable value + tax))