Epicor

Name: Epicor
Brand: Epicor
Rating: 4.1 (2091 reviews)

Leader

We’re the essential partner to the world’s most essential businesses.

Est 1972|Valuation $801.9M|Raised $211.3M|97 Ref Customers

LinkedIn 166K|Web traffic 252K|FTEs 5,000|HQ Austin, TX

MarketsProduction Planning ERP

Published Oct 14, 2026

01Common complaints

Consider alternatives in situations such as: 1. Support experience is mission-critical and the organization requires consistently high-touch vendor support without reliance on partners. Public reviews indicate variability in support responsiveness. 2. The organization needs a rapid, lightweight implementation (weeks to a few months) with minimal process redesign; community feedback suggests Epicor implementations often span longer timelines for full rollouts. 3. A requirement exists for a fully native cloud suite with tightly integrated CRM/e-commerce and unified reporting where minimal integration work is desired. 4. Training budgets and change management capacity are limited and the user base requires an extremely intuitive UX with limited onboarding. 5. The organization cannot tolerate performance variability in heavily customized environments or lacks governance to limit customizations.

Deal disqualifiers (poor fit)

Low tolerance for complex implementations or extensive change management
Minimal internal IT/ERP ownership and unwillingness to invest in partner expertise
Requirement for a tightly unified "single database" suite across CRM/ERP/e-commerce without integration work

Frequently cited limitations (from reviews and community discussions)

Variability in support responsiveness and perceived support quality
Implementation scope creep and unanticipated consulting costs
UI complexity and multi-step processes for some tasks
Performance latency, particularly in heavily customized deployments
Perceptions of portfolio fragmentation arising from acquisition history and cross-component integration needs

Roadmap/forward-looking notes (community-sourced; verify with Epicor)

Community posts have referenced experimental or beta capabilities in recent versions related to self-help portals and monitoring tools. Treat community-sourced roadmap comments as anecdotal until verified via official release notes and vendor communications.

02Why they buy

Unique selling points with user-validated signals

Manufacturing-specific functionality and workflows: users frequently cite production tracking, inventory accuracy, and end-to-end operational coverage as strengths.
Configurability: the product supports significant configuration, which can enable tailoring to industry requirements at the expense of greater implementation complexity.
Vertical orientation: Epicor is commonly used in industry-focused scenarios rather than purely horizontal implementations.

Unique selling points that are primarily vendor-claimed (require validation)

ROI and NPV figures presented in vendor-commissioned TEI materials (use these as starting assumptions and validate during diligence).
Broad scale metrics (customers, users, countries) that are reported by the vendor without a publicly documented methodology.

Areas where competitors may have advantages

Broader native suite integration and unified reporting in some competing products
Support sentiment and partner experience in selected competitive comparisons

03Field reports

This section summarizes both positive and negative feedback from public review platforms and community discussions.

Review landscape snapshot (volume and overall sentiment)

G2: well rated across multiple Epicor product profiles (Kinetic, Prophet 21, Grow, DocStar, etc.).
Capterra: product pages for Kinetic and Prophet 21 include review collections with a mix of positive and negative feedback.
Trustpilot (epicor.com): contains several negative service/support experiences.
Community forums (Reddit): recurring discussions emphasize support challenges, implementation realities, and the importance of partner selection.

Positive review excerpts (what users note)

From product reviews, some users report improved operational visibility and inventory accuracy after implementing Epicor products: - "We use Epicor for all the activities at work, from order entry, shipping all the way to invoicing… tailored to our company needs… pull real data to keep track of KPI’s." (Kinetic review) - "Our inventory accuracy is extremely high and we can always tell where an order is in process simply by drilling down within the system." (Prophet 21 review) Some community posts describe operational improvements after go-live, while also noting the importance of partner quality in achieving outcomes.

Negative review excerpts (what users strongly dislike)

From public review platforms and forums, recurring negative themes include support responsiveness and implementation-related issues: - "Very poor support… tried to resolve problems for month… very slow response to issues…" - "Avoid at all costs… virtually no support… months after buying it, we’re still teaching ourselves…" - "Do not buy this program!!!!! … months of expensive training… doesn’t do half what the sales team said… Incredibly expensive monthly support…" - Reports of many help tickets after switching interfaces and of missing data in certain tables compared to prior versions appear in several reviews. Community posts on Reddit and sysadmin forums frequently allege escalating service contract fees, slow response times, and implementation frustrations without suitable partner support.

Common reasons customers choose Epicor

Across reviews and analyst-style coverage, organizations select Epicor for:

Manufacturing functionality (job costing, scheduling, production tracking)
Industry-specific workflows for distribution, building supply, and automotive aftermarket
Configurability and extensibility when internal or partner expertise is available
Consolidating operational functions onto a single ERP backbone in product-centric businesses

Common reasons customers churn or consider alternatives

Evidence indicates churn pressure often stems from:

Support dissatisfaction (ticket responsiveness and perceived expertise)
Implementation overruns and unexpected consulting costs
Complexity and a learning curve for end users
Performance complaints, particularly where heavy customization exists
Concerns about suite integration following multiple acquisitions

Forrester TEI study (vendor-commissioned)

Epicor commissioned a Forrester Total Economic Impact (TEI) study for Kinetic. The study reports strong ROI and payback for a composite customer profile. Critical evaluation: - Commissioned TEI studies are useful for constructing a benefits hypothesis but are based on a composite model and vendor-provided references. They are not equivalent to an independently audited ROI across a representative sample. - Use vendor-commissioned studies as frameworks for benefit assumptions, and validate the assumptions through reference calls and organization-specific cost models.

Vendor success stories and events

Epicor’s site includes customer case studies and events, which describe successful deployments and product direction. These materials are vendor-curated and should be evaluated alongside independent reviews and reference checks.

Mixed results in community discussions

Public forums and review platforms show both successful go-lives with measurable improvements and implementations with extended timelines and unresolved issues. Execution quality (partner capability, internal project governance, and scoping) appears to be the primary determinant of success.

04Best fit

Company sizes (practical ranges)

Typical fit: mid-market to upper mid-market product-centric organizations, with flexibility depending on product and partner selection.
Vendor-commissioned case examples sometimes describe manufacturers with revenue profiles used for modeling; these are illustrative rather than prescriptive.

Industries / verticals

Discrete manufacturing, mixed-mode, make-to-order / engineer-to-order
Distribution and wholesale (Prophet 21)
Building supply
Automotive aftermarket
Select retail segments

Roles and personas

Decision makers: CFO, COO, VP Operations, CIO/IT Director
End users: production planners, buyers, warehouse staff, customer service, accounting

Strong fit criteria

Need for manufacturing-specific functionality (job costing, scheduling, traceability)
Ability to fund an implementation with experienced partners and internal project resources
Commitment to training and process standardization
Preference for industry-specific workflows over a generic horizontal suite

05The pitch

What the product does (objective summary)

Epicor is an enterprise software vendor focused on industry-specific ERP and adjacent applications for organizations that make, move, and sell products—primarily manufacturing, distribution, retail, building supply, and automotive aftermarket. Epicor's primary ERP product for manufacturers is Epicor Kinetic (available in cloud and on-premises deployment models), and the vendor also offers vertical products such as Epicor Prophet 21 (distribution) plus add-ons such as Epicor Grow (BI), Epicor CPQ, and content management. Epicor is positioned as a vertical ERP provider with a supply-chain orientation rather than a generic horizontal ERP.

Target market and positioning

- Primary target: mid-market to upper mid-market product-centric companies (manufacturers and distributors in particular), plus select retail/building supply and automotive aftermarket niches. - Positioning (vendor-stated): industry specialization, vertical functionality, supply-chain focus, and features described by the vendor that incorporate automation and AI-supported workflows. - Practical market reality: Epicor is commonly evaluated against other mid-market ERPs (NetSuite, Infor CloudSuite Industrial/SyteLine, Microsoft Dynamics 365, Acumatica, SAP Business One), especially for discrete manufacturing and distribution.

Get a comprehensive analysis of Epicor including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 14, 2026

01Common complaints

Consider alternatives in situations such as:

Support experience is mission-critical and the organization requires consistently high-touch vendor support without reliance on partners. Public reviews indicate variability in support responsiveness.
The organization needs a rapid, lightweight implementation (weeks to a few months) with minimal process redesign; community feedback suggests Epicor implementations often span longer timelines for full rollouts.
A requirement exists for a fully native cloud suite with tightly integrated CRM/e-commerce and unified reporting where minimal integration work is desired.
Training budgets and change management capacity are limited and the user base requires an extremely intuitive UX with limited onboarding.
The organization cannot tolerate performance variability in heavily customized environments or lacks governance to limit customizations.

Deal disqualifiers (poor fit)

Low tolerance for complex implementations or extensive change management
Minimal internal IT/ERP ownership and unwillingness to invest in partner expertise
Requirement for a tightly unified "single database" suite across CRM/ERP/e-commerce without integration work

Frequently cited limitations (from reviews and community discussions)

Variability in support responsiveness and perceived support quality
Implementation scope creep and unanticipated consulting costs
UI complexity and multi-step processes for some tasks
Performance latency, particularly in heavily customized deployments
Perceptions of portfolio fragmentation arising from acquisition history and cross-component integration needs

Roadmap/forward-looking notes (community-sourced; verify with Epicor)

Community posts have referenced experimental or beta capabilities in recent versions related to self-help portals and monitoring tools. Treat community-sourced roadmap comments as anecdotal until verified via official release notes and vendor communications.

02Why they buy

Unique selling points with user-validated signals

Manufacturing-specific functionality and workflows: users frequently cite production tracking, inventory accuracy, and end-to-end operational coverage as strengths.
Configurability: the product supports significant configuration, which can enable tailoring to industry requirements at the expense of greater implementation complexity.
Vertical orientation: Epicor is commonly used in industry-focused scenarios rather than purely horizontal implementations.

Unique selling points that are primarily vendor-claimed (require validation)

ROI and NPV figures presented in vendor-commissioned TEI materials (use these as starting assumptions and validate during diligence).
Broad scale metrics (customers, users, countries) that are reported by the vendor without a publicly documented methodology.

Areas where competitors may have advantages

Broader native suite integration and unified reporting in some competing products
Support sentiment and partner experience in selected competitive comparisons

03Field reports

This section summarizes both positive and negative feedback from public review platforms and community discussions.

Review landscape snapshot (volume and overall sentiment)

G2: well rated across multiple Epicor product profiles (Kinetic, Prophet 21, Grow, DocStar, etc.).
Capterra: product pages for Kinetic and Prophet 21 include review collections with a mix of positive and negative feedback.
Trustpilot (epicor.com): contains several negative service/support experiences.
Community forums (Reddit): recurring discussions emphasize support challenges, implementation realities, and the importance of partner selection.

Positive review excerpts (what users note)

From product reviews, some users report improved operational visibility and inventory accuracy after implementing Epicor products:

"We use Epicor for all the activities at work, from order entry, shipping all the way to invoicing… tailored to our company needs… pull real data to keep track of KPI’s." (Kinetic review)
"Our inventory accuracy is extremely high and we can always tell where an order is in process simply by drilling down within the system." (Prophet 21 review)

Some community posts describe operational improvements after go-live, while also noting the importance of partner quality in achieving outcomes.

Negative review excerpts (what users strongly dislike)

From public review platforms and forums, recurring negative themes include support responsiveness and implementation-related issues:

"Very poor support… tried to resolve problems for month… very slow response to issues…"
"Avoid at all costs… virtually no support… months after buying it, we’re still teaching ourselves…"
"Do not buy this program!!!!! … months of expensive training… doesn’t do half what the sales team said… Incredibly expensive monthly support…"
Reports of many help tickets after switching interfaces and of missing data in certain tables compared to prior versions appear in several reviews.

Community posts on Reddit and sysadmin forums frequently allege escalating service contract fees, slow response times, and implementation frustrations without suitable partner support.

Common reasons customers choose Epicor

Across reviews and analyst-style coverage, organizations select Epicor for:

Manufacturing functionality (job costing, scheduling, production tracking)
Industry-specific workflows for distribution, building supply, and automotive aftermarket
Configurability and extensibility when internal or partner expertise is available
Consolidating operational functions onto a single ERP backbone in product-centric businesses

Common reasons customers churn or consider alternatives

Evidence indicates churn pressure often stems from:

Support dissatisfaction (ticket responsiveness and perceived expertise)
Implementation overruns and unexpected consulting costs
Complexity and a learning curve for end users
Performance complaints, particularly where heavy customization exists
Concerns about suite integration following multiple acquisitions

Forrester TEI study (vendor-commissioned)

Epicor commissioned a Forrester Total Economic Impact (TEI) study for Kinetic. The study reports strong ROI and payback for a composite customer profile.

Critical evaluation:

Commissioned TEI studies are useful for constructing a benefits hypothesis but are based on a composite model and vendor-provided references. They are not equivalent to an independently audited ROI across a representative sample.
Use vendor-commissioned studies as frameworks for benefit assumptions, and validate the assumptions through reference calls and organization-specific cost models.

Vendor success stories and events

Mixed results in community discussions

04Best fit

Company sizes (practical ranges)

Typical fit: mid-market to upper mid-market product-centric organizations, with flexibility depending on product and partner selection.
Vendor-commissioned case examples sometimes describe manufacturers with revenue profiles used for modeling; these are illustrative rather than prescriptive.

Industries / verticals

Discrete manufacturing, mixed-mode, make-to-order / engineer-to-order
Distribution and wholesale (Prophet 21)
Building supply
Automotive aftermarket
Select retail segments

Roles and personas

Decision makers: CFO, COO, VP Operations, CIO/IT Director
End users: production planners, buyers, warehouse staff, customer service, accounting

Strong fit criteria

Need for manufacturing-specific functionality (job costing, scheduling, traceability)
Ability to fund an implementation with experienced partners and internal project resources
Commitment to training and process standardization
Preference for industry-specific workflows over a generic horizontal suite

05The pitch

What the product does (objective summary)

Target market and positioning

Primary target: mid-market to upper mid-market product-centric companies (manufacturers and distributors in particular), plus select retail/building supply and automotive aftermarket niches.
Positioning (vendor-stated): industry specialization, vertical functionality, supply-chain focus, and features described by the vendor that incorporate automation and AI-supported workflows.
Practical market reality: Epicor is commonly evaluated against other mid-market ERPs (NetSuite, Infor CloudSuite Industrial/SyteLine, Microsoft Dynamics 365, Acumatica, SAP Business One), especially for discrete manufacturing and distribution.

Get a comprehensive analysis of Epicor including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →