Shopify conditional logic, in the context of custom fields, means showing or hiding one field based on what a customer selects in another. For example, only showing an “engraving text” box after the customer checks “Add engraving.” Mini:Custom Fields Personalize supports this natively on the Basic plan and above ($5.99/month), including nested conditions where a field’s visibility depends on a chain of prior answers, no code required.
In this post:
- What Shopify conditional logic means for custom fields
- Real example: an engraving box that only appears on opt-in
- Step-by-step: setting up a conditional field
- Nested conditions: chaining more than one dependency
- Plan requirement and what conditional logic doesn’t do
- Common mistake: a condition referencing a deleted field
- FAQ
What Shopify Conditional Logic Means for Custom Fields
Here’s what shopify conditional logic can and can’t do on a product page, at a glance:
| Capability | Supported? | Notes |
|---|---|---|
| Show/hide a field based on a checkbox or dropdown choice | Yes | The core use case |
| Nest a condition inside another condition | Yes | Tested up to multi-level chains |
| Change a field’s price based on another field’s answer | No | Add-on pricing is set per field, not conditionally |
Shopify itself has no native conditional-field system for product pages, this is app territory, and it’s a real gap merchants run into as soon as they try to keep a product page simple while still offering optional add-ons like engraving.
Real Example: An Engraving Box That Only Appears on Opt-In
Say you sell bracelets and offer optional engraving for an extra charge. Without shopify conditional logic, every visitor sees a text box for engraving, even the ones who don’t want it, which clutters the page and invites empty submissions. With a conditional field, the engraving textbox only appears after the customer checks “Add engraving,” keeping the page clean for everyone else.
Step-by-Step: Setting Up a Conditional Field
In Mini:Custom Fields Personalize, setting up shopify conditional logic takes four steps. First, create the parent field, typically a checkbox or dropdown like “Add engraving?” Second, create the child field, your engraving textbox, and open its settings.
Third, in the child field’s condition settings, select the parent field and the specific answer that should trigger it, for example “Yes” on the engraving checkbox. Fourth, save and preview the product page to confirm the child field stays hidden until the parent condition is met.
Nested Conditions: Chaining More Than One Dependency
Conditional logic doesn’t stop at one level. A field can depend on a parent field that is itself conditional on another field, tested up to multi-level chains in Mini:Custom Fields Personalize. A practical case: “Add engraving?” reveals “Engraving style” (a dropdown), and choosing “Custom text” on that dropdown then reveals the actual engraving textbox, three fields deep, all conditional.
“Not only is the app easy to use, it’s highly customisable and solved a lot of legacy issues. On top of this the support is second to none and they go above and beyond. I’ve gone through a lot of apps over the years but I would put this top of my list overall in terms of service and performance.”
Source: The Precious People, United Kingdom (Shopify App Store review)
Plan Requirement and What Conditional Logic Doesn’t Do
Conditional logic is gated at Basic plan and above ($5.99/month), not reserved for Premium, worth stating plainly since merchants often assume advanced-sounding features are Premium-only, and this one isn’t. What shopify conditional logic doesn’t do: it can’t change a field’s add-on price based on another field’s answer, pricing is set per field independently of any condition.
Common Mistake: A Condition Referencing a Deleted Field
The most frequent support ticket around shopify conditional logic isn’t a bug, it’s a merchant renaming or deleting a parent field after a child field’s condition already points to it. The child field then either stops appearing or behaves unpredictably, since its trigger no longer exists. Before deleting or heavily renaming any field, check whether other fields have conditions pointing back to it.
Shopify’s own metafields documentation is a useful reference for how structured product data works natively, since Shopify has no built-in equivalent to app-level conditional fields.
See our guides on customizing product pages on Shopify and adding custom options on Shopify for more on building out a full custom field setup.
Frequently Asked Questions
- 1. What is conditional logic for Shopify custom fields?
- Shopify conditional logic means showing or hiding one custom field based on what a customer selects in another field, like revealing an engraving box only after a checkbox is checked.
- 2. Can I show a field only when a customer checks a box or picks an option?
- Yes, that’s the core use case for conditional logic: a child field’s visibility is tied to a specific answer on a parent field.
- 3. Does Shopify support conditional logic natively, without an app?
- No, Shopify has no built-in conditional-field system for product pages. It requires an app like Mini:Custom Fields Personalize.
- 4. Can conditional fields be nested inside other conditional fields?
- Yes, conditions can chain, a field can depend on a parent field that is itself conditional on another field, tested up to multi-level chains.
- 5. Is conditional logic available on Mini:Custom Fields Personalize’s free plan?
- No, conditional logic requires the Basic plan or above, starting at $5.99/month.
- 6. What happens if I delete a field that another field’s condition depends on?
- The dependent field can stop appearing or behave unpredictably, since its trigger condition no longer exists. Check for dependent conditions before deleting or renaming a field.
