Running a group

Opening several hotels at once

For a portfolio, send the room list as a spreadsheet rather than running the form twenty times.

Twenty hotels through a form is a week of clicking and a week of typos. For a portfolio, the same information goes in as two spreadsheets:

One row per hotel — code, name, city, state, GSTIN, address, PIN.
One row per room type — which hotel, the type, how many rooms, which floors, and the nightly rate.

It is always run as a dry run first, which prints exactly what would be created and writes nothing. Bad rows are named and refused before anything happens — a room type with no rate is refused outright, because it would make a hotel that looks created and cannot be sold.

Each hotel is created staged, and a hotel whose code already exists is left alone, never overwritten. So a second run after fixing three rows touches only those three.

Ask your Asar contact to run it; it needs the room list, not access to anything of yours.

More in Running a group

Running a group of hotelsOne login, one guest history, one set of reports — and each person scoped to the hotels they work at. Adding a hotel to the groupSetup → Add a hotel. One form builds a complete, sellable property. Every booking in the groupOne list across all your hotels, and why it shows different things to different people. Who works at which hotelTick the hotels a person works at. They see no others, anywhere in the product. Before a hotel takes its first bookingThe onboarding board lists what each hotel still needs. Work down it, then open the hotel. Seeing across all your hotelsReports are per hotel today. Group-wide dashboards and central rate changes are not built yet.