Commercial hot water is a different engineering problem than residential, and the difference is not just size. A house has a peak that lasts twenty minutes in the morning. A restaurant on Preston Road has a peak that lasts through a four hour dinner service, a salon near Stonebriar has a steady all-day draw at moderate flow, and a dental office has dozens of tiny short draws that punish a system with a high minimum activation flow. Sizing a commercial tankless bank means understanding the duty cycle, not just the gallons.
The second difference is consequence. If a residential water heater fails, somebody takes a cold shower. If a commercial water heater fails at a food establishment, the operation may not be able to legally serve. Texas Food Establishment Rules require handwashing sinks to deliver water at a minimum of 100 degrees F and manual warewashing wash water at 110 degrees F or above. High-temperature dish machines need a final sanitizing rinse well above what a building system supplies, which is why a booster heater sits downstream. Our job is making sure the building side never becomes the constraint.
That is why commercial installations are almost always multi-unit. A cascade rack of four 199,900 BTU condensing units gives roughly 800,000 BTU of input and lets the controller stage and rotate firing across the bank. Rotation matters: it distributes runtime so units age evenly instead of one workhorse failing at year six. It also means that when one unit locks out, the business runs at reduced capacity instead of zero. That N+1 logic is the entire argument for tankless in a commercial setting.
The infrastructure side is where commercial projects actually get expensive. A four-unit rack needs about 800 cubic feet of gas per hour. Standard small-commercial meters and the pipe feeding them frequently cannot deliver that, so the project includes a meter upgrade coordinated with the gas utility and a properly sized run, often 1-1/2 inch or 2 inch. We identify that on the site walk, before anyone signs a lease buildout schedule that assumes it is a drop-in swap.