Renaming Order Tag Filters for Improved Usability
Use Case
Author:
Yulia Andreyanova
Changed on:
2 Dec 2025
Problem
Order tags (`tag1`, `tag2`, `tag3`) are used for business-level categorization - such as brand, region, sales channel, or internal operational grouping. However, these technical tag names are not meaningful to end users and do not communicate what each tag represents.Because the labels do not accurately reflect their intended business purpose, users often experience confusion. This leads to several issues:- Users must rely on internal training or memorised mappings to interpret tag meanings
- Filtering accuracy depends on each person remembering the correct purpose of each tag (e.g., “tag1 = Brand”, “tag2 = Region”)
- The UI displays technical labels that do not align with the organisation’s terminology or operational language
Example
Consider EverFresh Foods, a large organic food distributor in the United States that supplies national and regional retailers such as Whole Foods, Sprouts, and local grocery chains.EverFresh relies on several external characteristics to classify and filter orders in their internal system:
- Brand - EverFresh, GreenLeaf, NatureBoost
- Region - West Coast, Midwest, Northeast, Southeast
- Sales Channel - Retail, E-commerce, Food Service
- Customer Tier - National Account, Regional Chain, Independent Store
- The sales team analyzes orders by Sales Channel.
- Logistics teams plan distribution routes based on Region.
- Category managers track performance by Brand.
- tag1 = Brand
- tag2 = Region
- tag3 = Sales Channel
- Logistics may group orders by the wrong region
- Analysts waste time trying to “decode” tags
- The UI shows terminology that does not match the company’s actual business language
- Operational errors directly impact delivery planning and reporting
Solution Overview
To make order filtering intuitive and aligned with business terminology, Fluent now supports renaming tag filters so that they reflect their true meaning.There are two ways to implement this:1. Screen-Specific Renaming
Using the`filter.overrides` section in the `fc.list` component, teams can rename tag filters only on specific pages where clarity is required.This option is ideal when different teams or workflows utilize tags in varying ways.2. System-Wide Renaming
If a tag has a consistent meaning everywhere (e.g.,`tag2` always means Brand), you can apply a translation-based label update.This updates the label across all screens automatically - filters, drawers, cards, and lists.Benefits
- Users see meaningful, business-oriented labels instead of technical ones
- Filtering becomes faster, clearer, and less error-prone
- Training requirements decrease significantly
- The UI aligns with business terminology, improving adoption and usability
- You can choose between system-wide consistency or screen-specific customization
