If your carrier has not uploaded from an integrated service such as RMIS or MyCarrierPackets (MCP), the steps described below can help you to troubleshoot the issue and get your carrier into the system.
Confirming Accurate Postal Codes
The most frequent reason a carrier fails to upload is the entry of an inaccurate postal code. The onboard services do not perform any validation of the data. If your carrier fails to upload, we suggest reviewing the carrier's packet to confirm they used a valid postal code. If the postal code is not valid, ask them to update the postal code and resubmit the packet.
To check the validity of the postal code, the following links are helpful resources:
The RMIS and MCP syncs run every five minutes. Depending on the volume of activity during a sync, it is possible that the creation of and updates to a carrier will happen across multiple syncs.
Because both integrations have workflows to set carrier status, it is possible that the carrier syncs into EKA in Inactive status but then is updated to the Active status on a subsequent sync.
The integration status log will display the status of your integration. To view the status of the integration, go to Integration Status from the top right menu. Toggle to the Subscriber view and locate either MCP or RMIS on the left side of the display.
If the squares are blank, that means that the integration is not currently active. Follow the instructions in the next section to check your credentials and enablement status of the integration.
If the squares are yellow, performance is degraded to some degree. If the squares are red, the performance is severely degraded. Performance can be impacted by the service provider directly. We recommend that you check the status with the service provider in addition to checking with the EKA team.
To check your integration credentials and the enablement status of the integration, go to Administration → Configurations → Company → Carrier Qualification Provider.
For MCP, Username and Password are required. To enable/disable the integration, tick the MCP Onboard box and Submit Changes.
For RMIS, five items are required:
- API Username
- API Password
- FTP Host
- FTP Username
- FTP Password
To enable/disable the integration, tick the Enable RMIS box and Submit Changes.
Both MCP and RMIS integrations have rules that will place the carrier into Inactive status. The status of the carrier can be readily seen in Operations → Data Management → Carriers.
If the carrier is in Inactive status, the carrier will need to be made Active before it can be used on a load. A carrier can be activated in Administration → Carriers → Inactive Carriers.
A contract start date will need to be entered.
For RMIS, an additional step will need to be taken prior to activating the carrier. In Administration → Carriers → Inactive Carriers, select the carrier to open it up to edit. The 3rd Party Status Override will need to be set to YES. The activation option will not be available until this setting is saved.
Manually Add Carriers
With both integrations, there is a workflow that will allow you to add a carrier manually in cases where the carrier cannot be entered via the integration or in cases where a carrier is urgently needed and is not uploading from the integration.
To add a carrier manually, you will first need to disable the integration. Please follow the steps described in the Integration Credentials section above.
Once the integration is disabled, the option to add carriers manually will be enabled. Go to Operations → Data Management → Carriers and click the green plus sign to Add a Carrier. Use the Express onboarding option ONLY.
Minimal data is required to create the carrier. We recommend that you add the DOT and/or MC Numbers when available to avoid duplicate carrier records from being created.
When a carrier is added manually due to an issue with the RMIS or MCP sync, the packet will sync to the existing carrier record once the issue is resolved.