Edge cases, single-yard regional vs multi-state scale (US LBM, Builders FirstSource)?

The trade-supply Magento playbook scales from one yard to a hundred, but the build complexity differs:

Single-yard regional lumber yard (1 branch, $2M, $10M GMV): the $4,999 build covers it. One BisTrack source, one delivery zone, one state tax-exempt regime, ~500 contractor accounts. Hyvä storefront + Magento Open Source. Net-30 via Apruve (cheaper than Resolve for smaller volumes). Total cost-of-ownership ~$8k year-one (hosting + Apruve + Avalara CertCapture + extensions), drops to $4k/yr ongoing. Tiny ops team (1 admin + 1 inside sales rep can run the entire ecom side).

Mid-market regional (3-10 branches, $10M, $80M GMV): $15k, $40k build. Multiple BisTrack sources with cross-branch transfer, multi-state cert workflow, 1k, 5k contractor accounts, custom-milling configurator. Adobe Commerce makes more sense at this scale for the native B2B Companies module. Resolve or TreviPay for Net-30 underwriting. Avalara for tax. ~$30k/yr ongoing cost.

Multi-state scale (US LBM, Builders FirstSource, 84 Lumber profiles, 50+ branches, $500M+ GMV): $150k, $500k+ multi-phase engagement. Multiple ERP sources (acquisition history usually means 2-4 different inventory systems), 50-state nexus, federated contractor identity, headless Hyvä + PWA for the contractor-app surface, custom OMS layer for cross-branch routing. 12-24 month delivery. At this scale you’re hiring a 3-6 person internal ecom team and I work alongside it as the technical lead. Quoted hourly, $25/hr math always visible.

If you’re at the multi-state acquisition-rollup stage, you also need a real PIM (Akeneo or Pimcore) as the catalog-of-truth, because each acquired yard has its own SKU master and reconciling them in Magento alone gets messy fast.