Skip to content
WallBettingRead the market
Read the market

Bet Builder: why related selections do not have independent prices

A Bet Builder groups conditions from one event into a combined proposition.

4 min read
01

Read the builder as one accepted combined proposition

A Bet Builder groups conditions from one event into a combined proposition. Where Zora offers that format, read the resulting combined price and accepted selection as a new product. It is not necessarily an ordinary accumulator made by multiplying every standalone price you can find elsewhere in the event menu.

Identify every included condition, the period and the final combined price in the summary. Then distinguish this accepted product from separate singles on the same event. The combined interface can apply its own compatibility checks and pricing logic. A set of individually available markets does not prove that every combination is offered. If the builder removes a condition or changes the price after an edit, inspect the resulting summary rather than relying on the earlier version. The relevant record is what the product accepted together. This article explains how to read that record; it does not claim that every fixture or player market supports a builder.

02

Related conditions do not create independent prices

The reason is dependence between conditions. A football home win and a home-team goal total can be related: particular scorelines satisfy both, others satisfy only one. Multiplying standalone prices without considering that relationship can produce a number that the combined market never offered. A high combined price also does not prove that the conditions are independent.

Consider a fictional home-win condition and a home-team Over 1.5 goals condition. A 1–0 home win satisfies the first but not the second; a 2–2 draw satisfies the second but not the first; a 2–0 home win satisfies both. The intersection is a narrower group of scorelines, and the conditions are related through the same scoring process. Multiplying their standalone decimal prices is not evidence of the price of that intersection. The combined offer must be read directly. This example describes logical membership, not the probability of any score or a recommendation to assemble a particular wager.

Bet Builder tutorial: subsequent choices depend on the first selection
Bet Builder tutorial: subsequent choices depend on the first selectionPublic Zora interface · 9 November 2026 · English version.An interface illustration, not a live price or an account test.
03

Logical overlap can narrow or duplicate a condition

There are logical overlaps as well as statistical ones. An illustrative condition of both teams to score implies at least two goals in the relevant period. Combining it with another condition can make that second condition redundant or leave only a narrower group of scores. The interface may reject certain combinations or price them together; do not treat a missing combination as a technical fault automatically.

For another illustrative comparison, both teams to score already requires at least one goal by each side in the relevant period. Adding a condition that does not further restrict those scorelines may be redundant, while a stronger total condition narrows them. The interface may reject, remove or price such overlaps according to the product's rules. Do not interpret every unavailable combination as a broken button. Also check that the periods align: a first-half condition combined with a full-match condition is not equivalent to two full-match conditions. Compact labels can hide that difference, so expand the summary before treating the combined wording as understood.

04

Exceptional treatment belongs to the combined product

Before confirming, read the complete summary and any rules for an abandoned event, void component or ineligible player market. A component's treatment may affect the combined product differently from a separate single. Save the accepted builder description as one record, including its period and final price, so a later comparison does not substitute individual market odds for the actual offer.

A void player component or an abandoned event may be handled under builder-specific terms. Do not automatically borrow the factor-one rule from an ordinary accumulator. Save the accepted conditions as one description, the stake, price and ticket reference. If the result differs from your expectation, identify the component and ask how its treatment affected the combined product. A screenshot of standalone prices cannot reconstruct the accepted builder price. The useful comparison follows the actual accepted package of conditions and its settlement rule, keeping it distinct from a collection of unrelated singles that happened to involve the same teams.