Self-serve order data import
Uploading order data for Event
Order data provides the ability to upload a set of orders into Event...
Add new, update, despatch or cancel,...all can be processed thought self-serve order data import
For those customers with no IT development ability but prefer not to add all orders manually, you can use the Event Self Serve Order import.
Create 'once-a-day' order files or drip feed new orders and updates throughout the day. Using this self service process through Event, you can decide...
How does it work?
Using the template below, add your order numbers, to and from addresses, quantities, dates and import...
Using AMI, your digital worker, you have 2 options for entering orders through the Self Service process:
-
Let AMI do the routing
AMI will consolidate your orders, build shipments, allocate the best carrier and equipment option and create the route.
Currently only 1 Stop per route.
You can then combine any routes to maximise load fill.
This is Events Semi-autonomous routing (SAR) function
AMI - fully autonomous routing (FAR)
Fully autonomous, multi stop, multi account routing.
Using AMI, we have developed our own in-house multi carrier heuristics to seamlessly and quickly route your orders for you.
coming Q4 2021...
-
Do your own routing
AMI will consolidate your orders and build shipments but you can tell her through the Order file the Route numbers to use, carrier and equipment type to route on and the sequence for your multi Stop routes.
Here you must add Carrier ID, equipment type for the carrier and Stop sequence number. Just as if you had routed it in Event!
coming Q4 2021...
Once the orders have been validated and successfully imported you can manually affect them in Route as required.
Order import templates
These are default templates to help assist you in building import files.
Please use them as guides.
When using Event's Self Serve order import the prefix is the most import field to get correct.
-
Prefix
this field determines how your digital worker AMI, will schedule your orders.
Each time you import an Order file, AMI will process exactly as you ask.
Provide a duplicate NEW order, AMI will duplicate the order.
-
Updating
Each Self serve order file should include only valid order detail.
For example, if you initially imported 50 NEW orders and are updating just 12 of them, just import a file with the 12 UPDATES.
You can of course mix NEW, UPDATES, CANX and DESPATCH all in the same order import file
Standard template - NEW. This would be an example of your 1st import file
Template showing basic information - NEW orders
AMI will process and allocate to your carriers
Notes:
Revenue_Owner = this is only for multi account connections. Leave blank if you have not connected CREATE ORDER. You can view this in ACCOUNT VITALS - Network Connections
Custom_Ref = If you have used the custom reference function in Create Order, then to use in the import file you must replace the Custom_Ref in the header with the name of your custom reference.
i.e. Custom reference = GL CODE, rename Custom_ref1 to GL CODE
Standard template - UPDATE. This would be an example of your 2nd import file
Template showing basic information - UPDATE / DESPATCH orders
AMI will process and allocate to your carriers
What is an order prefix?
The order file will require an order prefix. This prefix tells us the state of the order so AMI knows how to process it correctly.
-
NEW
The 1st time an order number [and line number combination, where Line number is used] is imported into Event.
-
UPDATE
Any change to an order [line number combination] that is already scheduled in Event. This could be quantity, products, address, booking time, date.....
-
DESPATCH
Operationally, at some point the order will be despatched on a vehicle for delivery. The despatched status required you to populate the Despatched Quantity field rather than the Quantity field.
This is different to an UPDATE in that we are showing a despatched quantity for the order. This allows Event to report on the estimated used during the routing stage against what was actually sent.
-
CANX
Any orders that need to be removed as no longer required can be set with this status.
The pre-requisite for a CANX is a NEW (there can be numerous UPDATES after the NEW.
Notification during the self serve process
During the import of a file, you will receive notification updates on validation failures / success.
There are 3 different notifications that you can subscribe to through your profile. We suggest you do this before you start to use Self Serve order import. To find out how click here
-
File import success
-
File import failure
-
Exception
This system exception can be used to provide to 3t Support to help with any issue more than just validation
So what happens once the import is successful?
When you have received a notification as seen below.....
...AMI has successfully validated and imported the order file and will now be building shipments and routes. They will start to be visible in ROUTE immediately.
During the routing process, if for any reason AMI is unable to match a carrier to a route for example, these orders will be placed in 'Unallocated' with a reason for the failure. You will need to tale remidial action to manually correct / route these.
How to build an Order file
What are the available inputs
Validation
Initial validation that must be passed to proceed;
CORRECT HEADERS / ORDER COLUMNS
Validation will fail if the headers and columns are named differently to the template or in different order.
Validation error message ' Column headers are not named correctly'
Specific validation
All these columns must be left in the import file.
Not required = can be left blank
1. REVENUE_OWNER
Not required. Format = the Account ID from Account Vitals
Only required if using Multi Account functionality
2. ORD_STATUS
Is required. Format is NEW, UPDATE, CANCEL
These status will be used to push through integration process which is expecting these status and has the functionality / rules to process.
Where the user has added a status of NEW, UPDATE, CANCEL and there is a value in the DESP_QTY show this message
3. ORD_NO
Is required. Format = number / letters
Valid this field for duplicates. We cannot import duplicates.
If their are duplicates and no LINE_NO used then validation error =
Validation error message 'ORDER_NO error. Duplicate ORD_NO found. Please use LINE_NO or remove duplicate'
4. LINE_NO
Is required. Format = number (e.g 1 or can include '_' (1_01)
Valid this field based on duplicates in the ORD_NO field.
If their are duplicates for the combination of ORD_NO and LINE_NO used then validation error =
Validation error message 'LINE_NO error. Duplicate ORD_NO and LINE_NO found. Please remove duplicate'
5. COLL_DATE
Is required. Format is date only, not time
Validation error message 'COLL_DATE error. Collection date required or in the incorrect format. Format required is 01/01/1900.'
6. COLL_TIME
Not required. If added must be in time format 00:00, no seconds
If added validation is based on time format.
Validation error message 'COLL_TIME error. Please add a valid time, example 09:00'
7. DEL_DATE
Is required. Format is date only, not time
Validation error message 'COLL_DATE error. Collection date required or in the incorrect format. Format required is 01/01/1900.'
8. SRC_NAME
Is required. Must be a valid format. Numbers and letters
Same process for currently importing and adding / validating address.
Validation error message 'SRC_NAME error. Valid Source Name required'
This could be any address, not just Account address.
9. SRC_ADDRESS_1
Is required. Must be a valid format. Numbers and letters
Same process for currently importing and adding / validating address.
Validation error message 'Valid Source Address Line 1 required''
10. SRC_ADDRESS_2
Not required. Default is blank. This is only if customer adds
No validation error.
11. SRC_TOWN
Is required. Must be a valid format.
Same process for currently importing and adding / validating address.
Validation error message 'SRC_TOWN error. Valid Source Town required''
12. SRC_POSTCODE
Is required. Must be a valid format.
Same process for currently importing and adding / validating address.
Validation error message 'SRC_POSTCODE error. Valid Source Postcode required''
13. SRC_REGION
Not required.
Same process for currently importing and adding / validating address.
No validation error
14. SRC_STATE
Is required if country = US. Must be a valid format. Can be code or name. Validate against Country = if US.
Same process for currently importing and adding / validating address.
Validation error message 'SRC_STATE error. Valid Source State required as Country is US''
15. SRC_COUNTRY
Is required. Must be a valid format. Must be name, not code
Same process for currently importing and adding / validating address.
Validation error message 'SRC_COUNTRY error. Valid Source Country or code required'
example = United Kingdom
16. SRC_COUNTRY_CODE
Is required.
example = GB
17. DEST_CODE
Not required.
18. DEST_NAME
Is required. Must be a valid format. Numbers and letters
Same process for currently importing and adding / validating address.
Validation error message 'DEST_NAME error. Valid Destination Name required'
This could be any address, including Account address.
19. DEST_ADDRESS_1
Is required. Must be a valid format. Numbers and letters
Same process for currently importing and adding / validating address.
Validation error message 'DEST_ADDRESS_1 error. Valid Destination Address Line 1 required''
20. DEST_ADDRESS_2
Not required. Default is blank. This is only if customer adds
No validation error.
21. DEST_TOWN
Is required. Must be a valid format.
Same process for currently importing and adding / validating address.
Validation error message 'DEST_TOWN error. Valid Destination Town required''
22. DEST_POSTCODE
Is required. Must be a valid format.
Same process for currently importing and adding / validating address.
Validation error message 'DEST_POSTCODE error. Valid Destination Postcode required''
23. DEST_REGION
Not required.
Same process for currently importing and adding / validating address.
No validation error
24. DEST_STATE
Not required unless US. Must be a valid format. Can be code or name. Validate against Country = if US.
Same process for currently importing and adding / validating address.
Validation error message 'DEST_STATE error. Valid Destination State required as Country is US'
25. DEST_COUNTRY
Is required. Must be a valid format. Must be name, not code
Same process for currently importing and adding / validating address.
Validation error message 'DEST_COUNTRY error. Valid Destination Country or code required'
i.e United States
26. DEST_COUNTRY_CODE
Is required. Must be a valid format. Must be code, not name.
If not added we will lookup and use from our lookup.
Validation error message 'DEST_COUNTRY_CODE error. Valid Destination Country or code required'
i.e. US
27. DEST_CONTACT_NAME
Not required.
If added, validation error message if other than letters
Validation error message 'DEST_CONTACT_NAME error. Please use only letters'
28. DEST_CONTACT_PHONE
Not required.
If added, validation error message if other than digits are used.
Validation error message 'DEST_CONTACT_PHONE error. Please use only numbers'
29. DEST_CONTACT_EMAIL
Not required.
If added, validation error message if not a valid email format
Validation error message 'DEST_CONTACT_EMAIL error. Please add a valid email format'
30. SEGMENT
Not required
Can be added and stored in Segment in database.
31. HU_ID
Not required.
If added add to order.
No validation or check.
32. HU_TYPE
Required
Add to order.
No validation or check
= ITEM or UK PALLET
33. PLN_QTY
Is required
As a whole number
34. DESP_QTY
Not required
35. WEIGHT_UNIT
Required
Must be a valid unit from Event. kg, Ibs
Validation error message 'WEIGHT_UNIT error. Must be Kgs or Ibs.'
36. WEIGHT
Is required
Number upto 6 digits
Validation error message 'WEIGHT error. Must be a number upto 6 digits.
37. VOLUME
Not required
We will calculate on adding SO to database if not added using DIMS.
If added use.
Validation error message 'VOLUME error. Must be a number upto 3 digits.'
38. DIM_UNIT
Required
Must be a valid unit from Event. example: mm
Validation error message 'DIM_UNIT error. Must be mm, cms, m, inches.'
39. HEIGHT
Required
If added must be added in format of a number i,e 1200. No letters i.e. 1200mm
Validation error message 'VALUE error. Must be added in format 0000.'
40. LENGTH
Required
If added must be added in format of a number i,e 1200. No letters i.e. 1200mm
Validation error message 'VALUE error. Must be added in format 0000.'
41. WIDTH
Required
If added must be added in format of a number i,e 1200. No letters i.e. 1200mm
Validation error message 'VALUE error. Must be added in format 0000.'
42. VALUE
Not required.
For customs value
If added must be added in format 12.25
Validation error message 'VALUE error. Must be added in format 00.00.'
43. STACK_ON_TOP
Not required. If added added as Yes or No.
Validation error message ' STACK_ON_TOP error. Must be 'Yes' or 'No'.
44. STACK_ON_OTHER
Not required.
If added added as Yes or No.
Validation error message ' STACK_ON_TOP error. Must be 'Yes' or 'No'.
45. SKU_CODE
Not required unless using INCAB
Same validation as in Create Order
No validation error
SKU code in Event
46. SKU_NAME
Not required unless using INCAB
Same validation as in Create Order
No validation error
SKU name in Event
47. SKU_DESCRIPTION
Not required unless using INCAB
Same validation as in Create Order
No validation error
SKU_DESCRIPTION name in Event
48. SKU_QUANTITY
Not required unless usig INCAB
Same validation as in Create Order
No validation error
SKU_QUANTITY name in Event
49. ADR_CODE
Not required
Same validation as in Create Order
Validation error 'ADR_CODE error. Must be in format UN 0000'
ADR_CODE name in Event
coming Q3 2020...
50. ADR_DESCRIPTION
Not required
Same validation as in Create Order
ADR_DESCRIPTION name in Event
coming Q3 2020...
51. BOOKING_TIME_START
Not required. If added must be in time format 00:00, no seconds
If added validation is based on time format.
Validation error message 'BOOKING_TIME_START error. Please add a valid time, example 09:00'
coming Q3 2020...
52. BOOKING_TIME_END
Not required. If added must be in time format 00:00, no seconds
If added validation is based on time format.
Validation error message 'BOOKING_TIME_START error. Please add a valid time, example 09:00'
coming Q3 2020...
53. BOOKING_REFERENCE
Not required.
No validation as anything can be added
coming Q3 2020...
54. ADDITIONAL_INST
Not required.
If added just add to order.
This is Additional Instructions in Event
coming Q3 2020...
55. CARRIER_ID
Not required. Validation is a check against the connected carriers in the Account to find a match.
If added must be validated against STOP_NO and ROUTE_NO. If none of these then error message is
Validation error message ' ROUTE_NO error. No valid STOP_NO and / or ROUTE_NO added. Please add these to use this function.'
Validation error message ' CARRIER_ID error. You are not connected to this Carrier. Please invite them. to proceed.'
When added and validation passed we will use this information to create a route
If no rates then the route, stop and orders will be placed into unallocated with error message saying 'Route No [from file] had no carrier rates available'.
If availability added but none remaining create the route.
coming Q3 2020...
56. EQUIPMENT_TYPE
Not required
If added validate as per rate card process
Validation error message 'EQUIPMENT_TYPE error. Please use an Equipment type from your equipment table'
coming Q3 2020...
57. SERVICE_LEVEL
Not required.
If added just add to order.
This is Service in Event
coming Q3 2020...
58. ROUTE_NO
Not required
Not required. Validation is a max 13 digits. Unique to that day and Account.
If added must be validated against STOP_NO and CARRIER_ID. If none of these then error message is
Validation error message ' ROUTE_NO error. No valid STOP_NO and / or CARRIER_ID added. Please add these to use this function.'
Validation error message ' ROUTE_NO error. ROUTE_NO must be a number.'
When added and validation passed we will use this information to create a route, with a carrier and a Stop.
coming Q3 2020...
59. STOP_NO
Not required. Validation is a number. 2 digits
If added must be validated against ROUTE_NO. If no ROUTE_NO then error message is
Validation error message ' STOP_NO error. No valid ROUTE_NO and / or CARRIER_ID added. Please add these to use this function.'
Validation error message ' STOP_NO error. STOP_NO must be a 2 digit number.'
When added and validation has passed the ROUTE from the ROUTE_NO is created this indicates the Stop position. If Stop is 1, then add this Stop to the Route_NO in position 1.
coming Q3 2020...
60. BAY_NO
Not required.
If using then validation must be made of the COLL_DATE and COLL_TIME field at the same time.
Look up DOCK schedule to check date and time is valid for the Account DOCK. Is there a templated slot.
If not slot for the date time use error,
Validation error message ' COLL_TIME error. Your DOCK does not support this COLL_DATE / COLL_TIME combination'
The Bay name or number can be added here.
If bay number 2 is added for example, check that there is a valid Bay in position 2, regardless of name.
If the Bay number is not available use the error,
Validation error message ' BAY_NO error. There is no Bay for the requested Date / time in position 2. Please correct'
The Bay name or number can be added here.
If bay name, ARTIC ONLY is added for example, check that there is a valid Bay name for the account on that day and time for ARTIC ONLY.
If the Bay name is not available use the error,
Validation error message ' BAY_NO error. There is no Bay for the requested Date / time called ARTIC ONLY. Please correct'
coming Q3 2020...
61. DIRECTION
Not required. Validation is against BAY_NO being used. If it is that validation = INBOUND or OUTBOUND
Validation error message ' DIRECTION error. Please use INBOUND or OUTBOUND.'
coming Q3 2020...
62. SEAL_NO
Not required. Validation is against BAY_NO being used. If it is that validation = a number / letters (upto 30 characters)
Validation error message ' SEAL_NO error. Please use a number letter format upto 30 characters.'
coming Q3 2020...
63. WHS_NOTES
Not required
User can add notes. These will be added as free text to the WHS Notes section in DOCK on the Booking.
coming Q3 2020...
64. DOCK_STATUS_1_DATE
65. DOCK_STATUS_1_TIME
66. DOCK_STATUS_2_DATE
67. DOCK_STATUS_2_TIME
68. DOCK_STATUS_3_DATE
69. DOCK_STATUS_3_TIME
70. DOCK_STATUS_4_DATE
71. DOCK_STATUS_4_TIME
72. DOCK_STATUS_5_DATE
73. DOCK_STATUS_5_TIME
74. DOCK_STATUS_6_DATE
75. DOCK_STATUS_6_TIME
76. DOCK_STATUS_7_DATE
77. DOCK_STATUS_7_TIME
All the above
Not required. If using then validation must be to check ROUTE_NO field.
If this is added then lookup to get correct DOCK schedule and slot.
coming Q3 2020...
78. INVOICE NUMBER
Not required. Validation is against BAY_NO being used. If it is that validation = INBOUND or OUTBOUND
Validation error message ' DIRECTION error. Please use INBOUND or OUTBOUND.'
79. BILL OF LADING
Not required. Validation is against BAY_NO being used. If it is that validation = INBOUND or OUTBOUND
Validation error message ' DIRECTION error. Please use INBOUND or OUTBOUND.'
80. DELIVERY NAME
Not required. Validation is against BAY_NO being used. If it is that validation = INBOUND or OUTBOUNDValidation error message ' DIRECTION error. Please use INBOUND or OUTBOUND.'
81. POD NUMBER
Not required. Validation is against BAY_NO being used. If it is that validation = INBOUND or OUTBOUNDValidation error message ' DIRECTION error. Please use INBOUND or OUTBOUND.'
82. PO NUMBER
Not required. Validation is against BAY_NO being used. If it is that validation = INBOUND or OUTBOUNDValidation error message ' DIRECTION error. Please use INBOUND or OUTBOUND.'
83. CUSTOMER_REF_NUMBER
Not required. Validation is against BAY_NO being used. If it is that validation = INBOUND or OUTBOUNDValidation error message ' DIRECTION error. Please use INBOUND or OUTBOUND.'
84. CUSTOM REF1
85. CUSTOM REF2
86. CUSTOM REF3
87. CUSTOM REF4
88. CUSTOM REF5
89. CUSTOM REF6
90. CUSTOM REF7
91. CUSTOM REF8
92. CUSTOM REF9
93. CUSTOM REF10
94. CUSTOM REF11
95. CUSTOM REF12
96. CUSTOM REF13
97. CUSTOM REF14
Not required
The above are only required if using custom references in Create Order configuration
Parts data
How does it work?
Parts data can be used where no Handling units can be provided in the OMF.
It is a last resort, as this data should always be provided by the customer.
Standard template - Parts.
Template showing basic information.
note: Each tab is specific
Once the above file is completed, it can be uploaded in IMPORT, in the specific Parts upload.
There are 2 ways to deal with imported pats data:
-
If the part is not in the above file and imported into Event before the order is imported, the order will error until the part is uploaded. The error will then auto correct itself.
-
If the part is not in the above file and imported into Event before the order is imported, the order will be imported and routed automatically without DIMS or pallet quantities. This relies on there being a volume in the HU section in the OMF. This can be set in the IMPORT screen.