When should I use Custom Fields?

Summary

Custom Fields in Kombiner are useful when you need to store additional structured data that is not part of the standard setup. They help you adapt the platform to your workflows and integrations. In this article, we explain when Custom Fields are the right choice.

What does this mean in practice?

Kombiner already includes standard fields such as names, prices, and descriptions. Custom Fields are used when you need to go beyond this.

They allow you to extend your data model without changing the core system.

Examples:

• Adding technical specifications to products
• Storing ERP-related data on companies
• Adding internal notes or flags to requests

When should I use Custom Fields?

You should use Custom Fields when:

• You need to store additional structured data
• You are importing data from systems like Shopify or ERP
• You want consistent data across many items
• You need fields that are reusable across your organization
• You want to support internal workflows with extra data

When should I NOT use Custom Fields?

You should avoid using Custom Fields when:

• You are defining core product data like price or SKU
• You need to control system logic or pricing rules
• You are managing workflow states (e.g. order status)
• The data is critical for system behavior
• You need strict validation or required fields

In these cases, standard fields or system features should be used instead.

How Custom Fields work in decision-making

The typical flow:

1. You identify missing data in your workflow
2. You create a Custom Field to capture it
3. You apply it to the relevant area
4. You start using it across your data

The result is a more tailored and structured setup.

Best practices for choosing Custom Fields

• Only create fields when necessary
• Prefer structured fields over free text
• Reuse existing fields when possible
• Keep naming consistent across teams
• Think about long-term usage before creating fields

Important notes

• Custom Fields are flexible but not strictly enforced
• Data quality depends on how fields are used
• Some integrations may create fields automatically
• Overuse can make your data harder to manage

Common questions

Should I create a new field or reuse an existing one?

Always reuse existing fields when possible to keep your data consistent.

Can Custom Fields replace standard fields?

No, standard fields should always be used for core data.

What happens if I create too many fields?

It can make your system harder to manage and reduce data clarity.

‍