Hospitality & Overnightstay07

The guest sees a stay. CORE sees every promise beneath it.

Availability, booking, operations, check-in, housekeeping and settlement remain aligned across direct and connected channels.

SCROLL TO MOVE THE CONSEQUENCE ↓

07Discovery

Discovery

Overnightstay and direct hotel channels can show the same actual capacity while the property keeps its identity and guest relationship.

INTERACTION→CORE CONSEQUENCE→EVIDENCE

Booking truth

A booking binds room type, guest, rate, conditions, payment and channel source before capacity is reduced.

INTERACTION→CORE CONSEQUENCE→EVIDENCE

A real situation, end to end · HOS-01

One room. One capacity truth across every channel.

Follow one authorised result from the first signal to durable evidence.

01Signal
Books through Overnightstay or direct.
02OPS context
Shows capacity, room rules and extras.
03Human authority
The guest confirms room, dates, occupants, extras, cancellation terms and total before the stay is booked.
04Bounded handoff
OPS hands CORE the approved reservation and capacity claim; browsing history and unchosen alternatives remain private.
05CORE record
Reserves the offer with price and conditions.
06Shared consequence
The same capacity cannot be promised twice.
07Durable evidence
The booking receipt preserves channel, room type, capacity unit, rate version, terms and payment position.

System boundaryOPS keeps the operational context. NUMA may assist inside that context. Only the approved, scoped and attributable result crosses into CORE.