Where can Custom Fields be used in Kombiner?

Summary

Custom Fields in Kombiner can be applied to multiple areas such as products, companies, and requests. This allows you to extend your data across different parts of the platform. In this article, we explain where Custom Fields can be used and what they affect.

Where can Custom Fields be used?

When creating a Custom Field, you choose where it should apply. This determines where the field appears and where values can be added.

Custom Fields can be used in:

  • Products
  • Options
  • Categories
  • Companies
  • Requests

Each area uses Custom Fields slightly differently depending on its purpose.

What does “Applies to” mean?

“Applies to” defines which type of data the field is attached to.

For example:

  • A field applied to Products will appear on product pages
  • A field applied to Companies will appear on company records
  • A field applied to Requests will appear in request management

This ensures that fields are only shown where they are relevant.

How Custom Fields work across areas

The typical flow:

  1. You create a field and select where it applies
  2. Kombiner makes the field available in that area
  3. You add values to individual items
  4. The data is stored with each item
  5. The field can be used across the platform

The result is structured data across multiple parts of your system.

Key concepts

Product Custom Fields

Used to store product-specific data such as:

  • Specifications
  • Documents
  • External references

Option and Category Custom Fields

Used to enrich configuration data:

  • Option descriptions
  • Category-specific attributes

Company Custom Fields

Used for commercial or operational data:

  • VAT numbers
  • ERP data
  • Customer-specific attributes

Request Custom Fields

Used for internal workflows:

  • Priority
  • Internal notes
  • Status-related data

Best practices for using Custom Fields across areas

  • Choose the correct area before creating the field
  • Avoid duplicating the same field across multiple areas
  • Keep field usage consistent within each area
  • Use clear naming that reflects where the field is used
  • Plan your structure before scaling

Important notes

  • A field can only apply to one area at a time
  • Fields are not automatically shared across areas
  • Each area may display or handle fields differently
  • Some areas may have different input behavior (e.g. file uploads)
  • Data is always scoped to your organization

Common questions

Can I use the same field on products and companies?

No, you need to create separate fields for each area.

What happens if I choose the wrong area?

You will need to create a new field and migrate your data manually.

Do Custom Fields behave the same in all areas?

Not always, some areas may handle inputs and display differently.