Last updated June 8, 2026
Every flight block in the itinerary builder comes with a set of display controls under How this shows on the itinerary. These settings let you choose exactly how the arrival looks for your client — from a clean inline boarding-pass card to a dedicated arrival card with terminal and gate details — and how multi-leg connections are presented. The defaults work well for most trips, but knowing what each option does will save you time whenever a flight itinerary is a little out of the ordinary.
The Arrival display dropdown controls how (and whether) the flight's arrival is shown on the itinerary. There are five modes:
The smart default. JourneyFuse looks at the departure and arrival dates stored on the flight:
Use Auto for the vast majority of flights. It handles the common cases correctly without any extra clicks.
The arrival time is always displayed inside the boarding-pass card — even for overnight flights. No separate arrival card is ever added, regardless of when the plane lands.
An amber +1 (or +2) badge appears next to the arrival time on the boarding-pass card to flag that the flight crosses midnight. The badge is computed from the actual stored arrival and departure dates, so it is always accurate.
When to use: you've built a very compact itinerary and prefer a single-card look even for redeyes. The amber badge still signals the overnight nature of the flight to your client, so nothing is hidden — it's just condensed.
Always adds a richer arrival card on the landing day, even for a flight that arrives the same day it departs. The arrival card includes the terminal and gate details that live in the flight block, giving the client a dedicated "You've arrived" moment in the itinerary.
When to use: flagship international itineraries where the arrival experience matters — a Heathrow Terminal 5 arrival with lounge access, or an AMS arrival before a luxury transfer picks them up. The extra card is worth the visual weight when there's meaningful arrival detail to surface.
Places a minimal one-line "Arrival in [Airport]" row on the landing day. No boarding-pass card — just a lightweight location marker.
When to use: connection airports that don't merit their own card, or when you want to mark a transit location without cluttering the day view. Also useful when a full arrival card would repeat information already obvious from the day header (e.g., "Day 6 — Amsterdam").
Shows only the departure half of the flight. The arrival portion is de-emphasized and does not add any card or marker to the itinerary.
When to use: intermediate legs in a connection sequence when you are not using the consolidated connection card (see below) and you want to suppress the middle-leg arrivals. For example, a JFK → CDG → AMS itinerary built as three separate flight blocks — you might hide the CDG arrival on the JFK block and the AMS arrival on the CDG block, leaving only the final Amsterdam arrival visible.
Whenever a flight's stored arrival date is a later calendar day than its departure, the boarding-pass card automatically shows an amber pill — +1, +2, and so on — beside the arrival time. The number reflects how many calendar days after departure the flight lands.
This badge appears in every mode except Hidden. It is computed from the actual dates stored on the flight block, not from a rough time comparison, so a late-night departure that lands at 1 a.m. the next morning correctly shows +1, and a flight crossing the international date line shows the right offset too.
Note: this fixed a previous behavior where the badge was calculated from times alone and could incorrectly label a flight as "next morning" when the arrival was actually the same calendar day.
For flights with more than one leg — a connection itinerary like JFK → CDG → AMS — this toggle is shown below the arrival display dropdown.
Default: ON.
When the toggle is on, all legs are merged into a single connection card that shows:
The client sees one clean card for the whole journey instead of one card per leg.
When the toggle is off, each leg renders as its own individual boarding-pass card. This is the original one-card-per-leg layout.
Most of the time. A client itinerary for a New York → Paris → Amsterdam routing reads much better as a single "JFK → AMS · 1 stop" card than as two separate boarding-pass cards that interrupt the day's flow.
| Mode | Same-day flight | Overnight flight | Best for |
|---|---|---|---|
| Auto | Inline on boarding-pass card | + Arrival card on landing day | Most flights — use this by default |
| Inline only | Inline + amber badge | Inline + amber +1/+2 badge | Compact itineraries, redeyes |
| Arrival card | Dedicated card on same day | Dedicated card on landing day | Flagship arrivals with terminal/gate detail |
| Slim marker | One-line arrival row | One-line arrival row on landing day | Connection cities, lightweight waypoints |
| Hidden | No arrival shown | No arrival shown | Middle legs in a manual multi-leg layout |
Don't overthink it. Auto handles the most common cases — same-day and overnight — without any configuration. Only switch modes if a specific itinerary calls for it.
Overnight arrivals need dates, not just times. The +N badge and Auto mode both rely on the arrival date stored in the flight block, not just the time. If your flight shows no badge when you expect one, check that the arrival date field is set correctly (separate from the arrival time).
Connection cards and individual cards can coexist. You can have one multi-leg flight consolidated and another (a separate one-leg domestic hop later in the trip) showing as a standard boarding-pass card. Each flight block has its own independent settings.
Arrival terminal and gate surface on the arrival card. Whenever a landing-day arrival card is shown — that means Arrival card mode, or Auto mode on an overnight flight — the terminal and gate from the flight block are included. If your client needs that detail for a big airport like LHR, CDG, or JFK and the flight lands the same day, switch it to Arrival card so the card (and its terminal/gate) always appears.
Hidden arrival + Inline only = clean connection layout. If you prefer to build connections as separate flight blocks rather than using the consolidated card, set the middle-leg arrivals to Hidden and the final leg to Auto or Inline only. Your client sees each leg's departure cleanly without redundant arrival cards cluttering the day.
Track every reservation in one place — flights, cruises, hotels, and more — with automatic commission calculations and invoice generation.
When a client accepts a proposal, JourneyFuse builds the trip itinerary automatically from the approved option — no double entry.
The overview of Groups — coordinate multiple travelers under one record with a roster, shared itineraries, messaging, and an optional self-service booking page.