Work with Orders and Workspaces

Retrieve orders by ID, name, or airline, read the order in subsets, filter the orders panel, run parallel workspaces, and send documents and remarks.

Retrieve an order

Everything on this side of the manual starts the same way: get the order on screen. The retrieve prefix is *:

*ABC123            # Retrieve by order ID
*                  # Redisplay the order you already have loaded
*-DOE/JANE         # Retrieve the most recent order for this passenger name
*UA/ABC123         # Live retrieve from a specific airline, by its owner code
*ABC123/V2         # Retrieve a specific version of the order

Two of these deserve a second look:

The airline-scoped form goes to the carrier, not your files. *UA/ABC123 asks the airline directly for its current view of the order — reach for it when a booking was touched outside NDCTerm, or when you want the carrier's live state rather than your last-retrieved copy.
Orders are versioned. Every commit produces a new version, and *ABC123/V2 pulls up version 2 exactly as it stood. Reconstructing what a booking looked like before an exchange is a retrieve, not an archaeology project.

Read the order in subsets

A retrieved order can be long. Four display commands show one slice of the loaded order without re-fetching it:

*I                 # Itinerary only
*PAX               # Passengers only
*C                 # Contacts — passenger emails and phones, agency contact
*H                 # Version history — who changed what, and when

*H is the trail you read before touching a booking someone else built: each version with its change, in order. Pair it with *ABC123/V2 to open any version it lists.

The itinerary detail also preserves operational notes against the leg they belong to — terminal guidance, check-in instructions, and other carrier remarks appear with that segment instead of being flattened into a generic order note.

The orders panel

*L opens the orders panel — every order you can see, across carriers, browsable and searchable:

*L                 # Open the orders panel (*LIST works too)

*L takes no filter argument — there is no *L/-anything, and the parser rejects it. Filtering by status, airline, passenger, or date happens inside the panel itself, where the filters are visible and combinable. Type *L, then narrow. The airline list is built from the orders your agency can actually see, and each filtered row can be opened directly in an existing terminal workspace.

Deadline badges follow the order state: an unticketed booking shows its TKT LIMIT; a ticketed booking suppresses that spent deadline and shows VOID BY while its void window remains open.

The orders panel opened with *L, listing orders across carriers with status, passenger, and date filters inside the panel — The orders panel: browse and filter inside the panel — `*L` itself takes no arguments.

Parallel workspaces

A workspace is a full, independent transaction: its own command history, its own sidebar, its own booking in progress. You get several, and you switch between them with #:

#1                 # Switch to workspace 1
#2                 # Switch to workspace 2
#NEW               # Open a fresh workspace
#LIST              # List workspaces and what's live in each

This is how one agent runs several live transactions without stepping on any of them. The phone rings mid-booking: #NEW, handle the caller's cancellation, #1, and your half-built booking is exactly where you left it — selection, passengers, priced offers, entered data, all intact in its own sidebar. Nothing about switching commits or clears anything.

Use workspaces instead of the habit of abandoning a transaction to service something urgent. Ignoring your work costs you the rebuild; a workspace switch costs you a keystroke.

Email documents

Send booking documents from the loaded order — no export, no copy-paste:

EMAIL              # Confirmation to every passenger email on the booking
EMAIL/P1           # Confirmation to passenger 1 only
EMAIL/[email protected]          # Confirmation to an explicit address
EMAIL/INVOICE/[email protected]  # Invoice to an explicit address

The passenger-targeted forms use the contact data on the order — *C shows you what's there before you send.

Remarks and OSI

RMK VIP CLIENT - PREFERS AISLE        # Order-level remark
RMK/P1 GOLD STATUS MATCH PENDING      # Remark against passenger 1
OSI/UA PAX SPEAKS SPANISH ONLY        # OSI message to the carrier

Remarks are your notes on the order; OSI goes to the airline, addressed by carrier code, same as you've always used it.

Once the order is on screen, the servicing verbs take over — changing flights is covered in Service and Change an Order, and unwinding a booking in Cancel, Void, or Refund.