How it works

MMK is a powerful system, and fleets use it in different ways — so it helps to understand exactly what Floatist does with your data. This page explains where the information on a booking comes from and why a few things look the way they do.

For getting the integration connected and syncing boats, see the MMK setup guide.

Which way data flows

• MMK → Floatist (the main flow). Floatist pulls your MMK reservations and turns them into Floatist bookings, keeping them in sync. This is on by default.
• Floatist → MMK (optional). Floatist can also push to MMK, but only to block availability — and it does that with an option, never a confirmed reservation. See the next point. This is also how the MMK & NauSYS bridge keeps the two systems aligned.

Sync frequency

MMK bookings now sync much faster, allowing your booking team to use the Floatist booking calendar as a source of truth across multiple platforms, as well as see Floatist bookings quicker in MMK.

Pull (MMK → Floatist)

• Now to 4 months out — syncs every 15 minutes
• 5 to 12 months out — syncs every hour
• 13 to 24 months out — syncs every 6 hours

Push (Floatist → MMK)

This push runs on an hourly cadence. Floatist bookings are generated as an option in MMK, regenerating it if it falls out of sync.

This is an initial improvement — more syncing speed and integration improvements are coming soon.

Bookings created in Floatist appear in MMK as an “option”

When push is enabled and you create a booking in Floatist, it shows up in MMK as an option named “Floatist” — not as a reservation.

This is deliberate. Floatist needs to be able to release those dates if you later cancel the booking in Floatist, and MMK only lets us cancel options, not confirmed reservations. So Floatist holds the dates with an option; if you cancel in Floatist, we cancel the option and the dates free up again.

An MMK 'option' from Floatist is a real booking

An entry in MMK in OPTION status named “Floatist” is a confirmed booking — not a soft or tentative hold. Floatist only ever creates these options to represent real bookings, so you should treat every “Floatist” option as a genuine reservation. The option carries just the dates and yacht (no guest details), and MMK applies its own default base and check-in/out times, so those fields in MMK won’t match what’s in Floatist.

Where the guest details come from

An MMK reservation can involve one or two parties, and MMK’s API naming for them is famously confusing. Floatist untangles it like this:

• The charterer — the actual guest. Floatist shows this person as the booking’s guest whenever possible.
• The agency / agent — present only on an agency booking, where someone books on the charterer’s behalf. A direct booking has no agency at all — just the charterer.

So a direct booking has only a charterer; an agency booking has both.

On the reservation itself, MMK only stores the charterer’s name — not their full contact details. To fill in the rest (email, phone, address, country), Floatist looks that name up in your MMK address book and uses the matching contact.

Enter guest names as First name, then Last name

The address-book lookup matches on the full name, so it only finds the right person when the name was entered as First name → Last name. If a guest was entered the other way around (last name first), the lookup may fail or match the wrong entry — leaving the booking with a name but missing or incorrect email, phone, and address. Keep your team’s data entry consistent: always First name, then Last name.

Duplicate names pick the first match

If your MMK address book has several people with the same name, Floatist uses the first match it finds, which may not be the intended person. If a booking shows the wrong contact details, check for duplicate address-book entries on the MMK side.

When agency contact info is used instead

Sometimes a booking has no charterer details at all — for example a direct agency booking where only the agency is on file. For these cases Floatist has a setting, “MMK fallback to agent info” (on by default):

• When it’s on, Floatist uses the agency’s contact details as the booking’s guest info only if there is no charterer information at all.
• If any charterer information exists, the charterer always wins and agency info is never used.

This setting is configured by Floatist

“MMK fallback to agent info” is an account-level setting managed by Floatist support, not something you change yourself. If you’d prefer agency details never to appear on a booking, let us know and we can turn it off for your account.

Seeing the full MMK details on a booking

The booking’s guest fields only show one contact, but Floatist keeps far more than that — and you can see all of it on the booking’s Integration tab. Open any MMK-sourced booking and switch to Integration for the complete snapshot Floatist pulled from MMK:

• The reservation code, client price, and deposit.
• A side-by-side Client (charterer) and Agent (agency) comparison, each with name, company, VAT code, email, phone, address, city, zip code, and country — so even when the booking shows the charterer as the guest, you can still see the full agency details too (and vice versa).
• Extras — name, price, and whether each is payable at base. These are MMK’s extras and are not synchronized with Floatist’s own extras.
• The payment plan — each instalment’s date and amount.

This is the most complete view of what MMK holds for a booking — the place to look when a guest field seems incomplete and you want to check the underlying data.

Who can see the Integration tab

Because it contains financial and personal details, the Integration tab is visible only to the Admin and Booking Manager roles.

Which reservations sync, and what comes with them

• Statuses that become Floatist bookings: Reservation, Regatta, and Owner week. Options and offers in MMK are not imported. An owner-week reservation with no guest name shows as “Boat owner”.
• Financial details synced from MMK: the reservation code, price and currency, security deposit, the payment plan (instalment dates and amounts), and extras (with whether each is payable at base).