Last updated October 8, 2026
The proposal editor splits what used to be one long settings run into two cards you can read out loud: Details & terms — what you ask each traveler for, and what they agree to — and Deposit & payments, which is one sentence about money with everything else tucked behind it.
They sit in that order on purpose. You decide what the client hands over before you decide what you charge them.
The rail beside the editor lists every card on the proposal by its own name, under four headings:
Click a row and its card opens and scrolls into view. Each row carries a one-line summary — the same words the card shows when it's closed — with a status dot: green when it's set, amber when it's worth a look, red when it needs fixing, grey when there's nothing there. On a package, the Options row counts parts (Package: 5 parts · $18,400); on a bundle it counts categories (Bundle: 3 categories · client picks one each).
When a priced proposal would let your client accept without paying anything — no deposit, nothing invoiced at booking — the Deposit & payments row reads Nothing due at booking, or Nothing due at booking — card kept on file only. Is that right? when you're only holding a card. On a proposal that's otherwise ready to send, the dot is red.
Review & send asks the same question: "No deposit is due at booking. The client can accept without paying anything." with two answers:
It doesn't ask on a group booking page, an add-on offer, a proposal that takes payment through your own checkout link, or one where everything is paid at check-in — those are all set up that way on purpose.
Review & send also asks about protection when it isn't offered and no reason is recorded: Offer it opens the Travel protection card, and Client declined by phone records that as the reason (Other — Client declined by phone).
These cards are the new editor. The new proposal editor is now what you get by default. Classic stays available for two weeks under ⋯ → Switch to classic editor, and a banner at the top reads "The proposal editor has a new look. Everything you had is still here." with a Switch back to classic → link. Everything you set in either look is stored the same way and behaves identically for your client; only the editing surface differs. See the new proposal editor for where each classic control went.
Both cards keep these names on a group booking page and on an add-on offer. On a group page the rail's Who & what heading lists The group and The page travelers see instead of Trip & client and Intro message.
Under the card title, a one-line reminder of what it covers: "what you ask for, and what they agree to." The card is two halves side by side with a live preview of the client's experience on the right.
The heading reads 1 · We ask each traveler for. Everything you collect is a chip. A chip that's on shows a tick in front of its label (✓ Passport); a chip that's off is plain.
The chips are grouped under four headings:
| Group | Chips |
|---|---|
| ALWAYS | Name, Email, Phone |
| PASSPORT & ID | Date of birth, Passport, Nationality, Gender, Known Traveler # |
| PREFERENCES | Dietary needs, Medical / mobility, Shirt size, Frequent flyer #, Past guest # |
| CONTACT | Mailing address, Emergency contact |
Shirt size is asked of every traveler (Youth S through 4XL) for group t-shirts. Each answer saves to that traveler's own profile, under Travel preferences, so the lead and every guest on the booking keep their own size for the next trip. You can also set or change it by hand in Edit client → Preferences, or on a traveler's Preferences tab.
The three ALWAYS chips can't be turned off. Name, Email and Phone are how you reach the person who booked, so they're always collected — from the lead traveler only — and their chips are shown ticked and inert.
Passport, Mailing address and Emergency contact are groups, not single fields. Ticking Passport turns on the whole passport block (number, expiry, issuing country, and so on); ticking Mailing address turns on the four address lines. They count as one chip each, and unticking one clears the whole block.
Top right of this half, three preset chips: Basics, International, Everything. Clicking one replaces the whole chip selection in a single click. The preset stays highlighted while its chips are the ones you're collecting — so nudging a single field from required to optional in the drawer doesn't un-highlight it, but adding or removing a chip does. When your selection doesn't match any preset, the collapsed row for this card just calls it Custom.
International is Basics plus the passport block, including the passport issue date — the field a handful of suppliers and consulates ask for that most travelers never think about.
Below the chips, a row of smaller controls:
off → asked → required → off. The label always names the state it's currently in.More field options opens a drawer over the right-hand side: "Required or optional per field, who is asked, and the order they see."
That's where the per-field detail lives — required or optional for each individual field rather than each chip, which fields are asked of the lead traveler only, and the order the client sees them in. Anything you do in there is saved the same way and reflected back in the chips when you close it.
The heading reads 2 · Then they agree to.
A switch labelled My terms & conditions, with a note beside it saying where the wording comes from: · from your agency, or · from your profile when your own advisor terms are what will be used. Preview · Customize for this trip opens the Terms for this trip drawer — "Preview what the client reads, and customize it for this proposal" — where you can read the exact text and override it for this proposal alone without touching your saved terms.
Every set of supplier terms attached to this proposal is its own row with its own switch. Next to the supplier's name, the row says how the terms are stored — PDF, link or text — and, when the proposal has two or more options, which options they apply to: "· PDF · applies to all options."
The ⋯ menu on a row offers Edit, an Applies to section with a tickbox per option, and Remove.
+ Supplier terms ("· PDF, link or paste") opens a picker. At the top, a SUGGESTED list — suppliers already on the trip, each with a short reason. Below that, the rest of your supplier list. At the bottom, Not listed? Add supplier terms with three tabs:
| Tab | What you fill in |
|---|---|
| Supplier name and Their terms PDF — the file is uploaded and hosted for you | |
| Link | Supplier name and Link to their terms |
| Paste | Supplier name and Their terms — paste the text straight in |
Then Add supplier terms.
Each option has a Booked through field on its Terms & protection tab. Choose the supplier you'll book that option with, and its saved terms are added here automatically, applied to that option only. A client looking at your Universal option never sees Disney's terms.
When your client accepts, the booking is created with the Booked through supplier instead of a supplier guessed from the option's name.
Keep the cancellation policy with the supplier's terms. Under Suppliers, edit the supplier and set Supplier terms default to Write or paste text. Add the terms link with the link button, then paste the cancellation policy underneath. Every option booked through that supplier then carries both.
A row reading They confirm by with two chips: Ticking a box and Typing their name. Until you pick one for this proposal specifically, a note reads · agency default — meaning whichever your agency has set is what will apply.
On the far right of the same row, They don't need to agree. Pick that and the client accepts with no agreement step at all.
If nothing is attached, nothing gets signed. Turn on acceptance with no agency terms and no supplier terms and the card shows an amber notice: "No terms are attached, so nothing will be signed." It is not a blocker — but a proposal in that state is asking the client to agree to an empty page.
The right-hand column is titled with your client's names — What Tom & Rachel go through — and lays out the three steps as they'll meet them:
Underneath, an honest estimate: "About 6 minutes for two travelers. Anything you don't ask for now you can request later with a traveler-info link." It's built from the travelers, the chips, the forms, and whether they have to type their name — so watching it climb as you tick chips is the fastest way to feel how long your form actually is.
An add-on offer skips the details and pay steps entirely — it collects nothing and is billed onto the trip's existing invoice — so only Agree is shown.
Closed, the card reads as one line: Custom · 7 fields per traveler · My terms +1 supplier, tick to accept. With nothing attached it reads No terms, and with agreement off, no agreement.
An amber dot appears on the card when the proposal collects nothing beyond the lead traveler and has no document attached — together, that's a proposal asking the client for nothing and binding them to nothing. Either one alone is a normal choice and is left alone.
Top left, a currency chip: USD · change. Top right, a three-segment mode strip:
Switching segments rewrites the schedule and keeps what it can — the deposit amount you'd typed, the number of days you'd picked for the balance — so flipping through them to see what each looks like doesn't cost you your figures.
In Deposit, then balance, the card is one sentence with blanks you click:
Collect $500 ▾ when they book, then the balance 60 days ▾ before travel → Jan 11, 2027
Pay in full replaces the whole sentence with a single line: "Collect the full $18,400 when they book."
The first blank reads the deposit back to you in the shape you chose it:
| What you set | How the blank reads |
|---|---|
| Flat amount | $500 |
| Percentage | 10% ($1,840) |
| Per traveler | $200 per traveler ($400) |
| Per traveler, adults only | $200 per adult ($400) |
| Per room or cabin | $500 per cabin ($1,000) |
| Nothing set yet | No deposit set |
The total in brackets appears only when it differs from the rate, so a one-room booking reads $500 per cabin and a two-room one reads $500 per cabin ($1,000).
Until you've opened the picker once, a hint sits beside the blank: (flat · 10% · per traveler).
Clicking the deposit blank opens a picker with all four ways to work out a deposit, each priced against this proposal at the same time so you can compare them:
| Basis | What it means |
|---|---|
| A flat amount | One deposit for the whole booking, however many travel |
| Per traveler | Multiplied by the travelers on the booking · children count ▾ |
| A share of the price | Scales with whichever option and add-ons they pick |
| Per room or cabin | The way most cruise lines and some resorts take it |
Type a rate into any row and its figure updates; click the row's name to make it the deposit.
children count ▾ on the Per traveler row is a real control, not a note. It offers Children count and Adults only. Pick Adults only and the sentence says so — it reads per adult, not per traveler — because nothing else on the proposal records that choice.
The picker states its own assumptions in a header line, because two of the four figures are a rate multiplied by something you never typed:
How is the deposit worked out? Amounts shown for Four Seasons, $18,400, 2 adults, 1 child (not counted), 1 room.
At the bottom: "Different deposit for one option? Set it on that option's Terms & protection tab — it overrides this for that option only."
The editor previews one room. Your client hasn't picked a cabin yet — there is no cabin selection to read at the time you're writing the proposal — so a per-room deposit is previewed at whatever the party works out to, usually one. Whenever the figures are sized that way the card says so underneath: "Priced at 1 room — more cabins raise the deposit." Take that sentence seriously on a cruise: two cabins is twice the deposit, and it is right at checkout even though the preview shows one.
In Installments, the sentence grows a second clause:
Collect $100 per traveler ▾ when they book, then monthly ▾ on the 1st ▾ until 60 days ▾ before travel, at most any ▾ payments → 6 × $234
The cadence choices are weekly, fortnightly and monthly; a monthly plan also picks the day of the month (1st to 28th). The end is N days before travel — 30, 45, 60, 75, 90 or 120 — and at most caps the count (handy when a supplier allows only so many payments). The payments split whatever is left between booking and that point. There's no fixed monthly figure to set; the plan divides the balance across however many periods the client's booking date actually gives them.
Under the sentence, two small optional menus:
Below that, the card lists every payment a traveler booking today would get — When they book with the deposit, then each installment with its date and amount. It is worked out by the same code that writes the traveler's invoice, so what you see here is what gets created. Someone who books later gets fewer, larger payments that still end on the same date.
The list tells you when a plan can't spread out:
After someone books, each payment is its own row on their invoice. You can change any one payment's date or amount right there — click the date in the invoice's payment schedule — without touching the plan for anyone else.
The balance blank is deliberately not shown in Installments. The last payment there is the plan, and labelling it "the balance" named one thing while the list drew another.
Under the sentence, a rail from booking to travel. The first dot is Books with $500 today beneath it; each dated payment gets its own dot (Jan 11 / balance $17,900); the travel date is a hollow dot labelled travel. A payment whose date isn't settled yet shows as Date TBD rather than being quietly dropped.
In Installments the rail is replaced by the payment list above — ten dots can't carry ten dates and amounts legibly.
A payment you set to invoice rather than charge is named separately — $500 today · $200 invoiced, or $500 invoiced when nothing is charged at booking.
Under the rail: "Based on Four Seasons at $18,400. Other options and add-ons change the balance, never the deposit." And + Add a payment in between if you need a third date.
Add a third payment, date the deposit, or build anything the three segments can't describe, and the sentence is replaced by a table — one row per payment:
| Column | What it holds |
|---|---|
| Payment | The name the client sees on the invoice |
| Amount | A figure plus a type menu: flat, per traveler, % of price, per room, whatever's left |
| Due | When they book, Days before travel, A date, or At check-in |
| On $18,400 | What that row actually comes to for the previewed option |
The footer carries + Add a payment and the arithmetic: ✓ Adds up to $18,400 in green, or Under by $2,400 / Over by $150 in amber. Back to a simple deposit appears only when the rows really can collapse back into a deposit and a balance — it's hidden rather than shown-and-destructive, because it discards the middle payments.
A payment plan's row is not editable in the table. If your schedule includes an installment plan, its row reads Payment plan in the Due column and its menus are shut, with the reason on the row: "Switch to Installments to change the plan." Change the cadence and the end date from the Installments sentence, not here. Its money column shows the plan's whole total, with · 8 payments underneath.
Below the schedule, four tiles:
Price promise is not a switch, because "say nothing" is a real answer. The popover explains the question — "What are you promising about the price? Shown to the client next to the total and on the invoice" — and offers three:
| Promise | The hint under it | What the client actually reads |
|---|---|---|
| Not held until booked | The usual line until the supplier booking is placed | "Prices aren’t held until your booking is placed with the supplier, so price and availability can change until then." |
| Held until a date | A supplier hold or a fare that expires | "Pricing is held through September 30, 2026." |
| Say nothing about it | No promise shown | (nothing is printed) |
Each row shows the client's own sentence in quotes, so you're picking the words rather than a label for them. Pick Held until a date and a date picker appears on that row; typing the date is picking that promise, so the two travel together.
A hold that has already lapsed is read out in the past tense — "This price was held until September 30, 2026 and may now change." A dead promise is never printed as a live one.
Say nothing about it prints nothing at all. It does not fall back to a generic sentence, because showing a promise where you deliberately chose to say nothing is worse than showing nothing. (The general "Pricing and availability are subject to change until booked and confirmed" footer is a separate, availability-wide line and is unaffected.)
The popover's last line names your agency's starting point: "Agency default: Not held until booked · change in your agency settings."
Set it under Settings → Agency & Branding → Branding, in the Branding card, under Price promise on new proposals. The page's own note says what it does: "Stamped when a proposal is created. Changing it never edits proposals you already made."
So changing the default is safe — no proposal already in a client's inbox moves — and it's also why it only helps going forward. If you want a promise changed on a live proposal, change it on that proposal.
Advanced is a link under the tiles, and it holds the things most proposals never touch:
Closed, the card reads: USD · $500 at booking · balance 60 days before travel · card kept on file · price locked once paid. Pay in full stops at USD · paid in full at booking; an installment plan reads USD · $500 at booking · 6 monthly payments; and a proposal with nothing set reads USD · no deposit set rather than inventing a $0 deposit.
Once a proposal is accepted the card is read-only, and a line at the top says so:
Accepted Sep 12, 2026 — the schedule the client agreed to is on the trip's invoice.
That's the point: the agreed schedule now lives on the trip's invoice, which is where payments are actually taken and where any change has to be made. The quote expiry, price promise, planning fee and card-on-file settings lock at the same time.
An option carrying its own payment schedule also makes the card read-only — and shows that option's schedule rather than the proposal's, with a note saying so: "Four Seasons has its own payment schedule, and that is what this card is showing. Edit it on that option's Terms & protection tab." Two schedules edited from one surface is how an advisor clicks a chip and watches nothing happen, so the card points at the one place that schedule is really authored. The quote expiry, price promise and planning fee stay editable, because an option override can't contain those.
Two things you may have heard about are not shipped yet, and nothing in this release does them:
Both change what happens at acceptance and at checkout, not just the editor, so they're being built as their own releases. Until then, an approval-without-payment is best handled as a deposit you don't charge, and a provisional price with Held until a date or Say nothing about it.
This is part of JourneyFuse’s travel proposal software: branded proposals clients can review, choose from and pay on.
Paste a Viator link, search Viator from an excursion card, or pick from the tours that fit a cruise port day. Tours come in with Viator's photos, write-up and price, and the client's Book on Viator link credits you.
Track plans and confirmations, choose view-only or contributor sharing, and let travelers manage their own reservations.
Create stunning day-by-day itineraries your clients will love — with drag-and-drop blocks, image carousels, and a reusable template library.