Overview

It is common for courier activities to result in changes to the return packet AWB or transporter, such as a pickup reattempt via a different courier partner.
To address this scenario in the Omni system, an update option has been provided.
The update option can be accessed through the CIMS UI, which allows the AWB and transporter to be updated as needed.

Workflow

A new UI screen has been added in the CIMS module named Return Order Update.

Below steps can be followed to update the return AWB/ Transporter. The user will take a dump of return expectations from the marketplace, do a lookup from reporting, and then upload a CSV to update the return AWB/ Transporters.

Choose the client name, channel name, and fulfillment location from the respective dropdowns. These details should be chosen such that the return order to be updated belong to that client, channel, and fulfillment location.
Download the template. This screen takes a CSV file as input with the following fields.
1. returnOrderId
2. transporter
3. trackingId
Upload the CSV with the values as suggested below. Click on Submit button. Total return orders and Successful update count is shown in UI. In case of failure, a CSV would be available to download with each row and error message.

returnOrderId	transporter	trackingId
Return Order ID	The updated transporter name	The updated AWB number or Tracking number.

<aside> 🗒️ The return order with the Return Order Id present in CSV should exist in system against the selected client, channel and fulfilment location. The return order for which AWB/ transporter is getting updated should be a Non - CANCELLED status return order.

</aside>

<aside> ℹ️ Max limit of CSV upload 5000

</aside>

Integration APIs

A new API is introduced to update the status, tracking code, transporter and expected date of return order. Please refer to Update Returns API (Beta) (New API) for more details.