> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/forms/field-types.md).

# Field types

Vendor Space provides 17 field types to help you collect exactly the information you need from vendors. Each field type is designed for a specific kind of data, with built-in validation where appropriate.

## Input Fields

These fields collect data directly from the person filling out the form.

| Field Type   | Description                                       | Example Use                                  |
| ------------ | ------------------------------------------------- | -------------------------------------------- |
| **Text**     | A single-line text input for short answers.       | Company name, booth preference               |
| **Textarea** | A multi-line text area for longer responses.      | Product description, special requests        |
| **Email**    | A single-line input with email format validation. | Contact email address                        |
| **Phone**    | An input formatted for phone numbers.             | Business phone, mobile number                |
| **URL**      | An input with website URL validation.             | Company website, social media link           |
| **Number**   | A numeric-only input for quantities or amounts.   | Number of staff attending, years in business |

## Selection Fields

These fields let vendors choose from a predefined set of options that you configure.

| Field Type       | Description                                          | Example Use                             |
| ---------------- | ---------------------------------------------------- | --------------------------------------- |
| **Select**       | A dropdown menu where the vendor picks one option.   | Booth size preference, product category |
| **Multi Select** | A list where the vendor can choose multiple options. | Amenities needed, event dates attending |
| **Checkbox**     | A single yes/no toggle.                              | Agreement to terms, electricity needed  |
| **Radio**        | A group of options where only one can be selected.   | Payment preference, experience level    |

## File Fields

| Field Type      | Description                                             | Example Use                                             |
| --------------- | ------------------------------------------------------- | ------------------------------------------------------- |
| **File Upload** | Allows the vendor to attach a file to their submission. | Business license, product photos, insurance certificate |

## Date Fields

| Field Type | Description                                  | Example Use                               |
| ---------- | -------------------------------------------- | ----------------------------------------- |
| **Date**   | A date picker for selecting a specific date. | Preferred setup date, business start date |

## Advanced Fields

These specialized fields collect structured data that goes beyond simple text inputs.

| Field Type        | Description                                                | Example Use                                      |
| ----------------- | ---------------------------------------------------------- | ------------------------------------------------ |
| **Image Upload**  | Allows the vendor to upload an image with preview.         | Company logo, product photos, booth setup images |
| **Attendee List** | A multi-row table for listing people who will attend.      | Staff names, volunteer lists, team members       |
| **Social Links**  | Collects social media profile URLs in a structured format. | Instagram, Facebook, Twitter, website links      |

## Display Fields

These fields do not collect any data. They are used to organize and annotate your form for a better vendor experience.

| Field Type    | Description                                                     | Example Use                                                   |
| ------------- | --------------------------------------------------------------- | ------------------------------------------------------------- |
| **Heading**   | A section heading to break your form into logical groups.       | "Business Information", "Booth Preferences"                   |
| **Paragraph** | A block of descriptive text to provide context or instructions. | Explaining your booth assignment process, listing event rules |

> **Tip:** Use Heading and Paragraph fields generously to guide vendors through longer forms. A well-organized form with clear sections is easier to complete and leads to better quality submissions.

## Validation and Required Fields

* **Email**, **Phone**, **URL**, and **Number** fields include automatic format validation. If a vendor enters an invalid value, they will see a helpful error message before they can submit.
* Any input or selection field can be marked as **Required**, meaning the vendor must complete it before submitting the form.
* Display fields (Heading and Paragraph) cannot be marked as required since they do not collect data.

> **Tip:** Only mark fields as required when you truly need the information. Optional fields give vendors flexibility and can reduce form abandonment.