Software for destination wedding planners

Q: Does it handle guests arriving on different days?

Yes. Each guest carries an arrival day, departure and hotel, and Logistics groups everyone by arrival window so you can see who lands when.

Q: Can I build shuttles without doing it by hand?

Each arrival group has a one-click Build shuttle action that sizes transport to the guests in that window and feeds the driver manifest.

Q: Is it built for professional planners or couples?

Planner-first. The planner builds the room and logistics; the couple can be invited to place their own guests and approve decisions.

Destination planner software

A destination wedding is a normal wedding plus a logistics problem. Your couple is in New York, the venue is in Puglia, half the guest list is flying from three continents, and every vendor quote comes back in a different currency. Most planning tools were built for a hometown wedding where everyone drives in the morning of — they fall apart the moment travel, time zones and currencies enter the picture.

What destination planners actually need from software

After looking at how destination specialists work, the same gaps show up again and again in general-purpose tools:

Travel and arrivals per guest — not just "attending / not," but which day each guest lands, where they're staying, and when they leave. This is the spine of every shuttle and welcome-bag decision.
Shuttles built from real arrivals — grouping guests by arrival window and sizing transport to match, instead of guessing.
Multi-currency budgeting — a Tuscan venue invoices in euros, the band quotes in dollars, the florist in pounds. A single-currency budget is useless here.
Multi-day structure — welcome dinner, ceremony, farewell brunch, each with its own guest list and run-of-show.
One live guest list feeding seating, catering counts and transport, so a late RSVP change doesn't quietly break three other things.

How Mezze approaches it

Mezze was shaped by planning an actual 200-person destination wedding, so the travel loop is built in rather than bolted on. Guests carry arrival day, departure and hotel alongside their RSVP. Those arrivals group automatically in Logistics, and a shuttle can be built from any arrival window in one click — sized to the guests in it, feeding straight into the driver manifest. Multi-day weddings get a day each in one schedule. And because the guest list is the single source, RSVP changes ripple downstream to seating and catering without anyone re-keying anything.

Try it on a destination wedding

Add guests with arrival days, group them into shuttles, and plan every day in one place.

Open Mezze — free

Honest comparison

The established professional tools (Aisle Planner, Planning Pod, HoneyBook) are strong at client management, contracts and invoicing, and if that's your bottleneck they're worth a look. Where they tend to struggle for destination work is the connected travel layer — guest arrivals driving shuttles and manifests — and, in some cases, multi-currency. Trello and spreadsheets are infinitely flexible but nothing connects, so a single change means updating five places by hand. Mezze's wedge is the connected data: change one thing, everything downstream updates.

Questions we hear

Does it handle guests arriving on different days?

Yes — each guest carries an arrival day, departure and hotel. Logistics groups everyone by arrival window so you can see exactly who lands when.

Can I build shuttles without doing it by hand?

Each arrival group has a one-click "Build shuttle" that sizes transport to the guests in that window and feeds the driver manifest.

Is it built for professional planners or couples?

Planner-first. You build the room and the logistics; the couple can be invited to place their own guests and approve decisions.