Software for a pension or small hotel: what a small property really needs
Small hotel software should handle bookings, check-in, bills, and fiscal documents in one place. This guide separates must-haves from extras and lists vendor questions.
Contents
Key takeaways
- A small property needs one calendar, a channel connection, check-in that produces the KBS guest identity notification, a guest bill that survives corrections, and a fiscal document path through a licensed provider.
- Every extra module is another place where the same booking or the same guest can be recorded twice.
- One shared login saves a minute a day and removes the record of who did what; give each person their own.
- Ask for a full data export in a plain spreadsheet format, tested during the trial, before you sign anything.
- In the Ministry of Culture and Tourism's certified facility statistics for August 2026 (provisional), 12,385 facilities held a simple accommodation (Basit Konaklama) certificate with 277,561 rooms, about 22 rooms per facility (our calculation).
Small hotel software is a property management system (PMS): one place for the room calendar, bookings from every channel, check-in with the guest identity notification, the guest's bill and the fiscal document. A small property needs five or six jobs done reliably, not a resort's feature list. The rest can wait.
A small property is usually offered two things: a spreadsheet, or the full feature list of a resort system. Neither matches the work a pension actually does on a busy morning in July, when three bookings arrive at once and a guest is standing at the desk. This guide starts from the daily work, separates the must-haves from everything else, and gives you the questions to put to vendors, in writing, before you sign anything.
What does a small hotel actually need software to do?
It needs to finish the day's work: take the booking, hold the room, check the guest in, send the identity notification, keep the bill straight and hand over the right document. A feature is only interesting if it serves one of those jobs.
The day has a fixed order. Who arrives, which rooms are free, which bookings came from which channel, check-in, charges, check-out, close of the business day. Software that follows this order is easy to learn. Software that does not follow it forces your receptionist to translate between the screen and the work.
A booking must land once. A phone call kept on paper, a booking-site reservation in a portal and a walk-in typed into a spreadsheet will eventually sell the same room twice, usually on the busiest night of the season. One inventory, written to by every source, is the single most important thing small hotel software does.
Check-in produces three things at the same moment: the guest record, the identity notification and the first line of the bill. If your software handles these in three separate places, you are paying for the inefficiency every single arrival.
Corrections must be traceable. A charge posted to the wrong room is moved, or voided and re-posted, never deleted. Financial records that can be quietly deleted are not records; they are suggestions.
The fiscal document, an invoice or e-document, is issued through a licensed provider. The software's job is to hand over the right figures and keep the record of what was issued.
For a sense of scale: in the Ministry of Culture and Tourism's certified facility statistics for September 2026 (opens in a new tab) (provisional data), 12,225 facilities held a simple accommodation (Basit Konaklama) certificate with 273,955 rooms and 553,749 beds, about 22 rooms per facility (our calculation, not a Ministry figure). Public data. No endorsement implied. Most of this article is written for those properties.
Key pointThe test
Could you finish an ordinary day, from the first arrival to the close of the business day, without opening a spreadsheet or a second program? If not, the missing piece is a must-have, not a nice-to-have.
Which features are must-haves for a pension or small hotel?
Five: one room calendar, a connection to the channels you sell on, check-in that produces the guest identity notification, a guest bill that can be corrected, and a fiscal document path through a licensed provider.
One calendar means every source writes to the same room inventory: the booking site, the phone call, the walk-in, the agency email. A hold that expires returns the room to inventory by itself, without anyone remembering to release it.
A channel connection sends availability and rates out and brings bookings in. Ask which channels are supported, and how you can see that the connection last synced, because a silent failure is the expensive kind: you keep selling a room on one site that the other site already sold.
Check-in should prepare the KBS notification, the guest identity notification, inside the flow. It should not ask your receptionist to retype the same passport into a second portal.
The guest bill must handle charges, transfers between rooms, void and re-post, and a clean close at check-out. Ask to see a correction on a closed bill during the demo, not in the brochure.
The fiscal document is issued through a licensed integrator. Which document applies to you depends on your taxpayer status, so confirm it with your accountant rather than with a vendor.
Reports you will actually open: arrivals, departures, in-house list, daily revenue. A long report list is not a feature; it is a menu nobody reads. And if you take foreign guests, check the languages of the front desk screens and printed documents against the languages your staff actually read.
The five jobs, in the order they happen
| Job | What good looks like | Question for the vendor |
|---|---|---|
| Room calendar | Every source writes to one inventory; an expired hold returns the room | "If the same room is requested twice in one minute, what happens?" |
| Channel connection | Rates leave, bookings arrive, a dropped sync is visible | "Which channels, and where do I see the last successful sync?" |
| Check-in and identity notification | The KBS notification is prepared inside check-in | "Show me one check-in from arrival to notification." |
| Guest bill | Charges, transfers, void and re-post, close at check-out | "Correct a charge on a closed bill in front of me." |
| Fiscal document | Data prepared in the system, reviewed by a person, issued by a licensed integrator | "Which integrator, and who reviews before sending?" |
| Tomorrow's list | Arrivals, departures and in-house on one screen | "Show me tomorrow morning with no training." |
For the difference between these pieces of software, see PMS, channel manager and booking engine: what each one does.
Which features can wait?
Anything that does not touch today's booking, arrival, bill or document can wait until the property actually needs it.
Restaurant and bar sales matter only if you sell food and drink. Otherwise it is a screen nobody opens and a set of settings nobody maintains, and it still appears on the invoice.
Multi-property tools matter at the second property, not the first. Door locks, spa scheduling, guest apps and loyalty programs are real products, and each one is another place where the same guest or the same booking can be recorded differently. Every module costs more than its subscription: setup, training, and one more login to keep alive through the winter.
Price suggestions need history. A property with a short season may not have enough of its own yet, and a suggestion you cannot explain is not a decision you can defend to yourself at midnight in August.
With AI features, ask three things: what the assistant can do today, what a person must confirm, and whether you can see the record afterwards. A demonstration on a fictional property is not a deployment in yours.
TipThe one-week test
Before you ask for a module, name the person who will open it every week. If there is no name, it can wait until there is one.
Can one person run it from a phone?
Often yes for the daily jobs, but check exactly which screens work on a phone and which are desk work before you sign.
Owners mostly use a phone for four things: today's arrivals, a quick availability answer, a look at a bill, and an approval. If those four work comfortably on your own phone, the daily owner experience is covered.
Long bills, the close of the business day, group blocks and document corrections are desk work. Make sure the desk screens are not squeezed into a phone layout to make a sales point.
Test on your own phone, in your own lobby, on your own wifi. A demo on a vendor's laptop on a fast connection tells you little about your building, where the router lives behind the reception desk and the signal in the courtyard is one bar.
One shared login means every action is recorded under one name. When a charge is wrong, or a guest asks who opened their identity document, the record cannot answer. Give each person their own login with only the rights they need, and keep the list of people who can open identity documents short.
A browser-based system installs nothing. Ask whether anything needs an app store, and what happens at check-in when the internet drops. Write the offline answer into the contract: what you do at the desk when the connection is down, and how those bookings are entered afterwards.
Watch outShared logins
One password for the owner and two staff members saves a minute a day and removes the record of who did what. It also widens access to guest identity data to everyone who knows the password.
What compliance questions should a small property ask?
Ask how the system handles the guest identity notification, the fiscal document and personal data, then confirm your own duties, dates and penalties with your accountant or legal adviser.
In Türkiye, every stay involves a payment, a fiscal document (an invoice or e-document), a guest identity notification (KBS) and personal data (KVKK). Small hotel software touches all four, so the compliance questions are not optional extras; they are part of the purchase.
KBS: is the notification prepared and sent from the check-in flow, or do you retype it into a separate portal? Who notices when a notification fails, and what do they do? A failure nobody sees is a failure nobody fixes.
Fiscal document: which licensed integrator issues it, who reviews it before sending, and what happens to a wrong document. The answer should be void and reissue, never delete.
KVKK, the personal data protection law: where consent is recorded, how long data is kept, how a guest's request about their own data is answered, and who can open identity documents.
Data location: ask where data is stored and processed, and get the answer in writing rather than in a sales conversation.
"We are compliant" is not an answer. Ask for the mechanism, then take the mechanism to your accountant, because thresholds and dates change and only your adviser can confirm what applies to your property this year. For the details, see KBS explained: guest identity notification for hotels in Türkiye and e-Fatura vs e-Arşiv: invoicing guests and agencies in Türkiye.
NoteAsk how, not whether
A vendor can show you a mechanism: where the notification is prepared, who reviews a document before it is sent, how long data is kept. Only your accountant or legal adviser can confirm what your property must do, and when.
How do you get your data out, and what does leaving look like?
Before you sign, ask for a complete export in a plain format and read the notice period. Leaving should be boring.
The export should cover reservations, guest records, bills and issued documents, in a spreadsheet format you can open without the vendor's software. A PDF printout is not an export. Test the export during the trial, not at the end of the contract, when you have no leverage left.
Read the contract for the notice period, what happens to your data after it ends, how long the data stays available, and whether the export costs extra.
Ask whose account holds the channel connection. If it sits inside the vendor's account, leaving can take your channels with it, and rebuilding them costs you your ranking history on the booking sites.
Understand the pricing structure: per room, per module, per user, setup, support. Ask what is charged out of season when you want fewer rooms than in July. For the wider picture, see How hotel software is priced: licences, subscriptions and the costs around them.
Support: who answers in July at 23:00, in which language, and by which route. Backups: how often they run, and when a restore was last tested rather than last promised.
What belongs on a one-page comparison sheet?
Put every candidate on the same page, in writing, and make the vendor fill it in during the demo rather than after it.
Score the must-haves first. A vendor that fails one must-have is out, whatever else the sheet says. Keep the answers in writing and store them with the contract, so that the promise and the paperwork are in the same place.
Put the exit questions on the same sheet: export format, notice period, who holds the channel connection. Revisit the sheet after the trial, not after the signature. The trial is where the answers either hold or do not.
Two candidates are enough for a small property. Three is the maximum worth a week of your time.
Checklist
- One calendar: every channel, phone booking and walk-in in one inventory.
- Channel connection: which channels, and where a dropped sync is visible.
- Check-in produces the KBS notification without retyping.
- Guest bill: charges, transfers, void and re-post, close at check-out.
- Fiscal document: which licensed integrator, and who reviews before sending.
- Tomorrow's arrivals and departures on one screen.
- Phone test passed in your own lobby, on your own wifi.
- Own login for each person, rights limited to the job.
- Full data export in a spreadsheet format, tested during the trial.
- Notice period, end-of-contract data handling and support hours in writing.
- Your accountant has confirmed your KBS, e-document and KVKK duties.
For the broader vendor conversation, see How to choose a hotel PMS in Türkiye: questions to ask vendors.
What to do next
Fill the one-page sheet with your own property's answers this week, then ask two vendors to fill the same sheet in front of you. The order matters: the daily jobs first, the features second, and the exit terms before any signature. Take the compliance lines to your accountant, because that is the one part of the sheet a vendor cannot answer for you.
Frequently asked questions
Is a spreadsheet enough to run a small pension?
For a handful of rooms and a single sales channel it can hold the calendar. It cannot hold one inventory across several channels, produce the guest identity notification, or keep a bill that survives corrections. The moment you sell on more than one channel or a second person touches the bookings, the spreadsheet becomes the risk rather than the tool.
Do I need a channel manager if I only sell on two booking sites?
A channel connection is a must-have as soon as you sell in more than one place, because two booking sites plus the phone is already three sources for the same room. Whether it arrives as a separate product or inside the property management system matters less than whether one inventory feeds all of them and a failed sync is visible to you.
How long does it take to move from spreadsheets to a PMS?
There is no reliable public figure, so treat any promised duration as a claim to test. The practical answer: enter future reservations first, choose a cutover date at a quiet point in the week, run the old sheet alongside for a short overlap, and confirm the export works before you stop using it.
Does a small property have to send a KBS notification for every guest?
The guest identity notification is a legal duty of lodging facilities in Türkiye, and the practical question for a small property is how the system prepares and sends it. Which details are required, how foreign guests' documents are handled, and what happens when a notification fails should be confirmed with your accountant or legal adviser.
What should I check before signing a one-year contract for small hotel software?
Five things: the export format and whether you tested it, the notice period, what happens to your data when the contract ends, whose account holds the channel connection, and what is charged in the low season when you want fewer rooms. Add support hours in writing, and your accountant's confirmation of your compliance duties.
Sources
- Bakanlık Belgeli Tesislerin Oda ve Yatak Sayılarının İllere Göre Dağılımı, Eylül 2026 (Eylül 2026 Bakanlık Belgeli Konaklama Tesisi İstatistikleri, xlsx), 'Genel Toplam' row (opens in a new tab)T.C. Kültür ve Turizm Bakanlığı, Yatırım ve İşletmeler Genel Müdürlüğüyigm.ktb.gov.tr