Name change rule
Some airlines (for example, charter flights) allow passenger name changes until departure. Others do not allow name changes at all, or only until a defined cutoff before departure.
Overview
The Name Change Rule controls whether passenger name changes are allowed for a transport.
It lets you set separate rules for:
Office users (back office staff).
WebBooking users (customers).
It also lets you enforce a shared deadline (in days before departure).
Purpose
The purpose of this functionality is to:
Ensure consistent handling of name change requests.
Reduce last-minute changes that can cause supplier or cost issues.
Separate internal changes (Office) from customer self-service (WebBooking).
Preconditions
A transport option must already be created in the system.
Your supplier policy for name changes must be known.
Instructions
Open the relevant transport in Transport creation.
Go to the Name Change Rule section.
Configure the fields based on your supplier policy.
Save.
Field Descriptions
Do Not Allow Name Change Office
When enabled, Office users cannot change passenger names for this transport. This restriction applies after payment is registered.
Do Not Allow Name Change Web
When enabled, customers cannot change passenger names in WebBooking.
Name change deadline (days before departure)
Defines the latest point a name change is allowed. Example: set to 7 to allow name changes until 7 days before departure. After that, name changes are blocked.
The deadline is evaluated against the transport’s departure date.
FAQ
Why can Office users still change names before payment?
The Office restriction is enforced after payment is registered. Before payment, names can typically be corrected as part of normal booking edits.
Do Office and WebBooking use the same deadline?
Yes. Name change deadline (days before departure) is a shared cutoff. If a change happens after the cutoff, the system blocks it in both channels.
What happens if I block both Office and WebBooking name changes?
No one can change passenger names through normal UI flows. Only users with higher privileges or support processes can resolve it.
Does this affect other passenger edits (phone, email, SSR, etc.)?
No. It targets passenger name changes only. Other passenger fields follow their own rules and permissions.
Related pages
Last updated
Was this helpful?