Acumatica
Mid-market cloud ERP licensed by resource consumption rather than per named user, which makes it attractive where many occasional users need access. Sold through a partner channel.
Work orders, scheduling and dispatch for technicians who go to the customer, plus the parts they consume and the contract or warranty that decides who pays. It only earns its keep when van stock and technician time both land in the ledger without a re-key.
Stackmark rates Odoo’s field service as core: built and sold by the vendor as part of the suite.
The tier is read from the vendor’s own documentation, cited below, and says how the module is delivered — not how well it works for a given company. That is what the demonstration questions are for.
Does the scheduler account for technician skills, certifications and parts availability, or only for their calendar?
Is a van or truck a real stock location, so a part used on a job relieves inventory and costs the work order?
How are contract work, warranty work and billable work separated on the same job, and what reaches the invoice?
What can a technician do on the mobile app with no signal at the site, and what happens when they reconnect?
Other profiled systems whose records rate field service as core. Alphabetical; a listing is a documented fact, not a recommendation.
Mid-market cloud ERP licensed by resource consumption rather than per named user, which makes it attractive where many occasional users need access. Sold through a partner channel.
ERP built around asset-heavy and field-service operations, so the service, maintenance and project modules carry as much weight as the financial ones.
Microsoft’s modular business-applications line, where Finance & Operations covers larger enterprises and Business Central covers the mid-market. Its pull is tight integration with the rest of the Microsoft stack.
The pages the depth rating and module list were taken from. The module description and questions are Stackmark’s own, shared with the module page.