Component Custom Fields
The Custom Fields section allows you to capture additional information tailored to your unique business needs. This feature provides the flexibility to add specialised data to your components without altering the core system.

Custom Fields are used to collect extra, component-specific information beyond the standard fields. They are defined in Site Settings and, once configured, will automatically appear in the Custom Fields section of every component.
This is particularly useful for tracking unique data points such as supplier preferences, testing requirements, internal codes, or project-specific categorisations.
Field Types
These field types determine how users enter and select data for each custom field.
| Feature | Description |
|---|---|
| Dropdown | Allows users to select a single value from a predefined list. |
| Multiselect Dropdown | Enables the selection of multiple values, useful for tagging or categorising components under several attributes. |
| Date | Accepts a valid calendar date, ideal for tracking deadlines such as test due dates or expected deliveries. |
| Text | A free-form text field, suitable for notes, reference codes, or other descriptive information. |
Admin Configuration Required
Custom fields must be created and managed from Site Settings > Component > Custom Fields. Administrators define the field label, type, and available options (where applicable). Once saved, they are instantly available across all component records.
Important Notes When Using Custom Fields
Admin Setup Required: All custom fields must be defined in Site Settings > Component > Custom Fields before they appear on component records. Ensure your field list is configured correctly before users begin capturing data.
Plan Before Creating: Before adding new custom fields in Site Settings, map out exactly what information you need to capture. This helps you avoid creating duplicate or unnecessary fields, keeping your component details clean and focused.
Best Practices
Use Dropdowns for Standardised Data: For data that needs to be consistent for reporting, such as 'fabric composition' or 'sustainability certifications', always use the Dropdown or Multiselect Dropdown field types. This prevents typos and variations (e.g., "Cotton" vs. "cotton"), ensuring your data is reliable and easy to filter.
Keep Labels Clear and Concise: When naming your custom fields, use clear and straightforward labels. A good label should make it immediately obvious what information needs to be entered. For example, instead of a generic label like "Details," use something more specific such as "Care Instructions" or "Supplier Reference."