What do you like best about Acumatica?
What I like best about Acumatica is its flexibility. As someone who works with the platform from a consulting and implementation perspective, I regularly see businesses with very different processes and requirements, and Acumatica generally provides multiple ways to configure the system around those needs rather than forcing every organization into the same workflow.
The platform's reporting and data accessibility are particularly valuable. Generic Inquiries, dashboards, business events, import scenarios, and configurable workflows give consultants and power users a significant amount of control without requiring custom development for every business requirement. Generic Inquiries in particular are one of Acumatica's strongest features because they can be used not only for reporting, but also as the foundation for dashboards, notifications, integrations, and operational workflows.
Acumatica also has a strong integration and customization framework. The APIs and xRP platform make it possible to extend the ERP or connect it with specialized third-party applications when the native functionality does not fully meet a company's requirements. The ecosystem of integrated solutions is another benefit, especially for organizations that need capabilities beyond the core ERP.
From a UI/UX perspective, the web-based architecture makes the system accessible without requiring traditional desktop software, and users can personalize many screens, inquiries, dashboards, and workflows. There is certainly a learning curve, but once users understand how Acumatica organizes information, they can often accomplish a great deal without relying on IT for every change.
Another advantage is Acumatica's breadth. Financials, distribution, inventory, sales, purchasing, CRM, projects, construction, service management, and other functionality can exist within the same ecosystem. For organizations that would otherwise maintain several disconnected systems, having operational and financial information in one ERP can provide substantial value.
The licensing model can also be attractive compared with ERP products that primarily charge per named user. For organizations that need broader system participation across departments, Acumatica's approach can make it more practical to give more employees access to the ERP rather than limiting access because of individual seat costs.
Support and onboarding are heavily influenced by the implementation partner, but Acumatica provides a substantial amount of training and product documentation. From a consulting perspective, having access to training resources and a platform that can be configured extensively gives us more options when solving customer requirements.
AI and intelligent automation are areas where I see potential rather than something I would currently consider the platform's defining strength. Acumatica has been expanding its focus in these areas, but for my day-to-day work, the greatest productivity benefits still come from its established automation, reporting, integration, and configuration capabilities.
Overall, Acumatica's biggest strength is that it provides a highly configurable ERP foundation. It can support relatively straightforward implementations while also giving consultants and developers the tools to address much more specialized business requirements. That flexibility is one of the primary reasons I continue to see value in the platform, even though I have concerns about some of the product's recent changes and direction. Review collected by and hosted on G2.com.
What do you dislike about Acumatica?
My biggest concern with Acumatica is the gap that can sometimes exist between the direction of the product roadmap and the day-to-day experience of the consultants, administrators, and end users who actually work in the system.
The transition to the Modern UI is probably the clearest example. I understand and support the need to modernize the platform, but the transition has felt more aggressive than the maturity of the new experience warrants. In consulting and implementation work, reliability and efficiency are more important than simply having a newer interface. There are still areas where the Modern UI introduces additional clicks, inconsistent behavior, performance concerns, or limitations compared with workflows that were already well established in the Classic UI. Moving customers and consultants toward the new interface while those gaps still exist creates unnecessary implementation, training, and support overhead.
Performance is another area where the experience can be inconsistent. Acumatica is capable of handling complex organizations and significant transaction volumes, but larger Generic Inquiries, integrations, imports, and heavily used screens can expose performance issues. When troubleshooting these situations, it can also be difficult to determine whether the underlying problem is the ERP, an integration, customization, hosting resources, or the way a particular process was designed. That complexity can make performance problems particularly frustrating for customers because there is not always a simple or immediate answer.
Acumatica's flexibility is simultaneously one of its greatest strengths and weaknesses. Generic Inquiries, import scenarios, business events, workflows, APIs, customizations, and ISV integrations allow you to accomplish an enormous amount, but they also create complexity. Something that appears like a relatively simple business requirement can occasionally require a GI, business event, customization, third-party product, or consultant involvement. I would like to see more common business reporting and functionality available out of the box rather than requiring customers or partners to build solutions for requirements that are common across many implementations.
Upgrades can also become significantly more complicated once an organization has customizations and third-party integrations. The more value a customer gets from extending Acumatica, the more regression testing and remediation may be required when upgrading. This creates an unfortunate tradeoff where the platform encourages customization and integration, but those same capabilities can increase the cost and risk associated with staying current.
The partner-driven implementation and support model is another mixed experience. A strong Acumatica partner can make the product substantially better for a customer, but that also means the quality of implementation, training, customization, and ongoing support can vary considerably depending on who implements the system. For an end user, it may not always be obvious whether a frustrating experience originates with Acumatica itself, the implementation, an ISV, or the partner.
Pricing has a similar tradeoff. The licensing model can provide excellent value for organizations that need many users, but the true cost of an ERP implementation extends well beyond the core license. Implementation services, customizations, integrations, ISV products, upgrades, training, and ongoing consulting can substantially increase total cost of ownership. Acumatica can still provide a strong ROI, but customers should evaluate the complete ecosystem they will require rather than focusing exclusively on the initial software cost.
Finally, I think Acumatica needs to be careful about prioritizing AI and highly visible roadmap initiatives over refinement of the core ERP experience. AI has significant potential in ERP, but I would rather see intelligent functionality introduced where it solves specific business problems instead of AI becoming a goal by itself. Performance, reporting, usability, workflow consistency, and reducing the amount of effort required to accomplish common business processes are ultimately more valuable to me than adding AI functionality simply because the market expects it.
Overall, my frustration with Acumatica is not that it lacks capability. In many ways, the opposite is true. It is an extremely capable and flexible ERP platform. My current 6/10 assessment is driven more by execution and direction: I would like to see greater emphasis on stability, performance, consistency, and refinement of existing functionality before established experiences are retired or significant new initiatives are prioritized. Review collected by and hosted on G2.com.