System Default Mapping (NDR)

Using this document, users can understand the system default mapping for carriers within Shipsy

Instructions

Follow the given steps to understand how to access and understand the Default Carrier NDR Mapping saved within Shipsy:

Navigating to Integration Setup > Carrier Tracking

1. Click on the hamburger menu icon

2. Select setup and from the sub menu, select integration setup

3. From the drop down, select carrier partner

4. In the carrier partner setup, click on the carrier tracking tab

Understanding NDR Mapping

1. When navigating to the carrier tracking tab, users will by default land on the status mapping sub tab

2. To navigate to NDR mapping, click on the Failure Reason Mapping tab

3. Here, on the left, they will be able to see the list of all available carrier partners that have been setup

4. Also visible will be the type of tracking used by these carrier partners - API based or webhook based

5. On the right side of the screen, a tabular view will be visible a different set of tabs

6. The first tab for any carrier partner will always be titled Shipsy-[Name of the Carrier]

7. This tab denotes the default mapping that has been done within Shipsy for said carrier partner

8. This simply means, that within Shipsy, a set of defaults have been mapped to every failure reason code used by the carrier partner to ensure seamless carrier tracking without any errors in interpreting the different failure reasons shown by the carrier partner

A standard mapping is used within Shipsy to ensure that a 3PL integration can be made seamlessly. However, if required, users also have the capability of creating their own mappings that suit their business requirements.

Additionally, in the case of Delivery Failure Reasons, users also have the functionality of setting up their own failure reasons as per their use case.

Setting Up Custom Failure Reasons

1. Navigate to Setup > Admin > Appflow Config > Master Setup

2. Click on the Task Failure Reasons Tab

3. Click on the add new reason button

4. Input the required details in the add new reason form:

   1. Reason ID - Nomenclature of the reason stored within the system

   2. Name of the Reason - Name of the reason shown to end customers

   3. Reason Category - Category under which reason is to be clubbed

   4. Status - Active/Inactive

   5. Task Type - Delivery/Reverse Pickup/Forward Pickup

   6. Additional Selection - Reschedule/Is Partial

5. Once the user inputs all the required information, they can save a new failure reason

6. These reasons can also be mapped to 3PL reasons by creating a custom failure reason mapping for a 3PL