A complete guide to the NP command in Amadeus โ how to create or cancel NONAME elements for passengers in a group PNR when individual names are not yet available.
Group bookings rarely start with a complete list of passenger names. Travel agencies often hold group space weeks or months before the travellers are finalised, and the airline allows the group to be reserved without submitting individual names straight away. The NP command exists for exactly this situation. It creates a NONAME element that reserves a specific number of places for passengers whose names are not yet available, letting the booking be held and priced while the agency collects the traveller details. This guide explains what NP does, the syntax for each variation, and when it should be used.
What Does the NP Command Do?
NP is the Amadeus GDS command used to create or cancel NONAME elements for passengers in a group PNR.
Category: Group Booking.
It allows you to specify the number of passengers whose names are not yet available in a group booking.
A NONAME element holds the required number of unnamed places in the group. The booking is secured, priced, and managed as normal, but the individual passenger names are added and transmitted later using the standard name entries and the NT / NTSR commands.
Create a NONAME Element
To create a NONAME element for a specific number of passengers:
NP15This creates a NONAME element for 15 passengers. The group space is held for 15 unnamed travellers until the individual names are submitted.
Create Multiple NONAME Elements
To create several NONAME elements in a single entry:
NP2,3,5This creates multiple NONAME elements for 2, 3, and 5 passengers separately. Use this when the group is made up of sub-groups with different requirements โ for example, separate rooming groups, different passenger types, or travellers arriving on different dates โ and each sub-group needs its own unnamed element.
Cancel NONAME Elements
To cancel all existing NONAME elements in the group PNR:
NP0This cancels the existing NONAME elements in the PNR. Use it when the names have been finalised and the unnamed placeholders are no longer needed, or when the group composition has changed and the NONAME elements must be re-created.
When to Use NP
Use NP when creating or managing a group PNR where passenger names are not yet available, allowing the required number of unnamed passengers to be held in the booking. Typical scenarios include:
- Holding group space before the final passenger list is confirmed.
- Reserving places for a group whose individual travellers are still being collected.
- Managing sub-groups within a larger booking that have different requirements.
- Holding a block of seats for a tour or incentive group still in the sales phase.
- Adjusting the number of unnamed passengers when the group size changes.
- Cancelling NONAME elements once the names have been finalised and submitted.
How NP Fits Into Your Group Booking Workflow
A typical group booking session using NP might look like this:
- Create the group name element with
NG15EUROPE TOUR. - Search group availability with
AN07JULLONSYD/RGRP. - Sell the group space using
SS15G3/SGor waitlist withSS15C4/PG. - Add the NONAME element with
NP15to hold the unnamed places. - Collect the individual names and add them to the PNR.
- Cancel the NONAME element with
NP0once names are finalised. - Transmit the names to the airline with
NTorNTSR. - Issue the group tickets with
TTP.
Important: NONAME elements hold space, but they do not replace the airlineโs name submission deadline. The individual names must still be added and transmitted to the airline before the deadline, or the group space will be automatically cancelled.
Always track the airlineโs deadline carefully and confirm the NONAME element matches the actual expected group size. If the number changes, update the NONAME element before finalising the names.
How NP Relates to Other Group Booking Commands
- NG โ creates a group name element.
- AN/RGRP โ displays group availability.
- SS/SG or SS/PG โ sells confirmed or waitlisted group space.
- NP โ creates or cancels NONAME elements for unnamed passengers.
- SRGRPF โ adds a Group Fare SSR element with a remark.
- RTN / RTNR โ display individual passenger names in a group PNR.
- NT / NTSR โ transmit group passenger names to airlines.
- TTP โ issues the group tickets once names are accepted.
Frequently Asked Questions
What does NP15 do in Amadeus?
It creates a NONAME element for 15 passengers, holding the group space for unnamed travellers until individual names are added.
What does NP0 do?
NP0 cancels the existing NONAME elements in the group PNR. Use it when names have been finalised or the group composition has changed.
Can I create multiple NONAME elements in one entry?
Yes. Use NP2,3,5 to create separate NONAME elements for 2, 3, and 5 passengers.
Do NONAME elements replace the need to submit names?
No. NONAME elements only hold space. The individual names must still be added and transmitted to the airline before the name submission deadline.
Conclusion
The NP command allows group bookings to be held before the final passenger list is known. Use NP15 to create a NONAME element for a set number of passengers, NP2,3,5 to create multiple elements for sub-groups, and NP0 to cancel the elements once names are finalised. Remember that NONAME elements hold space but do not replace the airlineโs name submission deadline โ always track the deadline carefully and transmit names in time with NT or NTSR. Paired with NG, AN/RGRP, SS/SG, RTN, and TTP, the NP command ensures every group booking is held, managed, and finalised accurately.
