- Getting started
- Content Blocks
-
Discount
- 1. DISCOUNT TYPES OVERVIEW
-
2. DISCOUNT CONDITIONS SYSTEM
- 2.1 Overview
- 2.2 CONDITION LOGIC (Simple → Advanced)
- 2.2.1: ALL Conditions (AND) - "This AND That"
- 2.2.2: ANY Conditions (OR) - "This OR That"
- 2.2.3: Different Rules Per Category (OR Between Groups)
- 2.2.4: Alternative Bundles (OR Between Groups)
- 2.2.5: Cross-Category Requirements (AND Between Groups)
- 2.3 Pattern Comparison Table
- 2.4 Complete Logic Control Reference
- 2.5 Available Condition Types (Complete List)
- CART CONDITIONS
- CUSTOMER CONDITIONS
- DISCOUNT CONDITIONS
- ELIGIBLE CONDITIONS
- 2.6 Condition Behavior Notes
- 3. DISCOUNT VALUE OPTIONS
- 4. ELIGIBILITY SETTINGS
- 5. MAXIMUM DISCOUNT USES
- 6. APPLIES ON (PURCHASE TYPE)
- 7 Real-World Example
- 8. ADVANCED TIPS & BEST PRACTICES
- Condition > Eligible
- BXGY
- Upsell
- Forms And Fields
Overview:
The “Forms and fields” feature lets you build fully custom forms for checkout and thank you pages, store the answers in Shopify (attributes, notes, metafields), and control exactly who sees which fields using rules and field‑level display triggers.
1. Form-level configuration
At the first level you configure the form container (for example “My form”) and its global behavior.
- Form settings include title, description, border style, data storage location (Order attributes, Order notes, or Order metafields), and high-level visibility rules (for example “show only to wholesale customers”).
- A unique Form ID is generated here; this ID must be connected in Shopify checkout settings so the form is actually rendered on Checkout and/or Thank you pages.
Example – Wholesale-only extra info form
- Form title: “Wholesale order details” with description explaining required extra fields.
- Save data location: Order metafields (for structured CRM/reporting) and/or order attributes (for quick visibility in the order timeline).
- Rules: Show only when the customer has tag “Wholesale” and subtotal ≥ ₹5,000 so retail buyers never see the wholesale form.
2. Field-level creation and layout
At the second level, you add and arrange individual fields inside the form.
- The editor supports drag-and-drop so you can stack or reorder fields like text inputs, selects, radios, checkboxes, swatches, date/time pickers, phone inputs, and plain text blocks anywhere in the layout.
- Each field has shared configuration options such as label, required/optional, placeholder, help text, and custom error message, giving you full control over UX and validation feedback.
Example – Simple “Gift message” section
- Add a checkbox “Add a gift message” (optional).
- Below it add a multi-line input text field configured as “Required only when visible”, with help text “We’ll print this message on the gift card.”
- Drag the message field to appear directly under the checkbox so the relationship is visually clear in checkout.
3. Supported field types and behavior
The form builder supports a wide range of field types so you can capture many different kinds of data.
- Input text: Single-line or multi-line (textarea-style) with optional character type restrictions such as “all characters” or “numbers only” for things like invoice numbers or short notes.
- Select dropdown, Radio, Checkbox group, Swatch choices: Define a choice list (values + labels) and let the customer pick one (radio/select/swatch) or multiple (checkbox/some swatch setups), ideal for options like “Delivery window”, “Packaging type”, or “Reason for purchase”.
- Phone number: Specialized input optimized for numeric entry and phone formatting, useful for delivery or support contact numbers.
- Plain text / description block: Non-interactive content you can drop anywhere in the form to explain policies, show instructions, or highlight legal notices.
Date, time and Date of birth
- Date / Date+Time fields support disabling specific days (for example Sundays), defining allowed date range “from” and “to”, and enabling time slots so you can implement “choose your delivery date and time” logic.
- Date of birth field adds built-in age validation: you can set a minimum required age (for example 18 or 21), and the form will block submission and show your configured error message if the calculated age is under the limit; leaving the minimum age blank turns it into a simple DOB capture with no enforcement.
Example – Delivery date & time selector
- Date field: Allowed range from today+2 days to today+14 days; disabled days set to Sunday and public holidays.
- Time slots: 10:00–13:00 and 14:00–18:00 only; customers must choose a slot that matches the chosen date’s availability.
- Stored to order attributes/metafields, so your operations team can see “Preferred delivery: 12 March, 10–13h” directly on the order.
4. Conditional display triggers (field-level logic)
Beyond form-level rules, each field can have its own display trigger based on the value of other fields in the same form.
- You can define rules like “show this field when dropdown X = ‘Other’” or “show this textarea when checkbox Y is checked”, enabling dynamic, interactive flows inside a single form.
- This “intra-form” logic keeps checkout clean by hiding advanced or optional questions until they are relevant, while still persisting all responses to the same order attributes/notes/metafields pipeline.
Example – Other option and gift message
- Dropdown “How did you hear about us?” with options: Google, Instagram, Friend, Other.
- Add a text field “Please specify” with display trigger: only show when dropdown value = “Other”.
- Checkbox “Add a gift message” with display trigger for a text area: only show when checkbox is checked; if visible and required, the form enforces message entry before letting the customer continue.
5. Data storage and page coverage (Checkout + Thank you)
All form submissions are written into Shopify using supported storage locations so they can be used after the order is created.
- Order attributes and notes allow staff to quickly see responses in the order details and can be consumed by other apps or workflows (for example via Flow or external integrations).
- Order metafields store more structured or long-term data that can be queried later through the Admin API, analytics tools, or support systems (for example survey answers, internal routing tags, extra compliance details).
Forms and fields work both on the main checkout steps and on the Thank you / Order status pages, letting you collect:
- Pre-purchase data such as delivery preferences, compliance confirmations, or age verification at checkout.
- Post-purchase data such as NPS scores, marketing surveys, “How was your experience?” questions, or referral information on the Thank you page without redirecting to an external survey tool