Bowled: a bat or pad deflection can still hit the wicket
Why contact with the striker does not automatically prevent a bowled dismissal.
A legal delivery must break the wicket
MCC Law 32 says the striker is out bowled when a delivery, not being a no-ball, fairly breaks their wicket. It can first touch the striker's bat or person. An inside edge onto the stumps can therefore still be bowled.
A ball striking the stumps is not enough by itself if the wicket has not been fairly broken. That separate requirement matters when a ball brushes a stump without the necessary consequence.
Another person changes the route
If the ball touches another player or an umpire before striking the wicket, Law 32 does not give a bowled dismissal. Other dismissal provisions may be relevant depending on the facts. Do not label every broken wicket bowled from the score alone.
For a hypothetical legal ball deflected from the striker's pad onto the wicket, pad contact is not an exemption. LBW conditions are not needed to establish bowled when its own requirements are satisfied.
The dismissal has priority
The Law gives bowled priority when its conditions are met, even if another dismissal could also be justified. That helps explain the final scorecard label rather than proving the order of every possible appeal.
On ScoreZaap, wait for the reported decision if the delivery is being checked. A no-ball review can change the apparent wicket state. This explanation concerns the general Law and does not invent the outcome of a live replay.