Árni Gunnar Ragnarsson·November 6, 2026

#26.45 - Global Search Now Finds the Exact Record You Mean

Search has been rebuilt from the ground up. Every word you type now has to start a word in the same person, order or trip, so typing a first name and a surname finds the one traveller you had in mind instead of a long list of everyone who shares either name. Results are ranked by how well the whole name lines up, with orders first, and phone numbers, ID numbers, ticket numbers and booking references match however they're written — with or without spaces or dashes. Misspell something and search corrects it for you and shows what it searched for instead. It also returns results several times faster.

The order overview PDF is now a document you can hand to a third party with confidence. It names who the order is for and who issued it — the client, or the primary participant alongside the client being billed, each with their ID number — plus the agency's details and ID in the footer. The layout matches the customer portal: a branded header, a single clean bookings table grouped by booking group with travellers shown as initials and seat numbers, and participants and payment figures sharing one card. Prices now appear only once, and the overview regenerates automatically when you switch an order's client or edit the client details it prints.

Orders can now be named by their client or by their primary participant, so a company paying for ten employees, or a parent paying for three children, produces ten or three orders you can actually tell apart. The setting is workspace-wide with overrides per segment, trip and order, and the name appears consistently in admin, the customer portal, the overview PDF and the APIs. Alongside this, each participant now has their own overview in the portal — their bookings, their share of the price, payments registered to them — downloadable as a PDF, linkable from the order, and attachable as a card in an email.

Invoicing has had a substantial upgrade. Creating an invoice now shows every invoice already on the order and previews the next one line by line, so you see exactly what will be billed before you issue it. Change invoices can include a Changes page listing each booking added, repriced or removed since the last invoice, and invoices with a participants page now name who is on each booking. You can also correct an issued invoice's description and client reference in place without voiding it — the PDF re-renders and the invoice moves to a new version. Orders can carry credits too: a line that takes an amount off the order without touching the bookings it corrects, linked back to the booking it credits.

Elsewhere: lists now end each group with a participant breakdown by adults, children and infants, and gain passenger code (MR, MS, CHD, INF) and age columns for PNL and check-in work. Email actions can go to any combination of recipients — client, primary participant, other participants, group contact, workspace admin or a custom address — each greeted by name, and any email action can be placed in an order's action menu. Trip emails can be narrowed to orders with a balance, orders that haven't paid their deposit, or chosen segments. A new Order Placed trigger fires exactly once when an order leaves Draft, so thank-you emails stop repeating. Trip product availability is redesigned into a single row per line with a breakdown of this trip's share against other trips and direct sales, and PNRs let you exclude tickets that will never reach an order.

Also improved: long composed emails no longer fall back to the template, corporate clients show their company name in emails instead of appearing blank, manual Amadeus taxes no longer inflate ticket prices, booking external references survive a panel reopen, long trip names no longer hide the top of booking pages, and portal pages recover quietly from dropped mobile connections.

Want to get product updates directly to your inbox?

Sign up for our semi-regular newsletter to stay up to date with all the things happening at Itsy!

© Itsy ehf.AboutTermsPrivacyBlogChangelog