Questions hotels ask us.

Ananas PMS is the hotel edition of Ananas GDS: a cloud property management system with the front desk, reservations, rates, an OTA channel manager, a booking engine and revenue reports in one place — plus the tour-operator side most PMSs leave out: allotments, contracts, rooming lists and fact sheets. One login, one price grid, one guest record.

Both, and we label it honestly. Fact sheets, allotment and stop-sale calendars, partner contracts, rooming lists, invoicing with XRechnung, PMS connectors and the API are live today. The PMS modules — front desk, folio, channel manager, booking engine and revenue — are built and rolling out to early-access hotels first. Everything not yet in production carries an “Early access” tag on this site.

You can start free, with no credit card. Premium plans are being finalised right now, so we do not publish them yet. If you want every module switched on, ask us about Premium and we will set you up personally.

Yes. If you run Mews, Apaleo or Cloudbeds, Ananas connects to it and you can use Ananas for distribution — tour operators, fact sheets, allotments, invoices — while your PMS stays in charge. You can move the front desk over later, or never.

No. Ananas never holds guest money. Card payments go to the hotel’s own payment account, and Ananas stores no card numbers — only the token, the card brand and the last four digits.

Ananas GDS UG is a German company and builds for EU rules by default: a data processing agreement, guest data requests, consent kept apart from contact details, and this website measures visits without cookies.

Independent hotels, small hotel groups, resorts and apartment houses — especially those that sell through tour operators and DMCs as well as OTAs.

Yes. Ananas PMS is the hotel edition of Ananas GDS, made by Ananas GDS UG in Schweinfurt, Germany. One account works for both.

Start by connecting it, or import your rooms and facts by CSV or with your AI assistant. Early-access hotels get a personal setup from our team.

Yes. A folio can have several billing windows, each with its own payer and its own statement that balances on its own.

No. Cards are kept by Stripe on the hotel’s own Stripe account. Ananas stores only the token, the brand and the last four digits, and the money settles to the hotel.

Yes. You keep your own contract and hotel ID with each OTA. Ananas connects to the listing you already have; it does not create OTA listings.

No. Ananas sends only what changed, field by field. A new price sends only the price; a new minimum stay sends only the minimum stay.

The first release is pay at hotel: the guest books, gets an instant confirmation and pays on arrival. Card guarantees through the hotel’s own Stripe account are on the way.

Only if you want it to. You choose manual pricing, recommend mode — where each suggestion says why it was made — or triggers you define yourself.

No. Operators on Ananas see your calendars, fact sheets and invoices live and can sync them by API. Operators who are not get stop sales and allotments by email or PDF straight from the same calendar.

Since 1 January 2025 every business in Germany must be able to receive e-invoices from other businesses. Sending them becomes mandatory in stages from 2027. Ananas handles both directions.

No. The AI only creates drafts. A person reviews each draft in Ananas and applies it. Unknown or invalid fields are refused outright.

Yes. A versioned REST API returns JSON or XML, with a token per partner, an IP allow-list and a call log. Webhooks are signed and retried, with a dead-letter queue.