Tags vs. custom attributes — which should I use?

DigitBridge offers two powerful tools for organizing and classifying your product data: tags and custom attributes. While they may seem similar, they serve very different purposes depending on your use case.

Here’s a breakdown of how to decide which one is right for you:

Tags

Tags are flexible, non-structured labels that you can apply to products for temporary, campaign-based, or high-level grouping.

Use tags when:

• You want to quickly group products for a short-term initiative (e.g., Fall 2025 Launch, Clearance, Sample Pack)

• You need to mark items for internal reference (e.g., Needs Review, Missing Photos)

• You want lightweight, optional categorization that doesn’t require field mapping or values

• You want to allow broader, overlapping categories without enforcing data structure

Tags can be created freely in ERP under System Code Entry > Tags, then applied to items via the Product Management screen. How do I create product tags in ERP? How do I add tags to items in ERP?

Pros:
✔ Easy to create and apply
✔ Great for bulk filtering and short-term organization
✔ No rigid structure or required values

Cons:
✖ Not reportable as structured data fields
✖ No field validation
✖ Cannot be used in integrations

Custom attributes

Custom attributes are structured, field-based values that are permanently tied to your product records. Each attribute is defined with a name and value set (e.g., Fabric Type = Organic Cotton, Launch Season = SS24).

Use custom attributes when:

• You need structured data for analytics, reporting, or downstream integrations

• You want to enforce consistency in product classification

• You plan to use the data in workflows (e.g., pricing rules, vendor exports, or customer portal filters)

• You’re managing long-term data (e.g., Product Line, Core vs Seasonal, Compliance Category)

Attributes are created under Admin Tools > Custom Attributes, and can then be assigned to products on the Product Management screen. How can I create custom attributes? How do I use custom attributes in DigitBridge?

Pros:
✔ Structured and reportable
✔ Supports advanced logic and integrations
✔ Great for long-term metadata

Cons:
✖ More setup time required
✖ Less flexible — better suited for permanent or semi-permanent data

Quick comparison:

Still not sure which to use?

Ask yourself:

• Do I need this data for reporting, logic, or integrations? → Use a custom attribute

• Do I just need a quick way to group items for a short-term filter or campaign? → Use a tag