From Vertical AI Strategy to Production Commitments: Epicor at Insights 2026

From Vertical AI Strategy to Production Commitments: Epicor at Insights 2026

Field Preview / Enterprise Analysis 7 minutes 2026-05-02
Enterprise ERP · Field Preview
This is the second in a series on vertical AI strategy in enterprise ERP. The first covered Epicor's approach ahead of Insights 2026. Three things have shifted in the Epicor story since November: a defined cloud migration timeline, outcomes-based AI agent pricing, and carbon accounting built into the manufacturing core. Nashville is where all three get their first large-scale customer test.
75 of 100 Top Building Supply Companies on BisTrack Epicor Insights, vendor-supplied figure
9,000+ Hardware & Retail Stores on Epicor Epicor Insights, vendor-supplied figure
Jan 2028 Final Kinetic On-Premises Feature Release Epicor press release, January 6, 2026
55% Repeat Purchase Rate Lift, Propello Loyalty Epicor Insights customer award, vendor-supplied figure
Key Takeaway

In November 2025, the Epicor story was vertical AI strategy and a modular architecture built for mid-market manufacturers. By May 2026, that story has three new chapters: a published cloud migration timeline every on-premises customer must now plan around, an AI agent priced on procurement outcomes rather than access, and carbon cost roll-up embedded in the ERP ahead of regulatory requirements most mid-market manufacturers have not fully mapped yet.

In November 2025, I wrote about Epicor's vertical AI strategy and what made its modular architecture a practical fit for mid-market manufacturers who need to modernize without the disruption of a full platform rebuild. The core argument held: industry-specific data structures, people-centric AI, and phased adoption designed for resource-constrained operators. Six months later, the architecture story is the same. What has changed is the surrounding context, and three developments since that post have shifted what I am watching at Epicor Insights 2026 in Nashville.

The conference runs May 18 through 21 at the Gaylord Opryland Resort and Convention Center. Nearly 4,000 customers are expected, representing manufacturing, distribution, building supply, and retail — industries where Epicor's market position is deeper than casual ERP coverage suggests. For BisTrack and Lumber Track customers, this is the 18th consecutive year of these events. The first was held in 2007 with 60 attendees; some of those same customers are still in the room today.

The Market Penetration Numbers Deserve More Attention

Before getting to what is new, the vertical position numbers are worth stating plainly: 75 of the top 100 building supply companies run BisTrack, 55 of the top 100 softwood lumber companies run Lumber Track, and more than 9,000 hardware and retail stores operate on Epicor platforms. Vendor-supplied figures, but the customer award recipients at Insights events put texture on them — a distributor in business since 1798, a 120-year-old building supply company, a family business in its 65th year, a 23-year Epicor customer with 70 retail locations.

Businesses do not stay on an enterprise resource planning platform across generational ownership changes unless the software fits how they actually operate. That customer tenure is the structural argument for Epicor's position in these verticals, and it is the foundation on which every product announcement in Nashville sits.

The Cloud Timeline Is Now Fixed, and That Changes the Planning Conversation

In January 2026, Epicor published final on-premises feature release dates for Kinetic (tentatively January 2028), Prophet 21 (May 2028), and BisTrack (BisTrack Web Browser and API in July 2028, BisTrack Desktop as early as December 2026). Future innovation moves exclusively to Epicor Cloud after those dates. Active support and then sustaining support phases follow, but new capabilities — including everything in the artificial intelligence stack — are cloud-only from here.

This is not a cliff. Epicor has been deliberate about providing transition time, and the Ascend migration program offers readiness assessments and tooling to help customers through the move. What it does change is the planning horizon for every on-premises customer in the room at Gaylord Opryland. The question shifts from whether to migrate to when, and under what conditions the migration delivers the operational continuity those businesses depend on.

The customers who built their operations around Epicor's on-premises platforms did so because the software met them where they were. The Ascend program is Epicor's commitment to make the cloud transition work the same way.

For mid-market operators — manufacturers in the $20 million to $150 million revenue range, distributors managing complex inventory across multiple locations — the migration question is not purely technical. It is an operational continuity question. Nashville is where I expect to hear mid-migration customer evidence alongside the completed case studies, and where the Ascend program's practical effectiveness gets its most visible test.

Prism Business Communications Changed the AI Pricing Model

When I wrote about Epicor Prism in November, the general availability announcement at Insights 2025 in Las Vegas was the headline. Prism's network of vertical artificial intelligence agents — covering more than 200 use cases across finance, production, customer service, and operations — was positioned as a system of action built on 50 years of industry-specific data structure. That positioning still holds.

What arrived in September 2025 was a significant commercial extension: Epicor Prism Business Communications, the first ERP artificial intelligence agent with outcomes-based pricing. Customers pay only for request for quotation workflows that convert to purchase orders, not for access or usage. The agent automates the full request for quotation cycle — parsing supplier email responses, comparing multi-supplier multi-part scenarios, flagging missing data and inconsistencies, surfacing recommended next steps — without requiring separate portals or predefined templates.

The pricing structure is analytically meaningful. Outcomes-based pricing on an enterprise software feature is rare. It means Epicor is confident enough in the procurement cycle reduction to absorb the risk that customers who don't see results don't pay. For a customer base that has historically measured ERP value in operational outcomes rather than feature counts, that alignment of incentives is a more credible signal than a capabilities list.

Prism Capability What It Does Evidence or Pricing Model
Knowledge Agent Natural language retrieval from Epicor Learning and internal document bases Madsen's Custom Cabinets: IT saves 3 to 4 hours per week on employee questions (vendor-supplied)
ECM Agent Surfaces contract terms and procedural content from Enterprise Content Management Olympus Group: 5 to 10 minutes saved per document retrieval; 20% on-time delivery improvement projected (vendor-supplied)
Prism Business Communications Automates full request for quotation cycle from supplier email through purchase order creation Pay per converted purchase order — no conversion, no charge
Automation Studio Low-code custom agent development, powered by Workato Enables custom agent creation without dedicated engineering resources
Grow AI / Item Advisor Demand forecasting and related-item recommendations surfaced during order entry Direct revenue opportunity for distributors managing large product catalogs

Carbon Accounting in the ERP Is Ahead of Where Most Mid-Market Manufacturers Are

The Kinetic capability that has received the least coverage relative to its strategic value is carbon cost roll-up, currently patent pending. It treats carbon emissions as a cost currency inside the manufacturing process, using existing bill of materials and routing data to calculate the carbon content of every product shipped. The latest release adds full carbon accounting into statistical accounts in the general ledger — capturing carbon consumption as part of standard financial reporting rather than in a separate sustainability tool.

European Union carbon reporting requirements are already in force for large manufacturers. California is advancing similar mandates. Mid-market manufacturers that supply larger enterprises will face carbon reporting requirements from their customers before regulators reach them directly. Epicor's approach embeds the calculation in the data that manufacturers already maintain inside Kinetic — production schedules, materials, routings — which reduces the audit and reconciliation work that comes with maintaining carbon data in a system separate from operations.

For Nashville specifically, this capability is relevant to manufacturing customers supplying into regulated export markets or large enterprise supply chains that are already under reporting pressure. It is a capability most of them will need; fewer of them know it is already available in their ERP.

Propello's Loyalty Data Shows What Vertical Fit Produces

Epicor Propello, the company's cloud-based retail management platform, surfaces one of the clearest customer outcome stories in the portfolio. A 65-year family-owned garden center that migrated to Propello built an in-platform loyalty program. Since launch, more than 8,000 customers have enrolled. Repeat purchase rates among loyalty members are up 55 percent, and loyalty members spend 15 to 21 percent more than non-members — all vendor-supplied figures, presented at Epicor Insights with the customer on stage to accept an award.

That specificity matters. A mid-market retailer generating measurable loyalty lift from a capability embedded in its ERP platform — without a separate loyalty vendor, integration project, or data reconciliation layer — is the practical case for vertical software done well. It is also the kind of customer evidence that travels well in peer conversations at a conference, which is where a significant portion of ERP purchasing decisions actually get influenced.

What I Am Going to Nashville to Find Out

The three developments since November — cloud migration timeline, Prism Business Communications pricing, and carbon cost roll-up — each represent a product commitment that Nashville will either validate or complicate with customer evidence. I am most interested in the Ascend migration stories from operators mid-transition, not post-completion. And I want to understand whether the carbon accounting capability is being actively positioned to manufacturing customers with export exposure, or whether it is sitting undiscovered in the product catalog.

The connected worker investments — Acadia for documentation and certification, Connected Process Control for shop floor consistency — are the thread I wrote about in November that deserves a Nashville update. Data from the U.S. Bureau of Labor Statistics shows 22.5 percent of U.S. workers have been in their current job for less than a year. For manufacturers, that turnover rate makes knowledge retention an operational priority, not an HR one. A year into those acquisitions, Nashville should produce customer evidence of what that investment has actually delivered on the shop floor.

I will be publishing from Nashville at shashi.co as the conference develops.

Key Takeaway

The vertical AI architecture I wrote about in November is now operating inside a more defined commercial framework: a cloud migration timeline that gives on-premises customers a planning horizon, AI agent pricing tied to procurement outcomes rather than platform access, and carbon accounting embedded in the manufacturing core ahead of regulatory requirements. Nashville is where those commitments meet 4,000 customers who will test them against their own operations.

CIO / CTO Viability Question

If your organization runs Epicor on-premises, the Ascend program is worth a formal readiness assessment before Nashville, not after — the migration timeline is fixed, and the customers who start the planning conversation early have more options than those who begin under deadline. If you are already on Epicor Cloud, the more important question is whether Prism Business Communications' outcomes-based pricing model is mapped to your highest-friction procurement workflows, and whether your team knows that

Disclaimer: This blog reflects my personal views only. Content does not represent the views of my employer, Info-Tech Research Group. AI tools may have been used for brevity, structure, or research support. Please independently verify any information before relying on it.