YFCleaning is housekeeping and cleaning management for apartments, serviced apartments and hotels. Once connected to apaleo, it turns reservations into scheduled cleaning jobs, gives cleaning staff a mobile task list with checklists and photo documentation, and writes the housekeeping condition of each unit back to apaleo.
| Direction | Data |
|---|---|
| apaleo → YFCleaning | Properties and units |
| apaleo → YFCleaning | Reservations (Confirmed, InHouse, CheckedOut) with time slices, services, booker and primary guest |
| apaleo → YFCleaning | Maintenances (out-of-order / out-of-service blocks) |
| apaleo → YFCleaning | Reservation events in real time via webhook |
| YFCleaning → apaleo | Housekeeping condition of a unit only: Clean / Dirty |
YFCleaning writes nothing else back. It does not create, change or cancel reservations and does not touch rates, availability, folios, invoices or guest profiles.
Permissions requested (least privilege): reservations.read (derive cleaning jobs), setup.read (properties and units), maintenances.read (skip blocked units), operations.change-room-state (write Clean/Dirty back), plus offline_access, openid and profile. No write scope beyond the room state.
Personal data stored per reservation: guest name, number of adults and children, children's ages, arrival and departure time, unit and property — what a cleaner needs to prepare a unit (extra beds, cots, towels). Details in our privacy policy.
From the apaleo Store: open YFCleaning, click Connect, sign in to YFCleaning or create your account, confirm the apaleo permission screen — done.
From inside YFCleaning: sign in as an admin, go to Settings → PMS connection, click Connect apaleo, confirm the permission screen.
At that moment YFCleaning automatically stores the tokens for your account only, registers a webhook for reservation events (the endpoint URL contains a secret unique to your account), imports your properties and units, and creates the first cleaning jobs. Nothing to map, nothing to enter by hand — setup usually takes a couple of minutes.
Unit mapping: none required. YFCleaning uses the apaleo unit ID directly, so units match one to one and survive renames.
Properties: all properties of the connected account are synchronised. Exclude individual ones under Settings → PMS connection → Excluded properties.
| Reservation event | Cleaning job |
|---|---|
| Departure | Departure cleaning in the checkout time window |
| Arrival | Arrival preparation before the checkin window |
| Stay extension | Interim cleaning inside the stay |
| Room move | One job per unit, segmented, so each apartment gets its own cleaning |
| Cancellation | Matching open jobs are removed |
| Unit blocked (maintenance) | No cleaning scheduled for that period |
Keeping in sync: the webhook delivers events in real time; a reconciliation run once a day repairs anything a missed delivery left behind; opening the calendar refreshes the visible period. Manual trigger: Settings → PMS connection → Sync now.
Room status write-back: completing a job sets the unit to Clean in apaleo; a checkout sets it to Dirty. If a write fails because apaleo no longer knows the unit, run Sync now to refresh the unit list.
Please contact us first — most reasons for disconnecting are a setting we can fix in minutes.
From apaleo: Apps → Connected apps → YFCleaning → Disconnect app.
From YFCleaning: Settings → PMS connection → Disconnect. This deletes the webhook subscriptions YFCleaning registered in your apaleo account, revokes both the refresh and the access token at apaleo, and drops the stored tokens. If you disconnect on the apaleo side, run the YFCleaning disconnect afterwards as well so the webhook is cleaned up too. Your cleaning history, checklists and team stay in YFCleaning; only the apaleo link is removed.
E-mail: rental@yfbed.de
Web: yfcleaning.de/contact
YourFavoriteBed GmbH, Goldweiherstraße 59, 90480 Nürnberg, Germany
Common questions: You do not need apaleo to use YFCleaning — tasks can be created manually. Cleaners see only their assigned jobs and only the guest details needed to prepare the unit. If a booking looks stale, run Sync now; the nightly reconciliation catches it in any case. If the connection asks you to reconnect, the refresh token was revoked on the apaleo side — reconnecting is one click and no data is lost.