Shingle bundle calculator

The response returns base bundles without waste, the exact inflated count, and a whole-bundle purchase quantity after ceiling, so you never order a fractional pack. The same pure function powers the free browser tool and the paid API, so a counter quote matches a scripted purchase order later. Non-positive squares or pack rates and negative waste fail with invalid_input instead of silent nonsense. Pricing for successful API calls is the published base of $0.002 per item.

How squares become shingle bundles with waste

US roofing practice measures coverage in squares, where one roofing square equals one hundred square feet of roof surface. Manufacturers print how many bundles cover one square on the package—classic three-tab asphalt is usually three bundles per square, while some architectural laminates still use three or occasionally four depending on the series. Real roofs are not perfect: starter courses along eaves, ridge and hip caps, valley cuts, dormer intersections, and a few damaged tabs all consume extra product. Common field allowances are about ten percent for a simple gable, fifteen percent for a cut-up hip roof with valleys, and higher when matching complex architectural patterns. Start from the coverage identity base_bundles equals squares times bundles_per_square. That product is the net pack count if the roof were a perfect rectangle with zero scrap. Apply waste as a percentage of the net: waste_factor equals one plus waste_percent divided by one hundred, then bundles_exact equals base_bundles times waste_factor. Equivalently you can inflate squares first to squares_with_waste and multiply by the pack rate; both paths are algebraically identical. Purchase quantity bundles_needed is the ceiling of bundles_exact, because suppliers sell whole bundles only. The response also reports waste_bundles_exact (the fractional overage before ceiling) and waste_bundles (how many whole bundles the ceiling added relative to the net base), so a purchasing clerk can audit the allowance against company policy. The pipeline is deterministic floating-point arithmetic with no random seeds, no wall-clock timestamps, and no network calls, so identical inputs always produce identical JSON. Squares and bundles_per_square must be strictly positive; waste_percent must be non-negative so the inflated count stays defined and non-absurd.

What you send and what you get back

All three fields are required. Send three finite numbers: squares for the roof area already expressed in roofing squares, bundles_per_square for the manufacturer pack rate of the SKU you will buy, and waste_percent for the overage allowance as a percentage of base bundles. Missing fields, non-numeric strings, NaN, and Infinity fail with invalid_input and are not charged. When squares is zero or negative the request fails with a message that squares must be positive, so clients can correct a takeoff before retrying. The same positivity rule applies to bundles_per_square. Negative waste_percent is rejected because a negative allowance would undercut the net count rather than plan for scrap. On success the response echoes cleaned inputs, waste_factor, base_bundles, squares_with_waste, bundles_exact, integer bundles_needed, waste_bundles_exact, waste_bundles, a unit_note that one square equals one hundred square feet and that bundles_needed is a whole purchase count, and a short formula string for documentation. Classic check: twenty-two squares, three bundles per square, and ten percent waste yields base_bundles of sixty-six, waste_factor of one point one, bundles_exact of seventy-two point six, and bundles_needed of seventy-three. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance. Keep squares as true roofing squares after pitch and plan-area math are already finished elsewhere—this endpoint does not re-derive surface area from plan dimensions.

Where a shingle bundle calculator earns its keep

Homeowners who already hold an insurance or contractor estimate written in squares need a trustworthy bundle count before ordering online or booking a dumpster, especially when architectural laminates have a high unit price and long lead times. If you later need plan-area times pitch to invent the square count, hip and valley linear waste tables, starter-strip feet, ridge-cap bundles as a separate line, underlayment rolls, or drip-edge lineal feet, treat those as separate search intents and landings rather than overloading this squares-to-bundles order calculator. Roofing contractors convert takeoff squares into purchase orders by product SKU: swap only bundles_per_square when comparing three-tab versus laminate lines while holding squares and waste policy fixed, then rank total packs side by side. Building-supply counters quote walk-in jobs from a square figure the customer already has, apply the house waste rule, and print bundles_needed without re-measuring pitch on the spot. Property managers planning multi-building re-roofs feed a batch of square totals and pack rates through the API and attach bundles_needed to purchase orders so overstock stays intentional rather than accidental. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.