Resources
Import Specifications for Routing Orders
Route planning order data is a required element for the Syntelic Route Planning system. These records typically represent aggregate order lines (quantity, cube, weight, pallets, etc) for each delivery to be planned for shipment. Alternatively, multiple routing orders can be generated for each stop if it is desirable to break out quantities by product types, trailer compartment, container type or other criteria that is relevant to the route planning process.
Order data is typically generated daily (once or multiple times based on order cut-off times) and transferred to the route planning system for processing.
More guidelines for the formatting of imports can be found here: Import Formatting Guidelines
A summary of the attributes importable for each Routing Order are summarized in the table below. Some data fields are optional, but others are required, as indicated by the asterisk (*).
| FIELD NAME | DESCRIPTION | DATA TYPE | LENGTH |
|---|---|---|---|
| Ship Date* | Invoice date or delivery date of the order. | Date/Time | |
| Division ID* | Identifier of the owner Division of this transaction record. | Text | 25 |
| ID* | Unique identifier of the order record. | Text | 25 |
| Location ID* | Customer ID of the order addressee. | Text | 25 |
| Bill To ID | Optional bill-to-ID different from above. | Text | 25 |
| Route ID | Identifier of the route or load associated with the order. | Text | 25 |
| Stop Number | Number identifying the sequence of the delivery within the route. | Numeric | |
| Commodity or PRoduct Type | Used when route planners require more detailed information about each delivery’s order. | Text | 25 |
| Invoice or Order ID | Invoice number of the order record | Text | 25 |
| Quantity* | Cases or sale units. | Numeric | |
| Cube* | Total cubic volume of the order. | Numeric | |
| Weight* | Total weight of the order. | Numeric | |
| Pallets | Total number of pallets. | Numeric | 25 |
| Special Instructions | Text | 200 | |
| Flexible Columns | Optional field(s) as defined by the client. | Text, Numeric, Boolean, Date | Variable |