-
The_WerkstattHello Jotform Support Team,
Thank you for your previous assistance. I’ve implemented your recommendations and retested the form. While the location filtering for all workshops works correctly, there is still a main issues:
Pricing logic still not updating: The “Live Booking Summary & Total” only shows the base price and doesn’t change when the number of participants exceeds the minimum. For example:
- Candle Painting – 8 participants correctly showed €430. Changing the number to 12 should update the total to €516, but it stays at €430.
- Dip Dye – 11 participants (below the 12‑person minimum) correctly show €588. However, increasing to 13 participants should add the extra‑person fee, yet the total remains €588.
- No workshop shows any change beyond the base price when the participant count increases.
I’ve confirmed that the conditions populate the hidden pricing fields, and the Form Calculation widget uses the formula [Secret_Base_Price] + max(0, ([Number_of_Participants] - [Secret_Min_Pax])) * [Secret_Extra_Fee]. The formula is read‑only and linked to the Stripe field, yet the computed total does not update.
Could you please advise why the calculation isn’t triggered when the participant count changes, and how to ensure the correct calendar is displayed for Candle Painting? Any insight on fixing these remaining issues would be appreciated.
-
LaurenHi The_Werkstatt,
Thank you for reaching out to Jotform Support.
Here are some troubleshoot tasks you can try for participant-count and ensuring the correct calendar is displayed.
To make the participant-count always update, add these fields:
- Workshop selector: Single Choice/Dropdown (e.g., “Workshop A, Workshop B…”).
- Participant count: Number field.
- Price per participant: hidden Numberfield (optional if price varies).
- Total: Form Calculation widget.
Setup:
- If each workshop has a different price:
- Settings → Conditions → Update/Calculate Field:
- IF Workshop = A → set “Price per participant” to 100
- IF Workshop = B → set “Price per participant” to 150, etc.
- In the Form Calculation widget:
- Formula: Number of participants * Price per participant (or Number of participants * 100 if price is fixed).
- Click Save in the widget.
Common reasons it doesn't trigger:
- The Number field in the formula is an old/duplicated field.
- A condition is also writing to the Total field and overwriting the calculation.
- Formula was changed but Save in the widget wasn’t clicked.
To show correct calendar for selected workshop, add these fields:
- Workshop selector: Single Choice/Dropdown (“Workshop A, Workshop B, Workshop C…”).
- One Appointment field per workshop:
- “Workshop A – Date/Time”
- “Workshop B – Date/Time”
Setup:
- Hide all Appointment fields by default (Properties → Advanced → Hide field).
- Settings → Conditions → Show/Hide Field:
- IF Workshop = A → SHOW “Workshop A – Date/Time”
- IF Workshop = B → SHOW “Workshop B – Date/Time”
- (Recommended) Settings → Conditions → Enable/Require Field:
- IF Workshop = A → REQUIRE “Workshop A – Date/Time”
- IF Workshop = B → REQUIRE “Workshop B – Date/Time”, etc.
Give these a try and let us know how it goes!
-
The_WerkstattHello Jotform Support,
Thank you for your recent suggestion to use a “price per participant” setup. I appreciate your assistance, but I’d like to clarify why that approach doesn’t fit our business model and outline how we can adapt it to meet our requirements.
Why the standard solution doesn’t work
Our workshops have a revenue floor, meaning:
- If fewer than 10 people attend, we still charge for 10 participants (e.g., €430 for Candle Painting).
- If more than 10 people attend, we charge the base rate plus an extra fee for each participant above the minimum.
Under the standard “price per participant” approach (e.g., €43 × number of participants), an 8‑person group would only pay €344, which is €86 below our minimum revenue. We need to preserve this floor to avoid undercharging.
How we propose to use a hybrid solution
We can still adopt your simplified structure, but with two hidden number fields:
- Base Price – the cost for the first 10 participants (or 12 for Dip Dye).
- Extra Fee – the per‑person charge beyond that minimum.
Then, under Settings → Conditions → Update/Calculate Field, we’ll set these values for each workshop:
- Candle Painting: Base Price = 430, Extra Fee = 43
- Dip Dye: Base Price = 588, Extra Fee = 49
- …and so on for each workshop.
Finally, the Form Calculation Widget will use this formula:
Base Price + ( max(0, Number of Participants – 10) × Extra Fee )
This incorporates the revenue floor (via max(0, ...)) while still charging an overage fee when appropriate.
Could you please confirm that this approach will work within Jotform’s calculation and conditional logic framework, and let us know if there are any special steps we should follow to implement it correctly?
Thank you again for your help.
-
Lorenz JotForm SupportHi The_Werkstatt,
I cloned your form but I can't make it to work as well. It looks like there's an issue with setting up the Update/Insert conditions. Also, I'm not sure how are you able to add multiple DO statements on Update/Insert on a single condition, I'm not given any option to add or remove DO statements. I'm referring to this:
Now, the reason why it's not calculating was because you've set the numbers as string type, and you must convert them to number type. I tried doing it on a clone version, but I run into problems, where DO statements gets duplicated. Can you confirm if you're getting the same issue as below:
I might need to escalate this to our developers because of the issue, but can you confirm if you're getting the same as well?
Once we hear back from you, we can get moving on a solution
-
MMoyo
Hello,
Thank you for your update.
Yes, I can confirm that I am experiencing the same issues you mentioned:
- Multiple DO statements issue: I am not given the option to add multiple DO actions within a single “Update/Calculate Field” condition. Because of this, I had to rely on Jotform AI to recreate the conditions currently in the form, as I couldn’t manually configure multiple DO actions.
- Duplication issue: Yes, I am also seeing the problem where DO statements appear to be duplicated when editing or recreating conditions. This makes it difficult to manage the logic cleanly.
- String vs Number issue: I understand your point about values being treated as strings. I will review the fields to ensure all pricing values (e.g., 430, 43, etc.) are set as number types, not strings. However, even before correcting that, the structure of the conditions itself already seems unstable due to the issues above.
Given these limitations (especially not being able to add multiple DO actions properly and the duplication behavior), I believe this may be a system or UI issue rather than just a setup mistake.
Please go ahead and escalate this to your developers, as I’m currently unable to implement the required pricing logic reliably due to these constraints.
Looking forward to your feedback.
-
Lorenz JotForm SupportHi The_Werkstatt,
I created a ticket and escalated this to our Developers. Although we don't know exactly when it'll be fixed, we’ll circle back to this thread when we have an update.
Now, we can actually still work on your form, but I would suggest cloning your form and delete all existing Update/Calculate condition. I've already thought of a better approach to what you're trying to do, still using a condition, but should be set up manually. I just need a bit more information about the formula you want to incorporate like the one below:
Base Price + ( max(0, Number of Participants – 10) × Extra Fee )
Can you provide an example inputs and their actual result in total, so we can accurately test this on our end and provide you with the right steps on setting up the condition, and additional fields if needed.
Thanks for your patience and understanding, we appreciate it.
-
MMoyo
Hello Lorenz,
Thank you for escalating this to your developers — I really appreciate it.
Yes, I’m happy to provide clear examples of the pricing logic we are trying to achieve.
Pricing Logic OverviewWe use a base price (minimum participants) + extra fee per additional participant model.
🧪 Example Scenarios1. Candle Painting (10-person minimum)- Base Price: 430 EUR
- Extra Fee per person: 43 EUR
2. Dip Dye (12-person minimum)- Base Price: 588 EUR
- Extra Fee per person: 49 EUR
Formula We Want to AchieveBase Price + ( max(0, Participants - Minimum Participants) × Extra Fee )
Where:
- Minimum Participants = 10 (most workshops)
- Minimum Participants = 12 (Dip Dye only)
- I initially used Jotform AI to generate the current conditions because I couldn’t manually configure multiple DO actions.
- The current setup is unstable (duplicate conditions, string vs number issues).
- I’m happy to clone and rebuild from scratch manually, as you suggested.
Please let me know the best way to implement this cleanly using Jotform’s native tools, especially:
- How to correctly handle the minimum participant logic (floor)
- Whether we should use hidden fields vs direct calculation
- And how to avoid the multiple DO action limitation
Looking forward to your guidance.
-
Reymae JotForm SupportHi The_Werkstatt,
I checked your form, and you mostly have everything to make the formula work. First, you need to work on the Update/Calculate conditions. You can set them up like this:
Now for the Total Booking Fee, you can use the formula below:
You can clone and test my demo form here. Take a look at the screencast below to see how it works after:
Give it a try and reach out again if you have any other questions. -
The_WerkstattHi Jotform Support,
I am using the Stripe Checkout integration on a workshop booking form. I have set the payment type to "Custom amount" and am successfully pulling the price from a Form Calculation widget.
However, I am facing two critical issues:
- Missing Checkout Summary: On the Stripe-hosted checkout page, the customer only sees the price. It does not show a description of the service. How can I pass a value from a Short Text field (containing a summary of the Course, Date, and PAX) to the Stripe Checkout description or line item field?
- Metadata Not Recording: The submission data (Workshop selection and Appointment date) is not appearing in the Stripe dashboard payment details. Could you guide me on how to use the "Custom Data Field" or "Stripe Metadata" settings in the Additional Gateway Settings to ensure this information is recorded for invoicing purposes? ``
My goal is to ensure the customer sees a clear order summary before paying and that the data is stored in Stripe so we can automate tax-compliant invoices via API.
-
-
LaurenHi The_Werkstatt,
Thanks for reaching out to Jotform Support. Regarding the first issue, let me walk you through it:
- In Form Builder, click your Stripe field, open its Payment Settings, ensure Ask Billing Information to Customer is turned On, then under Custom Data Field select the Short Text field that contains your “Course – Date” description and save.
Regarding Metadata Not Recording, here's how you do it:
- Add a Short Text field (or combine both values into one Short Text via conditions/calculation), then in Form Builder → Stripe field → Payment Settings → Additional Gateway Settings, turn Ask Billing Information to Customer = On, set Custom Data Field to that Short Text so it appears in Stripe’s payment details.
- In the same Additional Gateway Settings panel, locate Stripe Metadata, map your Workshop selection and Appointment date fields to metadata keys (e.g., workshop, appointment date), then submit a test payment and check the Payment → Metadata section in your Stripe dashboard to confirm they’re stored for invoicing.
Give these a try and let us know how it goes.
-
The_Werkstattthis is all AI, your platform doesn't have all this things
-
Lorenz JotForm SupportHi The_Werkstatt,
I’ve gone ahead and moved your other concerns to separate threads to keep things tidy, and someone from our Support Team will help you with them here:
Stripe Check out page only display the price
Submission data not showing in Stripe Dashboard
Let us know if you have any other questions.
Your Reply
Something Went Wrong
An error occurred while generating the AI response. Please try again!