CHANGELOG

The Latest Updates to Tour Amigo

Oct 7, 2026

Custom Departure Codes

What's new?

You can now give each departure of a tour its own code, rather than relying on the code that is automatically generated by the system. Enter a code against any departure in Tour Management > Instance Manager, and it will appear in Report Builder, and in the booking sidebar for that departure.

This is designed for teams whose finance or reconciliation processes track each departure individually. If you don’t need it, there is nothing to change: departures without a code you’ve entered keep working exactly as they did before.

No set-up required

Departure Codes are available to all operators. There is no setting to switch on - simply add a code to a departure when you want one.

How departure codes work

Every departure already has a departure code. What has changed is that you can now replace it with one of your own.

Code type	How it works
Automatic code	Used when you haven’t entered a code. Built from the tour code followed by the departure date in DDMMYY format. For example, tour code DRG departing 14 October 2026 gives DRG141026. This is unchanged from previous behaviour.
Your own code	A code you type in for a specific departure, e.g. DT-APR-A. It replaces the automatic code for that departure wherever the departure code is shown.

Adding a departure code

Go to Tour Management > Instance Manager
Find the tour and the departure date you want to add a code to
Click the pencil icon to edit that departure
Enter your code in the Departure Code field
Click Save

*New Departure Code field when editing a specific tour instance*

Your code now appears as a small line beneath that departure’s date in the Instance Manager, so you can see at a glance which departures have their own code. Departures using the automatic code show no extra line.

*Custom departure codes are displayed on the Instance Manager overview*

Changing or removing a code

Open the departure on Instance Manager using the pencil icon
To change the code, overwrite it with a new one
To remove the code, clear the field completely

Changes apply to existing bookings straight away

Adding, changing or clearing a departure code updates every booking already on that departure, not just new ones. Report Builder reflects the new code immediately. If your finance team has already exported or reconciled bookings under the old code, let them know before you change it.

Rules for codes

A code is checked when you save. If it doesn’t meet the rules below, it won’t be saved and you’ll see a message explaining why.

Rule	Details	Message shown
Allowed characters	Letters, numbers, hyphens (-) and underscores (_). No spaces, full stops or other symbols.	“Departure code can only contain letters, numbers, underscores and hyphens”
Maximum length	50 characters. The field stops accepting input once you reach the limit.	None
Must be unique	Each code can only be used once across all of your tours and departures - not just within the same tour.	“This departure code is already in use”
Can’t match an automatic code	A code that matches another departure’s automatic code (e.g. DRG141026) is treated as already in use.	“This departure code is already in use”
Not case-sensitive	dt-apr-a and DT-APR-A count as the same code.	“This departure code is already in use”

Avoid the automatic-code pattern - because your codes can’t match any automatic code in your account, avoid codes made of a tour code followed by six digits. A distinct pattern - for example one that includes a hyphen or a month abbreviation - avoids unexpected “already in use” messages.

Where the departure code appears

Instance Manager

You will see your code as a small line under the departure date. Nothing extra is shown for departures using the automatic code.

Report Builder

Any report table that displays Departure Code will display both the automatic code and any custom codes.

*Custom departure codes are displayed alongside automatic departure codes in Reports*

Booking Journey

When booking a departure that has a custom code, it is displayed under Reference in the sidebar throughout the booking journey. Departures with an automatic code only show Reference and Supplier Reference, as before.

Third-party Supplier tours

For tours imported from third party suppliers, the supplier’s own departure code is now brought in with each departure. It shows in the sidebar during the booking journey.

Good to know

Existing setup is untouched - Your tour-level codes in Tour Management > Tour Details still work as before, and continue to form the automatic code for departures without their own code.
One code per departure - Each departure date can have a single departure code.
Codes are unique to your account - Uniqueness is checked only against your own tours, so codes used by other companies have no effect on you.
No bulk entry - Codes are added one departure at a time from the Instance Manager.

FAQ's

Do I have to add a code to every departure?

No. Add codes only where you need them. Any departure without one keeps using its automatic code.

Can connected tours share a code?

No. If you run modular or back-to-back tours, each departure of each tour needs its own distinct code, even where the tours connect. A shared prefix (e.g. DT-APR-A and DT-APR-B) is a simple way to keep related departures easy to spot in reports.

I changed the code. Will my older reports change?

Any report you run from now on will show the new code for every booking on that departure, including bookings made before the change. Reports you have already exported or saved outside Tour Amigo are not affected.

Why does my code say "already in use" when I haven't used it?

The code may match an automatic code belonging to another departure, or a code you’ve used with different capitalisation. Try a slightly different code.

How do I go back to the automatic code?

Open the departure in the Instance Manager, clear the Departure Code field and save.

TOUR MANAGEMENT