"Trades" covers a wide range of businesses in my client list — electricians, plumbers, HVAC installers, low-voltage contractors — and they split cleanly into two Acumatica product conversations depending on one question: are you primarily bidding and building projects (a trades subcontractor working under GCs), or are you primarily dispatching technicians to service calls at existing customer sites? The two look similar from the outside — "skilled trade doing physical work" — but they need almost entirely different edition and configuration choices.
Project-based trades: Construction Edition, subcontractor pattern
An electrical or mechanical subcontractor bidding commercial jobs under GCs needs the same commitment tracking, cost coding, and compliance document management as any other sub — I cover the GC-facing side of that compliance relationship in a companion post. Their own internal job costing runs on the same Construction Edition cost code and task structure as a GC's, scaled down: labor and material cost codes per phase of their scope, billed against their subcontract's schedule of values.
Service-call trades: Field Service Edition, dispatch pattern
An HVAC company doing residential maintenance calls, or an electrician doing service work rather than new-construction subcontracting, is a Field Service Edition fit instead — dispatch board, technician scheduling, service contracts, and equipment history at the customer's site are the core need, not project cost codes. Field Service Edition ships a visual dispatch calendar board for scheduling technicians, route optimization, and a mobile app for field techs to view schedules and complete service orders with e-signature capture — this is the product built for "which tech goes to which house today," which a project-oriented Construction Edition setup does not really address.
A mid-size mechanical contractor doing both new-construction subcontract work and a service/maintenance division is not an edge case — it is common, and it usually means running Construction Edition's project tooling for the bid-and-build side and Field Service Edition's dispatch tooling for the service side, on the same Acumatica instance, sharing the customer and inventory data. Scope this as two distinct workflows from the start rather than trying to force service calls through a project-cost-code structure or vice versa; I have unwound that mismatch on more than one instance where an implementer tried to make one hammer fit both jobs.
A note on licensing, since it comes up every time
Field Service Edition and Construction Edition are separate Acumatica editions with their own licensing — confirm with your VAR or Acumatica directly which suite (or combination) is licensed for the instance before assuming a feature is available. I have seen implementations stall for a week because a client assumed dispatch board access came bundled with a Construction Edition license it did not include.
Wrapping up
Ask "project-based or service-based" before anything else when scoping a trades contractor on Acumatica — it determines whether you are configuring Construction Edition cost codes and commitments or Field Service Edition dispatch and service contracts, and quite a few trades businesses genuinely need both running side by side.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.