Ticket Purchases Widget: Limit option availability and set price simultaneously

Hello,

I am trying to allow people to choose housing options for an event, and I only have 20 single rooms available. I would like to make it so that once the option is chosen 20 times, it is no longer an available option. I know that can't be done on a single choice question, so I tried the Ticket Purchases widget, and that lets me set how many are available, but not set a calculation value. Is there a way that I can set a price for something AND set it so that an option can't be chosen after it hits a certain quantity?

When I tried to use the AI assistant, it said it could add a calculation value, but then all it did was change the quantity of each room available. (which is what you'll see in the screenshot)

Thank you!

Hi NCSynod,

Thanks for reaching out to Jotform Support. I'm an AI assistant here to assist you.

Let me help you with that:

1. Why Single Choice and Ticket Purchases are limited

Standard Single Choice fields cannot limit how many times an option is selected across all submissions. For that, you need one of the inventory-style widgets. The Ticket Purchases widget can limit total availability per option (via the quantity in curly brackets) but, based on the available information, it does not support sending calculation values the way regular fields do.

2. Widget options that support quantity limits

To make an option unavailable after a certain number of selections, you can use one of these widgets:

• Inventory – Tracks a single item with an Available Quantity. Once it reaches zero, it can no longer be selected.
• Ticket Purchases – Lets you define ticket types with quantities in curly brackets (e.g., Single Room {20}) and limits how many can be selected until they run out.
• Gift Registry – Similar to Ticket Purchases, with quantities in curly brackets and a max selection.
• Quantity Gift Registry – Lets users pick quantities per item and also respects available quantities.

However, from the information available, only Quantity Gift Registry explicitly supports a calculation-related setting (Calculate Total), and that is for the total number of selected items, not a per-option price table like standard calculation values.

3. Practical approach for your use case

Given what is documented, you have two main options:

1. Use an inventory-style widget to enforce the 20-room limit
   For example, use Inventory or Ticket Purchases to manage the “Single Room” availability (set it to 20). This will ensure that once 20 are selected across submissions, the option is no longer available.
2. Handle pricing separately
   Because the widgets do not expose per-option calculation values like a regular Multiple Choice field, you would typically:
   • Use the widget purely to control availability (e.g., “Single Room {20}”).
   • Then use a separate calculation or payment setup that references the widget’s total (where supported, such as with Quantity Gift Registry using Calculate Total) or that charges a fixed amount per selected item if your pricing is uniform.

With the current documented behavior, there is no direct way to have Ticket Purchases both (a) manage per-option inventory and (b) behave like a standard field with custom calculation values per option at the same time. The AI assistant changing the quantities instead of adding calculation values matches this limitation.

If you can share how your pricing is structured (for example, whether all single rooms have the same price and whether you need different prices for other room types), we can suggest a more concrete combination of widget + calculation field.

Let us know if you have any other questions.

Okay, so how exactly do I go about option 2 that references the widget's total without just rewriting the question again? I don't want people to have to fill the same question out twice.

Hi NCSynod,

Let me help you with that:

To avoid asking the same question twice, you can use a widget that both tracks quantity and can send a single total value into your pricing flow, then base all pricing on that total.

The only inventory-style widget documented with a calculation output is Quantity Gift Registry, via its Calculate Total option. That total can then be used in a Form Calculation widget and, if needed, passed to a payment field.

Phase 1 – Set up Quantity Gift Registry to track rooms

1. Add a Quantity Gift Registry widget to your form and list your room options in Items, with quantities in curly brackets, for example:
   Single Room {20}
   Double Room {40}
2. Enable the Calculate Total option in the widget’s settings so it sends the total number of selected items out for calculation.
3. Keep this as the only place where users choose their housing, so they are not answering the same question elsewhere.

Phase 2 – Turn the widget’s total into a price

1. Add a Form Calculation widget to your form.
2. Open its settings and insert the Quantity Gift Registry widget field into the formula so it uses the widget’s total selection count.
3. Multiply that total by your room price (for example, [Quantity Gift Registry] × 100 if each room is $100). This gives you a single total price field, without re-asking which room they chose.

Phase 3 – (Optional) Charge via a payment field

1. Add your preferred payment element to the form.
2. Set its Payment Type to User Defined Amount.
3. Use the Get Price From option to select your Form Calculation widget so the amount to be charged comes directly from that calculation.

With this setup, respondents only interact with the Quantity Gift Registry widget once to pick housing, and that same interaction both limits inventory and drives the price, so there is no need to duplicate the question.

Give it a try and let us know how it goes.

With the quantity gift registry, is there a way to limit how many of any of the options they can choose?

Hi NCSynod,

Let me help you with that:

Based on the available information, the Quantity Gift Registry widget does not have Min Selection or Max Selection settings. It is described specifically as working “without Min and Max Selection” and simply lets users pick multiple quantities of each item, up to each item’s own available quantity.

If you need to limit how many items a single respondent can choose in total from a widget, the documented widgets with that kind of control are:

• Ticket Purchases – has Min Selection and Max Selection (but no per-item quantity input).
• Gift Registry – has Max Selection (but again, no per-item quantity input).

So with Quantity Gift Registry you can limit stock per option, but not the total number of options or units a single person can select across the widget.

Let us know if you have any other questions.

But can any of those options both limit the number a person can select AND do a calculation value?

Hi NCSynod,

Let me help you with that:

From the available information, the widgets break down like this:

• Ticket Purchases – Can limit how many items a person can select using Min Selection and Max Selection, but there is no documented support for sending a numeric value out as a calculation field (no calculation values / Calculate Total setting).
• Gift Registry – Can limit selection with Max Selection, but again, there is no documented calculation output.
• Quantity Gift Registry – Has Calculate Total to send the total number of selected items for calculation, but it explicitly works without Min and Max Selection, so it cannot limit how many items a person can select in total.
• Inventory – Can track an item’s Available Quantity and can be configured to submit just the quantity value, but it does not have Min/Max Selection across multiple items in one widget.

So, based on what is documented, there is no single widget that both:

• Limits how many items a person can select in total (Min/Max Selection), and
• Also provides a built-in calculation output (like Calculate Total or per-option calculation values).

To combine both behaviors, you would need to:

• Use a widget like Ticket Purchases or Gift Registry to control how many items a person can select, and
• Handle the pricing or scoring separately via a Form Calculation widget and/or other fields, instead of relying on a calculation value coming directly from those widgets.

Let us know if you have any other questions.

So how would I use the Form Calculation widget to get the cost of which option they chose using the ticket purchases widget or the gift registry widget?

Hi NCSynod,

Let me help you with that:

From the available information, Ticket Purchases and Gift Registry are documented for limiting selections and tracking inventory, but not for providing a numeric output that you can directly plug into a Form Calculation widget the way basic fields with Calculation Values do.

Here is what is documented and what it means for your setup:

• Ticket Purchases
  It lets you define ticket types with quantities in curly brackets and control how many items a person can pick using Min Selection and Max Selection. However, there is no documented feature like Calculate Total or per-option numeric output that you can directly use in a Form Calculation widget.
• Gift Registry
  It lets you list items with quantities in curly brackets and set a Max Selection for how many items a person can choose. Again, there is no documented calculation output that you can feed into a Form Calculation widget.
• Form Calculation widget
  It can perform calculations based on fields that provide numeric values (for example, basic fields with Calculation Values or widgets like Quantity Gift Registry when Calculate Total is enabled). The documentation only describes passing such a calculated total to a payment field using User Defined Amount and Get Price From.

Because there is no documented numeric output from Ticket Purchases or Gift Registry, there is no supported way described here to have the Form Calculation widget automatically compute the cost based directly on which option was chosen in those widgets.

In other words, with the information available, you can either:

• Use Ticket Purchases / Gift Registry to control inventory and selection limits, but handle pricing outside of those widgets (for example, with separate fields that do support calculation values), or
• Use a widget like Quantity Gift Registry that has Calculate Total for numeric output, but without Min/Max selection limits.

Reach out again if you need any other help.

Hi NCSynod,

There's a workaround you can try with the help of the Update/Calculate Field condition. We'll assign a value for each option. Let me show you a demo:

1. In Form Builder, click on the Add Element button on the left side. Under the Form Elements, below the Basic tab, drag and drop a Number element that will show the amount of the selected option.
2. Now, on the orange navigation bar on top, go to the Settings tab and select Conditions from the left menu.
3. Next, click on the Add Condition button and choose the Update/Calculate Field condition.
4. Create the condition below for each option, and click on the Save button.

Here's a screencast of how this works:

Give it a try and let us know if you’ve got other questions.