Vertical SaaS · Saas

HVAC Distribution Vertical on Acumatica

HVAC Distribution Vertical on Acumatica: a practical Acumatica fit review focused on availability, replenishment, warehouse execution, landed cost, and order allocation. It separates documented product capability from configuration, integration, and customisation work.

John Kihiu12 min read

HVAC is the trade where I see the cleanest, most complete case for combining Acumatica Distribution Edition and Field Service Edition, because HVAC businesses genuinely straddle both worlds more often than plumbing or electrical: distributing equipment and parts, and running a maintenance-contract-heavy service business with recurring preventive maintenance visits, not just break-fix calls.

Preventive maintenance contracts are where Field Service Edition earns its keep

Field Service Edition supports PM contract templates with cycle frequencies, allowed-trip counts, escalation clauses, and bundled inclusions as core functionality — this is built specifically for the HVAC maintenance-contract business model (twice-yearly filter and coil service, bundled into an annual contract price) rather than being adapted from a generic service module. Getting the contract templates right at setup — cycle frequency, what is included versus billed as an add-on, escalation for missed visits — determines whether the recurring-revenue side of an HVAC business is actually visible in the ERP or still tracked on a separate spreadsheet the office manager maintains.

CONFIG · PM CONTRACT TEMPLATE
PM Contract Template: RESIDENTIAL-ANNUAL-2VISIT
  Cycle: Semi-annual (Spring / Fall)
  Included: Filter replacement, coil cleaning, refrigerant check
  Excluded (billable add-on): Refrigerant recharge, part replacement
  Escalation: If visit not scheduled within 30 days of due date,
              auto-create a follow-up dispatch task flagged "overdue PM"

The dispatch board is the daily-use screen — treat it as such

The visual dispatch calendar board with drag-and-drop scheduling and color-coded order status, plus route optimization plotted on a map, is the screen an HVAC dispatcher lives in all day, and it is worth investing real configuration time in — technician skill tagging (who is certified for commercial rooftop units versus residential splits), service territory boundaries, and appointment-window defaults that match how the business actually promises appointment times to customers. Getting this screen right has a bigger impact on day-to-day operations than almost any other configuration decision on an HVAC implementation.

Equipment history ties parts distribution back to service

Because Field Service Edition's equipment tracking links installed units to their service history, and Distribution Edition tracks the parts inventory, an HVAC business selling and installing its own equipment gets a genuinely useful loop: a technician dispatched to a unit sees what was installed, when, and what parts were used on prior visits, pulled from the same instance that manages the parts warehouse. That loop is native once both editions are configured against the same equipment records — it is not something you have to build from scratch, but the equipment record discipline (always linking the sold unit to the customer's site record at time of sale) has to be enforced or the history chain breaks.

Wrapping up

HVAC is the trade most likely to need the full Distribution Edition plus Field Service Edition combination running well together, with PM contract templates and the dispatch board as the two screens worth the most implementation attention. Enforce equipment-record linkage at the point of sale so the service history loop actually closes.

John Kihiu
Acumatica ERP Developer · Laravel Engineer

Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.