Set up required fields

Overview

Required fields ensure customers don't miss important product choices. When an option is marked as required, customers must select or fill it out before they can add the product to their cart.

Make specific options mandatory so customers must make a selection before adding products to their cart.

Making an Option Required

Within an Option Set

1. Navigate to Option Sets page
2. Open the option set you want to edit
3. Click on the option you want to make required
4. Check the box Option is required for this option set below the Option Type and Option Label fields
5. Click Save in the contextual bar

The option is now required for all products using this option set.

Understanding Shared Options

If you're using a shared option across multiple option sets, the required setting is independent for each option set.

How It Works

• An option can be required in one option set and optional in another
• Marking a shared option as required only affects the current option set you're editing
• Each option set maintains its own required/optional settings

Example:

You have a "Gift Message" option shared across two option sets:

• Birthday Gifts Option Set: Gift Message is required ✓
• Standard Products Option Set: Gift Message is optional

The same option behaves differently depending on which option set is applied to the product.

Customer Experience

What Customers See

When an option is required:

• An asterisk (*) label appears next to the option
• If they press "Add to Cart" without selecting a required option, it triggeres the validation rule preventing them from adding the product to their cart
• In case of a "hidden label" option, the label is not visible (nor is the asterix *) to the customer but the validation rule still applies

Validation Messages

If customers try to add a product without completing required fields:

• Option input field or select is highlighted
• An error message appears for that specific option

When to Use Required Fields

Good Use Cases

• Personalization details - Name, date, custom text that's essential to the product
• Critical selections - Size, color, or configuration that affects the product
• Mandatory add-ons - Options that must be chosen for the product to be complete

When to Keep Optional

• Nice-to-have features - Gift wrapping, gift messages, bonus items
• Preference-based options - Upgrades or extras that some customers may not want
• Additional information - Non-essential fields that provide extra context

Best Practices

Be Strategic

• Only mark truly essential options as required
• Too many required fields can frustrate customers and reduce conversions
• Consider making fields optional and using conditional logic instead

Clear Labeling

• Use descriptive labels that explain why the field is required
• Example: "Gift Recipient Name (Required for personalization)"
• Help customers understand what information is needed
• Avoid hiding labels for required fields

Test the Flow

• Go through the checkout process as a customer
• Ensure required fields are obvious and easy to complete
• Verify error messages are clear and helpful

Combining with Other Features

Required + Conditional Logic

You can combine required fields with conditional logic:

• Show a required option only when certain conditions are met
• Example: Make "Engraving Text" required only when "Add Engraving" is selected

Required + Pricing

Required fields work with priced options:

• Customers must select/fill the required option even if it has an additional fee
• Useful for mandatory upgrades or essential customizations