Everything we have built into the platform, chronological, per feature.
You can now change the arrival and departure of a booking yourself, with a calendar and a suggestion for the new rent. Villantis also has a status page that anyone can open, extras can be described in English and French, and everything premium is switched on from one block. Also on these days: an open portal tab asks you to reload after an update, properties that are not live no longer take enquiries, and a round of smaller fixes.
On the Booking tab, card Stay, Arrival and Departure can now be changed. A calendar under the fields shows your current dates, the new ones and what is already taken. When the dates change, Villantis suggests a new rent: the current rent plus the difference in price between the new and the old period. Use this puts it in the Rental field. The rent never changes by itself, and with no price for one of the nights there is no suggestion.
The screen warns about a different changeover day, a stay shorter than the minimum and a year that is not open yet, and you can still save. Dates that overlap another booking or a closure cannot be saved at all. The dates are locked on a booking that comes from a connected feed (iCal or the channel connection), after the stay and after a cancellation. Once the stay has started, only the departure can change. The guest gets no separate email about the change. Emails that become due on the new dates, such as the balance reminder, go out as usual, and a contract you already sent counts as out of date, so you send it again.
What to do: nothing. Change the dates in the booking when a guest asks. More in the documentation.
Villantis administrators can no longer change Rental, Discount or what is charged per cost line on a booking, also not with support access or emergency access. The fields are read-only for them. The owner and the agent keep changing the amounts. The one exception is a property that Villantis manages itself, with no owner and no linked agent.
What to do: nothing. More in the documentation.
The portal already left guest details out for people who may not see them. There is now a second check at the moment the answer is sent: if a booking without guest details would still carry a guest field, the answer is refused and Villantis is alerted. You will not notice this unless something is wrong.
What to do: nothing. More in the documentation.
A file that comes with an email from a guest, shown with the message on the Messages tab, can only be opened once a virus scan has found it clean. While the scan is running, or when it found a problem, there is no download link. This is the first step. Files that came in before keep working as they did, and the scan itself for these attachments follows in a later update.
What to do: nothing.
The portal's code used to carry internal developer notes to your browser. They are now removed when the portal is published, and licence texts stay. This does not change anything you see or do.
What to do: nothing.
On a property without an owner and with one commission agent, every booking counted for that agent automatically. When the first owner was linked to such a property, that automatic link ended and bookings without an agent of their own lost their commission. Now the agent is fixed on those bookings at the moment the owner is linked, and a line in the property's log says which bookings were changed.
What to do: nothing. More in Reporting, under Commission.
On a property with no owner and no linked agent, Villantis manages the property itself. It now sees and manages the property attachments there (policies and agreements) without asking for support access, and the warnings about an attachment that is about to expire reach it too. On every other property nothing changes: without support access Villantis still does not see your attachments.
What to do: nothing. More in the documentation.
A message, a file, chosen extras, a cancellation request or a dog request from a guest normally goes to the owner or the agent. When nobody else can receive it, it reaches Villantis Support. Without support access that email now names only the property, the booking number, the dates and the kind of notification. The guest's name, email address, phone number, message text and file name are left out, and a reply goes to Support instead of to the guest. A new enquiry already worked this way.
What to do: nothing. More in the documentation.
When an agent is unlinked from a property, or removed, the bookings of that property that were assigned to this agent get a new link to the guest's My booking page. A link the agent saw earlier no longer opens anything. The price is that the link in emails the guest already received stops working too. Every email sent from now on carries the new link.
What to do: nothing, unless a guest tells you that the link in an older email no longer opens. The link in their most recent email works. More in the documentation.
Requests to the portal are now recorded technically for 90 days: who, when and which part, never the content. If a Villantis administrator changes something, also on a property where it has no support access, that can be traced afterwards. You do not see this record. The Support access log on your property stays the place to look.
What to do: nothing. More in the documentation.
Villantis administrators have a new view under Reporting → Status. It lists every monitoring alarm per group with its state, since when, 30 day bars and the changes of the last 7 days, next to tiles for active alarms and the channel sync. Owners and agents do not see it; the public page stays on status.villantis.com.
What to do: nothing. More in the documentation.
On a property where Villantis otherwise only reads, the card OpenGDS / channel connection on the Connections tab was missing for the platform. It is shown again on every property.
What to do: nothing. More in the documentation.
On status.villantis.com you can see whether Villantis is working, without signing in. It shows six parts: Booking widget, Emails to guests, Owner portal, Incoming email, File uploads and Nice2Stay. Each part says Works or Problem, shows a bar for each of the last 30 days and the share of time it was available. Below that, Past incidents lists recent problems that have been resolved. The page never shows a property, a guest or an error message. You find the link in the footer of villantis.com.
What to do: nothing. Bookmark it if you want to check before you call us. More in the documentation.
Under Costs & extras, next to the description of an extra, there is a button + EN/FR. It opens a field for the English and one for the French description. A guest now sees the extra in their own language: in the offer, the extras email, on their booking page, in the booking widget and in the rates block. A language you leave empty falls back on the Dutch description, so nothing breaks for extras you already have.
What to do: add an English and a French description to your extras if you have guests in those languages. More in the documentation.
On the Administration tab the platform now has one card Premium with four switches: mails from your own domain, your own email flow, your own rental contract and the property site. Under each switch it says whether the feature is in use. The separate premium switches on the Guest contact and Contract & payment tabs are gone. The property site is now a premium feature: without it the card on The house tab says that the feature is not enabled yet, and a site that was already online stays online but is no longer updated. You can still choose not to use a premium feature, for example by unticking Send mails from own domain. The right stays, and the platform sees that you do not use it.
What to do: nothing. Want a premium feature for a property? Ask via Support. More in the documentation.
A portal tab that you left open during an update used to run the old version against the new system, which could damage data when you saved. Now a bar appears: There is a new version of Villantis. Reload to continue. Until you click Reload, saving is refused. What you had typed is not lost: open property settings and an open booking come back after the reload, and other typed text is shown in a window so you can copy it.
What to do: when you see the bar, click Reload and carry on. More in the documentation.
Under What's new in the sidebar there used to be a version number that was never updated. It now shows the date of the newest release notes, for example 30 Oct.
What to do: nothing.
The booking widget of a property that is still in preparation no longer loads, shows no price, and a request sent to it anyway is refused: no booking card, no email, no contact. Before, such a property could still receive enquiries. Your own calendar and board keep working.
What to do: switch the property to live in the Ready to go live? card on the Overview tab when it really rents to guests. More in the documentation.
When you unlink an agent from a property, that is now written to the property's log. You keep seeing that agent under Agents, with the property unticked, so you can invite them again. This works for unlinking from 29 October on.
What to do: nothing. More in the documentation.
A visitor of your booking widget can now ask for the price at most 60 times per minute. Someone who asks far more often, a script for instance, sees no price block for a moment while the widget keeps working. Before, one such visitor could make the price disappear for everyone. An ordinary guest will not notice.
What to do: nothing.
The reminder email to the owner about an agreement or policy that ends or renews could be lost when sending failed on the last day. It is now tried again for up to 3 days after the date, and the email says yesterday or 2 days ago instead of a number of days left.
What to do: nothing. More in Costs and agreements.
It was possible to put two attachments on the same cost line. A line now holds one attachment. A second one is refused, and that save leaves the attachments as they were.
What to do: to replace an attachment, remove the old one first and then add the new one.
When you set an email in your own flow to be sent separately and then saved it in the editor, the setting was lost. It now stays. The quality check also no longer judges the order of the reminder days on a property that has its own email flow, because that flow sets the moments itself.
What to do: nothing. If you saved an email in the flow editor earlier, check that the ✂️ is still on where you want it.
When the email address on a booking is not valid, the email round now skips that booking with one log line instead of failing every round, and the nightly quality check flags the booking (without the address itself). The guest gets no email until the address is right.
What to do: if a guest says that nothing arrived, check the email address on the booking. More in the documentation.
The email editor on a phone no longer scrolls sideways after you insert an image or type a very long word. In the cost rows on Costs & extras the Amount column is wider, so an amount of five digits fits, also in French.
What to do: nothing.
The Manage tab of a booking now has a log of what happened to it, and when you choose a password the requirements tick off as you type. Also on this day: the booking widget and the email editor look tidier, a note when the widget shows a price on a property with flexible prices, half-filled price rows stay, your own enquiry confirmation can show what is paid on site, the welcome email no longer mentions a deposit of € 0, new quality control points for placeholder texts, and two rules for Villantis Support on property attachments and invitations.
At the bottom of the Manage tab of a booking there is a block Log. It lists what has been written down about the booking, newest at the top: the kind of entry (Offer + contract sent, Down payment confirmed, Signed contract saved, Booking changed, …), the date and time, who did it and a note where there is one. The first ten lines show; Show all opens the rest. You cannot edit the log. Because a note can hold an email address, you see it only when you may see the guest's details. Villantis Support sees it only with support access.
Two labels were also made clearer: a change to a booking now reads Booking changed (it used to name only the channel, amount and discount), and the storing of a signed contract reads Signed contract saved. An address change shows (empty) for a part that was empty, instead of a dash.
What to do: nothing. Open a booking and go to Manage when you want to know what happened. More in the documentation.
When you choose a password (at your first sign-in, after Forgot password? and under Change password in your profile), the requirements now stand below the field: at least 12 characters, an uppercase letter, a lowercase letter and a number. Each one gets a tick as soon as your password meets it, and the button only turns on when all of them are ticked. In your profile it also checks that both passwords match. If the server still refuses a password, the message is now in the language of the portal and lists the requirements. Before, it was an English message without the list.
What to do: nothing. More in the documentation.
The calendar in the booking widget on your website shows two months side by side. Their heading now reads jul / aug 2027, and dec 2027 / jan 2028 across the new year, instead of a dash. On the Connections tab the two code blocks that were called Snippet: … are now Booking widget: for the owner's website and Booking widget: for the agent's website (also in Dutch and French). The code itself did not change, so nothing on your website needs replacing.
What to do: nothing. More in the documentation.
When Show the price in the booking widget is ticked on a property with flexible prices, a note now appears under the checkbox on the Connections tab, and the quality control reports it too. The widget then shows the exact price for every period a guest picks, also where the property site only gives a from-price. If you never touched the checkbox, nothing is reported: flexible prices keep the price hidden by default.
What to do: if the note shows and you do not want it, untick the checkbox. If you do want it, leave it as it is. More in the documentation.
On the Prices tab, a + Period or + Step row that you had only half filled in could disappear when you added another row, removed a different one, changed the occupancy tiers or set a price in the price calendar. Worse, the ✕ next to a half-filled step could remove the wrong row. Now the row stays until you fill it in or remove it. Save still does not store a half-filled period: it says Not complete: a year or period without a valid date is not saved.
What to do: nothing. More in the documentation.
If you built your own enquiry confirmation in the email flow and put {terplaatseblok} in it, that block stayed empty. It now shows the same on-site lines as the standard confirmation. When the email also has the request details ({aanvraaggegevens}), the on-site costs appear once, where you put {terplaatseblok}, and no longer under the request details as well.
What to do: nothing. More in the documentation.
On a property that asks no security deposit (Deposit is 0), the welcome email and the paid-in-full email said that a deposit of € 0 would be returned. They now only mention the final cleaning. A property with a deposit reads as before.
What to do: nothing. More in the documentation.
On live properties the check already looked for placeholders in the contract details. It now also looks at the texts guests read in their emails: Property name, Short description, Sender name, Address, Arrival and departure, People on site, Extras, Additional costs and the captions of the Arrival photos. A text such as placeholder, xxx or tbd gives an attention point on the Overview tab with the field and the text. An empty field is fine.
What to do: if the check names a field, replace the placeholder with the real text. More in the documentation.
For the agent's commission on a cancellation, a property has no owner when it has no owner account and no usable Owner's email address. The Sender email address is for sending and never counts as an owner. So on such a property the commission is recorded according to the agreement, even if a sender address is filled in. A property with an owner account is not affected.
What to do: nothing. More in the documentation.
When you give Villantis Support View only access, support now really sees the property attachments (Costs and agreements on the Administration tab) with Open, Download and the preview, but without Add file or Replace. Until now the list stayed hidden at that level, although the rules allowed it. Each time support opens or downloads one, it shows in the Support access log.
The other way round: without Assist or emergency access Villantis Support can no longer withdraw an invitation you sent to an agent. The Withdraw button is greyed out and the server refuses it, the same as for unlinking an agent.
What to do: nothing. More in the documentation and under Agents.
What to do: nothing.
The confirmation to the guest and your notification of a new enquiry now list the same amounts as the price in the booking widget and the offer, and a returning-guest discount is no longer asked of you twice. Also on this day: on a property without an owner account the agent's commission on a cancellation follows the agreement, the subject of a notification no longer carries the guest's full name, and the labels you type show as plain text in emails.
When a guest sends a request, the confirmation and your notification now show the same lines as the widget: the rent, a discount if there is one, the costs (cleaning, for example, and the extras the guest ticked), the tourist tax or the line that says it is included, and the total. What is paid on site stands apart below it. Before, your notification only had the rent and the tourist tax, so its total could differ from what the guest saw.
What to do: nothing. More in the documentation.
The banner Returning guest in your notification used to say Remember to apply the discount to their quote. That was no longer true: the discount is already in the amounts of the enquiry emails. The banner now says This discount is already included in the price above.
What to do: do not deduct the discount a second time when you write the offer.
When a booked stay on a property without an owner account is cancelled, an amount is retained and the agent has commission terms, nobody is asked to decide. The commission is recorded as yes according to the agreement, the same way as the owner would have granted it. In the Cancellation fold-out on the Payment tab of the booking you read recorded as agreed (no owner) on the date, and a line is added to the booking log. No decision email goes out, and the nightly quality control no longer warns about a missing owner email address on such a property.
What to do: nothing. If a property has no owner and you do not want the commission on cancellations to follow your agreement, change the commission terms of the agent before you cancel. More in the documentation.
The subject of your notification of a new enquiry, extras, a cancellation request, a message from the guest and a file from the guest used to carry the guest's full name. It now shows the first name and the initial of the last name (for example Anna V.) together with the booking number, so the full name no longer sits in every mailbox list and forwarded mail. The full name is still in the email itself.
A new enquiry on a property that nobody manages ends up at Villantis Support. That email now comes without the guest's details, only the property, the booking number, the dates and the number of guests, unless Support has support access to that property.
What to do: nothing. If you filter your mail on the guest's name in the subject, use the booking number instead. More in the documentation.
The names you give to cost lines, extras and on-site payments are now shown as typed in the guest's emails and in your notifications. A name with a sign such as < or & could come out wrong or be read as formatting. Names without such signs look exactly as before.
What to do: nothing.
A guest can send you a file from their booking page and you see at once that it is new, photos and PDFs open without downloading, you can put images in your emails, a discount can be typed when you add a booking, a guest address you fill in also lands on the contact, a bundled email gets a proper subject, and the tourist tax included in the rent has its own line. Also on this day: above the board a list of everything that is waiting for you, an unanswered guest message stays on that list until you answer, the overdue down payment follows one rule, you can fill in a guest's address yourself, a guest gets a message box on the booking page and you are told at once, the Messages timeline also shows every email that was sent, support emails have a button to the ticket and your replies by email land in the ticket, support tickets can be assigned and have a new screen, every notification to you is in English, the reply to a guest can go without greeting and sign-off, the channel choice is grouped, the booking widget can show a price estimate, Villantis sees property attachments only with support access, and a few smaller things.
A visitor who picks dates and the number of guests in your booking widget now sees a block Price estimate before sending a request. It shows the rent, a discount if there is one, the costs that apply (cleaning, for example), the tourist tax and the total. What is paid on site and the security deposit are listed apart, with the line Estimate, the owner confirms the booking. The block also appears when the dates are already in the link, and it speaks the language of the widget.
What to do: nothing to replace on your website, the snippet and the link you already use show it. Check the checkbox if you want it the other way round. More in the documentation.
The policies and agreements you attach under Costs and agreements on the Administration tab are now as private as the guest details. Villantis Support sees them only while you have given support access to that property, or while Villantis has started emergency access. Without access the list is replaced by the note Property attachments are only visible with support access.
What to do: nothing. Only if you ask support for help with an agreement or a policy, give View only access first. More in the documentation.
On the guest's My booking page there is now a block Send a file, under the message block. The guest presses Choose a file and Send file and sees their own files with a state: being checked, received or file rejected. A PDF, JPEG, PNG, WebP or HEIC file, up to 10 MB, at most 5 files per booking.
What to do: nothing. It is on wherever the booking page is on. More in the documentation.
A file the guest sent shows as the chip 📎 new file on the card on the board, as a counter on the Documents tab of the booking, and as View new file from the guest in Open actions. Open the Documents tab, or download or open the file, and it counts as seen: the chip, the counter and the item go away, and the list says seen on … by …. Files with a virus, files still being scanned and your own uploads never count as new. Villantis Support with read-only access sees the counter but does not clear it, so you keep the reminder.
What to do: have a look when the chip is there. More in the documentation.
In the Documents tab of a booking, and in the attachments under Costs and agreements on a property, a JPEG, PNG or WebP photo now has a small preview. Click it for a large view with Download and Close. A PDF has an Open button that opens it in a new tab. Other types, HEIC photos for example, can still only be downloaded. Looking only works after a clean virus scan.
What to do: nothing. More in the documentation.
There are three places now. In a draft in manual sending mode, press Insert image. With your answer to a guest (Messages tab, Reply to the guest), press Add image; the image goes below your text. And on the property, tab The house, the block Arrival photos takes up to four photos with a caption, for example where the key box is. They appear in the welcome email, under the address and the arrival times.
What to do: nothing, unless you want pictures in a mail. More in the documentation.
The form behind + Booking now has a field Discount next to Amount (€). Type a percentage (15%) or an amount (200). It works like the discount on the booking screen, including the notice when the discount is higher than the rent. A discount that cannot be read is refused with a message, and nothing is saved.
What to do: nothing. More in the documentation.
When you fill in a guest's address on the booking (Booking tab, card Guest), the parts you changed now also go to that guest's contact. It only completes the contact: a part that is empty there is filled in, a part that is already there stays as it is. To change an address that is already on the contact, use Contacts.
What to do: nothing. More in the documentation.
When several emails go out together as one message, the subject was sometimes only the property's name. It now follows the part the guest has to act on: the contract first, then the balance request, the deposit request, the offer and the welcome email. A message with the contract in it is named after the contract.
What to do: nothing. More in the documentation.
For a property that includes the tourist tax in the rent, the card Price on the booking screen now has the line Tourist tax: included in the rent, without an amount. Before, the total said incl. tourist tax and there was no line to explain it. The total, the emails and the contract are unchanged.
What to do: nothing. More in the documentation.
Above the board there is now one list of everything that is waiting for you, across all your properties: requests to decide on, money to tick off, guest messages to answer, contracts to send again, property checks, support answers and invitations. What is late sits on top under Overdue; the rest is in groups (Decide, Money, Messages, Emails and contract, Properties, Support, Invitations) that you can filter with the buttons under the heading. Each row has a button that takes you to the right place, the booking on the right tab, the property at the field, the ticket. The money rows say Tick off receipt. Click the heading Open actions to fold the list away; it remembers that in your browser. Choose one property at the top of the board and the list follows. The invitations and commission proposals that used to sit in a banner above the board are in this list now, with Accept and Decline.
For Villantis Support the list also holds the support requests that wait for an answer (with Only assigned to me), the property checks of live properties and failed channel syncs; booking steps only appear on properties where support may work along.
What to do: nothing. It is there when you open the portal. More in the documentation.
When a guest writes to you from the booking page, it now counts as unanswered. (A guest who replies to one of your emails reaches your own mailbox directly; those replies are not on the list yet.) It shows in Open actions as Reply to the guest's message, and on the booking, on the Messages tab, as Unanswered message from the guest. It goes away when you save a reply to the guest, or when you press Resolved, for a guest you sorted out by phone, say. Automatic replies (an out-of-office message), anything marked as possible spam and mail from a sender Villantis could not verify do not count. Only messages that arrive from now on are tracked.
What to do: answer the guest, or press Resolved when no answer is needed. More in the documentation.
The badge on the card, the Down payment received step and the Open actions list now all use the same rule, so they can no longer disagree. A booking is overdue only when it is Confirmed, the down payment has not been ticked as received and its date has passed. It no longer shows on a booking that is still an Offer, on a channel booking (the guest pays the channel), on an Own stay, or when nothing is charged.
What to do: nothing. More in the documentation.
On the booking, on the Booking tab, the card Guest now has four address fields: Street and number, Postcode, Town and Country. Use them when your property does not ask the guest for the address (the setting Let the guest fill in their own address is off) (the contract was waiting for it) or to correct what a guest typed. Once street, town and country are filled in, the contract can go out. When that setting is off and a confirmed booking has no address yet, the Next step card and Open actions say Fill in the guest's address, and the button Go to the address puts the cursor in the first empty field. After a cancellation only the owner can still change it. Villantis Support can see the address with support access, but never change it.
What to do: nothing, unless you handle addresses yourself. More in the documentation.
When a contract that was sent is out of date and can be sent again, the Next step card on the booking and Open actions now say Send the contract again, with the button Go to the contract. Until now you only saw the notice on the booking itself. Nothing is sent by itself: you still decide.
What to do: nothing. More in the documentation.
When you create a ticket under Support & feedback there is now a list Property: pick the property your question is about, or General / no specific property. If you manage exactly one property, it is already selected. The ticket page shows your choice under Property, and Villantis Support sees it too, in the ticket and in the email about it. Older tickets, from before this choice, show Requester's properties instead.
What to do: nothing. Pick the property when you write a ticket. More in the documentation.
You can now mark your own ticket as resolved, and reopen it, from the ticket page with Mark resolved and Reopen. Until now only Villantis Support could. Under Status a line shows who resolved or reopened it and when. Villantis Support is notified when you close a ticket.
What to do: nothing. More in the documentation.
Villantis Support now replies in the portal: the notification emails to support no longer reply directly to you, so the whole conversation stays in the ticket thread. Your own replies by email work as before. You still get every answer in your mailbox and can reply to it.
What to do: nothing. More in the documentation.
The email a guest gets when you answer from the booking screen (Messages tab, Reply to the guest) was the only guest email without the link to the guest's booking page. It now ends, like every other guest email, with View your booking → and the line Questions? Send us a message via your booking page →, in the guest's language. The link is only there when the booking page is on for the property.
What to do: nothing. More in the documentation.
For Villantis Support: on a ticket, in the box Ticket information, you pick a colleague under Assigned to, or Nobody to take it back. A line under it records who assigned it to whom and when. In the ticket list there is a column Assigned to and a filter Show → Assigned to me for your own tickets.
What to do: nothing. More in the documentation.
On Support & feedback the tickets are now a compact list: one row each with the subject, number, type, when it was last updated and the status. Click a row and the ticket opens on its own page, with ← Back to tickets at the top, the Original message, and the Conversation underneath. With more than one reply a button switches between ↑ Oldest first and ↓ Newest first (your choice is remembered). Replies from support are labelled Villantis Support, replies that came in by email by email. The box Ticket information on the side shows the status, type, created and last-updated time, who reported it, who it is assigned to and the property, with a button Reply that takes you to the reply field.
What to do: nothing. Same tickets, same replies, a different layout. More in the documentation.
The emails Villantis sends to you or your agent used to follow the language of the guest or were in Dutch. They are now always in English: a double booking, a pet request, extras chosen or requested, a cancellation request, a message from the guest, the decision on an agent's commission (and the page behind its link), the reminders for agreements and policies, a change of bank details, a change of owner, an agent being unlinked, and support access and emergency access. Dates are written the English way.
What to do: nothing. The guest's own emails are unchanged. They stay in the guest's language. More in the documentation.
Under Reply to the guest (Messages tab of a booking) there is a checkbox Add greeting and sign-off. It is ticked, as before: the email opens with a greeting and ends with the usual regards. Untick it and the guest receives only your text (with their own question quoted underneath) in the normal email layout, handy when you write your own greeting. Villantis remembers your last choice in your browser, and warns you with Your message already has a greeting or sign-off. Untick this box? when you typed one yourself.
What to do: nothing. More in the documentation.
On the guest's My booking page there is now a block Send a message: a field Your message and a button Send message. Every guest email that links to that page now has a second line under the link, Questions? Send us a message via your booking page →, which opens the page at the box. Until now a guest could only reply to an email.
What to do: nothing. It is on wherever the booking page is on. The notification email is in English, like every notification to you (see the item below). More in the documentation.
On a booking, the Messages tab now lists the guest emails Villantis sent, next to what the guest wrote, in one timeline with the newest on top. Each one shows the kind of email, the time and the subject, labelled Sent; Show email opens it as the guest received it, Hide email folds it away. This works in every sending mode, not only manual. Handy when a guest says they never got something. You can read exactly what went out and when.
What to do: nothing. Only the owner and an agent who may edit the booking see the timeline, as before. More in the documentation.
An email about a support ticket now has a button View and reply →. It opens the ticket in the portal: you sign in and land on Support & feedback with that ticket marked. Under the button it says You can also simply reply to this email. That works: your reply appears in the ticket below the other replies, marked by email. Support emails are always in English, and no longer repeat the original message under every reply.
[Ticket TKT-…] in the subject. A reply that cannot be linked still reaches Villantis Support, just not in the ticket.What to do: nothing. More in the documentation.
The channel list on a booking is now grouped: No guest (Own stay), Direct (WhatsApp, email, phone, returning guest, in person) and Through a channel (Nice2Stay, VillaSud, Booking.com, Airbnb and the channels you set a commission for). An own stay now stands out instead of hiding between the guest channels. The choices themselves and everything that depends on them are unchanged.
What to do: nothing. More in the documentation.
The extras email no longer opens with “Fancy a little extra comfort?”. It now says, in your guest's language, that they are staying with us for so many nights and can add the extras: just let us know and we'll arrange it. The word villa is gone from that sentence too, because not every property is a villa. Only the opening sentence changed.
The emails you get when you are invited or reset your password are now sent by the same mailer as every other Villantis email, including the plain-text version. They look the same, but land in the inbox more reliably.
What to do: nothing.
Villantis Support can now only look at a property unless you let it in, with a 4-hour emergency access that always tells you, accounts no longer pass passwords around, you can let Villantis Support look along for a limited time, the booking screen has tabs and a Next step card, channel payouts are confirmed with the amount you really received, and a cost can start in a given month. On a booking you now also choose, per cost line, whether it is charged, and you see what is paid on site.
A cost line you switch off for a booking (card Price) is now also left out of that booking's contract. Before, only the tourist tax followed; now the contract also drops the final cleaning, linen, EV charging point and your own cost items when they are off. With linen off, the contract also no longer says that linen is included in the rent. The security deposit always stays on the contract.
What to do: nothing for new contracts. For a contract that has already gone out, see the next item. More in the documentation.
If something that is printed on the contract changes after you sent it, the booking screen now tells you: The contract was sent with different details than now. Next to it is a button Send the contract again. That covers the rental, the discount, the guests, the dates, the guest's name and address, the cost checkboxes, and the property settings that appear on the contract (for example the bank details, the costs, the cancellation conditions).
What to do: when you see the notice on a booking, open it and decide whether to send the contract again. More in the documentation.
In the booking screen, card Price, every cost line of the property now has a checkbox in front of its name, the lines on the invoice as well as the ones paid on site. Untick a line and it is struck through and no longer counts in the total, the guest emails or the guest's booking page. The line stays on screen, so you can tick it again. Save, and the total is updated.
What to do: nothing, unless you want a booking to charge differently: for an own stay where you do want costs, tick them on. More in the documentation.
Under the total in the card Price there is now a block Payable on site: the costs the guest settles on arrival, the same lines as the block about paying on site in the guest email. They are not part of the total, because the guest does not transfer them. The block only appears when there is something to pay on site. A channel booking shows no cost lines at all. Its total is the rent.
What to do: nothing. More in the documentation.
Until now Villantis Support could make operational changes on any property. That is over: without support access, a property is read-only for Villantis. In the property's settings support sees Read only: ask the owner for support access (Assist)., and a booking shows 🔒 Read only; a change is refused. Skipping a guest email and deleting a contact now need View only access as well.
What to do: nothing. If you want support to change something for you, give Assist access. More in the documentation.
If there is an outage or an urgent problem and you cannot be reached, Villantis can give itself emergency access to a property. It needs a written reason (at least 10 characters) and a sign-in from the last 15 minutes, and it lasts 4 hours. It gives what Assist gives, plus the right to view, never change, the bank details. A guest's address, replies to guests and the private iCal link stay out of reach.
What to do: nothing, unless you get that email and do not recognise it: reply straight away, or revoke the access. More in the documentation.
When an account is created, the new user now gets an email from Villantis, in Villantis' style and in Dutch, English or French, with their email address and a temporary password. At the first sign-in the portal asks them to choose their own password (New password, Set password). The person who created the account never sees a password. The temporary password is valid for 7 days.
The button Email reset code on a user (under Agents) works the same way: it mails the user a code, and the user chooses a new password under Forgot password? on the sign-in page. The sign-in emails now also come in Villantis' style, in nl / en / fr.
What to do: nothing. If someone says the invitation expired, use Email reset code on their account to send it again. More in the documentation.
What to do: nothing. Don't recognise a message? Reply straight away. More in the documentation.
Owners and agents see guest details (owners their bank details too). So after signing in, as long as two-step verification is off for your account, the portal asks: Two-step verification: Turn on now or Later. It is not compulsory, and the question returns at your next sign-in until it is on. The invitation email carries the same tip.
What to do: choose Turn on now: scan the QR code with an authenticator app and confirm with the 6-digit code. It takes a minute. More in the documentation.
Villantis Support does not see a guest's contact details, messages, documents or emails. If a question needs it, you can now let support in per property: on the Administration tab there is a new card Support access. Choose Level (View only or Assist) and How long (24 hours or 7 days), then click Give access. With View only, support can view everything about that property, including guest details, and take two small actions: skipping a guest email and deleting a contact. With Assist, support can also change the property's settings, statuses, payment ticks and bookings. Every action is logged.
What to do: nothing. Without your action support keeps seeing no guest details. If support asks you to look along, give access in the card, and revoke it when done. More in the documentation.
The booking screen has been rebuilt. Under the header with the step bar there is now a Next step card that says in one line what is waiting on this booking (Fill in the rental amount, Send the offer, Balance received, Confirm the channel payout and so on) with a button that takes you to the right tab and field. Pressing it saves and sends nothing. The rest is split over five tabs: Booking · Payment · Messages · Documents · Manage.
What to do: nothing. More in the documentation.
For a booking where the channel settles with the guest (brought in through an iCal link or the channel connection, or with How it came in set to Nice2Stay, VillaSud or Gites) you now confirm what the channel actually paid you. On the Payment tab, next to Balance received, there is a field Received from …. It is filled in with the rent minus the channel's commission; correct it if the payout differs, tick Balance received and save. After the stay the Next step card reminds you. A payout higher than the rent is allowed, with a question whether that is right.
What to do: set Keeps on cancellation for the channels you use, and confirm the payout when the money is in. This applies to stays that depart on or after 24 October 2026, to cancellations from that day, and to bookings that came in from that day; older bookings stay as they were. More in the documentation.
The channel looks after its guests, so Villantis no longer sends any automatic email for a channel booking. No offer, payment, contract, welcome, review or cancellation email, and no drafts in manual mode. The guest's booking page shows no amounts to transfer, no bank details, no extras and no contract text, does not ask about a pet, and says that any refund goes through the channel. A message you type under Reply to the guest is still sent. This applies to every channel booking, also those from before 24 October.
What to do: nothing. If you want to write to such a guest, use Reply to the guest.
In Costs and agreements every cost line now has From (month) next to From (year), so a cost that begins in November 2026 counts from November in the reports and not for the whole year. Lines you saved earlier count from January, exactly as before; a one-off cost calls the same field Purchase month.
What to do: if you have a cost with Ends on in the middle of a year, note that the report now counts it up to and including the month of that date; it used to count the whole year of that date. Check the end date if a figure looks different. More in the documentation.
On the Administration tab, at the top of Agents and commission, the owner can switch on Agent handles everything and choose the agent. All notifications about the property and the guests' replies then go to that agent, with no copy to the owner. Only an agent who is linked to the property and has can edit all bookings can be chosen. If the agent leaves the property or loses that right, the switch counts as off, everything goes back to the owner, and the property check on the Overview warns you.
What to do: nothing, unless you want it. The decision about an agent's commission and the reminders for costs and agreements stay with the owner. More in the documentation.
If the logo of a property lives on another website, a button Copy logo to Villantis now appears under the Logo URL field (The house tab). It fetches the image once and keeps its own copy at Villantis, so your guest emails and property site no longer depend on the other website. The image must be a PNG or JPEG of at most 250 KB and 2000 × 1000 pixels. If it fails, the logo stays as it was and a message says why.
What to do: nothing; use the button if you like. The button works on the saved address, so save a changed address first. More in the documentation.
In manual sending mode, a link in a draft that starts with http:// or a bare www. is changed to https:// when you save or send the draft, and a message tells you how many were changed (for example 2 links converted to https).
A draft is now stripped of anything an email does not need (scripts, forms, embedded frames) when it is saved, opened or sent, and the editing window is isolated from the portal. The formatting the emails themselves use (text styling, lists, tables, links, images) is kept, and so are the emails Villantis writes. Nothing to do.
A fixed discount above the rent used to show as a minus line larger than the rent in the email and the contract, while the total was already limited to the rent. The discount line now shows what really comes off the rent, in the emails, on the guest page, in the contract and in the booking screen alike.
The booking screen opens with the facts, guest details stay with the people who handle the booking, files are scanned before anyone can open them, and "paid" is what you ticked.
When you open a booking, the screen is now wider (640 px on a computer, the full screen on a phone) and starts with what you want to know first: the guest's name, the reference, the property and the channel, a step bar that shows where the booking stands (Request through Deposit returned), and one line with the facts, Dates, Nights, Guests (for example "4 + 2 children"), Total (incl. fees) and Still due. On a cancelled booking that line shows the Cancellation amount instead of the total. Rent (excl. fees) now sits in the list below.
What to do: nothing. More in the documentation.
A guest's email address, phone number, address, messages, documents and sent emails are personal data, so they are now visible only to the people who handle that booking: the owner, and an agent who may edit the booking, one assigned to the agent, or any booking of the property when the agent has can edit all bookings. An agent without that right still sees the guest's name, the dates and the amounts; everything else says Not visible to your role. Villantis platform administrators no longer see guest details either; they can still make operational changes such as the status or the payment ticks, and every such change is written to the booking's log.
What to do: if an agent needs to see the guests of your property, assign the booking to that agent or switch on can edit all bookings for them under Agents and commission. More in the documentation.
The private iCal link (under Share your calendar on the Connections tab) contains guest data, so it is now shown only to the owner and to an agent with can edit all bookings. New is the button ↻ New link: it makes a new link and asks for confirmation first. The old link stops working within a minute, so every calendar that is subscribed to it has to be set up again with the new link.
What to do: nothing, unless you think the link has leaked: then renew it. The link is never renewed by itself. More in the documentation.
When a guest replies to an email about a booking that an agent manages, the reply now goes to that agent. As long as the agent still has the property. Otherwise it goes to the owner, as before. The address under "questions? mail us at…" at the bottom of the email is the same address. Guest emails still come from bookings [at] villantis.com.
Notifications about a booking of an agent go to that agent first: a new enquiry through the agent's own booking link, a pet request, an extras request, a cancellation request and a double-booking alert. The decision about an agent's commission and the reminder for agreements and policies stay with the owner. An agent who has been removed from the property gets nothing any more.
What to do: agents, keep an eye on the mailbox of your portal account: replies of your guests arrive there. Full order in the documentation.
Notifications about extras and cancellation requests could still go to an agent who had already been removed from the property. They now follow the same rule as all other notifications: only an agent who still has the property receives them, otherwise the notification goes to the owner.
Every document you upload, on a booking (including the signed contract) and under Costs and agreements on the property's Administration tab, is now checked for viruses before it can be downloaded. Until the check is done, the file shows being scanned and has no Download button; a clean file then downloads as usual. If the scan finds a virus or cannot be completed, the file shows virus found or scan failed (hover for the explanation), is never released, and is deleted automatically after 30 days. For a failed scan, upload the file again. The list does not refresh by itself: reopen the booking or the property to see the result.
What to do: nothing. More in the documentation.
The image for the signature on the contract must be a PNG or JPEG of at most 250 KB and 2000 × 1000 pixels. A damaged image, or a file that is not really an image, is refused with a clear message instead of being saved. Photos for the property site are limited to 2 MB each and must be a photo file; the portal still resizes your photos automatically before uploading, so you will normally not notice. Signatures you saved earlier keep working.
A booking counts as fully paid only when Balance received is ticked under Payments on the booking (or the "paid in full" email was sent, as before). The guest's My booking page, the week overview, the balance ✓ badge on the card, the outstanding balance in the statistics and the cancellation settlement all follow that one tick, so they can no longer disagree. If the balance is paid, the down payment counts as received too. A status alone (Balance paid, Stayed or Deposit returned) no longer means "paid".
What to do: older stays that were imported with such a status but without the tick now show the balance as open. That is intentional. Tick Balance received on the bookings you know were paid (a shadow booking never sends an email). More in the documentation.
The emails Signed contract received, Security deposit received and the replies about a pet were not sent when they were the only email ready at that moment; they only went out when they were bundled with another email. This has been the case since 13 August. They now go out on their own too. No guest was affected by this, because all real bookings are shadow bookings at the moment. Nothing for you to do.
When you permanently delete a booking, Villantis now also deletes everything stored with it: uploaded documents (including a signed contract), the copies of the emails sent to the guest, and any older versions of those files. Until now these stayed behind in storage after the booking itself was gone. The confirmation question says so before you delete. If a deletion cannot be completed, the booking stays and you can simply try again.
No more entering the same insurance policy twice.
A changed IBAN is the classic way to divert a payment, so bank details are now handled with extra care. The IBAN appears masked (NL•• •••• •••• ••43 00) in the Landlord and bank account card and in an agent's invoice details; click Show to read it or Change to enter a new one. Only people who need the bank details see them: the platform, the owner, an agent on a property without an owner account and an agent with can manage all settings. That switch now includes the bank details. Any other agent sees You don't have access to the bank details of this property., and in email previews and the sample contract the IBAN, BIC, account holder and landlord name and address are hidden for them. What the guest receives does not change.
What to do: nothing. It works from now on. If you give an agent the switch can manage all settings, know that this agent can now change the bank details too (you are notified of every change). More in the documentation.
Guest emails now arrive from bookings [at] villantis.com, shown as <your property> via Villantis, so a guest immediately sees whose email it is. Notifications to you or your agent (a new enquiry, a double booking, a pet or extras request, a cancellation request, the decision on an agent's commission and the reminders for costs and agreements) come from notifications [at] villantis.com, also for properties with premium, and can no longer be sent to a no-reply address. Support tickets use support [at] villantis.com both ways. Properties with their own sender domain keep sending guest emails from their own address and name. A guest's reply goes to the address under Owner's email address, otherwise Sender email address, then the owner's portal account or the managing agent, and as a last resort to Villantis Support, so a reply never disappears. Replying to a notification reaches Villantis Support. Behind the scenes, bounces and spam complaints are now tracked per kind of email: one spam complaint from an owner no longer silences all that owner's notifications, and we see delivery problems sooner. What to do: make sure Owner's email address is filled in on the Guest contact tab: the property check warns when guest replies would go to Villantis Support. The full picture is in the documentation.
On the Administration tab, Operating costs and Agreements and policies are now one card: Costs and agreements. Every line has a type, a description, an optional amount, a term and, if you like, an attachment. With an amount the line counts in the operating statement as before, and an attachment simply hangs on that line; without an amount it is an agreement, and you can now save one without a file and add the file later. The list of types is the same everywhere (rent is new as a cost type). When something stops is now set in one place, the term: ongoing, ends on a date (the property's Overview warns you from 30 days before until 30 days after), or renews every year with a notice period (it warns from 30 days before the last day to cancel: renews on 1 December with 30 days' notice, cancel by 31 October). The old field Until (year) is gone; a cost saved with an end year now shows as Ends on 31 December of that year, and your operating statements stay the same. Agents who do not manage all settings keep editing the costs, but cannot delete a line that has an attachment. A second browser tab with an older list can no longer delete an attachment it did not know about: only a file you remove yourself is deleted. Policies that were entered twice (once as a cost and once as a document) are linked into a single line. Your operating statements do not change.
Costs go up: the garage rent is indexed, the insurer has a new premium. When you change the amount of a saved cost line, the line now asks whether the new amount applies from a month (by default the next renewal month, or the current month) or whether this was a correction. A short summary under the line shows the history, such as € 480 until Nov 2026 · € 495 from Dec 2026, and the last step can be removed with ✕. The operating statement calculates every month with the amount that applied then, so last year's figures no longer change when this year's price goes up. Cost lines without a new amount work exactly as before.
Every line in Costs and agreements with a term now sends the owner a reminder email 30 days and 10 days before the last day to cancel (renews every year) or the end date (ends on), for example: your building insurance (Villa …) renews on 1 December 2026, you can cancel until 31 October 2026 (in 30 days). Several reminders due on the same day for a property come together in one email. It goes to the property's Owner e-mail (or the Sender e-mail), never to an agent, only for live properties, and once per line and date; a failed send is retried the next morning. The email contains no amounts, and the description never appears in the subject line or in any platform report.
Every email the platform sends (guest emails, owner notifications, reminders and support messages) now carries a plain-text version next to the designed one. Mail programs that prefer text show a tidy version with the same amounts, dates and links, and spam filters trust such emails more. The designed version is unchanged. The notification of a new enquiry now arrives from <property> · enquiry instead of from the name the guest typed; the guest's name is still in the subject line and replying still goes straight to the guest.
Names, subject lines and email addresses are now cleaned and checked in one place before any email goes out, so text typed into an enquiry form can never change who an email is sent to. An enquiry with an email address that cannot receive mail is refused straight away, so it no longer ends up on the board.
Accounts for the portal can now only be created by Villantis or by an owner inviting someone: nobody can sign themselves up any more. Changing the email address of an account only takes effect after the new address is confirmed, and the portal only grants access to accounts with a confirmed address. When signing in or resetting a password fails, the message no longer reveals whether an email address has an account. Nothing changes for you: you sign in exactly as before, including your authenticator code.
The user documentation now walks through the eight tabs of the property settings with the names you see on screen, for example Ready to go live? on the Overview, Additional costs and Extras (add-on for longer stays) on Costs & extras, When does each email go out? and Sending emails on Guest contact, and Agents and commission on Administration. Your concierge and other helpers now live in a card called People on site (this was called Services). The documentation also uses the exact board lane and menu names now (Request, Balance paid, Operating, Emails), and the manual sending mode has its own section. Nothing in the portal works differently.
The property settings now open on an overview that tells you what still needs attention before guests can book.
Operating costs can now be one-off, such as furnishing a room or installing air conditioning. On the Administration tab choose one-off under How often and fill in the purchase month, the purchase year and over how many whole years you want to write it off (0 to 30; 0 puts it all in the purchase month). The operating statement spreads the amount evenly over the months from the purchase month, to the cent, and stops after the last month; the line is marked write-off. It counts in full by default, or pro rata to occupancy if you prefer. It is a management view, not a depreciation for tax purposes. Your existing costs are unchanged.
On the Administration tab, right under the operating costs, there is now a card Agreements and policies: keep your insurance policies and your contracts with service providers (pool maintenance, the gardener, a rented garage) in one place. Per document you choose a type (insurance, maintenance, rental, other), add a description and, if you like, an expiry date. Add a PDF or image of up to 10 MB with + Add document; it is stored privately and only becomes part of the property when you press Save (Undo takes it away again). With an expiry date, the property's Overview and the nightly check warn you 30 days ahead, and again once it has expired. Only the owner, the platform and agents who may manage all settings see these documents (an agent on a property without an owner manages them too); guests never see anything of it. A document you delete is gone from the property when you save, and can be recovered for 180 days.
Actions outside the Save button (changing an agent's rights, a new week overview link, an email text, a booking link, a commission, the email flow, archiving or restoring a property) could, within a minute of someone else saving the same property, put back an older version of it: a policy you had just added could disappear, or an agent whose rights you had just withdrawn could get them back. These actions now read the property fresh, check rights on that fresh version and only change their own setting. Downloading an agreement or policy also checks rights on the latest version.
An operating cost of € 99,81 was saved as € 100, and a bookable extra of € 12,50 was offered to guests as € 13. Both are now stored to the cent, every euro field in the property settings accepts cents, and the request form on your website shows the same extras total as the email (€ 12,50 per night × 7 = € 87,50). Amounts you entered earlier were whole euros and stay as they are; re-enter one if it was rounded.
Every section of the property settings is now its own card with a clear heading, and the Live / In preparation status sits next to the property name. Checkboxes became switches (a changed switch gets a gold ring until you save), colour fields show their colour, photos are tiles with ◀ ▶ ✕ right on the photo, and empty lists show a dashed box. Longer explanations moved behind a ? next to the card heading, so the screen shows the fields first. "Tagline" is now called Short description. Lists (price periods, closures, cancellation steps, calendars, agents, people on site) are small cards with a label on every field, The house reads as one column with the property site in a single card, the code snippets under Connections fold away until you need them, and Down payment, Deposit and Deposit returned within show their unit (% of the rent, €, days after departure). Nothing works differently.
The property settings are now organised around what you want to do, in the order you usually set a property up: Overview · The house · Prices · Costs & extras · Guest contact · Contract & payment · Connections · Administration. Nothing was removed and nothing works differently; every setting simply moved to where you'd look for it. Where things went:
| Old tab | Now on |
|---|---|
| General | The house (sender and owner email → Guest contact; live → Overview) |
| Prices & costs | Prices · Costs & extras · Contract & payment (down payment, deposit, bank) · Administration (operating costs, channel commission, internal note) |
| Availability | Prices (changeover day, closures, booking years) |
| Communication | Guest contact (offering extras → Costs & extras) |
| Site | The house |
| Services | Guest contact |
| Access | Administration |
| Integrations | Connections |
| Contract | Contract & payment |
| Premium | At the place you use it: own sender domain and email flow on Guest contact, custom contract on Contract & payment, OpenGDS on Connections |
The separate save buttons for services, extras, costs and channel commissions are gone: one Save at the bottom saves everything. A bar shows how many changes are still unsaved, changed fields and tabs are marked, and Undo takes you back to the saved version. Only what you actually changed is sent, so nothing you didn't touch can be overwritten by accident. The settings stay open after saving, and closing with unsaved changes now asks what you want to do instead of silently losing them. Linking an agent on the Access tab no longer reloads the screen and throws away your other edits.
On the Prices tab you first choose how you charge: a fixed weekly price per season, or prices per night or per period. You then only see that model; switching back asks for confirmation so you don't lose periods by accident. Each season shows its weekly price and its periods in one row, and the minimum number of nights now sits outside the flexible model because it applies to both. The Costs & extras tab shows every cost in one table with its own options, tourist tax with all its options, and your own costs with their English and French names folded away. Prices, offers and contracts are exactly the same as before. One small change on your website's rates block: the long-stay discount table now only appears for properties on the flexible model, because that is the only model that applies it.
The welcome email no longer shows an empty "Manager / Concierge" line when no concierge is filled in. If you add your concierge as a person under Services (Guest contact tab, role "Concierge / key holder", shown in the welcome email), the guest now sees them once, in the "During your stay" block, instead of a separate line.
On a phone the tabs of the property settings now scroll sideways instead of stacking, the active tab is always in view, and lists such as costs, periods and closures become compact cards. On any screen size, from phone to tablet to laptop, nothing sticks out to the side anymore.
On The house, right below Domain, you can now set the website link that appears at the bottom of every guest email. Leave it empty and we use your domain, as before; existing links stay exactly as they are. Only real web addresses (https://…) are accepted.
The separate Concierge field is gone. Add your concierge as a person under Services on the Guest contact tab (role "Concierge / key holder", shown in the welcome email); the guest then finds them in the welcome email under "During your stay", introduced with "You can turn to:". The Overview reminds you if an old concierge text is still waiting to be moved.
The Guest contact tab shows all email moments on one timeline: down payment, balance, deposit, welcome and review, each with its number of days. If the order doesn't make sense, the same warning appears on the tab and on the Overview. Asking for a review is one line (on/off plus days). The house has two time fields for check-in and check-out, the languages as checkboxes that keep your default language first, and the country as a list. The remaining settings (contract choice and terms, calendar links, the week overview link, operating costs with description and period, channel commission) all have their place on Contract & payment, Connections and Administration. Guest emails and contracts are unchanged.
In a custom email flow (premium), a step for the balance reminder, deposit request or welcome email that had no own number of days could be scheduled for the arrival day itself. Such a step now follows your property settings (for example 56, 14 and 7 days before arrival), and the flow editor says so: "follows the property setting". A step with its own number keeps that number. No guest received an email at the wrong moment.
Every property now opens on a new Overview tab. It shows the property's own quality checks as a checklist, red points first, with a progress bar and a small number on each tab that still has something open. Click a point and you land on the field that needs attention. The "This property is live" checkbox moved here from the General tab; you can still tick it while points are open, the Overview simply tells you how many. A short "at a glance" block shows the changeover day, how emails are sent, connected calendars, the maximum number of guests and the down payment and deposit. This is the first step of a clearer layout for the property settings; more tabs follow step by step.
When Booking-channel infrastructure goes down for maintenance, the platform now waits politely and catches up by itself.
When a connected channel platform (such as OpenGDS) is unreachable (today's trigger was a real maintenance window on their side) Villantis now registers the outage once, stops hammering their servers (one careful probe every ~15 minutes instead of every property every two minutes), and keeps your desired availability and rates ready on our side. The moment the channel comes back, every connected property immediately receives its complete, current availability and prices, followed by a single "channel is back" notification (with the outage start in local time). Changes made during the outage are never lost: a property whose update was held back stays marked until it has really been delivered. The nightly quality control reports an ongoing outage as an attention point with the moment it started, instead of failing the whole run. It only escalates to an error when an outage lasts more than 24 hours.
The operations overview (Reporting) now shows weeks of paid rental per month and for the whole year, right below the occupancy row. It counts the nights of paid rental, divided by seven, and spreads a stay over the months it touches, so nothing is counted twice. A free stay (a booking without rent) counts towards occupancy but not as paid rental; your own stay at a special price for friends does count, and bookings from Booking.com or Airbnb via a calendar link always count, even though the link carries no price. Agent commission, including its minimum, is now only charged on paid rental that is not an own stay.
The cancellation amount is now fixed on the day of cancellation: the board, a resent email and the commission all show exactly what the guest was told. It no longer creeps up as the arrival date approaches. A guest only owes a cancellation amount once the booking is booked (down payment requested or a payment ticked as received); before that, the guest page simply says cancelling is free. Only the owner can change the cancellation amount (the platform may correct it on properties without an owner account, always logged), and agent commission on a retained cancellation amount is now the owner's decision per cancellation. The owner is asked by email with a secure one-time link, no login needed, and can also decide on the booking card; Slack shows when a decision is needed and when it was made. Bookings from a calendar link (iCal) now count as paid rental, and carry agent commission, only once an amount is entered, because Booking.com calendar feeds show bookings and owner blocks alike.
When you add or edit a booking, "How it came in" now also offers Nice2Stay, VillaSud, Booking.com and Airbnb, plus every channel you've set a commission for on that property. So a booking you enter by hand gets the right channel, and its channel commission is deducted correctly in the operations overview.
Saving a booking now only sends the fields you actually changed and are allowed to change. An agent can again add a note to a cancelled booking with an amount in cents, which used to fail. You can type amounts the way you're used to: 2.100,50, € 2.100,50, 2100.50 and 2 100 all work. An amount the portal can't read now stops the save with a clear message and a red outline, instead of being silently skipped. On a booking you can only view, every field, including the payment ticks, is now read-only.
Booking amounts are now stored to the cent: € 2.100,50 stays € 2.100,50 instead of becoming € 2.101. One calculation feeds the guest emails, the contract, the guest page, cancellations and commission, so the down payment and the balance always add up exactly to the total (30 % of € 2.100,50 is € 630,15 + € 1.470,35). Round amounts are shown without decimals (€ 2.100), amounts with cents always with two (€ 2.100,50), in the guest's language. Tourist tax is now calculated to the cent everywhere, so the contract and the emails show the same amount. Existing bookings can move by at most € 0,50 where a percentage used to be rounded to whole euros; payments already received are not affected. Imported CSV amounts such as "2.100,50" are now read correctly. The board, the booking screen, the operations overview and the commission overview now show and add up amounts to the cent as well. One thing to know when typing: "2,100" is ambiguous (two thousand one hundred in English, two euros ten in Dutch), so the portal asks you to type 2100 or 2.100 instead.
What an agent may change in a property's settings is now one clear rule, the same in the portal and on our side. On a property with an owner, the agent manages prices, seasons, booking years, closures, costs and extras, email timing and calendar links; the owner keeps the property details, addresses, bank details, guest page, weekly overview, website and the cancellation terms and contract. Owners can now tick "may manage all settings" per agent on the Access tab to hand over more; bank details, email addresses, access, commission and archiving always stay with the owner. The existing tick is renamed "may edit all bookings". On a property without an owner account the agent manages everything except access and commission. If something couldn't be saved because of your rights, you now get a message naming those fields instead of a silent skip. Agents no longer see the owner's bank details.
The internal note of a property is now shown on each booking card of that property (first line) and in full in the booking's detail screen, for key codes, arrangements with the cleaner and the like. Only people in the portal see it; it never appears in guest emails, the guest page or the contract.
Saving a property's settings now keeps everything the settings screen doesn't manage itself: operating costs for the reports, booking-channel commissions, open commission proposals and channel connections. Before, a save could silently remove them. We checked our backups: no data was lost in practice. An agent saving a property that has an owner can no longer clear the owner's cancellation terms or contract settings. Saving now always reads the latest version of the property, so two saves shortly after each other can't bring back old values.
Following an internal security review, guest-supplied text is now escaped even more strictly everywhere in the portal, with an automated test guarding it. No action is needed and no misuse was observed. Signed contracts and uploaded booking documents are now stored with versioning: an accidental delete or overwrite can be reverted for 180 days.
Also hardened today: the booking form is protected against abuse: one email address can send at most three requests per property per day, and one network at most twenty per hour across the platform, so nobody can misuse the form to send mail in our name (real guests never get near these limits). External calendar imports only fetch from public https addresses and stop at 2 MB, so a calendar link can never be pointed at internal systems. And the portal and the public booking pages now run with separate, minimal permissions behind the scenes.
The processing agreement now lists Slack (Salesforce) as a sub-processor for internal operational notifications to the Villantis team, limited to guest name, booking reference and property.
The highlights of every batch of improvements, written for owners, delivered by email and kept in a public archive.
Release notes tell you everything; the newsletter tells you what matters to you as an owner, with screenshots and set-up steps for the biggest change of the month. Every edition is archived at villantis.com/newsletter.html, so a new owner can read back what the platform has learned to do. The newsletter never changes a setting by itself, anything new is opt-in, and each edition says exactly where the switch lives.
Prefer a personal tone per booking? Switch a property to manual mode and every email waits as an editable draft.
Amounts change, drafts get cleaned up, but what the guest received should stay verifiable. Every guest email now stores an exact snapshot (subject + content) the moment it is sent. Click a sent email on the booking card or in a contact's history and you see the sent version, marked with its date; older mails from before the archive show as a re-rendered preview, clearly labelled.
Some owners want to write to their guests themselves. On the Communication tab a property can now be set to manual sending: the platform sends nothing by itself, not even the acknowledgement. Instead, every email waits fully prepared as a draft on the booking card, with the guest's name, dates and amounts already filled in, in the guest's language. Click into the real email to adjust the tone and the subject, save the draft for later, restore the original with one click, and send when it reads like you. The contract PDF still attaches automatically, and sent emails tick off exactly as in automatic mode, so the flow, board and reporting stay correct.
Safeguards built in: the board shows ✉ while drafts are waiting, a draft becomes outdated when the booking changes after you edited it (the server refuses to send it until you've checked), and the nightly quality control raises an alarm when a guest is still waiting for an acknowledgement after 12 hours, manual may be slow, it must never silently become never. And an email you deliberately don't want to send? Skip it: it stops counting everywhere and can always be restored.
Fixed-height editors like Squarespace no longer cover the enquiry form.
Some page builders (Squarespace's newer editor, for one) give embedded blocks a fixed height: the widget would grow after loading and the section below could slide over the enquiry form, making it impossible to fill in. The widget snippet on the Integrations tab now wraps the widget in a container with a minimum height, so the page reserves enough room from the start; the live height still adjusts automatically. Existing sites keep working; re-copy the snippet if you ever rebuild your page, and see the docs for a Squarespace-specific tip.
Hard bounces and spam complaints already marked the guest contact and stopped further sending; they are now also posted to the platform's monitoring channel the moment they happen, including temporary delivery failures (a full mailbox, a provider deferring mail), which were previously invisible. Those temporary failures never mark the contact: they usually resolve themselves, but seeing them is exactly how we catch a provider quietly refusing our mail.
Properties can rent strictly in whole weeks: the changeover setting “Saturday” or “Sunday” applies all year (the “in high season” variants only in high and peak season). Until now only the connected channels received that rule: the booking widget itself still accepted any arrival day. The widget now refuses other arrival and departure days with a clear message in the guest's language, shows the fixed day in its legend, and the enquiry API guards it server-side too. One rule, identical on your own website and on the channels.
The first email after an enquiry is the one a guest is actively waiting for, and the one most likely to land in junk with strict providers. After sending a request, the widget's confirmation now reminds the guest to check their spam folder and mark the sender as safe (Dutch, English and French), with an extra-clear note when the guest books with a Hotmail/Outlook address, where junk placement is most common. That one click also teaches the provider to trust the sender for every guest after them.
Prices and availability pushed, reservations with guest details coming back, via Zodomus.
Properties can now be connected to Booking.com and Airbnb through Zodomus, a certified channel-manager API, a full upgrade over the iCal link. Availability is pushed on every sweep round, so a direct booking closes the dates on the channel within minutes instead of waiting for the channel's iCal refresh. Nightly prices are pushed daily from the same engine that prices offers, the price calendar and Nice2Stay, one calculator, every channel. And reservations come back as bookings with the guest's name, contact details and the booked amount, so the board and the reporting show the real picture per channel.
Incoming reservations follow the shadow-booking rules (the channel does its own guest communication and payment, Villantis never emails these guests) and are covered by the same double-booking alert as the iCal import. Every push and every received reservation is recorded in the Channel sync ledger. Connection is done per property by the platform team; the iCal link remains available as the simple fallback.
The iCal import now raises the alarm when a channel sells dates you already booked.
iCal connections have an inherent blind spot: a channel refreshes your calendar on its own schedule (up to a few hours), so in that window a guest can still book dates that were just sold directly. The import now detects the collision: when an incoming reservation (new, or one whose dates shifted) overlaps an existing booking (a direct one, or a shadow booking from another channel) the card is still created (the dates are sold), but it carries a double-booking note in its log and the owner receives an alert email naming both references and the overlapping dates, within one sync round (≤ 30 minutes).
Back-to-back stays (arrival on someone else's departure day) are a changeover, not a conflict, and a channel's own feed never conflicts with itself. To keep the window as small as possible: after confirming a direct booking, refresh the connected calendar in the channel's extranet, Booking.com has a manual sync button for imported calendars.
Paste a channel's iCal link and its reservations block your dates automatically.
Properties on the flexible pricing model get a year grid next to the period rows: every day shows its price, gaps stand out in red, and setting a price is click start day → click end day → type the amount. Built for apartments where prices change often, TEFAF week up, a November weekend down, done in seconds. It is a friendlier window on the same period rows (one source of truth), and an automatic parity test guarantees the calendar and the price engine always agree.
Built for apartments, useful everywhere. Prices now have a yearly pattern (dd-mm periods that repeat, a price can never expire) plus year-specific exceptions that override it and expire by themselves: a trade-fair week at € 189 is one tick in the price calendar. Periods can carry a Friday/Saturday-night rate, and a long-stay ladder (e.g. ≥ 7 nights −10%, ≥ 28 −20%) is applied automatically as the discount on new enquiries, visible in the offer, contract and on the rates block. OpenGDS/Nice2Stay receive all of this automatically: rates are pushed per date from the same engine. Every combination is guarded by an engine-parity test suite.
You now enter the price per night and the calendar computes the week live (weekly-priced properties store ×7). An "only this year" tick stores exceptions, a weekend field sets the Fri/Sat rate, closures can be set and lifted straight from the grid, school holidays show as ▾ markers with details on hover, and the year arrows browse ahead. Properties on fixed weekly prices see their real engine prices in the grid too (read-only, the seasons stay where they are), with closures editable. Fixed: the calendar sometimes opened behind the property panel, and "clear price" left a year-specific price standing.
The link you give to Booking.com or Airbnb is now a dedicated channel iCal: it blocks your dates there but carries no guest names, emails or messages. Those stay in the private calendar, which is for your own calendar app only. Both live on the Integrations tab, now on friendly villantis.com addresses; the public JSON row is gone (channels speak iCal, and the booking widget reads the data directly).
On the Integrations tab you can now add the iCal export links of your channels, Booking.com, Airbnb, Google, anything that speaks iCal (up to five per property). Their reservations become shadow bookings: dates blocked everywhere, shown on the board and the week overview with the channel as source, and never a single email: the channel does its own guest communication. Feeds refresh every ~30 minutes; a reservation that disappears from the feed is cancelled automatically, freeing the dates. Import this property's channel iCal (dates only) into the channel too and the sync works both ways.
One iframe on your rates page; the platform is the single source of truth.
Owners' own websites often carry a hand-maintained price table, and those silently drift the moment rates change in the platform. The Integrations tab now offers a rates block: one iframe snippet for the site's rates page showing the season prices, additional costs (cleaning, linen, security deposit, tourist tax) and bookable extras, rendered live from the same configuration that prices the offers. Change a rate in the portal and every connected site shows it immediately.
The block dresses itself in the site's style: a transparent background by default, and accent, ink, font and bg parameters to match colours and typeface, plus lang for NL/EN/FR. It reports its own height, so no scrollbars. The booking widget and the property site already updated live; the last hand-maintained copy of the prices is now gone too.
One emblem across the whole platform.
All pages now carry a favicon: the portal, villantis.com, the guest pages, the documentation, the week overview and the property sites. One emblem, so a Villantis tab is recognisable at a glance.
Owner feedback: holidays optional, the booking source front and centre.
Three checkboxes under the week overview link (Integrations tab) decide what the page shows per property: the booking channel, the payment checkmarks and the school-holiday chips can each be switched off. Who is staying when is always on it. And the channel chip now also names Direct: a direct booking is a source too. The school-holiday switch also drives the chips on the board and in the calendar: one preference, three places.
"How it came in" can now be changed on an existing booking (the card's edit view), not just when adding one. Handy for marking a stay as Eigen verblijf after the fact: the card and week overview then show the house chip and drop the payment facts. Channels that came in via an import (VillaSud, Nice2Stay, …) stay selectable, so editing another field never silently erases the source.
France, Belgium and Germany join the Dutch chips. Each from its official calendar.
Next to the Dutch chips, bookings and free weeks now also show the French school holidays, Toussaint, Noël, hiver, printemps and été, per zone (A/B/C). A February week might read 🇫🇷 hiver · A+C next to 🇳🇱 voorjaarsvakantie · zuid: two markets off school in the same week. The dates come from the French ministry of education's official open data; the short Ascension bridge is deliberately left out. The same 3-night rule applies, and the nightly quality control now watches each country's date coverage.
Belgium has had two genuinely different school calendars since 2022: the Flemish community and the French community can be weeks apart (autumn 2026: Flanders 2–8 November, the French community 19 October–1 November). The chips name the community (🇧🇪 toussaint · fr, 🇧🇪 herfstvakantie · vl) so you see exactly which Belgian families are off.
German Ferien differ per Bundesland: sixteen calendars, deliberately staggered. All sixteen are in the data, but the chip stays calm: just 🇩🇪 herbstferien; hover it to see which Bundesländer are off (e.g. MV+SN for the February Winterferien). Loose single Pfingst days are left out.
Dutch school-holiday chips everywhere dates matter, plus a repaired nightly report.
Bookings and free weeks now show which Dutch school holiday they fall in, on the booking card, in the calendar and on the owner's week overview. The dates are the official national ones (rijksoverheid.nl), including the north/centre/south regions: a chip like herfstvakantie · midden+zuid tells you exactly which families are off school. Best part: a free week that falls in a school holiday gets an amber signal on the week overview. That is your most valuable unsold week. A stay counts from 3 nights of overlap, so a booking that merely touches a holiday's edge is not dressed up as a holiday booking. The nightly quality control warns when next school year's dates need loading.
The nightly check itself ran fine, but its Slack message silently failed for days: a routine deploy had reset the platform's permission list and dropped access to the table holding the Slack webhook, which also broke the Support view. Both are fixed, the permission list now lives in one place only, and an automatic test guards that every table the platform uses stays in it. Silence from the night watch will not go unnoticed like this again.
The week overview installs like an app, and new users get a guided start.
Add the owner's week overview to the phone's home screen (iPhone: Safari → share → Add to Home Screen) and it now behaves like an app: the Villantis icon with the property name underneath, full-screen without browser bars, and fresh data on every open.
The documentation now opens with a six-step walkthrough for first-time users: signing in, creating your property, what every settings tab does, previewing the emails, one test booking, and the go-live checklist, with links into the detailed sections.
One secret link: who is staying when, with how many, and what has been paid.
On the Integrations tab you switch on a read-only page at my.villantis.com/weekstaat: the current stay highlighted, upcoming bookings per month with the number of guests, a dog chip, the channel, and the payment checkmarks, including the date the balance is expected, with an amber signal when it is overdue. Enquiries and offers appear in their own muted style; free weeks show as gaps.
There is no login: the link itself is the key (an unguessable token), share it only with the owner. New link revokes the old one on the spot. The page is deliberately sparse: no e-mail addresses, no phone numbers, no amounts, and search engines are told to stay out.
Staying in your own house? On a manual booking, choose Eigen verblijf under "How it came in". The dates are blocked like any booking, and the week overview shows a house chip instead of payment facts. Leave the e-mail address empty and it is a shadow booking. No guest mails, ever.
Guest emails wait a few minutes after your last change, so several changes bundle into one message and you keep a short correction window. That waiting was invisible: you dragged a card and wondered why nothing hit the inbox. The card now shows a badge: ✉ sends in ~4 min, with the queued emails in the tooltip. It is fed by the exact decision logic that does the sending, so the badge and the mailbox can never disagree.
An email that only becomes due because another one was just sent (fully-paid confirmation → "additional amount due" for invoiced extras) could sit until the 07:00 full round. The quick round now takes one extra look after every send, so chains go out within minutes too.
One checkbox, four styles: the page builds itself from what is already there.
A review that has come in can be put on your property's page with a single button: Show on property site on the booking's card. The "What guests say" section shows the stars, the text and the first name, newest first, six at most. Removing it works with the same button; the site refreshes immediately. In the Reviews overview you can see which ones are on the site.
On the new Site tab you put a page of your own live at villantis.com/pand/<pand-id>: name, tagline, logo, photos, seasonal prices, extras and the booking widget, built automatically from your property settings and refreshed every time you save. Checkbox off = page gone.
You choose from four styles (Garrigue, Modern, Élégance, Azur), each with its own character; your logo and accent colour make it personal. Photos, intro text, features and extra sections are managed by you on the Site tab, photos are resized automatically on upload, the first one is the header photo. Coming soon: reviews on the page and a custom domain name (premium).
Guest links with an expiry date, and a foundation that has become faster and stricter.
Shortly after the stay, the guest can receive a single request to share their experience, stars and a comment, on their own booking page. The review lands in the platform: ⭐ with the score on the card, the full text in the reservation, and a Slack notification. You decide what to do with it.
All reviews are gathered under Reporting → ⭐ Reviews, with the average. And the request also works for properties with their own (premium) e-mail flow. It is tied to the moment, not to the flow, so a flow built before this feature does not miss it.
Per property on/off on the Communication tab (off by default), and can be overridden per booking in both directions. The request goes out once, at the moment you choose (default 7 days after departure, adjustable under "When does which e-mail go out?") and only within 45 days after departure, so switching it on later does not belatedly e-mail guests from months ago.
The "View your booking" link (and the older details and extras links) kept working forever, even years later, even if the e-mail had been forwarded. Ninety days after departure there is nothing left for the guest to do or see; the page then closes with a polite message. The security-deposit return e-mail falls comfortably within that window.
The money logic (offer amounts, cancellation settlement, security-deposit and down-payment dates) is now verified by 22 separate tests before every rollout. Deploying is only possible from committed code. The processing round that runs every two minutes now only visits properties where a guest e-mail is ready, instead of scanning everything. The portal's translation dictionaries live in their own file, and the platform runs on Node.js 22.
Cancelling with the security deposit settled, a down payment with a date, and replying to support tickets in the portal.
A ticket could only be marked resolved; replying had to happen outside the portal by e-mail, and the reporter never saw in their own overview what had become of it. Under every ticket there is now a reply field: the platform answers the reporter, the reporter can add to it themselves, and every response appears under the ticket and goes by e-mail to the other party. If the reporter responds to a resolved ticket, it is open again.
Same story as with the public API earlier today: the list of portal-API routes was only created when the environment was first set up. There were 57 live and 40 in the script. Everything added by hand since then (documents, flows, reporting, import) existed only in AWS. The list is now compared and completed on every rollout.
The lines were jumbled and you had to add things up yourself. Now it runs from top to bottom: first everything that has come in, with a Total received, then the cancellation charges deducted from it, and as the closing line To be refunded (or Still to pay).
An adjusted amount is no longer a separate charge but a single line: the original amount struck through with the new one next to it, and underneath in small print adjusted by us.
The cancellation settlement left the security deposit out of the picture, even though that money is sitting with us: the guest was told they would get nothing back, and had to hope the deposit would still come separately. Now everything that has come in counts: the down payment (or the full rent when paid in full) plus the received security deposit, and one amount rolls out: refund or additional payment.
What has come in is listed line by line: Down payment received € 675, Balance payment received € 1.575, Security deposit received € 750, instead of one amount of € 3.000 that leaves the guest guessing where it came from. If only the down payment is in, that is the only line shown.
At the same time, the sum took no account of what had actually been paid: it assumed the down payment was in, even when that checkbox was off. The Already paid line now follows the checkboxes under Payments. On the reservation itself you see the same calculation before you drag the card.
If you waive (part of) the cancellation charges, the guest only saw the lower amount, not that something had been done for them, and with a second e-mail also not what had changed. The settlement now shows both lines: Cancellation charges (30 % · 180 days before arrival) € 300 and below it Adjusted by us € 0, with the sentence: "We have adjusted the cancellation charges for you: instead of the € 300 our terms prescribe, we are charging € 0." In NL/EN/FR. If you simply apply the scale, nothing about the e-mail changes.
The field to override the cancellation amount was tucked away between "number of children" and "discount". It now has its own Cancellation block in the reservation, with above it what a cancellation means today: "If you were to cancel now, the scale says 30 % (€ 300) is due", and for a cancelled booking, what has been settled and whether the guest gets money back.
Leave it empty = the scale from the contract, 0 = waived, or enter your own amount. It now also says that timing matters: if you only set it after dragging the card, the guest already has the old settlement in their inbox. For that case there is a Resend cancellation e-mail button, so a correction actually reaches the guest.
Note: the date counts from the day the offer was sent. In a preview (where no offer has ever gone out) today counts, so the preview shows the same sentence the guest sees.
"On reservation" was the only moment without a deadline, and that made it hard to place among the others. There is now Down payment (days after the offer), default 7. That date appears in the offer, "transfer the down payment of 30 % (€ 675) before 20 August", and if it passes without the money coming in, you see ⏳ down payment overdue on the card. The date is never later than the balance date or the day before arrival, however you set the term.
The percentage sat as fixed text in the offer e-mail, even though it is configurable per property. At La Bergerie Callas (25 %) the amount was right (€ 675 of € 2.700) but the sentence below it said 30 %. The percentage now comes from the property setting, in all three languages.
56, 14 and 7 read like a strange order until you realise they are days before arrival, so a larger number is earlier. The three now sit together on the Communication tab, with the order below in plain language: balance reminder 56 d → security-deposit request 14 d → arrival information 7 d. Put them out of order and that line turns orange and the nightly quality check reports it.
What belongs where: Communication = when we send the guest something. Contract = the deadlines the guest is held to (cancellation scale, security deposit back within … days after departure). The two tabs now point to each other.
The deadline for the security deposit was fixed at one week before arrival, while the request goes out at a configurable moment. If you set that to 5 days, the e-mail asked for a transfer before a date that had already gone by. The deadline now moves along, normally a week, and with a later request the guest keeps two days. The contract states exactly the same term, from the same calculation.
Under every e-mail a link to their own booking: the status, their details, their extras, and cancelling as a request.
From the confirmation of their enquiry onwards, every e-mail to the guest carries a link at the bottom to their own booking page. It shows at a glance where their booking stands, what is still expected of them (details, down payment, balance with due date, security deposit, signed contract) and what the stay costs, the same cost table as in their e-mails, including what they pay on site.
The link works with that booking's reference and secret key. No login, no password, and nobody sees anything of another guest.
The guest had two separate pages: one to fill in their address, one to choose extras. Those are now sections on the same page. The buttons in the e-mails point to the right section, and links you sent earlier keep working. They redirect.
If the booking page is switched off for your property, those two buttons simply keep working: the guest then sees only the section they came for, without status, amounts and cancelling.
The booking page only said "Fill in your address details". It now also says why: the rental contract is waiting for it and follows immediately afterwards for signing (or, if the booking is not confirmed yet, as soon as it is). And the note accompanying a cancellation request has become mandatory: a request without a word of explanation is impossible for you to judge.
The guest sees what a cancellation costs today according to your property's cancellation scale, and can submit a request with an explanation. Nothing is cancelled automatically: you get an e-mail and a Slack notification, and on the board the card shows ⚠️ cancellation requested.
In the reservation you either put it through (status to Cancelled → the cancellation e-mail with the settlement goes out as always) or decline it with Decline request. The guest sees that on their page; the accompanying message you send yourself, using the reply field in the same drawer. Once payments can be made in the platform, this can become a real cancellation. Until then the settlement remains your decision.
The switches for what the guest can do themselves were tucked away under Prices & costs. They now have their own tab in the property settings, with a pointer to E-mails for the texts and the moments. One has been added: Own booking page ("My booking"), on or off per property: some owners do not want this feature.
The "paid in full" e-mail said "we will send the practical arrival information shortly before your stay". Shortly is vague; it now shows the date that e-mail actually leaves, "around 27 February 2027", just like in the down-payment e-mail.
That date comes from a setting you could not see until now: Welcome info (days before arrival), default 7. Together with Security-deposit request (days before arrival) it now simply sits under Costs & conditions, next to the balance term that was already there. Set it to 8 and the e-mail and the date in the text move along.
The E-mails overview also said "shortly before arrival" for those e-mails. It now shows the actual number of days of the selected property.
In the down-payment, balance and offer e-mails, properties with fixed weekly prices showed both "To pay on site: Final cleaning € 250" and, a paragraph further on, "To pay separately: Final cleaning € 250". That second line dated from the time when fixed weekly prices had no cost table yet. One of the two renderers had already been adjusted for that, the other had not. It now has.
A contact showed "petok ›": the bare key from the code. Every line now has a description (Pet confirmed, Rental contract sent, Signed contract received, Cancellation request, …), in all three languages. That list used to be maintained by hand; a test now derives what should be in it, so a new e-mail type does not land on your screen as a key again.
Under Payments there is now also Balance payment received, with the amount shown. Tick it and the booking moves to Paid in full; drag the card there and the checkbox is set. Remove the tick and the card goes back to Confirmed. One fact, one place, no two ledgers drifting apart. The "paid in full" e-mail is from now on tied to that same checkbox, just like the down-payment e-mail.
The amounts next to those checkboxes now come from the same calculator as the guest e-mails. The board used to recalculate the down payment itself as rent × percentage, leaving out the costs, the tourist tax and the chosen extras, so the amount on your screen could differ from what the guest saw on their invoice.
The contract only mentioned the price after discount. Now there are three lines, Rent € 2.500, Discount (10 %) -€ 250, Rent after discount € 2.250, so the guest also sees, in the document they sign, that they got a discount and how much. No discount? Then it stays one line, exactly as before.
The cost table only showed a dash with an amount ("− € 250"). It now says Discount (10 %), with the percentage if you entered the discount that way. E-mail and booking page take that label from the same place, so they cannot drift apart: the page, for instance, still showed "Extras" where the e-mail already named the extra.
The cost table showed a line "Extras € 50", which ones, the guest was left to guess. Now the name is there: EV Charging € 50. And an extra that is paid on site appears in the block listing what they settle on arrival; before, it only appeared in the separate confirmation e-mail, which no longer goes out before the offer.
The header of a column only counted bookings ending this year. An enquiry for next season did appear as a card in the column but was not counted, so from summer onwards you saw "€ 0" above a column full of work. Header and cards should say the same thing: count and amount now cover exactly what is open, this year and further ahead. Older years stay collapsed with their own count and total.
If you record an extra at "+ Booking" (the charging station, say) and drag the booking to Offer, the first thing the guest received was "Thank you! We have noted your choice of the following extras" (for something they never asked for) and only then their offer. That e-mail was not tied to a swimlane and therefore went out immediately, bypassing both the bundling and the quiet period.
Now no separate confirmation goes out before the offer: the extras simply appear in the offer. If the guest later adds something themselves, the confirmation does follow, neatly behind the rest and with the same quiet period.
The offer showed the charging station in the cost table and again a paragraph further on under "Would you like some extra comfort?". Whatever is already on the booking is no longer offered, and if nothing remains to choose, that entire block disappears.
At the bottom of every guest e-mail it said "Questions? Just reply to this e-mail, or write to us at …", followed by the sender address. For properties without their own sender domain that was no-reply@villantis.com, precisely the address where writing is pointless. It now shows the property's own e-mail address (Owner e-mail, otherwise Sender e-mail). If a property has no address of its own, the footer no longer names one and only "reply to this e-mail" remains, replies always arrived fine, as they are forwarded separately.
The list of public routes (enquiry, availability, iCal, details, extras) was only created when the environment was very first set up. After that, things were added by hand and the script fell behind reality. The list is now compared and completed on every rollout.
Two switches per property: no premium required.
Under Prices & costs there are two checkboxes under What the guest sees in the e-mails:
This is deliberately not a premium feature: it does not build a custom flow, it switches a block off. In the E-mails overview the extras card turns grey with "off", so you can see why nothing is coming. And the nightly check reports it if you do have extras configured while they are offered nowhere, otherwise there is a price no guest ever gets to see.
The dog was there right away, the extras only after you had chosen a period, because their price depends on the number of nights. It therefore looked as if a property had no extras. You now see immediately that they exist, with a note that the price follows once the period is chosen.
Dog and extras recorded right away on a booking of your own, and one e-mail fewer for the guest.
When you take a booking by phone or messaging app, you often already know whether a dog is coming along and whether they want the charging station. You now tick that straight away in the dialog: the dog is there if the property allows them, and the extras appear once the period is chosen, with the price calculated for the number of weeks, nights or persons.
Because you are taking the booking yourself, it is immediately confirmed: no enquiry that you then have to approve to yourself.
Drag a booking to Confirmed and the down payment, the balance, the contract and the security-deposit request could go out as four separate e-mails within the same minute. From now on they become one e-mail: one greeting, the parts one below the other with a divider, one sign-off, and the contract as an attachment. The subject is about the part the guest needs to act on. If the contract is included, the e-mail is named after it, so it can be found again later.
Each part is still ticked off separately, so nothing goes out twice and your communication history stays readable per type (with the note sent bundled).
The line "These are bundled…" sat as a separate column next to the e-mail cards instead of below them. A swimlane is a horizontal row, so that line took away width and squeezed the cards together, making it look as if an e-mail was missing. The line now sits above the cards, across the full width.
Also fixed: in a bundled preview the same heading appeared twice above the extras, because that table already carries a title of its own.
In the preview of an e-mail you did not see the Build your stay and Fill in your details buttons. They hang off a link with the booking's reference, and the preview booking does not have one, so it did not draw the button at all. You were therefore looking at a different e-mail than the guest receives. In a preview those buttons now point to the property's website, so you see them and a click does not produce an error. In the real e-mails they always worked.
The parts ran into each other. Now each section has a heading (Your down payment, Your rental contract, Security deposit received) with a thin divider above it, so a guest sees at a glance that there are several things in it.
You can also view such a combined message before it goes out: in the swimlane, next to the 🔗, click view preview and you see the e-mail exactly as the guest would get it, with the headings and the amounts of the selected property.
If the security deposit was already in, the same e-mail first contained the payment instruction ("transfer before 2 January") and, a paragraph further on, the confirmation that we had received it. The payment instruction and the separate security-deposit note now disappear as soon as you have ticked Security deposit received, and a box that would be left empty as a result is no longer shown at all. The preview now takes this into account too. It used to show an instruction the guest had long stopped receiving.
A guest e-mail only goes out once you have not changed anything on the booking for a few minutes. Drag a card to Confirmed and tick off the security deposit half a minute later, and previously the first e-mail was already on its way and the guest got two after all. Now the system waits until things are quiet and everything goes in one message.
A bonus that comes with it: a correction window. If you notice within that time that the amount is wrong or that you dragged the wrong card, the guest has not seen anything yet. The safety-net round now runs every five minutes for this, instead of every quarter of an hour.
The e-mails tied to a checkbox (security deposit received, pet confirmed/declined, signed contract) now join the bundling too. They used to sit outside the flow and therefore still went out separately.
In the E-mails overview you see per swimlane which e-mails can go together: they get a 🔗 and below the lane it says "These are bundled if they go out at the same time". Mind the word at the same time: if you only tick off the security deposit the next day, the first e-mail is long gone and the deposit confirmation follows as its own message. Date-driven e-mails (balance, security-deposit request, welcome info) therefore usually go separately. If one has to stay separate after all (the contract, for instance) set it to send separately in the flow editor with the 🔗/✂️ button. That e-mail then goes as its own message, the rest stays bundled.
The "add extras" e-mail also went out when the guest had long since chosen, via the booking form, their own extras page, or because you recorded it when taking the booking. That e-mail then asks about something already answered, and is now skipped.
The booking form on an owner's site was lagging behind. That can no longer happen unnoticed.
Extras are saved in two places: with the extras' own button and with a full property save. The second one knew the new choice per week / per night / per person, the first did not. It rebuilt the item and left the field out. Your choice therefore came back as "per stay". Both paths now use the same handler.
A test has been added right away that reads the fields from the editor in the portal and checks that they survive saving. If someone later adds a field without updating the save logic, that blocks the rollout.
The "we have received your down payment" e-mail fired as soon as you dragged a card to Confirmed, while the Down payment received checkbox was still off. So the guest received a confirmation of receipt you had not yet given. From now on the checkbox is the signal: switch it on and the e-mail goes out immediately. Next to the checkbox you now also see the amount of the down payment, calculated as in the e-mails (rent minus discount × the property's down-payment percentage).
The two new e-mails were being sent, but did not appear in the E-mails view. Cause: the list of e-mail types existed in two places and they were only in the old, no longer used list. That copy has been removed. There is now one registry. A test has also been added that derives the e-mail types from the source code and blocks the possibility of sending an e-mail you cannot see or preview anywhere.
If a guest travels with a dog, it now appears in the reservation under Pet, with Confirm and Decline buttons and the surcharge shown. The card gets a 🐕 to confirm badge, just like requested extras (➕ 1 to confirm), so you do not have to open every reservation to see whether something is waiting for you.
Press either button and the guest is notified. After all, they asked and read "we will confirm this with you". On Confirm: "your dog is welcome", with how the surcharge is settled (on site or via the bank account). On Decline: that it will not work for this stay and that the rest of the booking is unchanged. Both e-mails go once, can be viewed in the E-mails overview, and can be switched off there as well.
"Linen € 100" said nothing about where that amount came from. It now shows how it is built up: Linen · € 25 p.p. × 4 → € 100. This also applies to pool heating, the charging station and custom charges that count per week, night or person.
When you record a booking yourself, you now pick the period in a calendar instead of two date fields. Occupied days are struck through and not clickable; a changeover day is half-shaded, because one guest leaves in the morning and the next can arrive in the afternoon. The occupancy comes from the same source as the booking widget, so fixed closures and years not yet opened up are in there too. If you pick a period that cuts straight across an existing booking, the selection starts over instead of letting you create a double booking.
In the contract the down payment was still followed by Before with empty dots, while no due date exists for the down payment at all: it is due on reservation. This line had been amended before, but the correction did not work: a missing date was not returned empty but precisely as dots, so the date variant was always chosen. Now only the amount remains.
At a property with Security deposit (€) set to 0, the Security deposit received checkbox disappears from the reservation, but the save logic still looked that checkbox up. As a result the Save button broke before anything was stored: on such a property you could no longer change the rent, guest name or status. Every field is now looked up before it is read.
Drag a booking without an amount to Offer and no offer e-mail goes out: the flow skips e-mails that need an amount. That happened silently. The reservation now shows a warning next to the amount, with what to do: fill it in and save, and the e-mail follows by itself. The nightly check already flagged this as a point of attention.
The guest pages (the booking form in the iframe, the details page and the extras page) existed in two places. The e-mails and the embed code point to the one, but publishing went to the other. As a result guests were shown the old version for weeks while the portal was long up to date. There is now only one place, and the duplicate copies have been removed.
You do not need to re-place the embed code. It already points to the right place. Refresh the page and you see the current version.
The list of pages to publish is no longer maintained by hand but derived from the directory: a new page goes along automatically. A platform rollout always publishes the pages with it, so they cannot age apart. And every page carries a build stamp that the nightly quality check reads back: if one lags behind, is missing, or a second copy turns up somewhere, it is in the morning report.
An owner with their own rental contract no longer has to fit our mould.
The Contract tab now states at the top which contract a property sends: the platform's standard contract or a customised version. You can switch between them yourself; the custom text is kept if you temporarily fall back to the standard. The property overview lists it per property, so you see at a glance which properties deviate.
The terms and conditions can be filled in per property as articles with a heading and a text, per language separately. Leave a language empty and it falls back to our standard text. This way an owner can use their own terms without anything having to be programmed for each property.
The cancellation terms were the same for all properties (30/35/40/50/75/90/100 %). They can now be set per property as steps: from so many days before arrival, this percentage applies. That same scale drives both the contract and the cancellation e-mail, so the two can no longer contradict each other. The security-deposit term ("deposit back within … days after departure") is also configurable per property.
Under Costs (extended) there is a Charging station block (per week or per stay), and below it Custom charges: name what this property charges yourself, choose per stay / week / night / person / adult and the payment method. Custom charges behave like the fixed ones: they appear in the cost table of the guest e-mails, count towards the total to transfer with "via bank account", and end up in the contract.
Below the costs, the contract always contained the sentence that bed and bath linen are included in the rent, even at properties that charge € 25 per person for it. The contract now follows the cost setting: if the property charges for it, it appears as a cost line with amount and payment method, and that sentence disappears.
The rental-period paragraph invariably stated that high-season rentals run from Sunday to Sunday, with arrival at 16:00 and departure at 10:00, regardless of what the property said. That sentence now follows the property's changeover day and check-in/check-out times, and disappears entirely with a flexible changeover day. A factual error in a legal document, and exactly the kind of thing you only spot when you actually read the contract.
The enquiry form on your own site now asks straight away whether the guest is travelling with a dog and whether they want to add extras. The prices calculate live with the chosen dates and the number of guests, so with a charging station at € 50 per week, someone staying two weeks sees € 100. Whatever they tick lands on the booking immediately; you do not have to send them back for it later.
If pets are set to on request, it becomes a request: the guest reads that you will confirm it, you see it on the card with a Confirm or Decline button, and the surcharge only counts once you confirm. With allowed it is settled immediately. If no pet is coming along, nothing is charged. The enquiry notification in your mailbox now mentions both as well.
As soon as the pet checkbox was on a booking, the surcharge went into the amounts, even with on request, while the guest read on their details page that we would confirm it first, and even at properties where pets were set to none. Moreover, nobody was notified when a guest requested it, so that confirmation could never come. All three are now right.
Also fixed: the e-mail preview in the portal left the pet out and therefore showed a different amount than the e-mail the guest receives.
The entire Costs (extended) block (linen, pet, pool heating, mid-stay cleaning, charging station and custom charges) only worked with the flexible pricing model. At 11 properties with fixed weekly prices those costs were configured but never charged, without any notice. Both pricing models now calculate with the same engine.
In addition, for a while there were two blocks one below the other that both said "to pay on site". That is one block again, and an empty block disappears entirely.
A bookable extra always had one fixed price for the whole stay. Now you choose per extra whether the price applies per stay, per week, per night or per person. With a charging station at € 50 per week, a guest staying three weeks therefore sees € 150, with "€ 50 per week" underneath, in the offer e-mail, on the selection page and on the invoice.
This lets the guest indicate themselves whether they want to use something, instead of it always being passed on. What the guest ticks lands on the booking and, with "via bank account", counts towards the total.
With Security deposit (€) at 0, the contract merely stated that no deposit is asked. As if damage would never be recovered. It now adds that damage or breakage established after departure will be charged to the tenant at the repair or replacement cost. If a property does ask a deposit, the existing text with amount and repayment term remains.
The quality round now reports when the custom terms mention a security deposit while Security deposit (€) is 0: the same contract then says in the cost line that no deposit is asked. And when the first step of the cancellation scale does not match the down-payment percentage, because the contract then promises "the down payment (X %)" at a different figure than what was paid down.
Your property's rental contract can now be downloaded, the final cleaning is configurable everywhere and guest e-mails no longer get stuck.
The property's Contract tab has a Rental contract block: pick a language and download the contract that guests of this property receive, as an empty template. Guest name, dates and amounts stay open; everything that comes from your settings (landlord, bank details, security deposit, final cleaning, tourist tax, down-payment percentage and balance term) appears exactly as it will be sent. That way you check at a glance whether your contract is right.
Having a different contract used is not something you can do yourself: the contract text is legally fixed in the platform. For that, ask a question via 💬 Support in the left menu. That is also noted next to the download button.
A property can have periods in which it is not rented out at all: renovation, own use, or not-yet-opened. That already worked (such a period is closed in the calendar, the booking widget, the iCal feed and at OpenGDS) but until now only we could set it. On the new Availability tab you now do it yourself: start and end date plus a short reason. For a connected property the new availability goes to the channel immediately on saving.
Your calendar subscription shows the reason, so you can see why a period is closed. Two closures with the same reason used to merge into one appointment there; that has been fixed right away.
The choice via bank account or on site was only available with the flexible pricing model; properties with fixed weekly prices were immovably set to on site. The choice now applies to every property and works through everywhere: with via bank account the final cleaning appears as a line in the cost table and counts towards the total to transfer; with on site it sits in the "to pay separately" block and stays out of the transfer. The contract follows that choice automatically. Existing properties keep their current behaviour.
Drag a card to a next status and the corresponding e-mail is queued immediately with a separate background job. If that one job got lost (during maintenance on the platform, for instance) the e-mail sat there until the daily 07:00 round. A safety-net round now runs every quarter of an hour doing exactly the same check: anything still open goes out after all, and the availability is updated. Every e-mail still goes out at most once.
The nightly quality round now reports when a live property still has no real landlord name, address, account name, IBAN or BIC. Those fields appear literally in the contract and in the payment instruction of the guest e-mails. If a placeholder value remains there, a guest receives a contract with an unusable account number.
The address a guest fills in on the details page (for the contract) is stored on the contact. If that same guest later books the same property again, their address is pre-filled on that page. They only have to confirm, and can of course still change it. That already worked behind the scenes; what is new is that you now also see and can correct the address in the contact screen, under Address. Handy for a typo in a street name that would otherwise land on the contract just like that.
The Domain field asks for a hostname (pand.nl), but anyone who pasted an address from the browser (https://www.pand.nl/) silently got yet another https:// in front of it: a broken link in the footer of every guest e-mail. The field is now cleaned up on saving, and the quality round checks every property's website URL.
A booking notification in Slack now appears with the property's name and logo as the sender, instead of one generic integration name for everything. With several properties in the same channel you see at a glance which house it is about. If a property has no logo, the default sender remains; if Slack rejects the custom sender, the notification still goes out normally.
Changeover day, fixed closures and opening up booking years were scattered across Prices & costs and Conditions, even though together they answer one question: when can this property be booked? They now sit together on their own Availability tab. Prices & costs is once again about money only.
Behind the scenes the platform wrote an availability.json per property to a separate storage location. Nobody read that file: the booking widget, a property's website and the iCal feed all fetch their availability directly. For nearly all properties that write had been failing for months without it showing up anywhere, and at the only property with such a file the copy sat in a different place than the website read. That copy had been standing still since late July.
That second publication path is now gone entirely, including the write permissions, so it cannot come back. Nothing changes in what you see: the calendar, the widget, the iCal and the sales channel already worked directly from the same source.
In the booking, the block with Down payment received and Security deposit received was still called "Deposit", even though the down payment sits in it too. That is now Payments.
The cost section on the property has been cleaned up and the mid-stay cleaning is now truly configurable.
Next to Security deposit received, the booking now also has Down payment received, with a badge on the card so you see at a glance who has already paid.
Set Security deposit (€) to 0 and it works through everywhere: no more deposit request or confirmation e-mail, the contract states that no deposit is asked, the deposit disappears from the amounts in the guest e-mails and the Security deposit received checkbox disappears from the booking.
The included option only worked with the flexible pricing model. Properties with fixed weekly prices got the tax added anyway, the setting did nothing there. The choice now applies everywhere: nothing calculated separately, no "plus the tourist tax" in the balance e-mail, and the contract states that the tax is included in the rent.
Also fixed in the contract: the down payment was followed by Before with empty dots, because no due date exists for the down payment at all. That line now simply states the amount, since it already says it is due on reservation. And a final cleaning of € 0 is no longer listed as a cost line.
The export has become a week overview. You choose the year (default the current one) and get all weeks chronologically, including the weeks with nothing booked, as an empty row with the status free. That shows you straight away where the gaps in the season are. Weeks run from changeover day to changeover day.
For a booking of more than a week, the details sit on the first week and the following weeks stay empty apart from occupied, so adding up in Excel works out. Also fixed: the export now follows the property filter, with it set to one property, other properties still ended up in the file.
Until now only bookings via a sales channel announced themselves in the Slack bookings channel. An enquiry via the booking form or a manually recorded booking stayed silent. From now on every new booking arrives there, with property, guest, dates and where it came from.
Returning guests often call, message or e-mail directly. Until now those reservations only came in via the enquiry form. With the + Booking button at the top right you put such a booking straight on the board. Fill in property, name, dates and amount; the reference number and guest count are handled by the system. From there the booking follows exactly the same path as an enquiry via the form.
At the top, under Existing guest, you pick someone from your contacts; name, e-mail address and phone number are filled in and stay editable. A new guest you simply type in yourself.
No e-mail goes out unnoticed: by default the booking lands in Enquiry and nothing happens. If you pick a further status right away, the screen warns you that the flow will send the corresponding e-mail. Without an e-mail address it automatically becomes a shadow booking, dates blocked, not a single e-mail.
Properties without their own sender domain send guest e-mails from no-reply@villantis.com. That domain is verified, so the sender has to stay there. If a guest pressed Reply, that response reached nobody. From now on we set a reply-to address on every guest e-mail: the sender remains Villantis, but a reply goes to the e-mail address configured on the property (Owner e-mail, otherwise Sender e-mail). If a live property has no address at all, the quality check now reports it.
OpenGDS manages the room and rate codes itself. If a code is renamed or removed there, OpenGDS still answers our messages with "success". While nothing happens with them. Availability and prices would then silently stop arriving, without a single error.
From now on we verify the codes before we send anything. If something is off, nothing goes out and you get a Slack notification with the code in question. As soon as you correct the code on the property, synchronisation resumes by itself, immediately when you save in the portal, and otherwise within a few minutes via the daily round.
Bookings that arrive via a channel should always sit on the board as a shadow booking: the channel handles the guest communication, so our own guest e-mails must stay off. One test booking from before that rule missed the checkbox and got a down-payment e-mail anyway. The address did not exist, so no guest was reached. The integration now always sets the checkbox, and the quality check now raises the alarm for every channel booking without shadow. That check used to look only the other way.
Of the 796 texts in the portal, 35 were missing an English and French translation. Such texts silently fell back to Dutch, so an English- or French-speaking user suddenly saw Dutch without anything appearing broken. Everything is now translated, and the quality check guards against untranslated text being added again.
The quality round now also goes through all bookings. The most important rule: a shadow booking must never have sent a guest e-mail, with channel bookings the channel handles that communication itself. It also checks for missing or reversed dates and for bookings attached to a non-existent property.
In addition, we ask OpenGDS itself whether the configured room and rate codes still exist there. OpenGDS manages those codes itself. If one disappears or is renamed, we would be sending availability into the void without ever getting an error.
The contract states that the tourist tax applies "per person aged 18 and over", but calculated the amount over all guests. On a booking with children the contract therefore showed a higher amount than the quote e-mail (with 3 adults and 1 child and 7 nights at € 2,20, the difference was € 15,40). The contract now counts adults, and the quality check now compares for every property whether contract and quote state the same amount.
The season periods (which weekly price applies when) could until now only be set behind the scenes, now they simply sit on the property, under Prices & costs, as dd-mm. A period may also run across the turn of the year, for instance 20-12 → 05-01.
In addition you can set per booking year from which date it opens up, and give that year its own periods if desired (handy when the price structure shifts per season). A year that has not been opened up yet is closed everywhere: not bookable in the calendar, blocked in the iCal feed and at zero availability at OpenGDS. An enquiry sent straight to the API is refused as well.
Calculated dates (balance due date, security-deposit date, welcome e-mail) were determined via a detour through universal time. On the server that coincides, but outside that timezone a date could shift by a day. All date calculations are now timezone-independent and are tested in four timezones. A season period running across the turn of the year now also counts correctly. It used to fall back silently to the default season.
A full check round now runs across the entire platform: all e-mail types are rendered for every property in every language and checked by machine (± 1.270 checks) for duplicate cost lines, unreplaced text fields, and a correct sum of down payment, balance and total. On top of that, real tests run against the OpenGDS integration plus an audit of the property configuration. The result arrives as a structured report in Slack, complete with version number.
Per property you now indicate whether it really rents to guests. Live properties are judged strictly in the quality check; properties in preparation may still be incomplete and cause no false alarms. In the property overview you see at a glance which properties are live and which are still in preparation.
You can now indicate per property that a mandatory mid-stay cleaning only applies from a certain number of nights. Enter an amount and leave "mandatory from" empty to charge it on every stay, or put in e.g. 14 so the charge only appears automatically on the quote and in the offer e-mail for longer stays. The old free-text "condition" field (which did nothing) has been replaced by this working setting.
The final cleaning now sits with the other costs, with a choice of payment method. Choose on site and the amount appears under "To pay on site (to the property manager)" and stays out of the amount to transfer; choose via bank account and it is added as a line in the cost table towards the total. The contract automatically follows the same wording.
At properties on the flexible pricing model, the final cleaning appeared both as a line in the cost table (counted in the total to transfer) and in the block "To pay separately, on arrival, on site to the property manager". The guest was effectively presented with the charge twice. The separate text block now only mentions the security deposit; the final cleaning is placed solely according to the configured payment method. Properties with fixed weekly prices are unchanged.
All extra costs (linen, mid-stay cleaning, pool heating, pets, tourist tax) now sit in clearly grouped blocks with amount and payment method side by side. No mandatory mid-stay cleaning needed but still want to offer it optionally? That works as always via the Extras (bookable for longer stays) at the bottom of the property.
Guests can now book even on strictly locked-down networks.
The embedded booking widget is an iframe from another domain; some strictly locked-down (office) networks and privacy settings block such iframes. That is why every embed now has a visible fallback link, "Booking calendar not visible? Open the booking form →", which opens the booking as a fully fledged, standalone page on villantis.com (first-party, so beyond the reach of iframe blockers). This way everyone can always book, and you can also share that page separately as a booking link.
A clearer calendar, a dedicated support channel and the Villantis logo in the app.
New in the left menu: 💬 Support. Ask a question, share an idea for improvement or report a problem, with subject and message. Your ticket reaches us directly (by e-mail and in our team channel) and you get a response by e-mail. In the list and in your profile you see the status of your own tickets (open / resolved); the platform sees and manages all tickets.
The portal and the website now carry the Villantis emblem: a villa with a cypress and evening sun in the familiar terracotta, sage and gold tones. You see it on the login screen, in the left menu and on villantis.com.
In the Calendar you switch at the top right between Month · Week · Day. In the Week view every property gets its own strip with the guest name in the cell plus 👤 persons and price; the Day view shows per property who is arriving, departing or staying, with persons, price, channel and period. Much clearer than the hover in the month view.
Click a booking in any view (month, week or day) to open the full booking details right away.
The Week strip runs from changeover day through the next changeover day (Saturday or Sunday, detected automatically per property), so each property shows its own rental week. The strip spans 8 days so the closing changeover day, with both this week's check-out (▲) and the next guest's check-in (▼), always stays visible.
A profile of your own, and two-step verification to protect your account.
Click your e-mail address at the top right for your new profile: set your name and language, change your password and manage your 2FA, all in one place. Agents also find their invoice details there (sender, IBAN, prefix…). The separate language picker and the 🔒 button in the bar have moved here.
You can now secure your account with an authenticator app (TOTP): scan the QR code and confirm with a 6-digit code. For platform administrators 2FA is mandatory (set up once at first login). Owners and agents can optionally switch it on themselves via their profile. When entering your code you can tick "remember this device": the app then skips the code on this trusted computer for 14 days (even after logging out). If you do not tick it, the next login asks for a code again. In your profile, under Devices & sessions, you see a list of your remembered devices (name + last used) where you can forget each device individually, plus "Log out on all devices", which ends all sessions everywhere. Lost your authenticator? The platform can reset your 2FA via Agents → user → Reset 2FA.
Recording signed contracts, and the premium e-mail flow builder taken further.
Store documents on a booking, for instance the signed return contract the guest sends back, but also ID or extra agreements.
In the premium e-mail flow you can now drag e-mails between swimlanes and within a lane to change the sending order. And you can mute an e-mail (🔈): it stays in the flow but is not sent, handy for switching one off temporarily without throwing it away.
In the left menu, Reporting now has two sub-items: Operations (the existing overview per property/year) and Statistics. In Statistics, as an owner or agent you now see the same insight as the platform (KPIs, booking funnel, rentals per month, leaderboard, channels and quality) but limited to your own properties. The login data (currently active / login frequency / login times) stays platform-only. For the platform, the old Platform tab has moved to this spot.
Booking platforms that withhold a commission (Nice2Stay, VillaSud, Gites, …) can now be recorded per property as Booking costs per channel (%). They automatically appear as a cost line on the operating statement for the bookings via that channel. And on the board every swimlane now shows the year total (this year) instead of the all-time total, with each collapsed year card showing that year's total.
Undeliverable addresses and spam complaints are now handled automatically: SES itself stops sending to such addresses (protecting your deliverability) and the contact gets a warning in the Contacts list (⚠️ bounce / 🚫 spam complaint) next to the e-mail address, so you know which guests you can no longer reach by e-mail.
Every agent can now track for free which commission has already been invoiced (with their own invoice reference). The automatic invoice PDF and the detail view per booking (click the card → Details per booking) are premium, switched on per agent by the platform via Agents → agent → Premium. We are laying this foundation now so that we can later connect payments via Wero.
Commission now sits as a sub-item under Reporting (the separate tab on the left is gone), for agent, owner and platform in one place. New: on an ownerless property with exactly one commission agent, every booking automatically counts for that agent, without you having to assign each booking separately. Explicit assignment per booking always takes precedence.
On the operating statement, the commission paid to the agent now appears as a separate cost line (per month, pro rata by nights), so the net result is correct from the owner's point of view. Visible to owner and platform; for the agent themselves it remains income, not a cost. The line follows the normal commission assignment: it appears as soon as bookings are linked to the agent.
The e-mail editor now has a checkbox "Attach contract PDF". Switch it on for your own e-mail (or for a customised standard e-mail) and the contract is sent along as a PDF attachment, exactly as with the fixed contract e-mail. That way you can, for instance, send your own e-mail before the down payment with the contract included. For the fixed contract e-mail this happens automatically.
The week rounded off with dashboards, financial insight and careful handling of guest data.
Templates and Flows have been merged into one E-mails tab. You see every guest e-mail in the context of the flow and click it for a preview; owners adjust (for free) the intro/outro per property.
{aanbetaling}, {iban}, {kenmerk}, …), so you write the text around them yourself and the value always stays correct. Tables/panels (amount table, security-deposit block, arrival info) go between your text as block tokens. You can also put a text block in a box (with a title) to make, say, the payment details stand out.{voornaam}, {aankomst}, {bedrag} and {pand} are filled in automatically. Unmodified e-mails run the standard text unchanged.In the new Flows tab, decide for yourself which guest e-mail goes out at which swimlane status, instead of the fixed standard order.
A complete overview of the health of the entire platform, visible to platform administrators only. Pick a year and, if you like, filter on one property, the whole dashboard then refreshes to that house.
See who is active right now, how often each user logs in (sessions + active days) and at which hours of the day logins happen, with an hourly histogram in local time.
An accountant-ready overview per property and per year: rental revenue minus operating costs, per month with occupancy rate and a year total.
Flag a guest you would rather not host again, set up GDPR-proof.
All guest e-mails reviewed linguistically (NL/EN/FR), based on an external review.
Put an existing schedule on the board in one go: click ⬆ Import, pick the property and upload a CSV. The portal recognises the columns from the header row, shows a preview, and creates the bookings, plus, automatically, a contact for every row with an e-mail address. Everything comes in as a shadow booking by default (no e-mails), with the status derived from the dates. No existing file? Download a ready-made CSV template in the import dialog to fill in.
This release-notes page plus a complete manual of all portal features, reachable from the portal via the 📖 and 🕑 buttons, with the docs button jumping straight to the section for your current page.
The core of the rental process substantially extended and refined.
After the offer, the guest fills in their address details via a secure link (address, postcode, city, country). The details are also stored on the contact, so a repeat booking pre-fills automatically.
The rental contract no longer rides along with the offer with an empty address. It is now sent automatically once the booking is confirmed and the guest details are complete, with the address neatly filled in. On the board, badges show whether the details are in and whether the contract has been sent.
If a property allows pets (or "on request"), the guest-details page asks whether a dog is coming along. This fills the "Dog" column in the season export.
Linen, (mid-stay) cleaning, pool heating and tourist tax now count correctly in the quote. Per cost you choose via bank account or on site (cash); the quote splits this into "to transfer" and "to pay on site".
Arrival and departure days are now shown diagonally as half days. A changeover day (guest A leaves in the morning, guest B arrives in the afternoon) is instantly visible.
The public booking widget now knows half days too: a departure date remains selectable as an arrival date for the next guest, the standard booking mechanism.
Mark a booking as "shadow": it counts in the calendar, board and reporting, but no e-mails go to the guest. Ideal for loading an existing season schedule in parallel and testing it; untick to take it live.
Bookings from earlier years collapse per lane by year. The contacts list gained a search bar, sortable columns and a "last booking" year.
Per property, an owner signature on the contract: an uploaded image or the name in an elegant script typeface.
Premium properties send guest e-mails from their own domain via SES DKIM verification, with the DKIM records clearly displayed.
An enquiry or offer already holds the dates as an option (soft-book). The iCal calendar feed now shows the property name per item and its own colour per property.
The hidden honeypot field in the booking widget has been put back, so bot enquiries are quietly intercepted again.
From a single villa site to a multi-tenant platform for multiple properties and owners.
Villantis: one calm dashboard to manage bookings, guest communication, properties, agents and commissions, for multiple properties and owners at once, fully on AWS. With the board (swimlanes), the calendar, contacts, property management and template previews.
Alongside fixed weekly prices per season, now also prices per free-form period, optionally per occupancy (number of persons), with a fee-aware quote engine.
An agent proposes a commission per property (percentage × net rent, with minimum and markup); the owner confirms. For ownerless properties the arrangement applies immediately. The commission view shows earned, still to invoice and invoiced.
Agents can create and manage their own (ownerless) properties. Owners and administrators invite agents, reset passwords and manage roles.
A self-service flow on the login page: request a reset code and set a new password.
Per property a booking-widget embed, a public availability feed and a private iCal calendar to subscribe your calendar app to.
The platform is built on the complete booking and e-mail flow first developed and proven for a single villa.
From enquiry to stay, fully status-driven: auto-reply, quote, down-payment, balance, security-deposit and welcome e-mails go out automatically at the right moment.
An automatically generated rental contract (FR binding + NL + EN), tourist tax per person (18+) per night, and a cancellation calculation following the contract scale, now available for every property.