Epicor is a family of industry-specific ERP systems, not a single product. The Austin, Texas-based vendor sells Epicor Kinetic for manufacturing, Prophet 21 for wholesale distribution, BisTrack for lumber and building materials, Eagle for retail hardware and home centers, and iScala for some international mid-market operations. If you are shopping for “Epicor ERP” as a general-purpose accounting suite, you are looking at the wrong category. Epicor is bought for depth in discrete and configure-to-order manufacturing and in distribution operations; its financials are competent rather than category-leading.
Epicor Software Corporation is owned by private equity. Clayton, Dubilier & Rice bought the company from KKR in 2020 in a transaction valued at $4.7 billion, after KKR’s 2016 purchase and Apax Partners’ 2011 take-private that merged Epicor with Activant Solutions. Ownership shapes what you get: a disciplined release cadence, cloud-first messaging, a heavy partner channel, and pricing negotiated deal by deal rather than published on a rate card.
This guide covers which product fits which industry, where Kinetic’s manufacturing depth lives, how the cloud migration works for companies on on-premise ERP 10, how licensing is counted, and where Epicor is the wrong choice. It is written for US small and midsize businesses, roughly 20 to 500 users.
Disclosure: this article is editorial and independently researched. Wartaholic does not sell ERP software and receives no commission from Epicor or its partners. Vendor pricing is quote-based and changes frequently; the figures below are directional estimates for planning, not quotes.
What Epicor actually is
Epicor’s lineage explains its portfolio. The business traces to 1972, when Triad Systems was founded to sell point-of-sale and inventory software to retail hardware stores and auto parts jobbers. Triad became Activant Solutions in 2003. In 2011, the private equity firm Apax Partners bought Activant and merged it with Epicor, which had itself grown out of a 1999 merger of Platinum Software and DataWorks. The retail division was spun off as Aptos in 2015. KKR bought Epicor in 2016 and sold it to CD&R four years later.
The result is a collection of acquired, industry-specific products that share a brand, a partner channel, and a cloud platform, but not a common codebase. Epicor reported about $1.05 billion in revenue for fiscal 2022 and roughly 4,600 employees, placing it in the mid-market tier alongside Infor and Sage rather than the tier-one vendors.
Each Epicor product has its own data model, upgrade path, and partner ecosystem, so the useful first question is not whether Epicor is good, but which product, if any, was built for your industry.
Which Epicor product fits which industry
Epicor’s vertical split is unusually clean. The table below maps each product to the industry it was designed around, the kind of company that typically buys it, and how it is deployed. If your business does not resemble one of these rows, Epicor is probably not your shortlist.
| Epicor product | Primary industry | Typical company profile | Deployment |
|---|---|---|---|
| Epicor Kinetic | Discrete and configure-to-order manufacturing | Job shops, industrial equipment, aerospace and defense suppliers, medical devices | Single-tenant cloud or on-premise |
| Epicor Prophet 21 | Wholesale distribution | Electrical, plumbing, industrial, fastener, and JanSan distributors | Cloud or on-premise |
| Epicor BisTrack | Lumber and building materials | LBM dealers, millwork, truss and component plants | Cloud or on-premise |
| Epicor Eagle | Retail hardware and home centers | Hardware stores, farm and ranch stores, home centers | Cloud or on-premise |
| Epicor iScala | International mid-market | Multi-country subsidiaries, service and project businesses | On-premise or hosted |
Epicor Kinetic for manufacturing: where the depth is
Kinetic is the flagship and the product most people mean by “Epicor ERP.” It descends from Epicor ERP 9 and ERP 10, and it is aimed at discrete and mixed-mode manufacturers: job shops, industrial equipment builders, aerospace and defense suppliers, medical device makers, and anyone producing to order rather than to stock.
The manufacturing core is genuinely deep. Methods of Manufacturing defines how a part is built, including revisions, operations, and routings. Job Entry and Job Scheduling handle make-to-order and make-to-stock work, while Material Requirements Planning nets demand against on-hand, on-order, and scheduled receipts. Advanced Production adds constraint-based scheduling, and Quality Assurance supports inspection plans and nonconformance tracking for regulated industries. Lot and serial traceability is built in, which matters when a customer requires a full as-built record.
The Product Configurator is the module that most often decides the sale. It is rules-based: the buyer or salesperson selects options at quote time, and the system generates the bill of materials, routing, and pricing for that specific configuration. For configure-to-order manufacturers, that replaces the spreadsheet-and-engineering-ticket ritual that otherwise consumes a day per quote. The mechanism matters because the configured item becomes the job’s engineering record, so changes flow through costing rather than being re-keyed.
Kinetic’s data model is a single database per company with multi-site and multi-plant support, standard costing options (standard, average, last, and FIFO), and unit-of-measure conversions that handle the realities of buying in feet and selling in pieces. The browser-based Kinetic UI now covers most day-to-day screens, though the classic Smart Client remains for a subset of forms. Where Kinetic is weakest is financial consolidation and analytics; multi-entity, multi-currency rollups and global tax are workable but not the reason anyone buys it.
Prophet 21, BisTrack, and Eagle: the distribution and retail side
Prophet 21 is the distributor’s system, carrying the inventory depth that distribution actually requires: price matrices and customer-specific pricing, supplier rebates, purchasing and receiving, warehouse bin management, counter and outside sales, and ecommerce storefront integration. Distributors buy it for the same reason manufacturers buy Kinetic: a horizontal suite would need heavy customization to match the same processes.
BisTrack covers lumber and building materials with the quirks that industry demands: board-foot and linear-foot units of measure, special order handling, delivery scheduling, and support for truss and component manufacturing. Eagle serves retail hardware and home centers, with point-of-sale, member and dealer programs, and retail inventory. iScala came to Epicor through the 2004 acquisition of Scala and is mostly found in international subsidiaries and service or project businesses; it is the oldest and least strategic line in the portfolio, and buyers should ask pointed questions about its roadmap before committing.
The Kinetic cloud migration path from on-premise ERP 10
Most existing Epicor customers are not choosing between vendors; they are choosing between staying on ERP 10 on-premise and moving to Kinetic in the cloud. Epicor’s cloud offering is single-tenant, meaning you get an isolated environment rather than a shared multi-tenant database. That preserves customization flexibility, but it also means Epicor pushes updates on a schedule, typically a couple of releases a year, and you are responsible for regression testing what those updates might break.
The migration itself is not a rewrite if you stay on the same codebase, but the customization inventory is where the work lives. Business Activity Queries and Business Process Management directives generally survive. Classic C# UI customizations and Service Connect workflows are the problem children: they may need to be rebuilt as Epicor Functions or folded into Kinetic UI customizations, and some classic forms have no browser equivalent at the time of your migration. Partners routinely under-scope this step.
Data migration is the other recurring risk. Open work in process, general ledger balances, inventory valuation, open sales orders, and historical transactions all have to land correctly, and the only reliable way to know they did is to run a full parallel close and reconcile it line by line. Mid-market migrations commonly run six to twelve months, and heavily customized shops run longer.
How Epicor licensing is really counted
Epicor sells two ways. On-premise customers historically bought perpetual licenses plus an annual maintenance fee, commonly around 18 to 22 percent of the license value, though that percentage is negotiated and has drifted upward over time. Cloud customers pay a subscription that bundles hosting, updates, and support. Almost all pricing is quote-based, so two manufacturers of similar size can pay meaningfully different amounts.
Within either model, users are licensed by class. Named users are tied to a person; concurrent users are shared and are the cheaper choice for shift-based operations where the same seat is used around the clock. Data collection licenses cover plant-floor terminals and barcode or RF devices, and limited-use classes cover people who only need inquiry or time entry. Modules are licensed separately as well: financials, manufacturing, Product Configurator, Advanced Production, EDI, and analytics are all line items, which is why the configuration of the quote matters as much as the headline user rate.
As a planning estimate, cloud subscriptions for Kinetic commonly land somewhere in the range of $100 to $250 per named user per month before module add-ons, and total first-year cost including implementation often runs one and a half to three times the annual software cost. Treat both as directional only: the vendor publishes no rate card, bundles change, and any real number requires a scoped quote.
Implementation reality: what slips and what breaks
Epicor implementations are partner-delivered, and partner quality varies far more than software quality does. The same release that goes live on schedule at one manufacturer can drag for eighteen months at another; the difference is usually the integrator and the customer’s data, not the product.
The first ninety days are almost entirely about decisions, not configuration. Which costing method will you actually use, and does the shop floor understand it? How will you convert units of measure without corrupting inventory valuation? Who owns the item master, and how many of the current part numbers are duplicates or dead? These choices are hard to reverse after go-live.
The recurring failure modes are predictable. Item and bill-of-materials data arrives dirty from the legacy system, so the migration dry run reveals thousands of exceptions two weeks before cutover. Open work in process and inventory valuation do not reconcile on the first pass. Report requests pile up because the legacy system’s custom reports have no direct equivalent. And in the cloud model, the first vendor-pushed update after go-live catches a customization nobody tested. Teams that handle this well freeze scope early, run at least two full migration rehearsals, and keep a named owner for data quality rather than delegating it to the integrator.
Licensing surprises surface late too. Concurrent licensing looks generous until the business adds a second shift and the true-up arrives. Data collection devices often get counted separately from desktop users, and add-on modules that seemed optional during the sales cycle turn out to be required for a process the business assumed was standard.
Limitations: where Epicor is the wrong choice
Epicor is a poor fit for companies whose center of gravity is finance rather than operations. If you are a services firm, a professional employer organization, or a multi-entity holding company that needs clean consolidations, intercompany eliminations, and sophisticated revenue recognition, a horizontal suite such as NetSuite or a finance-first product like Sage Intacct will serve you better. Kinetic can do the accounting, but it is not why the product exists.
Analytics and reporting are the other soft spot. Epicor’s native dashboards and Business Activity Queries are workable for operational reporting, but serious financial and executive reporting usually means bolting on a third-party tool.
Cost and complexity rule Epicor out below a certain size. A fifteen-person job shop will spend more on implementation, training, and administration than the operational gain justifies, and lighter platforms such as Odoo or a specialized shop-floor tool will cover the same ground for less. The cloud model’s forced update cadence is also a real constraint for companies without internal IT capacity to regression-test twice a year. And since the retail division became Aptos in 2015, Epicor is no longer the natural answer for general retail outside its hardware and building-materials niches.
Frequently Asked Questions
Is Epicor ERP the same thing as Epicor Kinetic?
Effectively yes, for the manufacturing product. What was sold as Epicor ERP 10 was rebranded as Epicor Kinetic, and Kinetic is the current name for that line. The underlying data model and much of the functionality carried over, so an ERP 10 customer is not looking at a different product so much as a different user interface and a cloud-first delivery model. Note that “Epicor” as a company also sells Prophet 21, BisTrack, Eagle, and iScala, which are entirely separate systems.
Who owns Epicor, and does that matter to buyers?
Epicor Software Corporation is owned by Clayton, Dubilier & Rice, which acquired it from KKR in 2020 in a deal valued at $4.7 billion. KKR had owned it since 2016, and Apax Partners took the company private in 2011 and merged it with Activant Solutions. Private equity ownership is not inherently a problem, but it does mean you should read the contract carefully: renewal terms, price escalation clauses, and support commitments deserve more scrutiny than the demo does.
How much does Epicor Kinetic cost?
Epicor does not publish list pricing, so every figure is a scoped quote. As a rough planning range, cloud subscriptions commonly fall between $100 and $250 per named user per month before module add-ons, and total first-year cost including implementation often lands at one and a half to three times the annual software cost. Perpetual on-premise licenses carry annual maintenance, historically around 18 to 22 percent of license value. Treat all of these as directional, and ask for a written breakdown that separates software, services, and third-party items.
How long does an Epicor implementation take?
For a mid-market manufacturer with moderate customization, six to twelve months from kickoff to go-live is a realistic expectation, with another quarter of stabilization afterward. The schedule is driven by customization rework and data quality rather than by the software. Companies with heavy classic UI customizations, messy item masters, or multiple plants should plan for the longer end and budget at least two full data migration rehearsals before cutover.
About the Author
Wartaholic Writer is a contributing editor at Wartaholic, covering business software, CRM, and ERP selection for small and midsize US companies. Articles are researched against vendor documentation, published industry standards, and hands-on implementation practice, then fact-checked before publication.
Last updated: September 2026