Note the first table not a completed despatch / fulfilment record - it only lists the key fields that are captured initially
Field | Note |
Despatch Record Identifier | Internally generated |
Required Date | |
Related Order Number (s) | If created (and thus attached) to a production order, the job identifiers will be listed here |
Despatch Description | |
Despatch Source Type | Indicates origin of despatch requirement |
Web ordfer Numnber | where requirement originates from webstore |
Despatch Status | |
Despatch Sent Status | |
Allocated Status | |
Picked Status | |
Delivery Note | |
Ready Status | |
Sent Status | |
Ready to Invoice status | |
Financial approved status |
A despatch requirement needs address details of where the despatch is going and courier method
This is not likely to be populated at the point of job order creation
Field | Note |
Delivery Address Details | |
Recipient Name | |
Recipient Telephone | |
Recipient Mobile | |
Delivery Address : Street | |
Delivery Address : Town | |
Delivery Address : County | |
Delivery Address : Post Code | |
Delivery Address : Country | |
Courier Information | |
Consignment Number | |
Courier Information | |
Qty Boxes | |
Required Date | |
Required Time | |
Web Type | OTS. POD Both |
Shopify Deliver Method | |
Shopify Deliver Method |
Field | Notes |
SKU | |
Description | |
Weight | |
Price Based on weigh indicator | |
Expected QTY | |
Available QTY | |
Required QTY | |
To be Given Quantity | |
Allocaed QTY | |
Allocated Status | |
Picked QTY | |
Picked Status |
A despatch requirement can have one or more charge records
Field | Notes |
Delivery Identified | |
Charge Type | |
Charge Description | |
Produced Qty | |
Unit Price | |
Total Price |