The CCI Specification & import testing will allow for a bare minimum consignment information and successful creation in OneFlo. However there are a number of critical items that need to be sighted and confirmed to ensure a successful end to end integration.
All checks here will simply outline the CCI- Information Requirements
Criteria is ranked on impact to consigning process and frequency of error seen when moving live.
| Item | Detail | Impact | Confirmed |
|---|---|---|---|
| Correct Use of Consignment Sequences | Each Carrier & Customer relationship will have their own dedicated consignment, Item & Barcode sequences. | Wrong/Incorrect sequences will result in lost visibility of the freight. | |
| Barcode Match | The Scannable barcode within the Generated Label MUST match the data passed through in the <Barcode> element. | Not including this, or including the wrong value will loose all item level scan events from the carrier. | |
Dimension & Weight Data
| Dimension and Weight Data is required to be included at both a consignment and Item Level | Dimension and weight data are recorded at a consignment and Item level for reporting purposes to perform freight optimization and other commercially beneficial activities for the customers. While its not ideal that this information is not sent to the carrier, this is often corrected in the invoicing process as the carrier scans and weighs the freight in their processing of consignments. | |
| References | All required references should be included | References allow for Order numbers/ ERP numbers to be used as tracking numbers/look up orders in oneflo | |
| DG Data | Ensuring accurate DG data is passing through within the file is critical. | ALL DG data is critical as part of CoR. It is not good enough to flag Y/N for DG's | |
| Item Count | The Item count & Items within the file provided need to match the freight being despatched. |