Skip to end of banner
Go to start of banner

Omni System to allow updating Return Order AWB & Transporter

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Overview

Many times due to courier activities, the return packet AWB or transporter changes. Eg, a pickup reattempt via a different courier partner.
This scenario has been handled in the Omni system by providing an update option.

Scope Of Work

  1. Adding an option in CIMS UI to update the AWB and transporter.

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.

  1. 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.

  2. Download the template. This screen takes a CSV file as input with the following fields.

    1. returnOrderId

    2. transporter

    3. trackingId

  3. 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.

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

Max limit of CSV upload 5000

  • No labels