How Markets work in Kombiner
Summary
Markets in Kombiner combine country data with your organization’s settings to control what is allowed in each country. This affects orders, requests, and user interactions. In this article, we explain how Markets are structured and how they work in practice.
What is the structure of Markets?
Markets in Kombiner are built from two layers:
- Country data (global)
- Market settings (your organization)
The country layer includes basic information like name, region, and phone code.
The settings layer defines what is allowed in that country.
Where Markets are used
Markets influence multiple parts of the system:
- Orders and checkout
- Requests and quotes
- User onboarding and country selection
- Company and contact data
They act as a control layer across your platform.
How Markets work
The typical flow:
- Kombiner provides a list of countries
- You activate selected Markets
- You configure what is allowed per Market
- A user selects or is assigned a country
- Kombiner evaluates the Market settings
- The system allows or blocks actions
The result is behavior that adapts to each country.
How enforcement works
Markets do not behave the same in all cases:
- Orders → strongly enforced
- Checkout → evaluated with readiness checks
- Requests / quotes → partly controlled depending on setup
This means behavior can vary slightly depending on the flow.
Key concepts
Country data
Global information such as name, region, and phone code.
Market settings
Your organization’s rules for what is allowed.
Capabilities
Settings that define actions like:
- Allow orders
- Allow quotes
- Allow requests
Best practices for how Markets work
- Understand the difference between country and settings
- Test each Market before going live
- Keep rules consistent across countries
- Align Markets with real business operations
- Review behavior across different flows
Important notes
- Markets combine global data and local settings
- Enforcement varies depending on the action
- Some parts of the system rely on country names or codes
- Markets do not control all system behavior
- Data is always scoped to your organization
Common questions
Why do Markets behave differently across flows?
Because enforcement is stronger in some areas (like orders) than others.
Can I rely on Markets for full control?
Not completely, some features depend on additional setup.
What happens if country data is inconsistent?
It can lead to unexpected behavior across the system.