How Custom Fields work with integrations (Shopify & ERP)
Summary
Custom Fields in Kombiner can be created and populated through integrations such as Shopify and ERP systems. This allows external data to be stored and used directly within your platform. In this article, we explain how Custom Fields interact with integrations and what to be aware of.
What does this mean in practice?
Custom Fields are not only created manually. They can also be:
- Created automatically by integrations
- Populated with external data
- Updated during sync processes
This makes Custom Fields a central layer for storing integration data.
Examples:
- Shopify product attributes
- ERP company data
- External references or identifiers
When should I use Custom Fields with integrations?
You should use Custom Fields with integrations when:
- You are syncing product data from Shopify
- You are importing company data from an ERP system
- You need to store external attributes not in standard fields
- You want to extend imported data without changing core structure
- You need a consistent place for integration data
How Custom Fields work with integrations
The typical flow:
- An integration connects to Kombiner
- Data is imported from the external system
- Custom Fields are created or matched
- Values are stored on products, companies, or other items
- The data becomes available in Kombiner
The result is structured external data inside your platform.
Key concepts
Integration-created fields
Some fields are created automatically when data is synced.
Synced values
Values may be updated when integrations run again.
Manual vs integration fields
Fields can be:
- Created manually
- Created by integrations
Both behave similarly, but may have different sources.
Best practices for integrations and Custom Fields
- Avoid manually editing fields managed by integrations
- Keep naming consistent between systems
- Review fields created during imports
- Use Custom Fields for external data, not core logic
- Monitor how data changes during sync
Important notes
- Integration data may overwrite existing values
- Some fields are controlled by external systems
- Not all integrations behave the same way
- Field names and structure may come from external sources
- Data is still scoped to your organization
Common questions
Can I edit fields created by integrations?
Yes, but changes may be overwritten during the next sync.
What happens if I delete an integration field?
It may be recreated when the integration runs again.
Are integration fields different from manual fields?
They behave similarly, but may be controlled externally.