Dependent Custom Fields (Conditional Logic) – Shorter, Smarter Booking Forms
Online booking flows work best when every question feels relevant. OctopusPro’s Dependent Custom Fields (also called conditional or cascading fields) hide follow-up questions until a user’s previous choice makes them necessary. This trims pages, speeds completion, and lowers abandonment—benefits confirmed across UX studies on conditional logic and cascading selects.
What are dependent custom fields?
A dependent field is a follow-up question that becomes visible only after the customer selects a particular option in another custom field. The link can also carry an extra price or extra time so costs and durations update automatically. This concept mirrors “cascading dropdowns” in web forms and is commonplace in salon and childcare platforms.
Why use them?
-
Shorter, cleaner forms – customers answer fewer irrelevant questions, which research shows cuts drop-off.
-
Error prevention – only valid combos can be submitted, reducing admin edits later.
-
Dynamic pricing & scheduling – surcharges or extra labour time attach themselves automatically.
-
Scalable data – identical logic patterns exist in other enterprise tools, making the approach an industry standard.
Real-world examples
Beauty industry
Customer flow: A salon offers Facial Treatment Type with options Classic, Hydration Boost and Micro-Needling. Selecting Hydration Boost reveals a dependent field Select Skin Type (Dry, Oily, Sensitive). If the client chooses Sensitive, an automatic +15 min prep time is added and a $20 surcharge covers special products. The customer sees only questions that fit their chosen treatment, while the schedule and invoice stay accurate.
Childcare industry
Customer flow: A daycare’s Care Session field lists Half-Day and Full-Day. Choosing Full-Day triggers a dependent dropdown Select Meal Plan (Standard, Vegetarian, Allergy-Friendly). Selecting Allergy-Friendly adds $8 to cover ingredient costs and stores dietary notes for staff. Parents aren’t distracted by meal choices if they book half-day care, and invoicing reflects the add-on automatically.
How to configure in OctopusPro
-
Navigate to Settings ▸ Service Settings ▸ Services ▸ Custom Fields.
-
Edit the parent field (e.g., Care Session).
-
Click + Add dependent field (under the option you want to branch from).
-
Pick the follow-up custom field from the dropdown.
-
(Optional) set Price Adjustment or Extra Duration that applies when the dependent field is triggered.
-
Save. The logic is now live in the Customer Portal, Admin Portal, and Fieldworker app.
Where it appears
Customer Portal & branded app
During booking, the parent field shows first. Once a triggering value is chosen, the dependent question fades in, keeping the page compact and mobile-friendly. Pricing or time updates instantly so customers always see an accurate estimate.
Admin Portal
Admins see parent and dependent fields stacked together for quick review.
Fieldworker app
Confirmed bookings list both the chosen option and any dependent answers, plus the adjusted price and time, so technicians arrive prepared.
Best-practice tips
-
Choose clear parent labels like Treatment type or Care session so customers understand why a follow-up appears.
-
Keep dependent chains short—two levels are optimal for readability, matching UX guidance on cascading select depth.
-
Use helper text to explain surcharges (“+ $8 Allergy-Friendly meal”).
-
Test on mobile; conditionally loaded fields must scroll smoothly.
-
Audit reports monthly to verify dependencies still reflect your pricing strategy.
Summary
Dependent Custom Fields let you craft intelligent, industry-grade booking forms that reveal just the right questions at the right time. Whether you’re upselling a hydration boost facial or capturing dietary requirements for full-day childcare, the feature keeps your users focused, your data clean, and your pricing precise.
For more information please visit Octopuspro user guide, and subscribe to our youtube channel.