Conditional Logic (Smart Rules)

Audience: Retailer/Factory admins
Where: Settings → Data Management → Object attributes → Conditional logic
Applies to: Product lines such as shirts, jackets, suits

Overview

Conditional Logic lets you control what appears in the configurator based on a customer’s choices. You can show or hide entire attributes and even specific attribute options (e.g., show a fabric picker only when a feature is set to “Yes”). Rules can use ALL (AND) or ANY (OR) logic across multiple conditions.

What you can do

• Show or hide one or more attributes based on selected values
• Show or hide specific attribute options for a given attribute
• Mark shown attributes as Required when they appear
• Combine multiple conditions using ALL / ANY
• Preview the logic and toggle a rule Active on/off

What you cannot do

• Change the underlying attributes or options (requests for new attributes/options go to the Chaos team)
• Set default selections for templates here (use Style Templates for presets)

Prerequisites

• The controlling attribute(s) and any dependent attribute(s)/options already exist
• You know which values should trigger visibility

Steps — Create a rule

1. Go to Settings → Data Management → Object attributes → Conditional logic and click Create Conditional Logic.
2. Under Controlling attributes, choose When = All (AND) or Any (OR), then add each Attribute / Operator / Value condition.
3. Under Dependent attributes, choose an Action:
   1. Show attribute(s) — pick one or more attributes; optionally mark them Required when shown.
   2. Hide attribute(s) — pick attributes to hide when the condition matches.
   3. Show attribute options — pick a target attribute, then select which options to make available for that attribute when the condition matches.
4. Use the right-side Preview panel to verify what would display.
5. Activate the rule (toggle Active on).
6. Click Save.

Tip: Keep one intent per rule (e.g., “Sleeve Vents Fabric visibility”). This makes future edits and troubleshooting much easier.

Examples

Example A — Guayabera shirt: show fabric only when vents are enabled

Goal: Only show Sleeve Vents Fabric when Sleeve Vent is set to Yes, and make it required when it appears.

1. Controlling attribute: Sleeve Vent — Equal To — Yes
2. Action: Show attribute(s) → pick Sleeve Vents Fabric and check Required
3. Activate → Save → QA in configurator
   1. When Sleeve Vent = Yes → fabric attribute appears and is required
   2. When Sleeve Vent = No → fabric attribute stays hidden

Example B — Suit jacket: cuff color only when functional cuffs are enabled

Goal: Show Buttonhole Thread Color only if Functional Cuffs is Yes.

1. Controlling attribute: Functional Cuffs — Equal To — Yes
2. Action: Show attribute(s) → pick Buttonhole Thread Color
3. Activate → Save → QA in configurator

Example C — Short sleeve cuff style only for short sleeves (attribute options stay hidden otherwise)

Goal: Show the Short Sleeve Cuff Style attribute only when Sleeve Length is Short Sleeve.

1. Controlling attribute: Sleeve Length — Equal To — Short Sleeve
2. Action: Show attribute(s) → pick Short Sleeve Cuff Style
3. Activate → Save → QA in configurator

Best practices

• Prefer show rules (start hidden, reveal when relevant) to keep the UI clean
• Use concise rule names like “Show: Sleeve Vents Fabric when Vent = Yes”
• After adding rules, do a quick QA pass for each affected attribute path

Troubleshooting

• Rule not working: Make sure it’s Active and the controlling value exactly matches the option label.
• Attribute shown but options missing: Use Show attribute options when the goal is to limit visible options.
• Conflicting rules: Temporarily deactivate others and re-test to isolate the conflict.

Related how-tos

• Manage Attributes (Designs): Edit labels, groups, positions, images, and activation.
• Style Templates: Build presets that preselect a set of attributes for fast ordering.

Change log

2025-08-25 — Added option-level visibility, activation step, and segmented examples for shirts and suits.