Order Status Details
...
GetOrderStatusDetailsResponse
Field | Description | Required | Best Practice |
OrderStatusArray | An array of order status | TRUE | TRUE |
errorMessage | Response for any error requiring notification to requestor | FALSE | TRUE - Suppliers should provide as verbose as possible error messages in responses to minimize need for support to clarify. |
OrderStatusArray
Field | Description | Required | Best Practice |
purchaseOrderNumber | The associated Purchase Order Number from the customer | TRUE | TRUE |
OrderStatusDetailArray | Array of OrderStatusDetails | TRUE | TRUE |
Order Status Detail Array
Field | Description | Required | Best Practice |
factoryOrderNumber | The associated factory sales order number (This is used in the example of internal PO splitting at the factory level) | TRUE | TRUE |
statusID 5 | Paired standard order status from allowed values | TRUE | TRUE |
statusName 5 | Textual description of statusID | TRUE | TRUE |
expectedShipDate | The expected ship date for the purchase order | FALSE | |
expectedDeliveryDate | The expected date the order should arrive at customer also known as the “in hands date” | FALSE | |
ResponseToArray 4 | An array of human contact information such as email, phone, and rep name so the distributor knows who to get in contact to fix an issue. | FALSE | |
additionalExplanation 3 | This allows further detail about the status | FALSE | |
responseRequired | True or False to determine if it is necessary to provide information back to the supplier to complete the order | TRUE | TRUE |
validTimestamp | Time of order status | TRUE | TRUE |