The difference between single-select and tag fields for categorizing vendors and customers
The single-select field in Jestor lets you choose only one value per record — like a vendor's status —, while the tags field lets you assign more than one characteristic to the same record, like marking a vendor as both recurring and international at once.
Airtable, with single select and multi-select, and Notion, with select and multi-select, make this same distinction, but that's where Jestor stands out: the practical difference lies in how Jestor connects this field to card conditionals, automation, and permissions.
Why does telling single-select apart from tags matter?
Using the wrong field type — forcing a tag where there should be a single-select, or the opposite — makes reports and filters less reliable.
How to choose between single-select and tags in Jestor?
- Single-select field: works for mutually exclusive attributes — a vendor is active, inactive, or blocked, never two at once.
- Tags field: works for characteristics that can coexist — the same vendor can be recurring and international at the same time.
- A single-select field can be marked as required when the process requires every record to have a defined status.
- A tags field is usually left optional.
- Single-select fields used in a kanban also bring extra log metrics, like how long a card sits in a given stage.
| Field type | How many values per record | Example |
|---|---|---|
| Single-select | Only one | Status: active, inactive, or blocked |
| Tags | Several at once | Recurring + international |
To configure the right categorization field:
- Add a column.
- Choose "single-select" for status, stage, or any mutually exclusive attribute, or "tags" for characteristics that can add up.
- Define the options, colors, and whether the field is required.
Why choose Jestor to categorize vendors and customers?
Clearly separating these two field types avoids the common mistake of forcing a tag where a single-select should be, keeping reports and filters more reliable.
Frequently asked questions
Can a vendor have two tags at the same time?
Yes, tags accept multiple selections on the same record.
Does a single-select field accept more than one selected value?
No, by definition it only accepts one option at a time.
Can a vendor table become a table for another entity, like customers?
Yes, the field structure works for any entity that needs registration and categorization.
Can the single-select field be required while the tag field isn't?
Yes, this can be set separately for each field, based on the process's needs.
Reference video
Check out the Jestor YouTube channel for more content like this.
Discover Jestor
With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.