Feratel Visitor Registration
The successor to the MeldeClient import interface, connecting Camping.care to Feratel Deskline 3.0, the system your community uses to settle visitor taxes. Visitor tax sheets are sent as your reservations move: created, checked in, checked out, changed, cancelled. And the app adds guest card printing, both as a widget on the guest's own page and from your back office.
- Live
- Deskline 3.0
- Alpine visitor tax regions
Reporting out, guest cards back
- 5Reservation events it reacts to
- CardPrinted by the guest, or by you
- PerAccommodation, if you want
What setting it up involves
- 1
Install it from the App Store
Find the Feratel app in the App Store inside Camping.care and install it. On installation it adds its own fields (a GUID and a Blattnummer) to every reservation, each with its own unique values.
- 2
Enter the credentials Feratel gave you
On the settings page, your OE STAT and your Betriebsnummer. Both come from Feratel, and both have to be exactly right for the connection to work.
- 3
Choose what is sent, and for which units
The form settings page decides which data goes to Feratel (required fields show in grey) and which of your accommodations are in scope. Reservations for the units you select are the ones reported.
- 4
Map the age categories
The age table page lines Feratel's age categories up with yours. Feratel has one row per category; Camping.care may have several inside the same range, and each of yours can be mapped once.
Where this one belongs
Feratel Deskline is the tourism platform behind a lot of Austrian, Swiss, South Tyrolean and Bavarian destinations, and in those regions the visitor tax is settled through it rather than directly with the municipality. If that is how your community works, this is the connection you want, and the guest card half of it is what your guests will actually notice, because the card is what gets them onto the lifts and into the museums.
Feratel also runs a channel connection, which is a different app: Feratel Channel Manager is about distribution and availability. This one is about visitor registration and tax. Some parks use both, and they are configured separately.
Age category mapping is the step worth doing carefully. Get it wrong and the tax is calculated against the wrong bracket, which is the kind of error that only surfaces when the community reconciles.
Frequently asked
When is data sent to Feratel?
On reservation events, not on a schedule. Creating a booking sends a pre-registration; check-in converts it to an active reservation; check-out finalises it; a change resends the whole reservation; a cancellation notifies Feratel, including the cancellation date if it falls during the stay.
What credentials do I need?
Your OE STAT and Betriebsnummer, both issued by Feratel.
Can guests print their own guest card?
Yes. The app adds a widget to the guest view for exactly that, and you can also print the card from the back office.
Does it apply to all my accommodations?
Only the ones you select on the form settings page. Reservations for those units are reported; the rest are not.
Why does the app add fields to my reservations?
A GUID and a Blattnummer, unique per reservation. They are how Feratel identifies the tax sheet, so they belong on the booking rather than in a lookup table.
Is this the same as the Feratel channel connection?
No. That is a separate app for distribution and availability. This one handles visitor registration and tax, and the two are configured independently.