Conditional logic isn't working

Conditional logic can be tricky to get right, and small details matter a lot. If your fields aren't showing or hiding the way you expect, this guide will help you find the issue quickly.


Before you set up conditional logic

Conditional logic is much easier to get right if you plan it out before touching the app.

We recommend mapping out your logic first. Start by writing down which field should trigger the change, what value needs to be selected, and which field should appear or disappear as a result. Even a quick note like "if customer selects Yes in the Engraving field, show the Engraving Text field" is enough.

When you're ready to build it, treat it as a two-step process. First, create all your fields and add all your option values. Then go back through and set up the conditional rules. This way, you can select values from a dropdown rather than typing them manually, which avoids the exact match issues that cause most conditional logic problems.


Before you start troubleshooting: test on your live storefront

The theme editor preview doesn't always accurately reflect conditional logic. Before troubleshooting, open a product page directly in your browser and test there.

Check 1: Are both fields in the same Option Set?

Conditional logic only works between fields that are in the same Option Set. If the field you want to show or hide is in a different Option Set from the field triggering it, the logic will never work.

circle-check

Check 2: Does the value match exactly?

This is the most common cause of conditional logic not working or suddenly no longer working. The value you enter in the condition must match your option value exactly — same capitalization, same spaces, same punctuation.

A common reason this breaks is when you update an option value label but forget to update the condition at the same time. For example, if you change Gift wrap (+$5.00) to Gift wrap (+$8.00) but leave the condition referencing Gift wrap (+$5.00), the logic will stop working. If you ever change an option value label, always check your conditional rules and update them to match.

The easiest way to avoid this is to copy the option value directly from your option set and paste it into the condition field rather than retyping it.

Using Contains rather than Is gives you a little more flexibility here, since it only needs to find your text somewhere within the value rather than matching it exactly in full. We cover that in Check 3.


Check 3: Are you using the right condition type for your field?

The condition type you need depends on what kind of field you're referencing.

For a checkbox, use Contains with your checkbox value, for example Contains "Yes". Some versions of the app show Is Checked instead — either works.

For a dropdown or radio button, use Contains with the exact value, for example Contains "Gift wrap".

Using the wrong condition type is a common cause of logic silently failing with no error message.


Check 4: Is it set to "Any" or "All"?

If you want a field to appear when a customer selects option A or option B, make sure the logic is set to Any of the following match — not All.

All means every condition must be true at the same time. Any means the field will appear if at least one condition is met.

If your logic works for one value but not others, this is usually why.


Check 5: Are there duplicate fields in your Option Set?

If the same label on cart appears twice in an Option Set, the conditional logic won't know which field to trigger. The wrong field may show up, or nothing will trigger at all.

Scroll through your Option Set and look for any fields that share the same label on cart. Make each label unique by adding a character like ":" or adjusting the text slightly, then save and test again.


Still not working?

If you've worked through all five checks and the logic still isn't behaving correctly, try deleting the conditional rule and recreating it from scratch. Sometimes a fresh rule resolves issues that aren't visible in the settings.

If that doesn't help, contact our support team with a link to the product page where the issue is happening and a description of what you expect to see versus what's actually showing. We're happy to take a look.


Tips

  • Always test every possible selection on your live storefront, including selecting nothing, to confirm hidden fields stay hidden by default.

  • If you're setting up logic for the first time, the Conditional Logic setup guide walks through a working example step by step.

Last updated