Create and update a Stay

Create a Stay for a known Guest and keep its dates and status accurate. You need Stay create or update permission; available Guests and Units are limited to accessible Properties.

Create or edit

From the left sidebar, select Stays, then select the Add Stay button. To update one, select it and then select the Edit Stay button.

• Guest is required. It determines the Property and protects tenant scope. If no Guests exist, use the Add Guest or Import guests button first.
• Property follows the selected Guest; a Stay cannot be assigned across Properties.
• Room / accommodation unit selects an active Unit belonging to that Property. Leave it empty if individual units are not needed.
• Check-in and Check-out are required dates. Departure cannot precede Arrival and drives operational timing.
• Status is required: Upcoming, Checked in, Checked out or Cancelled.
• Source is optional and describes where the booking or Stay originated.
• Reference is optional and stores the booking identifier used by the source or Property.
• Notes are optional internal operational context; keep them necessary and appropriate.

For a new record, select the Add stay button; when editing, select the Save changes button. ELUNIA validates the record and opens the Stay page. From there, authorized users can create a manual Survey invitation using an active Survey for the same Property.

Checkout and stale departures

Changing Status to Checked out records an operational event. If a checkout-anchored Automation is active and its configured time is already due, the Stay may become immediately eligible for evaluation and a Survey invitation. Check Guest contact details and sending readiness before saving; ELUNIA still applies eligibility and exactly-once protections.

If Departure passed while the Stay remains Checked in, ELUNIA asks you to mark it Checked out if the Guest departed, or extend Departure if the Guest is staying longer. ELUNIA does not check the Guest out automatically.

An active integration-backed Stay is provider-authoritative. Avoid conflicting manual changes; inactive or disconnected integration authority returns the Stay to ELUNIA/manual lifecycle assistance.

If saving fails, correct the highlighted field, confirm the Unit belongs to the Guest’s Property, and ensure Departure is not before Arrival. Permanent deletion requires permission and no protected invitation, response, communication, automation occurrence, feedback or integration history. A blocked deletion preserves the stay and explains why. Use Cancelled only when that is the truthful business outcome; cancellation is not deletion.

Add a missing unit without leaving the Stay

Select the Guest first. If you can manage that Property, select Add new unit beneath Room / accommodation unit. In the dialog, enter Unit name, choose Type, then select Add new unit. The new Unit is selected automatically and your entered Stay details remain. Correct any errors inside the dialog, or select Cancel to return without creating a Unit. Creating a Unit does not save the Stay; finish with Add stay or Save changes.

For Check-in and Check-out, type the displayed date format with a four-digit year or use the adjacent calendar control. Separators such as /, . or - are accepted for day/month and month/day input according to your displayed format; ELUNIA never guesses which comes first. Impossible dates and Check-out before Check-in cannot be saved.

New manual Upcoming stays must start today or later in the property timezone. Past dates are disabled/rejected for that creation path. This does not prevent historical/imported stays or rewrite existing dates.