Baccarat Shoes, Burn Cards and Cut Cards: How a Shoe Begins and Ends
A shoe is a finite sequence of physical cards
Conventional Punto Banco often combines several standard decks in a shoe. After the cards are shuffled and prepared, cards are drawn in sequence without simply replacing each one for the next hand. A simulator must decide whether it models this finite inventory or approximates outcomes with independent random draws.
Those are different modeling assumptions. A tool claiming to reproduce the physical dealing process should track the card inventory and make clear which cards are observable and which are hidden.
Burn-card procedures vary by rulebook
Some traditional tables begin a shoe by revealing a card and using its baccarat value to determine how many following cards to burn. Under a commonly documented procedure, a ten or face card can correspond to ten cards burned. The specifics are not universal across every venue, digital implementation or game variation.
A burn procedure affects where observable dealing begins in the underlying shuffled sequence. It does not reveal the full order of the unseen cards to a person looking only at a Banker/Player/Tie scoreboard.
A cut card marks the approach to the end
A cut card is inserted before play to signal that the shoe is approaching its final hands. What happens after it appears depends on the table's rules, including whether the current hand is completed and how many additional hands are dealt.
As a result, dividing the total number of physical cards by an assumed fixed number per hand does not produce a reliable hand count for every shoe. Each hand may use a different number of cards, and some are unavailable through burn or cut procedures.
Keep shoe boundaries explicit in software
A basic dataset should store a shoe identifier and the hand sequence within that shoe. Card-level simulations may additionally record the ruleset, initial shuffle, removed cards, cut-card position, and the final stopping event.
This is important for historical analysis because appending a new shoe to the end of an old one without a boundary creates apparent streaks that never occurred within a single physical shoe. A visualization should offer an explicit reset or divider.
Model the known facts, not imagined hidden information
Even an accurate description of the burn-card and cut-card procedures is not a complete observation of the shuffled deck. Software should not silently fill unknown cards with invented values and then report them as factual observations.
Document the assumptions, whether a sequence is simulated or observed, and whether shoe boundaries are verified. These are data-quality questions rather than claims about winning a future hand.
Reference: Wizard of Odds, Baccarat Basics, https://wizardofodds.com/games/baccarat/basics/ . Always use the applicable table's published procedures.