Reprice
Validation of a previously observed offer against current price, availability and commercial conditions closer to booking.
Why it matters
Transaction concepts describe how a metasearch click becomes a downstream booking experience. Without context-preserving links, durable click identity, booking lifecycle events and reconciliation, search performance becomes disconnected from actual commercial outcomes.
What does it look like in practice?
A metasearch click ID travels through the deeplink, returns with booking events and is reconciled through cancellation/stay states. Breaking this lineage creates commercial attribution gaps.
Implementation questions
- Is search context preserved on the landing page?
- Is there a durable ID from click to booking?
- Are booking lifecycle events idempotent?
- Is provider state reconciled with internal state?
Common mistakes
- Treating a generic landing page as successful handoff
- Treating unknown booking state as failed
- Counting replayed conversions twice
Where does it appear in the travel stack?
Reprice commonly appears across transaction layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
NDC Offer/Order Lifecycle: Search to Servicing
Model NDC Offer/Order lifecycle across search, offer, revalidation, order creation, payment, ticketing, servicing and reconciliation states.
Explore →Stale Availability / Offer Expired Troubleshooting
Diagnose stale availability and expired offers across freshness, cache, token and revalidation layers between search and booking.
Explore →Cache Invalidation Patterns for Travel Pricing
Design TTL, event invalidation, stale-while-revalidate and live-reprice boundaries for hotel and flight pricing.
Explore →Agentic Travel Reference Architecture
Design AI agent → search → offer → reprice → confirmation → payment → booking → servicing with travel-specific authorization, idempotency and audit boundaries.
Explore →Travel Search → Offer → Reprice → Booking Reference Architecture
Design an end-to-end reference architecture for travel search, canonical offers, repricing, payment and booking across supplier integrations.
Explore →ARI vs Live Search vs Reprice: Hotel Pricing and Availability Lifecycle
Compare ARI, live search and reprice/check flows across freshness, granularity, latency, booking confidence and source-of-truth.
Explore →