Keydesk in September 2026: what works, what does not, and who should wait

Between now and the middle of November, a few hundred UK operators will decide what software runs their 2027 season. The forward book is at its annual low, the site is winding down, and it is the one window in the year when changing systems is not an act of self-harm.

If you are in that group and Keydesk is anywhere on your list, you need something better than a marketing page. You need to know what it actually does in September 2026, what it does not do, and whether the gaps matter for your site specifically.

So this is the readiness update. I intend to publish one of these every few months, and the format will stay the same: what shipped, what is still missing, and who should not buy yet. That last section is the one that matters most, and it is the one most suppliers leave out.

What changed since the summer

More than I expected when I started writing this. The short version is that Keydesk now does several things for you that it previously only recorded.

Pitchup went live as a two-way API integration in August. Availability, rates, stay restrictions and supported extras publish out to your listings, and bookings, amendments and payment-status updates come back into the same calendar as your direct and booking-office reservations. I wrote separately about why a direct-first product connected one at all.

Calendar sync connects everything else. Two-way calendar sync links a Keydesk unit to its listing on Airbnb, Booking.com, Vrbo, Hipcamp, HolidayFox, Agoda or any channel that publishes a calendar feed, so a booking taken on either side closes the dates on the other. A new connection can run in watch-only mode before it is allowed to block anything, and a feed that breaks or suddenly comes back empty keeps its last good set of dates rather than reopening your season.

Balances now collect themselves, with the guest's agreement. At checkout you can offer a deposit today with the balance taken automatically on the due date, or a weekly, fortnightly or monthly instalment plan. The guest sees the amounts and dates and consents to them separately, and a secure Manage Payments area lets them change their card, pay early or stop future collection without phoning you.

Refunds happen inside Keydesk. A full or partial refund of a card payment goes back through Stripe from the booking, with the reason recorded, and a refund made directly in Stripe is picked up and shown on the booking too.

The bookings list became a workspace. Views for what needs attention, today's arrivals, in-house guests, outstanding balances and provisional bookings, a queue for working through several bookings in a row, and amendments to stays that are already checked in.

Reporting shipped in late August. Revenue, occupancy and booking-channel split, a booking ledger holding every reservation and its financial detail, and a CSV export that goes to a bookkeeper without reformatting.

None of those is a small feature, but I would rather describe the whole picture than the most recent additions.

What works today

Eight areas, described as the jobs they do rather than as feature names.

Taking the booking. Booking-office reservations through a guided workflow, and direct online bookings through Keydesk Direct, your own booking journey with your logo, colours and photos of each accommodation type. Both land in the same place. If a guest leaves contact details and drops out before paying, an eligible journey can send them a recovery reminder, and preview mode lets you walk the whole journey yourself before it opens to the public.

Seeing the season. A continuous booking calendar across pitches, units and grades, where you can drag to create a booking or block dates by hand. Underneath it, the bookings workspace turns the season into today: who arrives, who is in, who owes money, what needs attention.

Pricing it. Nightly rates, fixed breaks such as Friday to Monday, per-person and per-pitch pricing, occupancy rules, restrictions and operating dates, with bulk changes you preview before applying. That preview step matters more than it sounds when you are moving a whole shoulder season by eight per cent.

Getting paid. Stripe card payments, deposit or payment in full, configurable deposits, payment requests by email or text, balance reminders, automatic balance collection and instalment plans where the guest has agreed to them, refunds, and an optional deadline that cancels an unpaid booking and puts the dates back on sale.

Staying in sync with channels. Full two-way API integration with Pitchup, and calendar sync with every other channel that publishes a feed, managed from one grid with a health summary for the whole account.

Selling more per booking. Extras attached at the point of booking, which is where firewood, hampers, hot tub hire, dogs and late checkout actually convert.

Knowing the guest. A customer directory with account-wide search, repeat and high-value segments, tags and duplicate detection. Returning guests are flagged on every booking screen with their visit count and lifetime value. Guests can add party members, children's ages and vehicle registrations themselves through a secure link that needs no account. Consent status, and archive, restore and erase actions for data requests, sit on the record.

Knowing what happened. The reporting and ledger described above.

That set is deliberate rather than partial. It is the work of taking a booking, pricing it, getting paid for it, running the day and understanding the season. If your site needs those things done well, Keydesk does them today.

What it does not do

Plainly, and without the word "yet" doing quiet work in every sentence.

• Central rate and content management across marketplaces. Rates, content and full guest bookings flow only with Pitchup. Calendar sync keeps dates aligned everywhere else, but a calendar feed carries dates, not prices or guest details, and each channel refreshes it on its own schedule. That is not a channel manager and I am not going to call it one.
• Holiday-homeowner administration. No owner accounts, site fees, utility billing or holiday-home sales. If you run a park where owners are a material part of the business, this is a hard exclusion.
• A branded guest app or push notifications.
• Automated marketing campaigns. Guest records hold consent status, history and segments. Apart from recovery reminders for abandoned checkouts, nothing in Keydesk runs a campaign against them.
• Discount and promo codes. There is no code or member-rate feature, so a returning-guest discount is not something Keydesk applies for you.
• Algorithmic demand-based repricing. Pricing is operator-controlled by design. The software does not move your rates for you.
• Accounting or EPOS integrations. CSV export is the route into your accounts today. There is no direct connection to an accounting package or a till system.
• Dispute and chargeback handling. Refunds run from inside Keydesk. Card disputes are still handled in Stripe.

There is a version of this list written as a roadmap, where every line ends with a season it might arrive in. I have deliberately not written it that way, because a shortlist built on features that have not shipped is how operators end up switching twice.

Who should not buy Keydesk this autumn

Four situations. If you are in one of them, I would rather you knew now than after a demo.

You need rates and content managed across several marketplaces. If Booking.com, Airbnb or an agency is where a serious share of your business comes from, and you need prices, restrictions and listing content pushed centrally from day one, Keydesk only does that with Pitchup. Calendar sync will stop most double bookings. It will not replace a channel manager.

Owners are a real part of your operation. Site fees, utilities, owner statements, holiday-home sales. None of it is in the product and none of it is close. A park with a hundred privately owned caravans has a software problem Keydesk does not currently solve.

You need proof at scale before you commit. Keydesk is a new product with a small number of sites on it. I can give you direct access to me and to the product, guided onboarding and a migration we work through together. I cannot give you four hundred reference sites, and if that is your buying criterion, it is a legitimate one and you should apply it.

Your season never really stops. The whole case for switching now rests on having a genuinely quiet window. If you take bookings steadily year-round with no low point, the timing question is harder than a general recommendation can answer, and the honest advice is to work out your own window before committing to any supplier, us included.

Who it does fit

The sites where Keydesk is a good decision this autumn tend to share four things.

Most of your business is direct, or you want it to be, and you are tired of paying a percentage on guests who already know you. One site, or a small number of sites, rather than a group with a head office. Your current system is a spreadsheet, a paper diary, or software you actively resent using and have been meaning to replace for two years. And you care about what the booking journey feels like for a guest on a phone at nine in the evening, because that is where most of your direct bookings are actually won or lost.

Campsites, touring parks, glamping sites and smaller holiday parks with pitches or hire accommodation. Sites that are commercially ambitious enough to care about conversion and channel mix, and small enough that enterprise software is a bad fit at any price.

How to check rather than take my word for it

The most useful thing you can do with any supplier, including this one, is to give them the same ten jobs and watch.

Bring the parts of your park that are awkward to configure. The pitch that is only available to certain unit types. The fixed-break rule you run in July but not in May. The group booking that spans four pitches with one payment. The amendment your current system makes you cancel and rebook. Ask to see those done live, not described.

Then ask what happens after the sale: what the migration route is for your existing and future-dated bookings, who does the work, and how you get your data out again if it does not work. The 62-point migration checklist covers the questions worth asking, and it is written to be used against any supplier rather than to make us look good.

If you want a like-for-like view against the market leader, the CampManager comparison is built on dated public evidence with sources linked, and it contains the same hard exclusions as this post.

The commercial position

£49 per month, per site, billed monthly, no long-term contract, no Keydesk commission on bookings. Onboarding, migration help and support are included rather than quoted separately, and so are calendar sync, automatic balance collection and instalments. Stripe charges its own processing fees on card transactions, which is the only other cost. That is all on the pricing page with the detail.

There is also an Early Partner Programme: up to ten businesses at £25 per month for the first twelve paid months, in exchange for regular feedback and the occasional interview. It is an application rather than a discount code, and it exists because early operators shape what gets built next. That is not a figure of speech. The order of work has already changed more than once this year because a small number of people said the same thing.

Where this is going

The roadmap is short on purpose: deeper connections with more channels, booking widgets for your own site, and marketing automation. I am not attaching dates to those here, because a date in a blog post becomes a promise I have not earned yet.

The direction underneath them matters more than the order. Earlier this month I wrote about why a booking system should act rather than record, and that is the standard the next year of work is aimed at. When I wrote that post, Keydesk did not collect a balance from a saved card. It does now. On payments, Keydesk increasingly acts for you. On availability, it keeps your channels aligned. On guest revenue, it recognises returning guests and recovers some abandoned checkouts, and has barely begun beyond that. Judged as a system of record it is already good. Judged against what I actually want it to be, it is early.

I would rather be judged against that standard while we are building than score well against a lower one.

If the exclusions above rule you out, that is a useful outcome and it cost you five minutes. If they do not, the pricing page has the full commercial detail, and switching covers how a move actually works, including what we do with your existing bookings.