> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/trade/concepts/odds-logic.md).

# Odds Logic: Benchmark and Model

How TRADE prices your markets, the difference between Benchmark and Model, and how to set up Model in Odds Settings

Odds Logic decides how TRADE prices the markets you receive. You choose it per league or per fixture in Odds Settings. There are two options, **Benchmark** and **Model**. Each one supports a different pricing strategy.

{% hint style="warning" %}
**Model is in beta.** It is available for Football and American Football PreMatch. To join the beta, contact your CSM.
{% endhint %}

## Benchmark and Model at a glance

Benchmark prices each market on its own, against the providers you choose. Model prices a whole group of related markets from one calculation, so those markets always agree with each other.

|                                 | **Benchmark**                                                                                  | **Model**                                                                                             |
| ------------------------------- | ---------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **How a market is priced**      | Each market is priced on its own, from the provider list you set for it                        | A few main markets feed the LSports Odds Model. Every other market in the group is calculated from it |
| **Consistency between markets** | Related markets can drift apart when they come from different providers                        | Related markets are mathematically consistent by design                                               |
| **What you configure**          | Settings for every market                                                                      | Settings for a market group. Individual markets can still be adjusted                                 |
| **Market coverage**             | A market is offered only when your providers cover it                                          | Calculated markets don't need provider coverage of their own                                          |
| **Best for**                    | Pricing against specific competitors, or staying aligned with a named provider on key fixtures | Consistent prices across related markets and wide coverage with less configuration                    |
| **Available at**                | Every level: sport, location, league, fixture                                                  | League and fixture level, on supported leagues                                                        |

Neither option is a fallback. Benchmark is the right choice when you want to follow named providers. Model is the right choice when consistency and coverage matter most.

## Benchmark

Benchmark is the way TRADE has always priced markets. For every market you choose a provider list, a margin, and the rest of your odds settings. TRADE aggregates the odds from the providers on the list, applies your margin, and publishes the market.

Because every market is priced independently, two related markets can come from different providers. For example, 1X2 can follow one provider while Double Chance follows another. Small differences between them can create **internal arbitrage**: a bettor combines selections across markets and locks in a profit against your sportsbook. Benchmark mode shows a reminder about this risk at the top of Odds Settings.

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-6d0b0ff347ab3a2c891a5e4635ca8884915dce0b%2Fodds-logic-benchmark-view.png?alt=media" alt="Odds Settings in Benchmark mode, with one row of settings per market"><figcaption><p>Benchmark: every market has its own provider list and settings</p></figcaption></figure>

For full configuration instructions, see the [Odds Settings user guide](https://docs.lsports.eu/u/trade/user-guide/booking-events-and-odds-settings/odds-settings.md).

## Model

Model removes the drift between related markets. TRADE groups markets that describe the same incident in the same period, for example *Goals FT* or *Corners 1st H*. Inside each group, a small set of **main markets** feeds the LSports Odds Model. Every other market in the group is a **derived market**, calculated from the same model output. Since every derived market comes from one source, the prices can't contradict each other. Double Chance always agrees with the 1X2 it is built from, and Both Teams To Score always agrees with Correct Score.

### Key terms

These terms appear in Odds Settings when you use Model.

| Term               | Meaning                                                                                               |
| ------------------ | ----------------------------------------------------------------------------------------------------- |
| **Market group**   | All markets for one incident in one period, such as Goals FT or Corners 1st H                         |
| **Main market**    | An input market of the group. For football goals: 1X2 and Under/Over. Shown with the **Source** state |
| **Derived market** | Any other market in the group, calculated by the model. Shown with the **Linked** state               |
| **Linked**         | The derived market follows the group and receives fair odds from the model                            |
| **Unlinked**       | The derived market was given its own provider list. It is priced on its own, the Benchmark way        |

### How Model calculates odds

Model follows the same path for every group:

1. **Collect the main markets.** TRADE takes the main-market odds from the group's provider list and cleans them, exactly as it does for any market today.
2. **Remove the margin.** Provider odds include the bookmaker's margin. The model converts them to fair probabilities first, so it works with real probabilities and not with someone else's margin.
3. **Fit the model.** The model finds the expected outcome of the fixture (for football: how many goals each team is expected to score) that reproduces the main-market prices.
4. **Derive every market.** Each derived market is calculated from that one fitted result. Over 3.5, Asian Handicap, Both Teams To Score and Correct Score all read from the same source.
5. **Apply your settings.** Your margin, min-max odds and odds ladder are applied to each market, and each market is published to your feed as usual.

Derived markets move only when the main markets move. If a provider updates a derived market directly, Model ignores that update.

## Setting up Model in Odds Settings

### Choose the Odds Logic

Open **Odds Settings** for a league or fixture from **Fixture Ordering** or the **Trading Floor**. Use the switch at the top to choose **Benchmark** or **Model**.

* Model is available at **league and fixture level only**. At sport and location level, only Benchmark is available.
* Model is available only for **supported leagues**. Leagues that aren't supported (for example, eFootball leagues inside Football) stay on Benchmark.
* Switching between Benchmark and Model starts from a clean slate. Settings from one mode don't carry over to the other.

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-1b62eade570468d6a4650837f815a4499ff95027%2Fodds-logic-model-overview.png?alt=media" alt="Odds Settings in Model mode for the England Premier League, showing market groups on the left and groups by period on the right"><figcaption><p>Model: market groups on the left, each group by period on the right with its Offered count</p></figcaption></figure>

The screen has two parts:

* **Market groups (left):** each group, such as Goals, Corners or Fouls, with its number of offered markets. Select a group to configure it.
* **Groups by period (right):** each group per period (1st H, 2nd H, FT, FT After OT) with an Offered toggle and count. Expand a row to see its main and derived markets. Groups the model doesn't cover yet are listed as **Unsupported** and priced the Benchmark way.

### Main and derived markets

Expand a group to see its markets. Main markets appear at the top with the **Source** state. Derived markets appear below with the **Linked** state.

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-e4420e7f99156bf7dd74d18c430a54670493af95%2Fodds-logic-main-and-derived-markets.png?alt=media" alt="The Goals FT group expanded, with 1X2 and Under/Over as main markets and derived markets marked Linked"><figcaption><p>Goals FT: 1X2 and Under/Over feed the model, and every derived market is Linked</p></figcaption></figure>

* Main markets stay **Offered** while their group is on, because the model needs them. You can still edit their margin and provider list.
* Turning a group on includes all its main and derived markets. No extra activation step is needed.
* Offering a derived market while its group is off turns the group on, together with its main markets.

### Configure a market group

Select a group on the left to open its settings. Choose **All periods** (recommended) to apply one configuration to every period, or **Period-specific** to set each period on its own.

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-8cc50f3a0e131c65c3d0b095954887103e715ebd%2Fodds-logic-group-configuration.png?alt=media" alt="Goals group configuration panel with Configuration level, Configurations and Provider List tabs"><figcaption><p>Group configuration: one set of settings for the whole group</p></figcaption></figure>

The **Configurations** tab holds the settings you already know from Benchmark: Margin, Min-Max Odds, Out Of Range Action, Min Difference, Odds Ladder, Line Types and Max Lines. The **Provider List** tab sets the list used for the group's main markets. If the main markets end up on different lists, the group shows **Mixed**.

### Override a single derived market

You can take one derived market out of the model. Select the market, open its **Provider List** tab, and choose any list other than **Link to Model**. The market becomes **Unlinked** and is priced on its own, like in Benchmark. The rest of the group keeps running on Model.

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-a21e39883abca3f20b3584c52a961e5c9f4aa492%2Fodds-logic-link-to-model.png?alt=media" alt="Derived market panel with the Provider List tab open and Link to Model selected"><figcaption><p>Link to Model keeps the market on the model. Any other list unlinks it</p></figcaption></figure>

{% hint style="info" %}
An unlinked market no longer follows the model, so its price can disagree with the rest of the group. This brings back the internal arbitrage risk for that market. Unlink only when you have a clear reason.
{% endhint %}

### Templates and Fixture Ordering

Templates have a type, **Benchmark** or **Model**, set when you create them. A Model template can be applied only to leagues and fixtures that support Model.

In **Fixture Ordering**, the **Attributes** column shows a **Model Supported** marker for every league and fixture that supports Model. When you select several hierarchies at once, Model templates are available only if every selected hierarchy is supported. Benchmark templates are always available.

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-c85d2b29308f8d465a0b75f403e58a48c2f8cb2b%2Fodds-logic-fixture-ordering-supported.png?alt=media" alt="Fixture Ordering competitions list for England with the Model Supported attribute tooltip"><figcaption><p>Fixture Ordering: the Model Supported attribute</p></figcaption></figure>

## Good to know

* **Suspensions:** if one provider suspends a main market, that provider is left out and the group keeps running on the others. If no provider has a valid price for the main markets, the model can't calculate, and the group's derived markets are suspended with the System suspension reason. See [Odds Suspension Logic](https://docs.lsports.eu/u/trade/concepts/odds-suspension-logic.md).
* **Main markets must be offered:** the model can use a main market only while it is Offered. You can't hide a main market and still use it to price derived markets.
* **Provider Odds+ packages:** main markets keep delivering provider odds next to the calculated odds. Derived markets deliver calculated odds only, with no provider breakdown. Odds Settings shows a confirmation before you switch to Model.
* **Coverage:** Model is available in beta for Football and American Football PreMatch, on supported leagues. More sports and InPlay are (Coming).

## Related concepts

* [Odds Settings](https://docs.lsports.eu/u/trade/concepts/odds-settings.md)
* [Margin Strategy](https://docs.lsports.eu/u/trade/concepts/margin.md)
* [Probability](https://docs.lsports.eu/u/trade/concepts/probability.md)
* [Odds Suspension Logic](https://docs.lsports.eu/u/trade/concepts/odds-suspension-logic.md)
* [Provider Odds+](https://docs.lsports.eu/u/trade/concepts/provider-odds+.md)
* [Fixture Ordering](https://docs.lsports.eu/u/trade/concepts/fixture-ordering.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lsports.eu/u/trade/concepts/odds-logic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
