Simplify Itinerary ID reference numbers should be a chronological Itinerary Count
G
Generous Ostrich
The itinerary ID's are too complicated, too long and have no chronological relevance. ie, if a recent itinerary number is 1408 and I produce approx 100 itineraries a year, I then know that itinerary number 1308 would have been produced roughly 1 year prior. Would be good to be able to carry on from the itinerary ID's I am using in .net. This would make the transition much easier and gives the client less chance of making a mistake with the randomly generated itnerary ID's such as 5BA8 7D34. The next itinerary I produced in our system was then coded as DEB2 80A6!! - There's no logic to this progression.
Jason Bragg
Merged in a post:
Editable ID Reference numbers or ability to display internal reference in client Itineary
P
Pretty Guppy
Is there a way to include the internal reference on the client's itinerary? If not, is it possible to allow customisation of the ID reference number, which will then display on the client's itinerary?
S
Semantic Chameleon
i am hiding always the ID reference toward the client. I am using their name as a reference
but the TW ID reference is useful for our exchange with suppliers.
U
Upper Sturgeon
this would be most useful as TW ID reference are not useful to us in anyway
F
Fern green Dingo
And the reference in Tourwriter should be the same with the integration with Xero, in the "reference" field. For now, the reference that shows in Xero is a combination between the reference and the Itinarary name. We would prefer our internal reference. Thank you.
E
Emerald Alpaca
Fern green Dingo I am still astounded by the automated alpha-numeric system, no logic and makes no sense and creates confusion especially when trying to reconcile payments when we so need a numbered sequence......Pls TW re-think this ! It was perfect on the .net version..
G
Green Spoonbill
Could we manually modify that number? Even if the program generates an automatic Itinerary ID number, can we have the option of editing it by hand so that it is the same one we use internally in other programs? Thank you!
R
Rolling Halibut
Please also remove the space as we have to now manually delete it every time if we want to look for an itinerary by its ID. Eg: 5BA8 7D34 > 5BA87D34
L
Liable Iguana
Rolling Halibut Agreed. Jason Bragg, why have you chosen to format the booking number in this way in that section? It causes issues with workflow links we have as the space between doesn't appear elsewhere and is separating values and causing identification issues. I don't see the logic in it the way it's been set up already. Thank you.
Jason Bragg
Merged in a post:
Simplify Itinerary ID reference numbers
B
Blue Swordtail
It is too complicated for travelers to remember reference numbers with letters and numbers
An itinerary id should be a number both for the customer and us to use as a reference. Easy for us to find and easy for the customer to remember.
Creating a reference that is almost like and password which is not ideal
Please reconsider and create a simple number please.
Jason Bragg
Merged in a post:
Can we set up the itinerary ID? The numbers generated are long and with no sense. For instance I use, HUE-3125 meaning client traveling in march, sell 1, year 2025. This should be customizable by every agent.
P
Puce Wren
Itinerary ID
S
Semantic Chameleon
similar to this : https://tourwriter.canny.io/feature-requests/p/itinerary-id-chronological-itinerary-count (8 votes)
and
and
D
Delighted Toucan
I strongly support this change as well :)
Load More
→