Skip to main content
Who is coming back, and what do we know about them?

Guests

One profile per guest, built once and reused every year: for the reservation, the invoice, the registration report and the mail you send in March. Scan a passport at check-in instead of typing it, collect the extra fields your park actually needs, and keep the whole database filterable for tomorrow's arrivals list or this winter's mailing.

  • Live
  • Included in the PMS
  • GDPR-minded by design
Entered once, used everywhere

The profile is the source

1Place a guest's details live
Name, address, date of birth, travel document. Captured once and reused by the invoice, the registration report and every automatic email, so a correction is made in one place.
ScanInstead of typing an address
The document scanner reads an ID card or passport straight into the profile. Faster at the desk, and the spelling matches what a government report expects.
OwnLanguage for every guest
The language on the profile is the language the automatic emails go out in, so a German family reads German without anyone choosing a template.
The bits that decide whether it stays clean

A database that is still useful in year three

Repeat guests, without a second profile

A returning guest books again and their details are already there. What happens when the new booking carries different details is a deliberate rule rather than an accident, so your source of truth stays the source of truth instead of quietly forking into two half-right profiles.

Custom fields for what your park asks

Membership number, sports club, dietary requirement, the electricity key you handed out. Add the fields you need and put them on the intake form, so the guest fills them in rather than your team asking at the barrier.

Filter it, then do something with it

Report lists turn the database into tomorrow's arrivals, everyone staying in a lodge next week, or the guests who came in the last three seasons and might come again. Use it as an operational list or export it for a mailing.

Guest data is the sensitive kind

A guest profile holds a name, an address, a date of birth and often a passport number, because your registration obligations need them. That makes it the most sensitive data on your site, and it is worth treating that way rather than collecting everything in case it is handy later.

So: put on the form the fields you have a reason for. Camping.care asks for a lawful basis in the sense that matters operationally: a field nobody uses is a field you are storing for no reason. The privacy statement covers how we handle it as a processor; what you ask for is your call.

The practical upside is the same as the compliance one. A short form gets filled in properly, and a profile with five accurate fields is worth more than one with fifteen guesses.

Frequently asked

Can guests fill in their own details?

Yes. The Guest Page gives every guest a personal link where they and their co-travellers complete exactly the fields you configured, before they arrive.

Does the ID scanner work at the kiosk too?

Yes. A guest checking themselves in unattended can scan their document there, and the profile is filled the same way as at the desk.

What happens when a returning guest's address has changed?

The overwrite rules decide what wins, so a repeat booking updates the profile rather than creating a second one. It is worth reading the guide once before your first busy season.

Can I email one guest by hand?

Yes, straight from their profile, for the times a stay needs a sentence a template cannot write.

Can I export the guest list?

Yes, through report lists, filtered however you need. What you may then do with it is governed by your own privacy notice, not by the export button.

DemoStart free