GUIDES · BETSLIP DOCTOR
Why can the same selection appear in several legitimate history records?
A selection describes one part of a ticket; it does not uniquely identify the history record. The same selection may be used in separate wagers, separate saved tickets or a manual entry alongside an imported row. Compare each row's record kind and ID, ticket and placement details, sportsbook and recorded source before deciding whether two rows refer to one placement.
For Bettors comparing recurring selections across imported and manual history · Updated
A leg is not the whole ticket
A selection can repeat while the ticket around it changes. The same market might be part of a different combination, appear at another sportsbook or belong to another placement. Even when the headline text matches, compare the event and market details, the other selections, the ticket context and the recorded placement time.
BSD stores history as records with their own identities. The imported record ID and revision identify an imported row. A manual row has its own ID and revision and is attached to a saved BSD ticket. A selection label helps you recognize a leg; it is not a substitute for those record identifiers.
Use the source and placement details together
When comparing two rows, first note whether each is imported or manual. Imported history reflects records the provider made available. A manual history row is self-reported, including its placement and financial result. These sources describe different evidence even if both contain a similar selection.
Next compare what is actually present: sportsbook or book reference, placement time, full ticket contents, status, source record ID and revision. Some provider fields may be absent and a ticket may be incomplete. When an identifier or timestamp is missing, the matching selection cannot fill it in. Keep that uncertainty visible.
- Compare the full ticket and its other legs, not only the repeated selection.
- Distinguish an imported sportsbook record from a self-reported manual entry.
- Use the row ID, revision and placement details where available.
- Treat missing source information as unknown instead of inferring a duplicate.
A possible overlap needs more than similar text
Two rows may represent one placement, or they may be separate placements that share a selection. BSD does not turn a matching label into automatic proof that they are the same. For a manual and imported row, an overlap link records a bettor's confirmation of the same placement and names the current record revisions and import digest.
A linked manual duplicate is excluded from the default list and financial totals. An unlinked manual row can still overlap an import, so a missing link does not prove that the bets were separate. Review the original record details before interpreting combined counts or totals.
Keep incomplete rows in view while you compare
A provider may not have supplied every selection or detail for an imported row. Currency or settlement information may also be unavailable. In those cases, one visible matching leg is not enough to decide that two whole tickets are identical.
Use what each record actually contains and note what is missing. A row that cannot be verified should remain unresolved in your comparison rather than being collapsed into another row based on a resemblance.
Illustrative example: one shared leg across separate tickets
Suppose a fictional bettor backs the same player market on two occasions. One ticket is a single; another combines that selection with other legs. The history rows share one leg but have different ticket context and placement details, so the selection alone cannot make them duplicates. If a separate manual row appears to describe the same placement as an import, the bettor checks the two record IDs and any explicit same-placement confirmation. This example is invented and contains no real selection, price, record or outcome.
Related questions
If two history rows show the same player and line, are they duplicates?
Not necessarily. Compare the full ticket, event, sportsbook, placement details, source and record identity. The shared selection is only one part of that comparison.
Can an imported record and a manual row both be present for one placement?
They can overlap. BSD has an explicit user-confirmed link for a manual row and an imported record. Until that relationship is confirmed, possible overlap remains unverified.