---
title: "Flight Reprice, Schedule Change, Ticketing and Order State"
description: "Separate reprice, schedule change, order, PNR, payment and ticket/document states across the flight-booking lifecycle."
slug: "flight-reprice-schedule-change-ticket-order-state"
translationKey: "guide-flight-reprice-schedule-change-ticket-order-state"
locale: "en"
type: "guide"
category: "flight"
tags: ["reprice","schedule-change","ticketing","order","pnr"]
publishedAt: "2026-09-26"
updatedAt: "2026-09-26"
reviewedAt: "2026-09-26"
sources:
  - title: "Travelport NDC Guide"
    url: "https://support.travelport.com/webhelp/jsonapis/airv11/content/air11/NDC/NDCGuide.htm"
  - title: "Duffel Orders"
    url: "https://duffel.com/docs/api/orders"
---
A flight transaction cannot be safely represented by one generic `status` field. Reprice, order/booking, payment, ticket/document and schedule-change states are separate lifecycles.

## State separation

```text
OfferState
OrderState
PaymentState
TicketState
ScheduleChangeState
ServicingState
```

Order CONFIRMED, Payment AUTHORIZED and Ticket PENDING can all be true at the same time.

## Reprice

Map reprice to MATCHED, PRICE_CHANGED, UNAVAILABLE or EXPIRED.

PRICE_CHANGED may require explicit user reconfirmation.

## Ticketing

An Order or PNR does not prove a ticket was issued. Keep ticket/document numbers and issuance state separately.

## Schedule change

Airline-initiated changes need their own lifecycle such as detected, pending action, accepted, alternate selected or refund/cancel.

## Unknown outcome

Order-create or ticket-issue timeout is UNKNOWN, not proven failure. Retrieve/reconcile before repeating the operation.

## Reconciliation

A periodic process should compare local order, provider order/PNR, ticket/documents and airline changes for drift.

## Observability

Track reprice-change rate, unknown-order rate, ticket-pending age, schedule-change pending age, servicing failure and reconciliation drift.