What I like most about Epicor Prophet 21 is that it’s designed specifically for distribution businesses, and it does a great job balancing deep operational functionality with a more modern, Microsoft-based ecosystem. It brings sales, purchasing, inventory, accounting, and warehouse workflows together in a single platform, which helps streamline day-to-day work across departments and keeps processes more consistent.
Another key strength is its flexibility around reporting and integrations. P21 works well with SQL Server, Power BI, Excel, and other Microsoft technologies, which makes it easier to build dashboards, automate reporting, and connect with external systems than many older ERP platforms.
I also appreciate how well it supports detailed distribution workflows, including pricing structures, order processing, inventory management, and wireless warehouse operations. At the same time, it remains customizable enough to fit different business processes without forcing everything into a one-size-fits-all approach.
From an IT and administration standpoint, the web-based architecture, API capabilities, and broader ecosystem support make it easier to maintain, troubleshoot, and expand over time compared with more legacy distribution ERPs. Review collected by and hosted on G2.com.
One of my biggest frustrations with Epicor Prophet 21 is that performance and responsiveness can be inconsistent at times, especially in cloud-hosted environments or during peak usage. Certain screens, inquiries, or processes can feel slower than expected for users who spend most of the day working in the system.
Another challenge is that while P21 is highly customizable, that same flexibility can also add complexity. Over time, customizations, Dynachanges, reports, integrations, and third-party add-ons can make an environment harder to troubleshoot, upgrade, and properly document. Some workflows also still feel like a blend of legacy design patterns alongside newer web-based functionality.
Reporting and data access are strong, but fully leveraging them often requires technical knowledge of SQL, views, business rules, and the underlying database structure. For companies without solid internal IT or BI resources, that can become a real limitation.
There can also be gaps between different modules or tools within the Epicor ecosystem, where certain features feel less unified than you’d expect from modern cloud-native ERP platforms. Upgrades, printing configurations, and integrations can sometimes require more vendor coordination and troubleshooting effort than anticipated. Review collected by and hosted on G2.com.