Home โ€บ Blog โ€บ Amadeus NU Command: Update Passenger Names

Amadeus NU Command: Update Passenger Names

A complete guide to the NU command in Amadeus โ€” how to update passenger name details such as family name, given name, and title in an existing PNR.

Passenger names are the most sensitive data in any PNR. A single wrong letter can cause a mismatch with the passport, block boarding, or trigger a rejection when the airline validates the ticket. When a name needs to be corrected, the PNR should not be cancelled and rebooked โ€” the name itself should be updated in place. The NU command is the Amadeus entry designed for exactly this. It allows you to modify the passengerโ€™s family name, given name, or title directly in the existing PNR, keeping the itinerary, seats, and pricing intact. This guide explains what NU does, the syntax for each variation, and when it should be used.

What Does the NU Command Do?

NU is the Amadeus GDS command used to update passenger name details in an existing PNR.

Category: Passenger Names.

It allows you to modify the passengerโ€™s family name, given name, or title.

Unlike a cancellation and rebooking, which would wipe the itinerary, seats, and any stored TST, NU changes only the name field. The rest of the PNR stays exactly as it is, which means the change can be made quickly and safely โ€” even after the ticket has been issued in some cases, depending on the airlineโ€™s rules.

Update Family Name, Given Name and Title

To update the family name, given name, and title for a passenger:

NU2/1SMITH/HANS MR

This updates the family name, given name, and title for passenger 2. The entry includes the passenger number, the name element number, and the full name in the standard format used elsewhere in the PNR.

Update Given Name

To update only the given name and title:

NU3/JANE MRS

This updates the given name and title for passenger 3, leaving the family name unchanged. This is useful when only a first name or title needs correction โ€” for example, when a name was entered with the wrong title, or when the spelling of a given name needs to be fixed after verifying the passport.

When to Use NU

Use NU when you need to correct or update passenger name information in an existing PNR. Typical scenarios include:

  • A misspelled family name discovered after the booking was created.
  • A given name entered incorrectly or with the wrong spelling.
  • A wrong title โ€” Mr instead of Mrs, or a missing title entirely.
  • A name that does not match the passport, detected before ticketing.
  • A legal name change that needs to be reflected in the PNR.
  • A name that was truncated or formatted incorrectly by an automated feed.
  • A correction after the airline rejects the ticket due to a name mismatch.

How NU Fits Into Your PNR Management Workflow

A typical name correction session using NU might look like this:

  • Retrieve the PNR and display the passenger names.
  • Compare the name against the passport or identity document.
  • Cancel any seat requests if the change is significant โ€” see the SX note below.
  • Enter the appropriate NU entry for the passenger and name field that needs updating.
  • Verify the correction by redisplaying the PNR.
  • Reprice the itinerary if the change affects the ticket.
  • Reissue or update the ticket if it has already been issued.
  • Reassign seat requests once the name is confirmed.

Important: If a name is being changed in a Group PNR or when seat requests are attached to the passenger, the system may reject the NU entry with the error CANCEL SEAT ITEM OR SPLIT PNR PRIOR TO NAME RE-ENTER.

In that case, cancel the seat requests with SX or split the PNR before running NU, and reassign the seats afterwards.

How NU Relates to Other Name and PNR Commands

  • NU โ†’ updates passenger name details in an existing PNR.
  • NM โ†’ adds a new passenger name to a PNR.
  • RTN / RTNR โ†’ display individual passenger names in a group PNR.
  • SX โ†’ cancels seat requests, often required before a name change.
  • TTE โ†’ deletes a TST when the name change requires repricing.
  • RH โ†’ displays the PNR history, including all name updates.

Frequently Asked Questions

What does NU do in Amadeus?

NU updates passenger name details โ€” family name, given name, or title โ€” in an existing PNR.

What does NU2/1SMITH/HANS MR mean?

It updates the family name, given name, and title for passenger 2 to SMITH / HANS / MR.

Can I update only the given name?

Yes. Use NU3/JANE MRS โ€” the entry updates the given name and title while leaving the family name unchanged.

Why does the system reject my NU entry?

Usually because seat requests are attached to the passenger. Cancel them with SX or split the PNR first, then retry NU.

Can I use NU after the ticket has been issued?

NU updates the PNR, but the ticket itself must also be reissued or updated. Rules vary by airline โ€” some allow minor corrections, others require a reissue. Always confirm the airlineโ€™s policy first.

Conclusion

The NU command is the correct way to update passenger name details in Amadeus. Use NU2/1SMITH/HANS MR to change the family name, given name, and title for a passenger, or NU3/JANE MRS to update only the given name and title. Because NU changes the name field without touching the itinerary or the stored pricing, it is far safer than cancelling and rebooking the PNR. If the system rejects the entry with the seat item error, cancel the seat requests with SX or split the PNR first, then retry. After the change, verify the PNR, reprice if necessary, and reissue the ticket if it has already been issued. Paired with NM, RTN, SX, and RH, the NU command completes your passenger name toolkit and ensures every booking matches the travellerโ€™s documents exactly.