Courier Exchange & Remote Driver Network 


The majority of Navigator users have a dedicated fleet of drivers who receive work via the Navigator mobile application though allocations on the control screens.

Should you require a driver resource outside of your dedicated fleet you have two system integrated options available:

  • Courier Exchange (CX)
  • Remote Driver Network (RDN)

Please read below for instructions and information on the two methods of integrated working.

Part 1

Courier Exchange (CX)

Coda have updated the Navigator and Courier Exchange integration, these steps cover work in CX.

Add your Courier Exchange credentials to Navigator;
This is done in the Control Panel > Offices > Courier / Haulage Exchange

Image Placeholder

  1. Tender a load
  2. Allocate and Confirm Load to the CX partner
  3. Tracking Updates

               a.       Acknowledged by CX Partner / Driver

               b.       On Route to Collection

               c.       Collected

              d.       On Route to Delivery

              e.       POD

Tender a Load

Image Placeholder

Tender load functions

Image Placeholder

Pickup and Delivery Times

By default these revert to the times on the docket

If you times are not specified on the dockets, you can amend these times to suit your post.

Broadcast / Notify Radius

This defaults to drivers in the radius of 30miles from the collection address, amend to suit your post.

Job Description

Defaults to Sameday as the most common of all Navigator based CX loads

Freight type

Defaults to N/A as this is more aligned to haulage variations, if applicable to your load, you can amend this to suit your post.

Body Size

By Defaults to N/A as this is more aligned to haulage variations, if applicable to your load, you can amend this to suit your post.

Vehicle Size

You have to select your required vehicle to reflect the client vehicle assigned which is featured top right of your screen view.


We recommend inserting in to Notes number of pieces and dimensions, the weight of the job is passed on the tender. Plus any other relevant notes which you advise.

Your CX Diary presenting the Tender

Image Placeholder

CX Bids will appear in the usual way at the footer

Image Placeholder

Allocate and Confirm Load to the CX partner

Image Placeholder

  • Allocate to your CX callsign.
  • Complete the CX number of the partner in the Handset Number field.
  • On screen feedback will display the CX number and Partner Name.

Allocation confirmation feedback

Image Placeholder

CX Partner’s view of the load


Image Placeholder

Full Details

Image Placeholder

  • The CX partner will need to Accept the load to feedback to Navigator

Your Navigator job summary view

Image Placeholder

Full Tracking View

  • POD including Photo / Signature Capture
Image Placeholder

Tracking Events

  • Acknowledge by driver on Handset
  • Driver on Route to Collection
  • Driver confirmed Collection
  • Arrived at Delivery Address
  • Final POD

Image Placeholder 

  • Tracking events and POD image / signature can display on your client facing tracking pages and Navigator update emails to clients.


Your CX Diary Dashboard – Completed Job

Image Placeholder

The CX Partner Dairy View – Completed Job

Image Placeholder

*Please note parts of the CX and Navigator Screen Shots are covered for data protection purposes in this document only


  • TMS Integration (API) is available to Courier Exchange Premium subscribers, you will need to check with Courier Exchange (CX / TEG) you have the required access.
  • Navigator Courier Exchange credits are required if you wish to take advantage of the automated functionality.
  • Pricing per credit: £0.07
  • Load Tendering = 2 Credits
  • Load Allocation / Confirmation = 2 Credits
  • Tracking updates = 1 Credit per update

  • To set up a CX driver for allocation purposes please review Part 3, the Notes.
  • Please see Part 4 FAQ for notes on the CX Integration and RDN functions.

Part 2

Remote Driver Network (RDN)

The RDN works using the standard Navigator mobile application working on a PAYG basis as opposed to a monthly driver subscription.

Why use the RDN?

When you have a known supplier who maybe a small man in a van company and you use them on an occasional use for regional or cover requirements.

Utlising the RDN for an occasional use driver, the driver will be provided access to the mobile application via an automated alert text message sent on allocation.

This text message will direct them to the app stores (Android - Google Play or iTunes for iPhone devices) which they will need to install (first time use only, providing they did not previously deleted the app), the text will also supply them with a username and password for login.

Image Placeholder

Example Automated Text - Sent when allocation has been made on Navigator Control Screens

Once logged in, the driver will be able to complete all the normal milestone updates and GPS Tracking will display the driver on your Control Screen Maps* .

  • Acknowledged
  • On Route to Collection
  • Collected
  • On Route to Delivery
  • Delivered (POD / Signature or Photo Capture).
  • The failure milestones, document scan and item scanning functionality are all available
  • Driver Tracking on Maps*

*Drivers are required to allow tracking when installing the application or make a change in settings to enable tracking.

Allocating to an RDN Driver

When allocating to a RDN Driver, the Handset Number will display on the allocation box.

Please complete their mobile number and Save Changes, this will send the Text Message alert to the driver.

Image Placeholder

Driver App Login

You can instruct the driver to enable the Remote Driver Network on the App, this will remove the need for a navigator server address.

Drivers use the code (their telephone number) and the pin from the text message to access the Navigator app.

IOS                                                                                                      Android

Image Placeholder                                     Image Placeholder

First Time RDN Use (Driver Registration)

When you allocate to a new driver on the RDN you will be provided with this pop up.

Please complete the driver name, email and address details (only the Name is mandatory).

This will not appear again once you have Registered on RDN.

Image Placeholder

CX Number

The RDN registration has the CX Number for you to complete.

Why should you complete this?

In some examples, you may tender a job from Navigator to the CX and the driver will use the Navigator mobile via the RDN to complete the job (not their own app or the CX app).

If you complete the CX number on the registration form, the POD will be sent from Navigator to the CX to complete the job in CX.

For this to work, the job must have been first tendered on the CX from the Navigator system (please see Tender a load from this document).


  • Navigator RDN credits are required if you wish to take advantage of the automated functionality
  •   Pricing per RDN credit: £0.70

Part 3

Setting up Drivers for CX and RDN

Within the Driver file you need to select the Handset type to Uses RDN (Remote Driver Network) Handset.

Image Placeholder

Selecting Handset type to Uses RDN will enable the CX allocation to function as well as the RDN function.

Part 4


  • Will a drivers receive a text message on every RDN allocation?
  • Yes, they will sent the text message with login details.

  • Is the Navigator App functionality the same for an RDN driver as a normal in house driver?
  • Yes, once the driver has logged in to the app, they will have all the same functionality as a normal fleet driver.

  • How do I set up my Navigator system to link with my CX account?
  • Navigator can link with CX at an Office level, in Control Panel > Offices > Courier Exchange > complete username and password of a CX user.
  •   Can I post a multi drop loads to CX?
  • Unfortunately we could not identify within the CX API a supported method of sending muti drop jobs.