Skip to main content

How does Tern handle multiple confirmation numbers on a lodging activity with per room pricing and what your Host needs?

How confirmation numbers behave on a lodging activity with per room pricing, what transmits to your host, and what to do by host.

Written by Thea Delamater

Each lodging activity in Tern holds one confirmation number. If you're using per room pricing to sell more than one room or cabin on a single lodging activity, and each one comes back with its own confirmation number, Tern treats the first confirmation number you enter as the primary.

You can still record the rest under Additional Confirmation Details, but only the primary syncs out to your host's back office when you have a Tern-to-host sync set up.

What transmits and what does not

The confirmation number you enter in the Confirmation Number field on the Booking & Pricing tab is what syncs to your host's back office. Anything you add under Additional Confirmation Details stays inside Tern for your own records.

If your host does not sync with Tern, or your host reconciles commission inside Tern, nothing goes out externally. All the confirmation info you record lives in Tern for your reporting.

What to do when you have more than one confirmation

You have two options. Which one you pick depends on how your host reconciles commission.

Option 1: Keep one lodging line and log secondaries in your host's back office

Use this when you want to keep the single-authorization, per-room-selection experience for your client. Enter the first confirmation number in Tern. Log the rest directly in your host's back office. This keeps your per-room pricing setup clean in Tern and still gets every confirmation to your host for reconciliation.

Option 2: Split into separate lodging activities

Use this when your host's back office doesn't offer a quick manual submission path, or when you want each confirmation to transmit on its own through Tern. Create a separate lodging activity for each room. Each one has its own confirmation number, supplier, and pricing, and each one syncs independently.

Splitting into separate activities changes the client experience. Each activity generates its own authorization instead of one combined authorization for the full booking.

By host

If your host reconciles commission in Tern.

No workaround needed. Enter the first confirmation number in the Confirmation Number field, and record the rest under Additional Confirmation Details. Nothing has to go anywhere else.

If you are a TPI advisor.

Use Option 1. Keep the rooms on one lodging line in Tern with per room pricing. Enter the first confirmation number in Tern. Log the rest directly in TPISuitcase using Quick Submit. This is TPI's recommended workflow.

If you are a Nexion advisor.

Use Option 2. Split into separate lodging activities so each confirmation number transmits on its own. Nexion does not currently offer a quick-submit path for adding secondary confirmations to an existing booking.

If you are a Uniglobe advisor.

Use Option 2. Split into separate lodging activities. UTC does not currently offer a quick-submit path for adding secondary confirmations to an existing booking.

Any other host with a sync set up.

If your host has a quick manual submission path in their back office, Option 1 works. If not, use Option 2.

What's coming

Support for adding additional confirmation numbers directly in Quick Booking is coming soon. Once shipped, you'll be able to record every confirmation number in one place in Tern. The first confirmation number you enter will still be the one that syncs to your host's back office. If you need every confirmation to land in your host system, keep using Option 1 or Option 2.

Related

Did this answer your question?