Check-in, registration details, extras and departure, step by step on the right stay.

Arrivals, guests, rooms, registration data, documents, extras, payments and departures remain connected to the same stay. Front desk therefore works with one current process instead of several lists.

Booking state, arrival, departure, in-house stay, payment state and room context can be filtered and searched. This turns the booking list into clear daily control.

Front desk reviews guests, required registration data, documents, optional extras and the summary in sequence. Only the confirmed final step sets the stay to in-house.

Yes. STRYK creates individual guest steps from the expected guest count. Master data and required document details can therefore be reviewed per person.

First and last name form the basis. The property can additionally require salutation, title, email, phone, date of birth, nationality, address and custom fields.

Front desk can select an existing CRM guest. Duplicate detection helps avoid accidentally creating a second master record for the same person.

Document type, number, issuing country, issue and expiry date plus a file can be recorded per guest. Property settings determine for which nationalities a document is required at front desk.

Yes. Custom text, selection or confirmation fields add exactly the information the operation needs. Required fields apply consistently across PMS, online check-in and kiosk.

Yes. Active extras can be selected directly during check-in. STRYK calculates quantity and price per booking, night, guest, or guest and night and adds the amount transparently to the stay.

Yes. A deposit actually collected can be recorded during check-in; the paid amount increases only up to the booking total.

Rooms and housekeeping use the same operational state. Front desk sees the context on the stay and can distinguish ready from an occupied room whose stayover service is complete.

STRYK takes confirmed arrivals into check-in from the arrival date. Late arrivals remain workable after usual reception hours; incorrect stay dates are not hidden by an artificial early check-in.

The stay receives in-house status and an actual check-in timestamp. Registered guests, user and process are connected traceably in the activity log.

The specific room becomes occupied and receives the housekeeping context “stayover service required”. Calendar, room centre and housekeeping then use the same state.

Yes. STRYK checks the new room for availability and sufficient capacity over the remaining stay. Reason, old room and new room remain traceable on the booking.

Stay, room, amount already paid and-where permitted-open POS or restaurant charges are shown together. Front desk therefore sees the real balance before completion.

Open POS charges assigned to the booking flow into the check-out total and invoice completion. Outlet, description, state and amount remain reviewable.

Yes. STRYK creates and finalises the invoice from the booking. Without a successfully created invoice, check-out is not treated as cleanly completed.

Depending on the property workflow, cash, credit card, bank transfer, OTA paid, company account or invoice only are available. An actual payment is recorded only for the open invoice amount.

The stay closes with an actual check-out timestamp. The room changes to departure room-cleaning open and immediately enters the housekeeping workflow.

A confirmed arrival can be marked no-show only after the configured check-in time has elapsed. STRYK applies the stored cancellation logic, shows fee and refund and flags cases requiring manual review.

Only employees with the right role. If permission is missing or a step cannot be saved, the stay remains unchanged and front desk immediately sees what needs attention.

Only employees with the right role. If permission is missing or a step cannot be saved, the stay remains unchanged and front desk immediately sees what needs attention.