Managing Fields and Properties

Fields and properties define how product data is structured and enriched in Hypotenuse AI's Product Database. Fields store essential product information, while properties define how each field behaves when enriching or displaying data. Understanding these concepts will help you manage and optimize your product database effectively.

In this article

1. What are fields?
2. Understanding field properties
3. Managing fields
   1. Creating a new field
   2. Editing a field
   3. Deleting fields
   4. Reordering fields
4. Field datatypes
   1. Short text
   2. Long text
   3. Single select
   4. Multi select
   5. Numbers

What are fields?

Fields represent product attributes in your database, appearing as column headers. Each field stores specific types of product data, such as names, descriptions, prices, or tags.

Understanding field properties

Field properties define how each field should behave during enrichment and display. Properties also help the AI understand and standardize data for better consistency. Key field properties include:

• Datatype: Defines the kind of data a field holds (e.g., text, numbers, tags)
• Units: Specifies measurement units where applicable (e.g., cm, kg, USD)
• Definition: Provides a clear explanation of the field’s purpose
• Guidelines: Establishes rules for formatting and enrichment

Managing fields

Creating a new field

You can add a new field through:

1. Display Settings – Navigate to the display settings in the top right of the product database and click New Custom Field

2. During Import – When importing data, you can define a new field and specify its datatype

Note: The datatype of a field must be set when creating it and cannot be changed later

Editing a field

You can modify field properties but not the datatype. To edit a field:

1. Display settings – In the Display settings window, select the pencil icon next to the field you want to edit

2. Field headers – Click on the field headers on the database directly and select Edit properties to adjust its properties

Deleting fields

To delete a field in your database: 

1. Display settings – Select the pencil icon and then Delete 

Reordering fields

To change the order of fields in your database:

1. Display settings – Drag and drop the field header to a new position
2. Hiding a field – click on the eye icon

Field datatypes

Each field has a specific datatype, which determines how data is stored and structured, as well as how it should appear when enriched

(1) Short text

Short text fields store small, unstructured snippets of text that are typically only a few words long.

✅ Best for:

• Product titles and model numbers – Simple descriptors that don’t require additional formatting
• Brand names and proper nouns – A concise way to store single-word identifiers
• Dimensions or measurements without units – Use this when numerical values require special characters, ranges, or formatting beyond simple digits. For example, measurements with hyphens (e.g., "42-inch"), voltage ranges (e.g., "230V - 350V")

❌ Avoid using Short Text when:

• The field requires long descriptions (use Long Text instead)
• The data needs structured selection from a predefined list (use Single tag or Multi tags)

(2) Long text

Long text fields are used for storing more detailed and structured content, such as descriptions, specifications, or bullet-point lists

✅ Best for:

• Product descriptions – Detailed text that goes beyond a few words
• Key features or bullet points – Where multiple points need to be listed in one field
• Internal notes or extended metadata – Text that requires explanation rather than classification

❌ Avoid using Long Text when:

• The content needs predefined categories or standardization (use Single tag instead)
• The field should contain short, structured attributes (use Short Text)

(3) Single tags

Single tag fields restrict a field to one predefined value, ensuring consistency across entries.

✅ Best for:

• Attributes that have only one valid selection per product (e.g., size, country of manufacture, warranty type)
  • Example: A “Size” field using Single tag allows choosing only Small, Medium, or Large—preventing inconsistencies like “M” vs. “Med” vs. “Medium”
• Classifications where values do not overlap (e.g., a product can be either New or Used, but not both)

❌ Avoid using Single Tag when:

• A product can belong to multiple categories at the same time (use Multi Tags instead).
• There is no strict need for predefined values (use Short Text for free input).

(4) Multi tags

Multi tag fields allow a product to have multiple values from a predefined list or free-form text.

✅ Best for:

• Attributes where multiple values may apply (e.g., colors, features, compatible devices).
• Flexible keyword tagging (e.g., SEO metadata, product categories).

❌ Avoid using Multi tags when:

• A product should only have one definitive value (use Single tag instead).

(5) Numbers

Numbers fields store numerical data and can include unit selections for standardization.

✅ Best for:

• Measurements and quantities (e.g., weight, voltage, dimensions).
• Pricing and numerical attributes (e.g., discounts, ratings, energy efficiency).

❌ Avoid using Numbers when:

• The field represents categorical values rather than numerical ones (use Single tag or Short Text).
• The number needs additional metadata or descriptors (use Short Text for labels like “42-inch TV”).

With this information you should be able to map and edit your field properties like a pro!

Next, learn about how you can use guidelines to shape the enrichment values of each datatype.

If you need further support, please reach out to support@hypotenuse.ai and a member of our team would be more than happy to assist you!