Epicor just shipped the most significant AI agent update in manufacturing ERP history. Prism agents execute work directly inside Kinetic. But the quoting module still relies on manual data entry and does not read CAD files. Here is the gap.
Prism overview
At Epicor Insights 2026, the company unveiled the most aggressive AI agent strategy in manufacturing ERP. Epicor Prism is a network of vertical AI agents that execute work directly inside Kinetic, Prophet 21, and Propello. President Vaibhav Vohra positioned Cognitive ERP as six capabilities: Industry Data Model, Vertical Agents, LUX Agentic Design System, Agent Foundry, Headless ERP, and Time to Value.
The Prism Knowledge Agent already processes over 70,000 requests per month, according to TEC's analysis of Epicor Insights 2026. Prism agents were demonstrated performing real tasks: generating sales orders via natural language, auto-setting order priority when expedite dates change, and reconciling supplier invoices with purchase orders. Epicor claims to be the first ERP company to ship all six capabilities simultaneously.
The Prism Agent Foundry is the most strategically significant piece for the quoting workflow. It is a marketplace where customers and partners can build, verify, and share their own AI agents inside the Epicor ecosystem. Kramer & Co described it as "a marketplace play that could meaningfully expand Epicor's stickiness if adoption follows." For quoting, this is a direct integration path.
Agent Foundry
The Agent Foundry marketplace is built for exactly the kind of scenario a quoting front-end addresses. Epicor has built agents for order management, invoice reconciliation, and business communications. But it has not built a quoting agent that reads CAD files and performs dimensional takeoffs.
This is not an oversight. Epicor's strength is order-to-cash workflows for established product lines. The Epicor Kinetic quoting module is designed for organisations that sell configured products: items with defined BOMs, standard pricing, and established production routing. For the job shop that receives an RFQ with a CAD file of a part they have never machined before, the Kinetic quoting module requires manual data entry of every dimension, material spec, and process step.
The ERP quoting module limitations Epicor shops article covers why the Kinetic quoting module creates a 2-5 day quoting cycle for complex RFQs. The estimator must manually extract data from CAD files, transcribe it into the quote form, calculate costs, and enter pricing. This all happens within an ERP module designed for structured product data, not one-off job shop quoting.
Quoting gap
The gap is specific and measurable. Epicor Kinetic can manage the entire quote-to-cash process once structured data is in the system. It can apply pricing rules, calculate margins against standard costs, generate sales orders, and track fulfilment. What it cannot do is convert an unstructured incoming CAD file into the structured data it needs to start that process.
CADLink, Epicor's integration with QBuild, bridges CAD data into Kinetic BOM and Item Master records. But it is designed for product data management in engineering-to-order workflows: a CAD engineer creates a part, and CADLink pushes that part data into the ERP. It is not designed for the job shop estimator who receives a customer's CAD file and needs to quote the one-off part. CADLink assumes the part already exists in the design system, not that the estimator is pricing a part they have never seen before.
Epicor Prism Business Communications is an ERP AI agent with outcomes-based pricing that improves RFQ workflow, but its focus is on the communication side of RFQs (converting RFQs to POs), not on the CAD takeoff and estimating side. The quoting gap remains: no CAD file processing, no dimensional extraction, no historical part matching.
Integration path
The Agent Foundry creates a clean integration path. A quoting front-end like Kwantflow processes CAD files locally on the estimator's machine, extracts dimensional data and geometric features, matches against historical jobs, and generates structured estimate data. That structured data, which includes material list, cycle times, setup costs, tooling requirements, and markup feeds directly into Kinetic's quoting module via the Prism agent framework or MCP protocol.
This is a fundamentally different integration from CADLink or standard API connectors. The estimator does not leave their quoting tool to use the ERP, and does not leave the ERP to use a separate quoting tool. The quoting front-end acts as an agent inside the Epicor ecosystem, handling the CAD-to-estimate step that Kinetic cannot do itself.
For shops evaluating Kinetic upgrades in 2026, this matters because the ERP buying decision has changed. The signs your quoting process needs fixing guide helps shop owners identify whether their quoting bottleneck is the ERP module or the workflow before it.
Integration depth
The integration goes deeper than pushing estimate numbers. A well-integrated quoting front-end sends back the structured data Kinetic needs for production: estimated cycle times per operation, material requirements with supplier pricing, tooling specifications, and outside processing costs. The estimator creates the estimate once, in their quoting tool, and the ERP uses that data without re-keying.
This matters for margin accuracy. The cloud vs local estimating for Epicor shops comparison explains why a local-first quoting front-end that integrates with Kinetic preserves data sovereignty while delivering structured estimates faster than manual entry.
For shops running Epicor Kinetic on-premise or in the cloud, a local-first quoting front-end that feeds estimates through the Prism agent framework means CUI-sensitive CAD files never leave the estimator's machine. This is especially relevant for defence shops where the November 10 CMMC Phase 2 deadline makes cloud CAD processing a compliance concern.
Market timing
The timing of this opportunity is unusually clear. Epicor launched Prism at Insights 2026 just weeks ago in May. The Agent Foundry marketplace is open for partners. The Prism Business Communications agent already charges outcomes-based pricing for RFQ-to-PO conversion. The infrastructure for a quoting agent integration exists and is actively seeking partners.
For Epicor Kinetic shops, the upgrade cycle creates a natural decision point. Shops moving to Kinetic or evaluating the Prism platform in 2026 are already asking whether the ERP can handle their quoting workflow. The answer from the Epicor forum discussions is consistent: the quoting module handles configured products well, but one-off RFQ intake remains a manual process. A quoting front-end that integrates through the Agent Foundry fills this gap without requiring the shop to abandon Kinetic or adopt a separate cloud quoting platform.
The signs your quoting process needs fixing diagnostic helps shop owners determine whether the bottleneck is their ERP module or the intake workflow before it.
What is missing
Epicor's Cognitive ERP announcement is genuinely impressive. Six simultaneous capabilities, a functioning Agent Foundry marketplace, headless ERP via MCP, and an agentic design system (LUX) are real products, not vaporware. The Prism Knowledge Agent's 70,000 monthly requests prove real adoption.
What is missing is the quoting-specific agent that reads CAD files. Epicor has built agents for order management (Prism Order Agent), invoice reconciliation (Prism AP Agent), and business communications (Prism Business Communications). None of these touch the defining challenge of job shop quoting: converting an unstructured CAD file into a priced estimate. The Prism Agent Foundry is designed for partners to fill exactly this kind of gap.
For Epicor Kinetic shops, the practical question is whether the Prism platform reduces their quoting cycle time today. The answer is: not yet, not for the CAD-to-estimate step. The agents help once structured data is in the ERP, but they do not help get it there. That is the gap a quoting front-end fills.
What it means
For shop owners evaluating whether to upgrade to Epicor Kinetic or adopt the Prism platform, the quoting gap has a clear implication: the AI agents will not fix your quoting bottleneck. The Prism agents handle order management, invoice reconciliation, and business communications. They do not handle CAD takeoff, dimensional extraction, or historical part matching.
The opportunity is to build the quoting front-end that feeds into the Prism ecosystem. A local-first quoting tool that processes CAD files on the estimator's machine and sends structured estimates to Kinetic via the Agent Foundry gives the shop the best of both worlds: local IP security with enterprise ERP integration.
<a href="/platform">Explore Kwantflow platform features</a> for Epicor Kinetic integration. Your quoting tool should talk to your ERP.
Ways estimators can keep quote review clear:
- Epicor Prism ships six cognitive capabilities simultaneously including vertical AI agents, an Agent Foundry marketplace, and headless ERP via MCP protocol.
- Prism agents can generate sales orders, auto-prioritise orders, and process 70,000+ Knowledge Agent requests per month, but cannot read CAD files or perform quoting takeoffs.
- The Prism Agent Foundry is a marketplace where Kwantflow could integrate as a dedicated quoting agent that processes CAD locally and feeds estimates to Kinetic.
- Epicor quoting module still requires manual data entry for dimensional data, material specifications, and process planning. This is the same structure it has had for years.
- CADLink bridges CAD and Kinetic BOM data but is designed for product data management, not for one-off RFQ intake and quoting.
