If you require a feed of line level status updates, we can easily set this up to come back to you via csv file. You can then pick up this file and processes it as you wish.
Here are the available fields we can use on the tracking csv file (note all of these are visible on the GetOrderStatus API call if you are using that).
| Field Name | Description | Sample Value |
|---|---|---|
| TrackingId | Unique line level id (either provided or panther generated it not) | 1023200000012 |
| ConsignmentNo | Order number | order123 |
| StatusId | Single digit character for status | B |
| StatusName | Descriptive name for status | Booked |
| DateBookedFor | Customer Delivery/Return Collection Date | |
| Exception | Boolean (either yes or no depending on status) e.g. Damaged status would be true. | 1 |
| DateCreated | Datetime stamp of the status update | 2014-08-06 13:55 |
| DateDelivered | Delivery date is successful | 2014-08-12 00:00 |
| SupplierName | Supplier collection name | Bluehouse Imports |
| SupplierCollectionDate | Supplier collection date | 2014-08-11 |
| Depot | Panther Depot that will serve this order (based on postcode/area) | Leeds |
| FailureCode | Failure status code (if an unsuccessful delivery/collection attempt has been made) | n |
| FailureDescription | Failure status description | Customer Not In |
| ScanInStatusId | Three letter code for scan IN status | RWG |
| ScanInStatusName | Descriptive name for status | Received in Warehouse – Good |
| ScanOutStatusId | Three letter code for scan OUT status | ODA |
| ScanOutStatusName | Descriptive name for status | Out for Delivery (All) |
| NoOfItems | Qty of items for the order line | 2 |
| ProductCode | SKU for the order line | sku123 |
| MinBookDays | If Pather book orders, this would be a client provided value to control first date offered | 7 |
| AdditionalOrderType | Custom field available for sending additional order classification if required | SX |
| Client_Line_Number | Custom field available for sending additional unique line number | 1234 |
Here is an example of a typical tracking csv file, we can adapt the columns visible and their display order very easily so please let us know your requirements.
Below is a breakdown of our status codes:
Standard line level status codes:
| StatusId | Description |
|---|---|
| AS | Awaiting Stock |
| B | Booked |
| C | Cancelled |
| CO | Collected |
| D | Delivered |
| DM | Damaged |
| E | Edited |
| F | Fulfilled |
| H | On Hold |
| LT | Lost In Transit |
| NC | Not Collected |
| NR | Not Received from Supplier |
| O | Open |
| OD | Out for Delivery |
| P | Partial |
| PD | Part-Delivered |
| Q | Quarantined |
| R | Refused |
| RD | ReDelivery |
| RH | Received in Hub |
| RTS | Returned to Supplier |
| SOC | Shipped to 3rd Party |
| T | TRASHED |
| UD | UnDelivered |
Barcode scanning statuses (not shown on tracking csv files by default):
| StatusId | Description |
|---|---|
| OAG | Open (Awaiting Goods) |
| ODA | Out for Delivery (All) |
| ODP | Out for Delivery (Partial) |
| OPD | Received in Warehouse (Damaged) |
| OPG | Received in Warehouse (Partial) |
| ORB | Received in Warehouse (Complete) |
| RWD | Received in Warehouse – Damaged |
| RWG | Received in Warehouse – Good |
Reason Codes
| REASON CODE | DESCRIPTION | APPLIES TO STATUS |
| BIA | Incorrect Address rebook | B |
| BRB | Regular booking | B |
| CLB | Client Rebooked | B |
| RAU | Auto Rebooked | B |
| CAC | Abusive Customer | C |
| CAR | Already Routed | C |
| CCC | Client Cancelled | C |
| CDF | Incorrect Customer Data / Fraud | C |
| CDM | Damaged | C |
| CDO | Duplicate Order | C |
| CHP | Holding Policy | C |
| CNS | No Stock | C |
| CRC | Customer Cancelled | C |
| NTF | Not To Be Fulfilled | C |
| H1 | Awaiting Cust Callback | H |
| H2 | Awaiting Client Call Back | H |
| H3 | Awaiting Scans | H |
| Q1 | Incorrect Phone No. | Q |
| Q2 | Incorrect Address | Q |
| Q3 | Unable To Contact | Q |
| Q4 | Awaiting Collection | Q H |
| Q5 | Awaiting Delivery | Q H |
| Q7 | Material Shortage | Q |
| Q8 | Missing Customs Details | Q |
| Q9 | Incorrect Weight Dims | Q |
| ad | Cannot Find Address | UD NC |
| ag | Agent Error | UD NC |
| bm | Vehicle Capacity Issue – Manually Routed | UD |
| ca | Cancelled Late (Client) | UD NC |
| cc | Cancelled Late (Customer) | UD NC |
| cd | Customer Did Not Order | UD |
| cr | Customer Rebook | B |
| d | Damaged on delivery vehicle | UD |
| da | Damaged in Warehouse/Trunk | UD |
| dp | Damaged on unpacking | UD |
| dr | Delivery Error | UD |
| f | Cancelled within SLA | UD NC |
| g | Loading error | UD |
| h | Traffic congestion/Adverse Weather | UD NC |
| i | Vehicle breakdown | UD NC |
| it | Data Error | UD NC |
| j | IT issue | UD NC |
| k | Insufficient driving time | UD NC |
| l | Incorrect customer data | UD NC |
| lh | Product Too Large/Heavy | UD NC |
| lw | Loaded onto wrong pallet/trunk | UD |
| m | Wrong item sent | UD NC |
| mc | Manually routed (VCI) | NC |
| mp | Mispick | UD |
| n | Customer not in | UD NC |
| nc | Not Collected (VCI) | NC |
| p | Cannot access address | UD NC |
| pp | Postponed out of SLA | UD NC |
| pt | Postponed within SLA | NC UD |
| q | Refused- Packaging Damaged | UD |
| r | Customer not ready to accept | UD NC |
| s | Not despatched from supplier | UD |
| sc | Service Completed | UD NC |
| sf | Suspected Fraud | UD |
| t | Vehicle Capacity Issue – Failure | UD |
| ti | Transport Issue | UD |
| u | Received damage from Client | UD |
| ur | Unable to Repair | UD NC |
| v | Misroute/Missort | UD |
| vc | Incorrect Weights & Dims | UD |
| z | Nothing To Collect | NC |