How Markets control orders, quotes, and requests
Summary
Markets in Kombiner control what users can do in each country, but not all actions are enforced in the same way. Orders are typically enforced strictly, while quotes and requests may depend on your setup. In this article, we explain how Markets affect different flows.
What does this mean in practice?
Markets define what actions are allowed in each country, such as:
- Placing orders
- Requesting quotes
- Submitting forms
However, the system does not enforce all actions equally.
When should I understand this?
You should understand this when:
- Setting up Markets
- Troubleshooting unexpected behavior
- Launching in new countries
- Managing international availability
- Supporting users across regions
How Markets control different flows
Orders (strong enforcement)
Orders are the most strictly controlled by Markets.
- Orders can be blocked if not allowed
- Checkout evaluates Market readiness
- Backend logic enforces rules
This makes order behavior reliable and predictable.
Checkout (readiness checks)
Checkout may evaluate whether a Market is ready.
- Missing setup can block or warn
- Behavior depends on configuration
- Readiness plays an important role
Quotes and requests (partial enforcement)
Quotes and requests are less strictly enforced.
- Often controlled in the interface
- May depend on frontend setup
- Not always enforced the same way everywhere
This can lead to differences between expected and actual behavior.
How it works
The typical flow:
- A user selects or is assigned a country
- Kombiner identifies the Market
- Market settings are evaluated
- The system determines what is allowed
- The user sees the result
The outcome depends on both settings and flow type.
Key concepts
Strong enforcement
Orders are enforced directly by the system.
Partial enforcement
Quotes and requests may depend on setup and interface logic.
Readiness
Some actions depend on whether the Market is fully configured.
Best practices for controlling flows
- Always test Markets across all flows
- Do not assume all actions behave the same
- Validate both frontend and backend behavior
- Keep rules simple and predictable
- Document expected behavior for your team
Important notes
- Orders are the most reliable enforcement point
- Quotes and requests may behave differently
- Some features depend on frontend implementation
- Market readiness can affect checkout behavior
- Misalignment can cause confusion for users
Common questions
Why can users submit requests in a disabled Market?
Because request behavior may not always be strictly enforced.
Can I rely on Markets to block all actions?
Not fully, enforcement depends on the flow.
What is the safest way to control availability?
Use Markets together with proper testing across all flows.