VAKTIN·
NAME·LISTS — rooming lists → the Opera rooming-import template

Drop any tour operator's rooming list — a Nordic Visitor package, a group organiser's spreadsheet, a channel export, a CIE Tours rooming-list PDF, or a Katla / Fosshótel PDF name list — and get back a sheet in the full Opera Cloud rooming-import template, every column in order, ready to import; each name split into its parts, room types turned into your property's codes, nationality as its ISO code, and a running line count filled in. A rooming list written night by night — a pre-night, each main-tour night, a post-night — is merged back into real stays: a room listed on back-to-back nights becomes one reservation for the whole run, never four one-night ones. The rooms are then grouped into one booking per stay — the arrival block and the return leg each become their own block to tick and import — and a duplicate guard un-ticks any room whose guests & dates are already in the list, so the same reservation can never ship twice. Everything runs in this browser.

How it works ▾
  1. Drop one or more files (.xlsx, .csv, .tsv, .pdf) — or paste the rows straight from a spreadsheet, an email or a PDF (see the paste box below the drop zone). Five shapes are read automatically: flat tables (columns detected by name — Passengers / Room Type / Check in / Check Out / PAX / Nationalities and many aliases), sectioned group rooming lists — Fosshotel or Gate 1 exports with the dates in the IN … OUT … header — as a spreadsheet or as the CIE Tours PDF, reservation-sheet name lists with separate First / Middle / Last columns (e.g. a G Adventures sheet — a room's guests are stacked on consecutive rows; when the sheet carries its tour itinerary, the roster is split into one booking per stay at your hotel, with that stay's real dates — never the flight span), and Katla / Fosshótel PDF name lists (the In: … Out: … header dates, guests as Last, First, sgl/dbl rooms).
  2. Set the room-type codes for this property in the left rail (e.g. Twin Room → STA). They're remembered per hotel.
  3. Pick which bookings to include — every stay, chain of touching date sections or booking reference is a group with its own date range, matching one block in Opera. Tick the block you're importing, export, and repeat for the next block; the line numbers renumber to match. Rooms flagged dup (same guests & dates already in the list — a re-added file, an updated name list) start un-ticked so they can't double-book; ticking a whole block leaves them off — to keep one anyway, tick that row itself.
  4. A room the operator listed on back-to-back nights arrives as one reservation for the whole run and is marked ×N in the Source column (N = nights merged). Only touching nights merge — a night away in between, or a change of room type, stays two separate bookings, and the dates are editable if you need them split.
  5. Fix anything in the preview — every cell is editable. Mis-split surnames, a wrong date, a missing code.
  6. Export the Opera name-list as .xlsx or .csv, or copy it to paste straight into an existing sheet.

Drop a rooming list here

Excel, CSV or a PDF rooming list — a tour operator's rooming list, a group name spreadsheet, a CIE Tours PDF, or a Katla / Fosshótel PDF. Add as many as you like; they merge into one name list.

.xlsx · .csv · .tsv · .pdf — unpacked in this browser, no upload, no library
⛨ runs entirely in this browser — no guest data leaves this machine
…or paste a list instead

Copy the rows straight out of Excel, Google Sheets, an email or a PDF — include the header row — and paste below. The columns are figured out automatically; paste again to add another list.

Pasting drops it in automatically.