Shopify form conditional logic shows or hides a field from another field’s answer. In SK Form Builder, each rule can combine conditions with AND or OR. The operators in the catalog are equals, contains, is empty, and greater or less than. The catalog does not list eight operators, and it does not put these rules on a paid tier only.
Use a rule when some visitors should never see a question. Leave the field visible when everyone needs to answer it. A hidden required field that the shopper cannot reach may still block submit. This behavior has not been verified, and the catalog does not say whether hidden fields drop their required flag. Test that path.
Other form products also advertise conditional logic. The Jotform Shopify listing was read as a search excerpt, not a full page. That excerpt advertises conditional logic. It is not a full audit of Jotform’s rule builder, and this article does not quote a Jotform price.
Add a rule only when it shortens the form
A contact form with name, email, and message does not need logic. A wholesale form does, if retailers and distributors answer different follow-ups. A custom-order form does, if a file upload appears only when the shopper chooses “I have artwork.”
The rule sits on the field you want to show or hide. It points at another field. It does not create a new page by itself. Multi-step pages are a separate feature, with their own titles and progress navigation. You can use both: a choice on step one can reveal a field on a later step. Confirm that in a storefront test. The catalog does not print a diagram of cross-step rules.
AND versus OR
AND means every condition in the rule must be true. OR means any one of them is enough.
Example: show a VAT field only when the country equals a value you care about AND the buyer type equals “business.” If either answer is missing, the VAT field stays hidden. That is AND.
Example: show a “tell us more” box when the reason equals “order problem” OR the reason equals “something else.” One match is enough. That is OR.
Do not mix the two ideas in your head and then build a rule you cannot explain to support. If you cannot say the rule in one sentence, split it or delete a condition.
Operators the app documents
- Equals: the answer matches a value, such as a radio choice named Retailer.
- Contains: the answer includes a string. Use this on text you control. Shoppers spell company names in more than one way, so contains is a weak gate for approval.
- Is empty: the field has no value yet. Use it to reveal help, not to hide the only email field.
- Greater or less than: a numeric comparison, such as a quantity or an order-volume number.
Those are the operators named in the catalog. Starts-with, ends-with, and a date comparison are not in that list. Date fields exist as inputs. They are not, by themselves, a show-and-hide operator.
URL parameters can prefill text, email, URL, and address fields for a logged-in customer or from the query string. Prefill is not the same feature as conditional logic. A parameter can fill a field. A rule then reads that field. Test both if you build links from a campaign.
A wholesale example and a retail example
Put a required select at the top: “I am a retailer” or “I am a distributor.”
Retailer
When the select equals retailer, show the store website and a typical monthly unit count. Hide the territory field. The website uses the URL field type so an invalid address fails validation.
Distributor
When the select equals distributor, show territory and a larger volume number. You can add a greater-than check if you only want a follow-up when volume is above a number you choose. Hide the single-store website if it does not apply. Keep email visible for both. You cannot reply without it.
Staff still approve the account. The rule only changes the form. It does not hide retail prices. Price hiding is the quote app, described on Request a Quote and Hide Price.
File upload and other fields you can reveal
A yes or no choice can reveal a file upload. The upload uses an extension allowlist and checks type and size in the browser. The catalog does not publish a megabyte cap. Tell the shopper which extensions you allowed, in the field label, because the rule will not explain the allowlist for you.
A product selection field and a quantity stepper can stay hidden until the shopper says they want a custom order. A submission can then create a draft order from product fields. The logic does not set the price. Staff do that on the draft order.
Submit both answers from the storefront, not only from the editor preview. Confirm the revealed field is required only when it is visible. A hidden required field that still blocks submit is a broken rule, and the catalog does not promise that hidden fields drop their required flag. Check it.
Plan prices are Starter at no charge, Basic at $4.99 a month or $49.90 a year, and Pro at $12.99 a month or $129.90 a year. Conditional logic is not assigned to one of those prices in the catalog.
Questions about form rules
Can one answer reveal a file upload?
Yes. Point the upload field’s rule at the choice that should reveal it. Test with an allowed extension and with a file type you blocked.
Can rules use URL parameters?
Prefill from a URL parameter is a separate field behavior. A rule can read the field after it is filled. The catalog does not describe a rule that inspects the URL on its own.
Are these rules limited to a paid plan?
The catalog does not say that. Do not promise a plan gate that the feature list does not contain.
Build the rule in SK Form Builder and submit both branches from the storefront. Install SK Form Builder when the operators above match the form you need.