Objectives
1. Improve accuracy and efficiency in the general freight despatching process.
2. Standardize integration output from Customer system.
3. Enable more advanced reporting to enable analysis such as accurate association of freight cost to orders.
How does Order Lookup work?
Complete Message Transmitter Service
- The Customer system generates a File with consignment Information on the Customer's Server. The File must be.
- CSV/XML Format
- Contain the order file Information listed below
- Limited to one file per Order
- EFM Installs a Windows Service on the Customer's Server to pick up this File and send it to our Message Transmitter Service which transforms this File into a standard Message that OneFlo can interpret.
- Customer uses OneFlo Portal to "Look up" the consignment that can now be found within the system.
Custom Message Transmitter Service
- The customer system sends an XML Payload of all required data, to a custom API End Point.
- This Payload must meet OneFlo information requirements perfectly.
- Customer uses OneFlo UI to "Look up" the consignment that can now be found within the system.
WARNING
Custom Services are only available upon evaluation and require internal approval before moving forward.
Performing Order Lookup
System Component Map
Components
Customer System
Customer's system used as the source system for order data. Provider order data is exportable into an EDI file that will act as a data feed to the Message Transmitter process
Customer Workstation
Customer uses their consigning workstations to access the OneFlo portal to be able to access OneFlo functionality.
OneFlo Portal
OneFlo is a cloud based, multi-carrier, Logistics Management System designed for consigning, manifesting & tracking consignments, tracking carrier performance & enabling logistics-based reports for analysing supply chain activity. Order Lookup is accessed via the OneFlo Portal.
OneFlo Order Integration Service
The Order Integration service is designed to increase the efficiency of the despatch process by identifying and loading order data based on EDI files. The service identifies order EDI files and loads the contents as an order into OneFlo. Once loaded the order is accessible in the OneFlo portal and upon selecting the order all order data is mapped to the consignment creation form. The population of this data reduces data entry required by the despatch teams and increases accuracy of the consignment data.
OneFlo Postback Report.
In order to populate consignment number against the original Order in efm a OneFlo Postback data file can be generated on a nightly schedule. This data file will be transferred over to Customer where a efm service will load the file data to update Orders. This function requires Customer to nominate an FTP server that OneFlo can use to place the nightly batch file.
OneFlo AutoPrint Service
The AutoPrint service reduces the time required for users to generate labels when creating a consignment. Most web portal present the document in a page and require the user to progress through a print dialog process. This service communicates with the OneFlo portal for the user accounts and recognises when a new consignment is created. OneFlo creates a print job in the cloud and the AutoPrint service recognises a new job and processes the document automatically to generate a printed label.
Customer Information Requirements
Customer order data required may vary depending on the process the Order Lookup integration is intended to achieve.
Order Level Information
Field No. | Field Name | Type | Length | Required | Description |
|---|---|---|---|---|---|
| 1 | Order Reference Number | Text/Numeric | 30 | Required | Must be Unique |
| 2 | Additional Reference | Text/Numeric | 30 | Not Required | |
| 3 | Receiver Name | Text | 30 | Required | |
| 4 | Receiver Address 1 | Text | 30 | Required | |
| 5 | Receiver Address 2 | Text | 30 | Not Required | |
| 6 | Suburb | Text | 30 | Required | |
| 7 | State | Text | 3 | Required | |
| 8 | Postcode | Text | 4 | Required | |
| 9 | Contact Name | Text | 20 | Recommended | |
| 10 | Contact Phone | Text | 15 | Recommended | |
| 11 | Contact Email | Text | 50 | Recommended | |
| 12 | Authority to Leave | Boolean | 5 | Required | true/false/blank |
| 13 | Delivery Instructions | Text | 60 | Recommended | |
| 14 | Special Instructions | Text | 60 | Not Required | |
| 15 | User Field1 | Text | 30 | Not Required | Custom fields configured in OneFlo. Defined in https://portal.oneflo.com.au/MyUserFields/Index |
| 16 | User Field2 | Text | 30 | Not Required | Custom fields configured in OneFlo. Defined in https://portal.oneflo.com.au/MyUserFields/Index |
| 17 | User Field3 | Text | 30 | Not Required | Custom fields configured in OneFlo. Defined in https://portal.oneflo.com.au/MyUserFields/Index |
| 18 | User Field4 | Text | 30 | Not Required | Custom fields configured in OneFlo. Defined in https://portal.oneflo.com.au/MyUserFields/Index |
| 19 | User Field5 | Text | 30 | Not Required | Custom fields configured in OneFlo. Defined in https://portal.oneflo.com.au/MyUserFields/Index |
Item Level Information
| Field No. | Field Name | Type | Length | Required | Description |
|---|---|---|---|---|---|
| 1 | Reference | Text | 30 | Not Required | Defined: https://portal.oneflo.com.au/MyProducts/Index |
| 2 | Code | Text | 30 | Not Required | |
| 3 | Description | Text | 30 | Not Required | |
| 4 | Items | Numeric | 5 | Not Required | number of items of this type / dims / weight |
| 5 | Length | Numeric | 5 | Not Required | in centimetres, must be whole number |
| 6 | Width | Numeric | 5 | Not Required | in centimetres, must be whole number |
| 7 | Height | Numeric | 5 | Not Required | in centimetres, must be whole number |
| 8 | Weight | Numeric | 5 | Not Required | in kilograms, can include decimal |
| 9 | Volume | Numeric | 5 | Not Required | in cubic metres, can include decimal |