How Custom Field data is stored and used

Summary

Custom Field data in Kombiner is stored directly on each item, such as products or companies, while the field itself is defined centrally. This allows you to reuse the same field across many items. In this article, we explain how Custom Field data is stored and how it is used across the platform.

What does it mean that data is stored per item?

In Kombiner, Custom Fields are defined once, but their values are stored individually on each item.

This means:

• The field structure is shared
• The data is stored separately per product, company, or request

Example:

You create a field called “Material”

• Product A → “Steel”
• Product B → “Wood”

Each item stores its own value, even though they use the same field.

Where Custom Field data is stored

Custom Field values are stored as part of each item’s data.

This applies to:

• Products
• Options
• Categories
• Companies
• Requests

The data is saved together with the item, which means it follows the item wherever it is used.

How Custom Field data is stored and used

The typical flow:

1. You create a Custom Field
2. Kombiner makes it available in a specific area
3. You add values to individual items
4. The data is stored with each item
5. The data can be displayed or used across the platform

The result is a flexible and reusable data structure.

How the system uses the data

Once stored, Custom Field data can be used to:

• Display additional information on pages
• Support internal workflows
• Store imported data from integrations
• Enrich products, companies, and requests

The system reads the stored values whenever the item is loaded.

Key concepts

Stored per item

Each item has its own Custom Field values.

Shared structure

The field definition connects all values across items.

Reusable data

The same field can be used across many items and contexts.

Best practices for storing and using data

• Use consistent values across items
• Avoid mixing different types of data in one field
• Keep field definitions stable once in use
• Test how data appears before scaling
• Use structured types for better consistency

Important notes

• Data is always stored within your organization
• Each item stores its own values independently
• Changing a field definition can affect how data is used
• Data is not automatically validated in all cases
• Some system features may use Custom Field data differently

Common questions

Is Custom Field data shared between items?

No, each item stores its own value.

What happens if I change a field?

It may affect how the stored data is displayed or used.

Can I access this data across the system?

Yes, the data is available wherever the item is used.

‍