For destination management companies

Contract hotels, price tour operators, and run the operations in between — from one platform.

A DMC is a commercial party, not just a logistics desk: you contract hotels on your own terms, price what you sell to tour operators, and run the transfers, fleet, and excursions in between. Ananas GDS gives you a mandate-based contracting and fee engine for the commercial side, plus an operations suite for the rest — connected directly to the hotel and tour-operator data you already work with.

Create a Free Account
Destination operations dashboard
The commercial layer

Contracting and pricing, DMC to hotel and DMC to tour operator.

Every hotel relationship you operate runs under a mandate — Principal or Agent — and the platform enforces which pricing mechanism is even valid for each one, so a markup can't quietly appear where you're not actually the party at risk.

Principal or Agent — one mandate per hotel, per operator

A mandate is your authority to operate one hotel relationship for one tour operator. In Principal mode, you contract the hotel in your own name and resell to the operator with your own margin. In Agent mode, you manage an existing direct hotel–operator contract on the operator's behalf and earn a fee instead — you're not in the price chain, so the platform won't let you mark one up by mistake. The mode is set once and locked; changing the arrangement means a new mandate, not a silent edit.

Markup, commission, per-unit, or retainer

Four fee mechanisms on one engine: an invisible markup baked into the price, a visible commission line, a fixed per-unit charge (per passenger, transfer, room-night, or excursion participant), or a flat recurring retainer. Rules resolve most-specific-first — a rule for one operator and one operation type beats a general one, which beats your DMC-wide default.

Your own services always price as principal

The transfers, excursions, and service requests you deliver directly are always priced as principal — whatever the underlying hotel contract mode is — because you're the one actually bearing the cost.

An immutable fee ledger

Every fee computed is recorded permanently with the exact rule and snapshot that produced it, so a partner dispute six months later has a real answer. Ananas never touches or settles the money — it calculates and records; the invoice is raised elsewhere.

Sound familiar?

Destination operations run on spreadsheets and phone calls.

Before Ananas GDS
  • Markup and commission tracked in someone's private spreadsheet
  • Rooming lists rebuilt per operator, by hand
  • Transfers and excursions tracked on spreadsheets
  • Driver and vehicle documents checked manually, if at all
  • Dispatch conflicts discovered the day of, not before
  • Guest special requests lost between hotel, DMC, and operator
  • No shared record of what data was actually relayed to whom
With Ananas GDS
  • Markup or commission set once per mandate, applied and logged automatically
  • A permanent rooming ledger, shared with the hotel and operator
  • Transfer and excursion ledgers, structured like the rooming ledger
  • Fleet & crew registry blocks dispatch on an expired document
  • A dispatch board with conflict detection before it's a problem
  • Special service requests tracked against the reservation they belong to
  • A relay console with provenance stamped on every record

An operations suite built for the DMC role, not repurposed from one.

Transfer ledger

Movement and delay tracking for every transfer, structured the same way as the platform's hotel rooming ledger.

Fleet & crew, with compliance blocking

A vehicle and crew registry that blocks a dispatch outright when a document or certification has expired — not just a reminder email.

Dispatch & assignment board

Assign drivers and vehicles to movements with conflict detection, so double-bookings surface before the day of travel.

Manifests & meet-and-greet

Arrival and departure manifests with meet-and-greet coordination, plus printable driver and guide day sheets, a dispatch roster, and an airport rep sheet — for staff who never get a platform login.

Excursions & local suppliers

Excursion operations run as their own ledger, backed by a local supplier registry — the same operational discipline the platform already applies to hotel rooming.

Relay console

Hotel → DMC → tour-operator data flows through configurable relay modes — pass through, block, override, or anonymize — with provenance stamped on every relayed record.

Both sides, one platform

You already sit between hotels and tour operators. Now your software does too.

Hotels, tour operators, and DMCs share contracts and permissions on the same platform. A rooming list a hotel maintains, a booking a tour operator confirms, and a transfer your team dispatches are all part of one connected record — instead of three separate systems that only agree with each other by coincidence.

Connected hotel, DMC, and tour operator data

Stop reconciling by hand. Run destination operations from one platform.

Create a free account and connect your hotel and tour-operator partners — transfers, fleet, dispatch, and excursions, all in one place.

Create Free DMC Account