When should I use Markets in Kombiner?

Summary

Markets in Kombiner are used when you need to control where your business operates and what users can do in each country. They help you manage international setups and restrict actions based on location. In this article, we explain when Markets are the right tool.

What does this mean in practice?

Markets allow you to define how your business behaves in different countries.

Instead of having the same setup everywhere, you can control access and functionality based on location.

Examples:

  • Only allow orders in selected countries
  • Allow quotes in some countries but not others
  • Limit availability during rollout

When should I use Markets?

You should use Markets when:

  • You want to restrict sales to specific countries
  • You need different rules for orders and requests per country
  • You are expanding into new markets gradually
  • You need country-based control in your storefront
  • You want structured country selection for users

When should I NOT use Markets?

You should avoid using Markets when:

  • You are controlling pricing or currency
  • You are managing product logic or configuration
  • You are defining internal workflows
  • You need detailed regional pricing rules
  • You are managing taxes or shipping logic directly

Markets are designed for availability and access, not full business logic.

How Markets support decision-making

The typical flow:

  1. You define which countries you operate in
  2. You configure allowed actions per country
  3. Users interact with your system based on their location
  4. Kombiner controls what is available

The result is a structured and controlled international setup.

Best practices for using Markets

  • Start with a small number of countries
  • Clearly define what is allowed per country
  • Align Markets with your business operations
  • Keep rules simple and easy to understand
  • Review settings regularly as you expand

Important notes

  • Markets are not a full rule engine
  • Behavior may differ between orders, quotes, and requests
  • Some features are enforced more strictly than others
  • Markets depend on correct country data
  • Overcomplicating setup can create confusion

Common questions

Should I use Markets for pricing differences?

No, pricing is handled separately.

Can I use Markets for rollout?

Yes, they are useful for gradually enabling countries.

Do Markets affect all users automatically?

They apply based on how country is selected or assigned.