What are Custom Fields in Kombiner?

Summary

Custom Fields in Kombiner allow you to add structured data to products, companies, requests, and more. This helps you tailor the platform to your specific business needs without changing the core setup. In this article, we explain what Custom Fields are and how they are used.

What are Custom Fields?

Custom Fields are used to store additional information on top of your standard data in Kombiner.

You can find them under Content → Custom Fields, and they can be applied to different areas such as products, options, categories, companies, and requests.

Unlike standard fields like product name or price, Custom Fields are flexible and defined by your organization. This means you decide what data to store.

Examples:

• A product manual link
• A company VAT number
• A request priority flag
• A product specification value

Each Custom Field consists of:

• A field definition (what the field is)
• A field value (the data stored on each item)

When should I use Custom Fields?

You should use Custom Fields when:

• You need to store additional data not included in standard fields
• You want to tailor Kombiner to your internal workflows
• You are importing data from external systems
• You need structured data instead of free text
• You want to enrich products, companies, or requests

How Custom Fields work

The typical flow:

1. You create a Custom Field
2. You assign it to a specific area (e.g. Products)
3. The field becomes available on relevant pages
4. You add values to each item
5. The data is stored and used across the platform

The result is a flexible data layer that extends your existing setup.

Key concepts

Field definition

This defines the structure of the field (name, type, and where it applies).

Field value

This is the actual data stored on each product, company, or request.

Best practices for Custom Fields

• Use clear and consistent naming
• Keep fields focused on a single purpose
• Avoid creating duplicate fields
• Plan your structure before adding many fields
• Use structured types instead of free text when possible

Important notes

• Custom Fields only apply within your organization
• Changes to a field can affect all existing data
• Different areas (products, companies, etc.) may display fields differently
• Not all fields are validated automatically
• Some features depend on how fields are configured

Common questions

Can I edit a Custom Field after creating it?

Yes, but changes may affect existing data using that field.

Are Custom Fields shared across organizations?

No, they are only available within your own organization.

Can I use Custom Fields for pricing or logic?

No, Custom Fields are designed for storing data, not controlling core system behavior.

‍