JetFormBuilder Tour Booking Form With Price per Person and Date

To build a JetFormBuilder tour booking form with a price per person, save each departure date as its own post with a price_adult field. Feed those departures into a Select field with the Get values list from JetEngine Query generator, using price_adult as each option's calculated value. A Calculated Field then multiplies that price by the number of travellers.

Child rates, the single supplement and extras live in JetEngine meta fields on the tour, and the formula reads them with %META::field_name%. No custom code is needed.

• Map the client's pricing rules before you build
• The content structure
• Query only the current tour's departures
• Build the booking form
• How the total price formula works
• Show the price and use it in the submission
• When to use JetBooking instead
• Troubleshooting

Map the client's pricing rules before you build

Ask these questions first. Each answer becomes a field or a form setting.

The content structure

Tours post type

Create a Tours post type in JetEngine with these meta fields. Store every price as a plain number, with no currency signs or thousands separators.

• child_factor: the share of the adult price a child pays, for example 0.7
• single_supplement: the charge per single room
• extras_price: the per-person price of an optional extras package (one field per extra if there are several)
• deposit_percent (if deposits are used): the deposit share, for example 20
• max_travellers: the most people one booking can include
• price_from (optional): the lowest adult price, shown in listings

Fill in child_factor, single_supplement, extras_price and deposit_percent on every tour. Use 0 for an unused supplement or extra, 0 for deposit_percent when no deposit is taken, and 1 for child_factor if children pay full price. An empty value can leave the total blank or showing NaN.

Departures post type

Create a Departures post type with departure_date and price_adult. Link each departure to its tour, either with a JetEngine relation (one tour to many departures) or with a meta field that stores the tour's ID. Title each departure as its date, such as 12 May 2027, because the form uses the title as the dropdown label.

Separate records let the form list only that tour's dates, with each option carrying its own price.

Destinations (optional)

Add a Destinations taxonomy, or a post type related to Tours, so each destination page can show its tours in a Listing Grid.

Query only the current tour's departures

1. In JetEngine's Query Builder, add a Posts query for the Departures post type.
2. Filter it to the tour being viewed: compare the departure's tour link (relation or meta field) with the current post's ID, using JetEngine's dynamic value for the current object.
3. Show only future departures by comparing departure_date with today. Store dates in a format that compares correctly.
4. Order by departure_date ascending, save, and confirm the query preview returns items.

If you type the pipe string (shown below) by hand, use the number in the browser URL while editing the query (…&id=NN), not the query's own "Query ID" text setting.

The current-object filter has to resolve to the tour when the form builds its options. That can depend on your setup, especially with Enable Auto-Update, which reloads options through a separate request. Open a real tour page and confirm the dropdown lists only that tour's dates. If the preview stays empty, see our common JetEngine Query Builder mistakes and fixes.

Build the booking form

Create the form in JetFormBuilder and place it on the single Tour template. %META::% reads from the post where the form sits, so on any other page it has no tour to read. Field names must be unique on the page and use only lowercase Latin letters, numbers, - and _, with no spaces.

Departure (Select, name: departure)

Make the field required. Check whether the Select field in your version offers a Placeholder setting. If it does, add one such as Choose a departure date. If it doesn't, the earliest departure starts out selected and priced, so make sure travellers can see which date is chosen. Set FILL OPTIONS FROM to Generate Dynamically, then:

GENERATOR FUNCTION: Get values list from JetEngine Query
QUERY ID:           select your Departures query
OPTION VALUE:       ID
OPTION LABEL:       post_title
CALCULATED FIELD:   price_adult

OPTION VALUE and OPTION LABEL take post properties such as ID and post_title. CALCULATED FIELD takes the meta key price_adult, the same way the docs use _regular_price. The option source documentation also shows a pipe format typed into the FIELD NAME box: query ID | value | label | calculated value. With a query ID of 47:

47|ID|post_title|price_adult

Each option's value is the departure's post ID, its label is the date, and its calculated value is that date's adult price.

Adults and Children (Number, names: adults, children)

Make both required. Give adults a default and min value of 1 and children a default and min value of 0. A max value on a Number field is the same for every tour, because one form serves them all, so set one only if all tours share the same limit. For a per-tour cap, use a Select with the Numbers range by meta value generator, which builds options from 1 up to a number stored on the tour. Set its META KEY (default _max_quantity) to max_travellers.

Separate limits cap each field on its own. A combined adults plus children cap needs your own validation, so check the head count against max_travellers before you confirm a booking.

Single rooms (Number, name: single_rooms)

Required, with a default and min value of 0.

Extras (Radio, name: extras)

Use Manual Input. In the bulk editor, each line is Label : value : calc:

No extras : no : 0
Add the extras package : yes : 1

Make No extras the default. The CALCULATE value works as a 0/1 switch, and the price stays in the tour's extras_price field. Don't build several extras as one Checkbox and count on how ticked values combine. One Radio or Switcher field per extra keeps each on its own line of the formula.

Total (Calculated Field, name: total_price)

• VALUE TYPE: as Number. Only this mode uses each option's CALCULATE value.
• DECIMAL PLACES NUMBER: 2
• THOUSANDS SEPARATOR: a comma, if the client wants one
• CALCULATED VALUE PREFIX: your currency sign, such as $ (or CALCULATED VALUE SUFFIX for currencies written after the amount)

Put total_price inside a Conditional Block that shows only when departure is not empty, so visitors never see a broken total before a date is chosen.

Paste this formula into the Calculated Field. The wrench icon above the field lists every available macro.