Skip to main content
135 integrations, and room for yours

Partners

Two kinds of partner. People who sell and implement Camping.care in their own market, and companies whose product should talk to it. Both start with a conversation and neither requires a contract to begin reading the documentation.

Where you might fit

Four kinds of partnership

ResellerYou sell Camping.care in your market and earn on the subscriptions you bring. We handle the platform, you own the relationship.
Implementation partnerYou configure and migrate parks (rate structures, channels, hardware) as a service, in your own language.
Local expertYou know your country's reporting rules, fiscal hardware and booking channels, and campsites there trust you.
ReferralYou have campsite clients but do not want to implement software. Send them to us and earn on it.

Integrating your product

Read starfish.care/docs/appstore first. Most integration questions are answered there, the documentation is public, and you do not need our permission to start building against a test environment, which means you can find out whether this is viable before either of us spends time in a meeting.

What we need to know when you do get in touch: what your product does, which Camping.care data it needs, whether you have a public API of your own, and who supports the integration once it is live. That last one matters more than people expect: an integration nobody owns becomes a support problem for the operator in the middle.

Categories that already exist: payments, access control, channel managers, accounting, energy and metering, statistics and government reporting, fiscal printers. If yours overlaps with an existing app, say so. Sometimes the right answer is extending it rather than building a second one.

How it goes

From first e-mail to listed app

  1. 1

    Tell us what you are building

    Product, the data it needs, whether it has a public API, and who supports it. The contact form has a partner option.

  2. 2

    Build against the API

    Public documentation, a test environment and scoped permissions. Most integrations need nothing from us at this stage.

  3. 3

    We review and publish

    We check the integration, agree how it is supported and in which countries, and list it in the App Store where operators can install it themselves.

What partners get

  • Scoped API accessyour app asks for the permissions it needs and no more, so operators can see exactly what it can reach
  • App Store listinginstalled by operators from inside their own environment, no manual setup call
  • Technical contacta named person on our side while you build, not a shared inbox
  • 700 campsitesacross 16 countries, in the market you are already selling to

Partner questions

What does it cost to become a partner?

Nothing to apply, and nothing to read the documentation or build against a test environment. Commercial terms for resellers and referrals are agreed per partner and depend on the market.

Do I need to be a developer to be a partner?

No. Reselling, implementation and local expertise are not development roles. Only the integration route needs someone who can write code.

Can I white-label Camping.care?

Ask us. Some resellers front the relationship entirely and others sell it as Camping.care; what is possible depends on the market and the volume.

Which countries are you looking for partners in?

Anywhere in Europe where campsites are underserved by their current software. There are already partners in the Netherlands, Germany, Austria, Italy, Finland and Luxembourg.

My integration already exists as an app. Now what?

Tell us anyway. Extending an existing app is often better for operators than a second app doing nearly the same thing, and we can introduce you to whoever built it.

DemoStart free