Greek eCharter integration

For operators in Greece, the Greek eCharter integration covers two ways to get crew and charter data to Greek authorities: a per-booking XLSX export, and a bulk JSON export covering multiple bookings at once.

Note

Unlike the Croatian eCrew integration, the Greek workflow is file-based, not API-based — you download the files from Floatist and upload them to the Greek eCharter portal yourself.

Per-booking XLSX export

The portal requires the guests and the skipper to be submitted separately, so Floatist downloads a single ZIP — greek-manifest-<date>-<boat>.zip — containing two XLSX files:

File	Contents
passengers.xlsx	The charter guests.
crew.xlsx	The skipper.

Both files use the identical column layout below. Upload each to its matching section in the eCharter portal.

The export includes the 8 columns the portal requires:

Column	Content
A	Full name
B	Document number
C	Sex (M / F)
D	Nationality (using the portal’s nationality codes)
E	Date of birth (YYYY-MM-DD)
F	Embarkation date (auto-filled with the booking’s check-in date, YYYY-MM-DD)
G	Embarkation time (always 17:00)
H	Embarkation port (always the booking’s departure base)
I	(left blank)

Use Floatist as the source of truth for the crew list, then download the XLSX from the booking’s crew-list view and upload it to the Greek eCharter portal — no double entry.

Bulk export to Greek eCharterParty (JSON)

Note

The bulk JSON export is an additional option for exporting crew list data to Greek authorities. Your team can continue using the per-booking Excel export above, or use the JSON export instead, depending on your operational preference.

Floatist can build a JSON file for the Greek eCharterParty portal’s bulk-upload format, covering multiple bookings at once. You review each booking’s readiness in Floatist, download the file, then upload it yourself on the eCharterParty portal, no manual reformatting.

1. Enable the eCharter integration

Go to Settings > Integrations > eCharter and check Enable eCharter bulk export.

2. Set up your company details

Every charter party the export builds now includes your company as the legal broker party, using the identity set at Settings > Global settings, under Company details. Fill in your Legal name and Tax ID (VAT): the export blocks any booking until both are set. Company email, Company phone, and Address are also sent in the JSON when set.

3. Set up your bases

Back on the eCharter integration page, under Bases, fill in each Greek base’s Authority code (the port authority’s system code, for example kl-peiraia) and Port UN/LOCODE (for example GRPIR). Both are required for any booking starting or ending at that base.

4. Set up your boats

Under Boats, make sure every boat has a Call sign. eCharterParty checks the call sign against the vessel already registered in the portal, so a boat without one, or with a mismatched one, cannot be submitted.

5. Add your charter terms (optional)

If you have Charter terms set at Settings > Bookings > Charter terms, the export includes them in each charter party’s additional_terms field. Your terms are converted from rich text to plain text automatically. A booking with no charter terms configured exports normally; the field is simply left out.

6. Export bookings in bulk

From the bookings list, select the bookings you want to export (up to 200 at a time), open Actions, and choose eCharter export. Floatist checks each booking and shows its status:

• Ready: everything needed is present.
• Review: the export will include the booking, but something was defaulted or looks unusual, for example no invoice price was found, so the freight defaults to 1 EUR.
• Blocked: required information is missing, with a link to fix it directly in eCharter settings, the crew list, or the booking.

Expand a row to see its specific issues and jump straight to the fix.

Click Continue to move past the ones that aren’t blocked.

7. Review the charterer and broker

The second step, Charterer & broker, lists one group per booking with the parties Floatist pre-filled for it — a charterer and, where applicable, a broker agent — so you can check what was guessed before it’s exported. Each row shows:

• Include — switch a row off to leave it out of the export entirely, rather than sending it half-filled.
• Type — Charterer or Broker agent.
• From — where the row’s values came from: MMK client, MMK guest, Booking contact, or Not in Floatist when nothing could be pre-filled and it needs to be entered manually.
• Name, Email, Phone, ID / passport no., VAT / tax ID, Address, and (for a broker) Contact person.

Every booking also needs a charter price, entered in the group’s header — required because the port authority needs a real price, not a default.

A booking group starts expanded if it’s missing a charterer or a price; otherwise it starts collapsed, with a summary badge (e.g. “1 charterer · 1 broker”) in its header.

8. Download and upload

Click Download JSON to save charter-parties.json, containing every booking that isn’t blocked and has a charterer and a price. Upload that file to the Greek eCharterParty portal’s bulk-charter-party upload tool. Floatist does not submit the file on your behalf.

Tip

Each charter party’s client_id field carries a Floatist booking reference, for example floatist[AB222232], so you can trace an exported entry back to its booking. For bookings imported from MMK or NauSYS, that system’s own reference is appended too, for example floatist[AB222232],mmk[MMK-778899], so you can match the row to how you already track it there.