Integrations overview
CampOne is the operating system of your campground — but you’ll have other systems on site. The integrations layer lets each system feed into CampOne (or out to it) without manual double-entry.
Every integration is per-tenant: each campsite admin enables and configures the ones they actually use, with their own credentials, encrypted at rest. None of the data leaves your tenant.
What’s available
Section titled “What’s available”| Integration | What it does | Direction |
|---|---|---|
| Worldline Saferpay | Drives the in-store payment terminal from /kasse — cashier hits a button, customer taps card. | CampOne → terminal |
| Salto KS | Issues a guest PIN / door code on every confirmed booking and revokes it on check-out. | CampOne → locks |
| Schranken (barriers) | Adds the guest’s licence plate or RFID tag to the entry-barrier allowlist for the booking dates. | CampOne → barrier |
| Cookpit / Timbrage | Imports staff clock-in / clock-out events from Cookpit into CampOne’s time tracking. | Cookpit → CampOne |
| Salesforce | Syncs guests as Contacts and bookings as Opportunities, both directions. | bidirectional |
| SAP B1 / S/4HANA | Posts a daily summary journal entry to SAP for accounting. | CampOne → SAP |
| HESTA direct | Submits the monthly accommodation statistics directly to BFS, replacing manual CSV upload. | CampOne → BFS |
| External Shop POS | Lets an external till (Lightspeed, Zettle, on-site shop) post transactions into CampOne for unified revenue reporting. | external POS → CampOne |
| Booking.com | Channel manager for rates, availability, and incoming reservations. | bidirectional |
For each integration we also publish a status pill on the settings card — green / yellow / red — so the front desk sees at a glance whether the connection is healthy.
Where to find them
Section titled “Where to find them”Sign in as a tenant admin and go to Settings → Integrations. The tab has three sub-sections:
- API Keys — for external POS systems and other API-key consumers.
- Channel Manager — for Booking.com.
- Vendor Adapters — the eight cards listed above.
Each card has the same shape: a switch to enable, the credential fields, a Test connection button (green / red feedback), a Sync now button when applicable, the timestamp of the last sync, and an inline log of recent activity for that integration.
What you need to set up
Section titled “What you need to set up”Most integrations require credentials from the vendor. We don’t ship pre-provisioned sandboxes — your campground signs the contract with the vendor (or your existing IT partner), and you paste the credentials into the relevant settings card.
Per integration we publish a prerequisites section that says exactly what to ask for, who to contact, and any preconditions (e.g. SAP needs a Service-Layer user, BFS needs a registered BUR-Nummer).
What happens if a sync fails
Section titled “What happens if a sync fails”Every adapter writes to its own audit log. If a sync fails:
- Transient errors (network blip, vendor 5xx) — automatic retry, nothing for you to do.
- Authentication failed — you get an in-app notification and an email. Open the settings card, re-paste the credentials, click Test connection.
- Unrecoverable errors (mismatched hotel ID, suspended room) — the offending mapping is auto-disabled so it doesn’t block every other sync. Notification + email tell you what to fix.
The Booking.com integration adds a sweep that fires once an hour and alerts you on three consecutive failures, so a quietly broken connection doesn’t go unnoticed.
Multi-site groups
Section titled “Multi-site groups”If you operate several campsites under one organisation (a TCS-style group), each site configures its own credentials. The Group Console at /group/integrations will surface a roll-up across all sites in your group — see the Group Console docs.
Where data lives
Section titled “Where data lives”All credentials are encrypted at rest with a key that never leaves the platform. Sync logs and event records are scoped to your tenant — they never appear in any other operator’s view. Detailed data residency is in Security → Architecture.