NDR Shipment Reports
The NDR Shipment-Level Reporting Schema enables users to create configurable reports for shipments that are part of the NDR shipments. It provides shipment-level visibility through a wide range of available fields, filters, and scheduling options.
Purpose
This schema is intended to help users build reports based on their specific operational and analytical requirements. Instead of using a fixed report format, users can select the required columns, apply filters, and generate reports that are relevant to their business use case.
Why It Matters
With this schema, teams can better understand NDR trends, track shipment-level actions, review customer and courier responses, and identify areas that need operational attention. It also supports recurring reporting through scheduled report generation.
About This Document
This document lists all available filters and columns in the NDR Shipment-Level Reporting Schema, along with descriptions for each field. Use it as a reference while configuring, generating, or reviewing NDR reports. We will first explain the logic behind filters and then the columns (related descriptions) which are given below:
Filters
| Filter Group | Filter Label | Column applied on | Filter Tooltip | Filter Type | Mandatory? | Values | Limitations |
|---|---|---|---|---|---|---|---|
| Delivery Type | Delivery Type | Delivery Type | Indicates whether the shipment is forward shipment or reverse pickup shipment | Multi-select Dropdown | TRUE | Forward, Reverse Pickup | |
| Date Range | Created At | Created At | Timestamp for when the shipment was created in ClickPost (in the configured timezone) | Date Range | TRUE | Default- Last 7 Days | Max date range of 3 months, future date cannot be selected |
| Order Date | Order Timestamp | Timestamp when the order was placed by the customer (if not explicitly passed, same as Created At timestamp) | Date Range | FALSE | Max date range of 3 months, future date cannot be selected | ||
| Pickup Date | Pickup Timestamp | Timestamp when the shipment was picked up from the pickup location | Date Range | FALSE | Max date range of 3 months, future date cannot be selected | ||
| Delivery Date | Delivery Timestamp | Timestamp when the shipment was delivered successfully | Date Range | FALSE | Max date range of 3 months, future date cannot be selected | ||
| RTO Mark Date | RTO Mark Timestamp | Timestamp when the Return to Origin process was marked, indicating the start of the return logistics cycle | Date Range | FALSE | Max date range of 3 months, future date cannot be selected | ||
| RTO Delivered Date | RTO Delivered Timestamp | Timestamp when the Return to Origin shipment was successfully delivered back to the original sender or warehouse | Date Range | FALSE | Max date range of 3 months, future date cannot be selected | ||
| Latest Tracking Update | Tracking Update Timestamp | Timestamp of the most recent update in the ClickPost system of the tracking status of the shipment (in the configured timezone) | Date Range | FALSE | Max date range of 3 months, future date cannot be selected | ||
| First NDR Date | NDR1 Timestamp | Timestamp corresponding to the first delivery failure | Date Range | FALSE | Max date range of 3 months, future date cannot be selected | ||
| Last NDR Date | Last NDR Timestamp | Timestamp of the most recent unsuccessful attempt to deliver the shipment | Date Range | FALSE | Max date range of 3 months, future date cannot be selected | ||
| Carrier | Carrier Partner | Carrier Partner Name | Name of the logistics partner responsible for the shipment delivery | Multi-select Dropdown | FALSE | List of carrier partner names for the enterprise | |
| Carrier Partner Account | Carrier Partner Account Name | Name of the account associated with the carrier partner | Multi-select Dropdown | FALSE | List of carrier partner account names for the enterprise | ||
| Tracking | Status | Latest Status | Current status of the shipment in ClickPost's logistics management system, indicating progress and latest updates | Multi-select Dropdown | FALSE | List of uber statuses | |
| Stuck Shipment? | Stuck Shipment? | Indicates whether the shipment is not progressing through the expected lifecycle stages (no tracking updates since the last 3 days) | Boolean Dropdown | FALSE | Yes, No | ||
| SLA Breached? | SLA Breached? | Indicates whether SLA committed by carrier partner has been breached or not (blank in case SLA is not available) | Boolean Dropdown | FALSE | Yes, No | ||
| Number of Delivery Attempts | Number of Delivery Attempts | Total number of times delivery was attempted for a shipment before it reached a terminal state | Multi-select Dropdown | FALSE | 0, 1, 2, 3, 4, 5+ | ||
| Pickup Details | Pickup Pincode | Pickup Pincode | Postal code of the pickup location | Multi-select Dropdown | FALSE | List of pincodes | |
| Pickup City | Pickup City | City of the pickup location | Multi-select Dropdown | FALSE | List of cities | ||
| Drop Details | Drop Pincode | Drop Pincode | Postal code of the delivery location | Multi-select Dropdown | FALSE | List of pincodes | |
| Drop City | Drop City | City of the delivery location | Multi-select Dropdown | FALSE | List of cities | ||
| Invoice Details | Payment Mode | Payment Mode | Mode of payment (Cash on Delivery or Prepaid) | Multi-select Dropdown | FALSE | COD, Prepaid | |
| Invoice Value | Invoice Value | Monetary amount associated with the invoice | Value Range | FALSE | |||
| NDR | Number of Failed Delivery Attempts | Number of Failed Delivery Attempts | Total number of times delivery was attempted but not successful, indicating issues in logistics and delivery coordination | Multi-select Dropdown | FALSE | 0, 1, 2, 3, 4, 5+ | |
| Customer Feedback Present? | Total Customer Feedbacks Received | Shipments where customer feedback was present | Boolean Dropdown | FALSE | Yes, No | ||
| Operational Feedback Present? | Total Operational Feedbacks Received | Shipments where operation feedback was present | Boolean Dropdown | FALSE | Yes, No |
Columns
| Field Group | Field Name | Field Description | Sample Value/s | Data type | Mandatory Field? |
|---|---|---|---|---|---|
| Order Details | AWB | Air Waybill number, unique identifier for each carrier used to track the shipment | AWB-K8F3L9Q2X7M | String | TRUE |
| Order Details | Order ID | Unique identifier of an order (can be same for multiple shipments) | ORD-7K2LM9P4Q8X | String | FALSE |
| Order Details | Reference No. | Unique identifier of a shipment in ClickPost | REF-9S2LG7C8P1E | String | FALSE |
| Order Details | Delivery Type | Indicates whether the shipment is forward shipment or reverse pickup shipment | Forward/Reverse | Enum | FALSE |
| Order Details | Created At | Timestamp for when the shipment was created in ClickPost (in the configured timezone) | 2025-01-05 10:15 | Date (UTC) | FALSE |
| Order Details | Order Timestamp | Timestamp when the order was placed by the customer (if not explicitly passed, same as Created At timestamp) | 2025-01-04 9:12 | Date (IST) | FALSE |
| Order Details | Carrier Partner Name | Name of the logistics partner responsible for the shipment delivery | Delhivery | String | FALSE |
| Order Details | Carrier Partner Account Name | Name of the account associated with the carrier partner | DEL-Primary | String | FALSE |
| Order Details | Carrier Partner via Aggregator | Carrier used to ship the product via an aggregator | Shiprocket | String | FALSE |
| Order Details | Channel Name | Name of the channel through which the order is received | Shopify | String | FALSE |
| Product Details | Number of Items | Total number of items in the shipment | 1 | Integer | FALSE |
| Product Details | Number of Boxes | Number of boxes in the shipment | 1 | Integer | FALSE |
| Product Details | Product SKU Codes | Comma separated SKU codes for the items in the shipment | SKU-AX12B9 | String | FALSE |
| Product Details | Item Names | Comma separated item names in the shipment | Wireless Mouse | String | FALSE |
| Product Details | Shipment Length | Length of the outer shipment box (in cm) | 10.5 | String | FALSE |
| Product Details | Shipment Breadth | Width of the outer shipment box (in cm) | 8.2 | String | FALSE |
| Product Details | Shipment Height | Height of the outer shipment box (in cm) | 4.5 | String | FALSE |
| Product Details | Shipment Weight | Total weight of the shipment (in g), crucial for calculating shipping costs | 0.5 | String | FALSE |
| Invoice Details | Invoice Number | Unique identifier for the invoice | INV-1001 | String | FALSE |
| Invoice Details | Invoice Date | Date when the invoice was issued | 2025-01-05 | Date (IST) | FALSE |
| Invoice Details | Invoice Value | Monetary amount associated with the invoice | 1499.99 | String | FALSE |
| Invoice Details | Currency Code | Currency used for the invoice value | INR | String | FALSE |
| Invoice Details | Payment Mode | Mode of payment (Cash on Delivery or Prepaid) | COD/Prepaid | String | FALSE |
| Invoice Details | COD Value | Amount to be collected upon delivery | 0 | Integer | FALSE |
| Invoice Details | Pricing Zone | Pricing zone associated with the shipment, determined on the basis of the uploaded pincode mapping | Local | String | FALSE |
| Invoice Details | Shipping Cost | Cost associated with shipping the order, including carrier fees and surcharges | 45 | String | FALSE |
| Pickup Details | Pickup Name | Name of the pickup location or the contact name associated with the pickup location | Rahul Sharma | String | FALSE |
| Pickup Details | PickUp Address Type | Type of pickup address such as residential or commercial | Warehouse | String | FALSE |
| Pickup Details | Pickup Pincode | Postal code of the pickup location | 110001 | Integer | FALSE |
| Pickup Details | Pickup City | City of the pickup location | New Delhi | String | FALSE |
| Pickup Details | Pickup District | District of the pickup location | Central Delhi | String | FALSE |
| Pickup Details | Pickup State | State of the pickup location | Delhi | String | FALSE |
| Pickup Details | Pickup Country | Country of the pickup location | India | String | FALSE |
| Pickup Details | Pickup Organisation | Name of the organization responsible for pickup coordination | ABC Logistics | String | FALSE |
| Pickup Details | Pickup Vendor Code | Hub code of the pickup location (not supported for all carriers) | VEND-001 | String | FALSE |
| Pickup Details | From Warehouse | Origin warehouse of the shipment | WH-DEL-01 | String | FALSE |
| Pickup Details | Taxpayer Identification Number (TIN) | Taxpayer Identification Number (TIN) of the pickup organisation | TIN1234567890 | String | FALSE |
| Drop Details | Drop Name | Contact name associated with the drop location, typically the customer name | Ankit Jain | String | FALSE |
| Drop Details | Drop Address Type | Type of delivery address such as residential or commercial | Home | String | FALSE |
| Drop Details | Drop Pincode | Postal code of the delivery location | 201001 | String | FALSE |
| Drop Details | Drop City | City of the delivery location | Ghaziabad | String | FALSE |
| Drop Details | Drop District | District of the delivery location | Ghaziabad | String | FALSE |
| Drop Details | Drop State | State of the delivery location | Uttar Pradesh | String | FALSE |
| Drop Details | Drop Country | Country of the delivery location | India | String | FALSE |
| Drop Details | Drop Organisation | Organisation where the shipment is dropped | Khanna Retail | String | FALSE |
| Drop Details | Shipment Zone | Pickup and drop pincode zone mapping based on the selected config (Order Creation or AWB Generation APIs, Uploaded Pincode Zones, or Clickpost Zone) | Local | String | FALSE |
| Tracking | Latest Status | Current status of the shipment in ClickPost's logistics management system, indicating progress and latest updates | Order Placed | String | FALSE |
| Tracking | Latest Timestamp (Carrier) | Timestamp of lastest status update received from the carrier | 2025-02-01 10:15 | Date (IST) | FALSE |
| Tracking | Latest Remark | Latest note from the carrier regarding the shipment status, providing insights into the current progress | Shipment created | String | FALSE |
| Tracking | Latest Location | Latest geographic position of the shipment | Delhi | String | FALSE |
| Tracking | Updated Timestamp | Timestamp of the most recent update in the ClickPost system of any data related to the shipment (in the configured timezone) | 2025-02-01 10:20 | Date (UTC) | FALSE |
| Tracking | Tracking Update Timestamp | Timestamp of the most recent update in the ClickPost system of the tracking status of the shipment (in the configured timezone) | 2025-02-01 10:25 | Date (UTC) | FALSE |
| Tracking | First Rider Allocated Timestamp | Timestamp when the first delivery rider was assigned to the shipment | 2025-02-01 9:45 | Date (IST) | FALSE |
| Tracking | Latest Rider Allocated Timestamp | Timestamp when the latest delivery rider was assigned to the shipment | 2025-02-01 9:50 | Date (IST) | FALSE |
| Tracking | First Rider Reached Pickup Location Timestamp | Timestamp when the first delivery rider reached the pickup location | 2025-02-01 10:05 | Date (IST) | FALSE |
| Tracking | Latest Rider Reached Pickup Location Timestamp | Timestamp when the latest delivery rider reached the pickup location | 2025-02-01 10:10 | Date (IST) | FALSE |
| Tracking | Pickup Timestamp | Timestamp when the shipment was picked up from the pickup location | 2025-02-01 10:20 | Date (IST) | FALSE |
| Tracking | Origin Hub In Timestamp | Timestamp when the shipment arrived in the initial hub | 2025-02-01 18:10 | Date (IST) | FALSE |
| Tracking | Origin Hub Out Timestamp | Timestamp when the shipment left the initial hub | 2025-02-01 22:10 | Date (IST) | FALSE |
| Tracking | Destination Hub In Timestamp | Timestamp when the shipment arrived in the last hub | 2025-02-02 8:10 | Date (IST) | FALSE |
| Tracking | First Rider Reached Drop Location Timestamp | Timestamp when the first delivery rider reached the drop location | 2025-02-04 9:10 | Date (IST) | FALSE |
| Tracking | Latest Rider Reached Drop Location Timestamp | Timestamp when the latest delivery rider reached the drop location | 2025-02-04 9:20 | Date (IST) | FALSE |
| Tracking | Delivery Timestamp | Timestamp when the shipment was delivered successfully | 2025-02-04 9:45 | Date (IST) | FALSE |
| Tracking | Receiver's Name | Name of the person collecting the order upon delivery | Ankit Sharma | String | FALSE |
| Tracking | Stuck Shipment? | Indicates whether the shipment is not progressing through the expected lifecycle stages (no tracking updates since the last 3 days) | No | String | FALSE |
| Tracking | Committed SLA by Carrier | Service Level Agreement timeframe committed by the carrier for shipment delivery | 2 days | String | FALSE |
| Tracking | SLA Breached? | Indicates whether SLA committed by carrier partner has been breached or not (blank in case SLA is not available) | No | String | FALSE |
| Tracking | Ageing from SLA Breach | Duration since the Service Level Agreement (SLA) was breached, indicating how long a shipment has been delayed beyond agreed terms | 0 | String | FALSE |
| Tracking | Order to Delivery TAT | Time taken for a shipment from the order date to successful delivery | 48 | String | FALSE |
| Tracking | Order to Pickup TAT | Time taken for a shipment from the order date to pickup | 12 | String | FALSE |
| Tracking | Pickup To OFD1 TAT | Time taken for a shipment from pickup to the first OFD (Out For Delivery) attempt | 24 | String | FALSE |
| Tracking | OFD1 to Delivery TAT | Time taken for a shipment from the first OFD (Out For Delivery) attempt to successful delivery | 12 | String | FALSE |
| Tracking | Pickup to Delivery TAT | Time taken for a shipment from pickup to successful delivery | 36 | String | FALSE |
| Tracking | RTO AWB | Return to Origin Air Waybill number (if different from the original AWB) | RTO-AWB-1001 | String | FALSE |
| Tracking | RTO Mark Timestamp | Timestamp when the Return to Origin process was marked, indicating the start of the return logistics cycle | 2025-02-05 10:00 | Date (IST) | FALSE |
| Tracking | RTO Delivered Timestamp | Timestamp when the Return to Origin shipment was successfully delivered back to the original sender or warehouse | 2025-02-07 10:30 | Date (IST) | FALSE |
| Tracking | OTP Verified Cancellation? | Indicates whether the order cancellation was verified using a One-Time Password | No | String | FALSE |
| Failed Delivery Attempts | Number of Delivery Attempts | Total number of times delivery was attempted for a shipment before it reached a terminal state | 1 | Integer | FALSE |
| Failed Delivery Attempts | Number of Failed Delivery Attempts | Total number of times delivery was attempted but not successful, indicating issues in logistics and delivery coordination | 0 | Integer | FALSE |
| Failed Delivery Attempts | Total Notifications Triggered | Total number of NDR-related notifications trigerred for this shipment | 3 | Integer | FALSE |
| Failed Delivery Attempts | Total Notifications Successful | Total number of NDR-related notifications trigerred successfully for this shipment | 3 | Integer | FALSE |
| Failed Delivery Attempts | Total Feedbacks Received | Total number of feedbacks (customer + operational) received for this shipment | 1 | Integer | FALSE |
| Failed Delivery Attempts | Total Customer Feedbacks Received | Total number of customer feedbacks received for this shipment | 1 | Integer | FALSE |
| Failed Delivery Attempts | Total Operational Feedbacks Received | Total number of operational feedbacks received for this shipment | 0 | Integer | FALSE |
| Failed Delivery Attempts | Total Instructions Sent | Total number of instructions sent to the carrier partner for this shipment | 2 | Integer | FALSE |
| Failed Delivery Attempts | Total Instructions Delivered | Total number of instructions succesfully delivered (via API or File) to the carrier partner for this shipment | 2 | Integer | FALSE |
| Failed Delivery Attempts | Total Instructions Delivered via API | Total number of instructions succesfully delivered via API to the carrier partner for this shipment | 1 | Integer | FALSE |
| Failed Delivery Attempts | Total Instructions Adhered | Total number of instructions adhered by the carrier partner for this shipment | 2 | Integer | FALSE |
| NDR1 Details | OFD1 Timestamp | Timestamp indicating the first attempt made to deliver the shipment | 2025-02-01 9:30 | Date (IST) | FALSE |
| NDR1 Details | NDR1 Case ID | The NDR case ID for the first failed delivery attempt | NDR1001 | String | FALSE |
| NDR1 Details | NDR1 Timestamp | Timestamp corresponding to the first delivery failure | 2025-02-01 14:10 | Date (IST) | FALSE |
| NDR1 Details | NDR1 Reason | Bucketized NDR reason for the first failed delivery | Customer Unavailable | Enum | FALSE |
| NDR1 Details | NDR1 Remark | Remark for the first failed delivery | consignee unavailable due to unforseen circumstances | String | FALSE |
| NDR1 Details | NDR1 No. of Notifications Triggered | Total number of notifications trigerred for the first failed delivery attempt | 2 | Integer | FALSE |
| NDR1 Details | NDR1 Notifications Triggered Channels | Channels through which notifications were trigerred for the first failed delivery attempt (comma separated) | SMS, Email | Enum | FALSE |
| NDR1 Details | NDR1 No. of Notifications Successful | Total number of notifications successfully trigerred for the first failed delivery attempt | 2 | integer | FALSE |
| NDR1 Details | NDR1 Notifications Successful Channels | Channels through which notifications were successfully trigerred for the first failed delivery attempt (comma separated) | SMS, Email | Enum | FALSE |
| NDR1 Details | NDR1 Feedbacks received Channels | Total number of feedbacks (customer + operational) received for this particular NDR count | AI Agent,Brand,Tracking Page | String | FALSE |
| NDR1 Details | NDR1 No. of customer feedbacks | Total number of customer feedbacks received for this particular NDR count | 1 | Integer | FALSE |
| NDR1 Details | NDR1 No. of operation feedbacks | Total number of operational feedbacks received for this particular NDR count | 1 | integer | FALSE |
| NDR2 Details | OFD2 Timestamp | Timestamp indicating the second attempt made to deliver the shipment | 2025-02-02 9:20 | Date (IST) | FALSE |
| NDR2 Details | NDR2 Case ID | The NDR case ID for the second failed delivery attempt | NDR2001 | String | FALSE |
| NDR2 Details | NDR2 Timestamp | Timestamp corresponding to the second delivery failure | 2025-02-02 14:30 | Date (IST) | FALSE |
| NDR2 Details | NDR2 Reason | Bucketized NDR reason for the second failed delivery | Customer Not Available | Enum | FALSE |
| NDR2 Details | NDR2 Remark | Remark for the second failed delivery | Second attempt failed | String | FALSE |
| NDR2 Details | NDR2 No. of Notifications Triggered | Total number of notifications trigerred for the second failed delivery attempt | 2 | Integer | FALSE |
| NDR2 Details | NDR2 Notifications Triggered Channels | Channels through which notifications were trigerred for the second failed delivery attempt (comma separated) | SMS, Email | Enum | FALSE |
| NDR2 Details | NDR2 No. of Notifications Successful | Total number of notifications successfully trigerred for the second failed delivery attempt | 2 | integer | FALSE |
| NDR2 Details | NDR2 Notifications Successful Channels | Channels through which notifications were successfully trigerred for the second failed delivery attempt (comma separated) | SMS, Email | Enum | FALSE |
| NDR2 Details | NDR2 Feedbacks received Channels | Total number of feedbacks (customer + operational) received for this particular NDR count | AI Agent,Brand,Tracking Page | String | FALSE |
| NDR2 Details | NDR2 No. of customer feedbacks | Total number of customer feedbacks received for this particular NDR count | 1 | Integer | FALSE |
| NDR2 Details | NDR2 No. of operation feedbacks | Total number of operational feedbacks received for this particular NDR count | 1 | integer | FALSE |
| NDR3 Details | OFD3 Timestamp | Timestamp indicating the third attempt made to deliver the shipment | 2025-02-03 9:10 | Date (IST) | FALSE |
| NDR3 Details | NDR3 Case ID | The NDR case ID for the third failed delivery attempt | NDR3001 | String | FALSE |
| NDR3 Details | NDR3 Timestamp | Timestamp corresponding to the third delivery failure | 2025-02-03 14:15 | Date (IST) | FALSE |
| NDR3 Details | NDR3 Reason | Bucketized NDR reason for the third failed delivery | Customer Not Available | Enum | FALSE |
| NDR3 Details | NDR3 Remark | Remark for the third failed delivery | Third attempt failed | String | FALSE |
| NDR3 Details | NDR3 No. of Notifications Triggered | Total number of notifications trigerred for the third failed delivery attempt | 2 | Integer | FALSE |
| NDR3 Details | NDR3 Notifications Triggered Channels | Channels through which notifications were trigerred for the third failed delivery attempt (comma separated) | SMS, Email | Enum | FALSE |
| NDR3 Details | NDR3 No. of Notifications Successful | Total number of notifications successfully trigerred for the third failed delivery attempt | 1 | integer | FALSE |
| NDR3 Details | NDR3 Notifications Successful Channels | Channels through which notifications were successfully trigerred for the third failed delivery attempt (comma separated) | Enum | FALSE | |
| NDR3 Details | NDR3 Feedbacks received Channels | Total number of feedbacks (customer + operational) received for this particular NDR count | AI Agent,Brand,Tracking Page | String | FALSE |
| NDR3 Details | NDR3 No. of customer feedbacks | Total number of customer feedbacks received for this particular NDR count | 1 | Integer | FALSE |
| NDR3 Details | NDR3 No. of operation feedbacks | Total number of operational feedbacks received for this particular NDR count | 1 | integer | FALSE |
| NDR4 Details | OFD4 Timestamp | Timestamp indicating the fourth attempt made to deliver the shipment | 2025-02-04 9:25 | Date (IST) | FALSE |
| NDR4 Details | NDR4 Case ID | The NDR case ID for the fourth failed delivery attempt | NDR4001 | String | FALSE |
| NDR4 Details | NDR4 Timestamp | Timestamp corresponding to the fourth delivery failure | 2025-02-04 14:05 | Date (IST) | FALSE |
| NDR4 Details | NDR4 Reason | Bucketized NDR reason for the fourth failed delivery | Returned to Origin Initiated | Enum | FALSE |
| NDR4 Details | NDR4 Remark | Remark for the fourth failed delivery | Marked for RTO | String | FALSE |
| NDR4 Details | NDR4 No. of Notifications Triggered | Total number of notifications trigerred for the fourth failed delivery attempt | 1 | Integer | FALSE |
| NDR4 Details | NDR4 Notifications Triggered Channels | Channels through which notifications were trigerred for the fourth failed delivery attempt (comma separated) | Enum | FALSE | |
| NDR4 Details | NDR4 No. of Notifications Successful | Total number of notifications successfully trigerred for the fourth failed delivery attempt | 1 | integer | FALSE |
| NDR4 Details | NDR4 Notifications Successful Channels | Channels through which notifications were successfully trigerred for the fourth failed delivery attempt (comma separated) | Enum | FALSE | |
| NDR4 Details | NDR4 Feedbacks received Channels | Total number of feedbacks (customer + operational) received for this particular NDR count | AI Agent,Brand,Tracking Page | String | FALSE |
| NDR4 Details | NDR4 No. of customer feedbacks | Total number of customer feedbacks received for this particular NDR count | 1 | Integer | FALSE |
| NDR4 Details | NDR4 No. of operation feedbacks | Total number of operational feedbacks received for this particular NDR count | 1 | integer | FALSE |
| NDR5 Details | OFD5 Timestamp | Timestamp indicating the fifth attempt made to deliver the shipment | 2025-02-05 9:15 | Date (IST) | FALSE |
| NDR5 Details | NDR5 Case ID | The NDR case ID for the fifth failed delivery attempt | NDR5001 | String | FALSE |
| NDR5 Details | NDR5 Timestamp | Timestamp corresponding to the fifth delivery failure | 2025-02-05 14:20 | Date (IST) | FALSE |
| NDR5 Details | NDR5 Reason | Bucketized NDR reason for the fifth failed delivery | Returned to Origin Initiated | Enum | FALSE |
| NDR5 Details | NDR5 Remark | Remark for the fifth failed delivery | Final attempt failed, marked RTO | String | FALSE |
| NDR5 Details | NDR5 No. of Notifications Triggered | Total number of notifications trigerred for the fifth failed delivery attempt | 1 | Integer | FALSE |
| NDR5 Details | NDR5 Notifications Triggered Channels | Channels through which notifications were trigerred for the fifth failed delivery attempt (comma separated) | Enum | FALSE | |
| NDR5 Details | NDR5 No. of Notifications Successful | Total number of notifications successfully trigerred for the fifth failed delivery attempt | 1 | integer | FALSE |
| NDR5 Details | NDR5 Notifications Successful Channels | Channels through which notifications were successfully trigerred for the fifth failed delivery attempt (comma separated) | Enum | FALSE | |
| NDR5 Details | NDR5 Feedbacks received Channels | Total number of feedbacks (customer + operational) received for this particular NDR count | AI Agent,Brand,Tracking Page | String | FALSE |
| NDR5 Details | NDR5 No. of customer feedbacks | Total number of customer feedbacks received for this particular NDR count | 1 | Integer | FALSE |
| NDR5 Details | NDR5 No. of operation feedbacks | Total number of operational feedbacks received for this particular NDR count | 1 | integer | FALSE |
| Last NDR Details | Last NDR Timestamp | Timestamp of the most recent unsuccessful attempt to deliver the shipment | 2025-02-05 14:20 | Date (IST) | FALSE |
| Last NDR Details | Last NDR Reason | Reason for the most recent unsuccessful attempt to deliver the shipment, indicating the cause of the failure | Returned to Origin Initiated | String | FALSE |
| Last NDR Details | Last NDR Remark | Notes regarding the most recent unsuccessful attempt to deliver the shipment, including reasons for failure and any relevant comments | Final attempt failed, marked RTO | String | FALSE |
| Last NDR Details | Last Customer Response | The most recent NDR-related customer feedback received for this shipment | Reattempt | Enum | FALSE |
| Last NDR Details | Last Feedback Source | The source of the most recent NDR-related customer feedback received for this shipment | AI Agent | Enum | FALSE |
| Last NDR Details | Last Feedback Timestamp | Timestamp of the most recent NDR-related customer feedback | 2025-02-05 15:00 | Date (UTC) | FALSE |
| Last NDR Details | Last NDR Reason Customer Confirmation? | Indicates whether or not the customer agreed to the most recent NDR reason mentioned by the carrier partner | Yes/No | Enum | FALSE |
| Return Details | Return Name | Contact name associated with the location to which the package should be returned in case of non-delivery | Rahul Sharma | String | FALSE |
| Return Details | Return Pincode | Postal code for the return location | 110001 | String | FALSE |
| Return Details | Return City | City of the return location | New Delhi | String | FALSE |
| Return Details | Return State | State of the return location | Delhi | String | FALSE |
| Return Details | Return Country | Country of the return location | India | String | FALSE |
Updated 7 months ago
