The two messages a stay sends
Rentals adds two stay-specific emails: an arrival note before check-in and a thank-you after departure.
Receipts, confirmations, reminders, reschedule notices and cancellation messages use the existing Bookings emails.
Before you begin
- A worker running
bin/plugin kahunacart workto send queued emails. See CLI. kahunacart.settingspermission to enable or disable messages under Notifications.
The arrival note
The arrival note contains the property’s private instructions, followed by stay dates, arrival and departure times, any damage deposit and a booking management link.
Enter instructions once per property in What to tell them before they arrive on the booking rule.
The arrival note defaults to three days before check-in. Change pre_arrival_days in the settings to adjust this interval. Its minimum is one day.
The arrival note has no calendar attachment.
Conditions that delay sending
- Cancelled, rejected, expired and no-show bookings do not receive the note.
- An overdue unpaid balance prevents the arrival note from being sent. A balance with a future due date does not. If payment information cannot be checked, the note is held back.
Eligibility is checked again on later sweeps. After an overdue balance is paid, the next five-minute sweep can send the note if the booking is eligible.
Changes to arrival instructions
The email uses the property’s current arrival note, not a copy saved at booking. Editing it changes what future recipients receive. Cancellation policies are also read from the current property rules.
Access instructions and door codes
Private access instructions are included only in the arrival email.
They are excluded from public listings, quotes, receipts, confirmations, reminders, the management page, front desk, calendar feeds and API responses.
Only the arrival email and the property editor read the access instructions. Tests verify that other outputs do not include them.
Keep door codes in the dedicated instructions field, outside public descriptions and other messages.
The thank-you
The thank-you contains a brief message and a link to the property. It defaults to one day after departure, controlled by thank_you_days. Set 0 for the departure day.
The thank-you is sent only for a confirmed or completed stay where the guest attended. Cancelled, rejected, pending and no-show bookings are excluded.
The thank-you does not check payment status. It can be sent for an attended stay even if a balance remains outstanding.
Duplicate-send protection
Workers claim each message before sending it, preventing duplicate sends from concurrent workers or repeated sweeps.
If eligibility checks prevent delivery, the claim is released so the message can be considered again later.
Disable a message
Enable or disable each message under KahunaCart → Settings → Notifications. Disabled messages are not claimed or recorded as sent.
These messages are absent from an order’s Send email… menu. Successful sends still appear on its timeline. See Notifications.
pre_arrival_days and thank_you_days control timing only. Use Notifications to enable or disable delivery.
Override a message template
Each email has a Twig template pair in templates/emails/. Copy it to user/themes/<your-theme>/templates/emails/ to override the content:
| Message | Templates |
|---|---|
| The arrival note | rental-pre-arrival.html.twig, rental-pre-arrival.txt.twig |
| The thank-you | rental-thank-you.html.twig, rental-thank-you.txt.twig |
HTML emails extend the core layout and inherit its colours, logo and footer.
Related
- Settings -
pre_arrival_days,thank_you_daysandbalance_reminder_days - Taking payment - the balance-due email, and what a late balance does
- Emails and reminders - every other message a booking sends
- Notifications - the switch per message, for the whole store
- Developers - the three jobs behind the two messages