Home โ€บ Blog โ€บ Amadeus NM Command: Create Passenger Names

Amadeus NM Command: Create Passenger Names

A complete guide to the NM command in Amadeus โ€” how to create passenger name elements for single travellers, families, children, infants, and passengers with different family names.

Every PNR begins with the passenger. Before an itinerary can be booked, a fare quoted, or a ticket issued, the travellers must be named in the booking. The NM command is the Amadeus entry that does this. It creates passenger name elements according to the passenger type and family-name structure โ€” supporting single passengers, multiple passengers with the same family name, children, infants, and multiple family names. Getting the format right at the point of entry prevents problems later with ticketing, APIS data, and airline passenger manifests. This guide walks through each major NM variation with a working example.

What Does the NM Command Do?

NM is the Amadeus GDS command used to create passenger name elements in a PNR.

Category: Passenger Names.

The NM command is used to add passenger names to a PNR according to the passenger type and family-name structure.

The command supports several different formats: a single passenger, multiple passengers sharing the same family name, mixed adult-and-child bookings under one family name, standalone children, infants travelling with an adult (with either the same or a different family name), and bookings where multiple different family names appear in the same entry. When a name needs to be corrected after it has been saved, use the NU command to update the details without cancelling and rebooking the PNR.

Single Passenger

Create a single passenger with one family name:

NM1RAVEL/TOM MR

This creates a single passenger, RAVEL/TOM MR. The 1 indicates one passenger, the family name and given name are separated by a slash, and the title (MR) is entered after the given name.

Multiple Passengers with the Same Family Name

Create more than one passenger with the same family name:

NM2MEYERS/HANS MR/HEIDI MRS

This creates two passengers โ€” MEYERS/HANS MR and MEYERS/HEIDI MRS โ€” sharing the family name MEYERS. The family name is entered once, followed by each given name and title separated by slashes.

Adult and Child with the Same Family Name

Create an adult passenger and a child with the same family name:

NM2HOBART/JAMES MR/BILL (CHD)

This creates an adult (HOBART/JAMES MR) and a child (HOBART/BILL (CHD)) under the same family name. The (CHD) indicator tells the system that the second passenger is a child, so the correct fare and passenger type code are applied.

Single Child

Create a child with a single family name:

NM1BRADLEY/MICHAEL (CHD)

This creates a single child passenger, BRADLEY/MICHAEL (CHD). Children cannot travel alone unless the airline provides an unaccompanied minor service, in which case the corresponding SSR is added to the PNR.

Infant with the Same Family Name

Create an infant associated with an adult with the same family name:

NM1BRILL/SUSAN MRS (INF/LISA)

This creates an adult passenger, BRILL/SUSAN MRS, with an infant associated to her โ€” BRILL/LISA. The (INF/โ€ฆ) format associates the infant with the adult traveller and applies the infant passenger type code.

Infant with a Different Family Name

Create an infant associated with an adult with a different family name:

NM1BROCH/R MRS (INFLEWIS/SUSAN)

This creates an adult (BROCH/R MRS) with an infant who has a different family name (LEWIS/SUSAN). The infantโ€™s full family and given name are entered inside the brackets, so the association is recorded correctly even when the family names differ.

This format is common when a parent travels with a child under a different surname โ€” for example after a legal name change or in blended families.

Multiple Family Names

Create a multiple family name element:

NM1NELSON/FRANK MR 1EDWARDS/RICHARD MR

This creates two passengers with different family names in a single entry โ€” NELSON/FRANK MR and EDWARDS/RICHARD MR. Use this format when travellers with unrelated surnames are booked together, such as friends or colleagues travelling on the same itinerary.

When to Use NM

Use NM when creating a PNR and adding passenger names, including adults, children, infants, or passengers with different family-name structures. Typical scenarios include:

  • Creating a booking for a single traveller.
  • Booking a family or couple with the same family name.
  • Adding an adult and a child to the same PNR under one family name.
  • Booking a child travelling alone with the unaccompanied minor service.
  • Associating an infant with a parent, whether the family names match or not.
  • Booking unrelated travellers with different family names on the same itinerary.
  • Recording cabin baggage or extra seat passengers using the specialised NM formats.

How NM Fits Into Your PNR Management Workflow

A typical booking session using NM might look like this:

  • Confirm the travellers with the customer โ€” family names, given names, titles, and passenger types.
  • Enter the NM entry with the correct format for each passenger group.
  • Add the itinerary using SS.
  • Add contact details with AP, ticketing arrangement with TK, and any SSRs with SR.
  • Review the passenger list with RTIM and check the itinerary with RTAM if there are married segments.
  • Price the booking with FXP and review the TST.
  • Save with ER or ET, then issue the ticket with TTP.
  • If a name must be corrected, use NU rather than cancelling and rebooking.

How NM Relates to Other Passenger Name Commands

  • NM โ†’ creates passenger name elements in a PNR.
  • NU โ†’ updates or corrects an existing passenger name.
  • NM correction entry โ†’ used for specific corrections to name elements.
  • RTN โ†’ displays passenger names from a group PNR.
  • RH โ†’ displays the PNR history, including name entries and corrections.

The distinction matters: NM creates names; NU corrects them. Use NM at the start of a booking, and NU when a saved name needs to be updated without touching the rest of the PNR.

Important: Passenger names must match the passengerโ€™s passport or identity document exactly. Even small differences โ€” a missing middle initial, an incorrect title, or a transposed letter โ€” can cause problems at check-in, during APIS transmission, or when the airline validates the ticket.

Always confirm the spelling, order, and title with the customer before entering the name. If the name must be corrected after saving, use NU โ€” and remember that a name change on an issued ticket may require a reissue, subject to the airlineโ€™s rules.

Frequently Asked Questions

What does the NM command do in Amadeus?

NM creates passenger name elements in a PNR for adults, children, infants, and passengers with different family-name structures.

What does NM1RAVEL/TOM MR mean?

It creates a single passenger named RAVEL/TOM MR. The number 1 indicates one passenger.

How do I add a child to the same family name?

Use NM2HOBART/JAMES MR/BILL (CHD). The (CHD) indicator tells the system that the second passenger is a child.

How do I associate an infant with an adult?

Use NM1BRILL/SUSAN MRS (INF/LISA) for the same family name, or NM1BROCH/R MRS (INFLEWIS/SUSAN) for a different family name.

How do I add passengers with different family names?

Use NM1NELSON/FRANK MR 1EDWARDS/RICHARD MR to enter multiple family names in a single entry.

How do I correct a name after it has been saved?

Use the NU command to update the passenger name in the existing PNR without cancelling and rebooking.

Conclusion

The NM command is the passenger name creation tool in Amadeus. Use NM1RAVEL/TOM MR for a single traveller, NM2MEYERS/HANS MR/HEIDI MRS for passengers sharing a family name, NM2HOBART/JAMES MR/BILL (CHD) for an adult and child in the same family, NM1BRADLEY/MICHAEL (CHD) for a standalone child, and the (INF/โ€ฆ) format for infants travelling with an adult. For unrelated travellers, enter multiple family names in a single entry. Getting the format right at the point of entry ensures the passenger type codes, fares, and SSRs are applied correctly, and it prevents problems during ticketing and APIS transmission. If a name needs to be corrected later, use NU rather than cancelling and rebooking. Paired with SS for the itinerary, AP for contact details, TK for ticketing arrangements, SR for SSRs, and FXP for pricing, the NM command completes your passenger name toolkit and ensures every booking is built on accurate traveller data.

Focus Keywords

  • NM command
  • Amadeus NM
  • passenger name element
  • NM1RAVEL
  • NM2MEYERS
  • NM child passenger
  • NM infant passenger
  • NM multiple family names
  • NU command
  • Amadeus passenger names