> ## Documentation Index
> Fetch the complete documentation index at: https://docs.solya.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Business Center

> Configure the business rules that guard your plans — block or warn when a policy is breached.

The **Business Center** is where you define the business policies Solya enforces
across your plans. Its core feature is **business-logic rules**: configurable
constraints that Solya evaluates *before* plan operations — adding an item, validating
a plan, or submitting it for approval — so your decisions stay within your policies.

## Rules and rulesets

* A **rule** is a single constraint (for example, *"a rebalance plan can't exceed
  €50,000"* or *"no more than 20 items per shop"*).
* A **ruleset** is a named group of rules. You can apply a ruleset to a specific plan,
  and one ruleset is your organization's **default** — used whenever a plan doesn't
  specify another.

A rule can belong to several rulesets, and a ruleset contains many rules.

## Enforcement modes

When a rule is triggered, its **enforcement mode** decides what happens:

<CardGroup cols={3}>
  <Card title="Block" icon="ban">
    Prevents the action entirely — the item can't be added, or the plan can't be
    validated.
  </Card>

  <Card title="Warn" icon="triangle-exclamation">
    Allows the action but shows a warning so the user can decide knowingly.
  </Card>

  <Card title="Log" icon="file-lines">
    Silently records that the rule fired — no interruption to the user.
  </Card>
</CardGroup>

## What a rule covers

* **Category** — the domain it belongs to (capacity, assortment, ordering, transfer,
  pricing, distribution, compliance).
* **Condition** — the logic being tested (a threshold, metric, or value).
* **Scope** — which products, shops, brands, suppliers, or taxonomies it applies to.
* **Plan types** — which plans it guards: restock, rebalance, markdown, pre-season,
  supplier return, and supplier exchange.
* **When it fires** — the moment in the workflow it is checked (e.g. before adding an
  item, before validating an item, before changing a plan's status, or before
  generating a recommendation).
* **Violation message** — the custom message shown when the rule triggers.
* **Priority** — the order in which rules are evaluated.

## Rule templates

Solya ships a catalog of ready-made templates you can instantiate and tune, including:

* **Max plan value** — cap the total value of a plan.
* **Max plan quantity** — cap the total number of items.
* **Max items per shop** — limit items per location.
* **Max quantity per variant** — limit the quantity for a single product variant.
* **Max plan value per brand** — cap value per brand within a plan.
* **Budget (OTB) envelopes** — keep spending within allocated budgets.
* **Size-curve rules** — enforce size-distribution policies.
* **Markdown-calendar rules** — prevent conflicting markdowns.
* **Supplier & return/exchange rules** — enforce supplier constraints and return windows.

## Working in the Business Center

<Steps>
  <Step title="Open the Business Center">
    Go to **Intelligence layer → Business Center** to see your rulesets and rules.
  </Step>

  <Step title="Create a ruleset">
    Create a named ruleset (for example *"Strict Q4"*), optionally starting from your
    default rules.
  </Step>

  <Step title="Add a rule">
    Use the rule wizard: pick a template (or start from scratch), set the condition
    (e.g. a €50,000 threshold), choose the scope, and select **Block** or **Warn**.
  </Step>

  <Step title="Set your default ruleset">
    Mark one ruleset as the organization default so it applies wherever a plan doesn't
    specify another.
  </Step>

  <Step title="See rules in action">
    As you build plans, blocks and warnings appear directly in the plan's validation
    panel, with the message you configured.
  </Step>
</Steps>

<Note>
  Rules evaluate the data Solya holds about your inventory — much of which comes from
  the [data layer](/en/data-layer/overview). Keeping ingestion healthy keeps rule
  evaluation accurate.
</Note>