> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/en/daily-operations/move-and-cancel.md).

# Room changes and cancellation

## Move a guest to another unit

1. Open the reservation and select Change room.
2. Choose the move operation.
3. Select an available destination room, apartment or bed.
4. Review the guest, dates and destination, then confirm.
5. Verify that the guest appears on the new unit's card.

For checked-in guests, the move takes effect from the operation time. Time spent in the previous unit remains in the history. Do not try to rewrite history by manually changing a unit code.

## Exchange two reservations' units

1. Open Change room for one reservation.
2. Select the exchange operation.
3. Choose the correct second reservation.
4. Review both guests, both units and their dates.
5. Confirm and check both reservations afterward.

Both sides are validated together. Availability or a bed's guest-capacity limit may prevent the exchange. Do not create two new bookings to bypass the error.

## Cancel a reservation before check-in

1. Select the correct reservation.
2. Open Cancel reservation.
3. Complete the confirmation and any required reason.
4. Check the updated reservation status.
5. If money was received, handle any refund separately through [financial transaction records](/en/finance-and-reporting/transactions.md).

For a guest who has already checked in, use check-out instead of reservation cancellation. Cancellation does not automatically refund money through a bank or payment terminal.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.interaktifotel.com/en/daily-operations/move-and-cancel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
