Industry Insights
ERP AI agents: what a job shop can actually run
Most agents your ERP vendor announced are gated behind a cloud edition you may not license. Four questions to ask before the renewal call.
Most of the AI agents your ERP vendor announced this year are gated behind a cloud edition you may not be on: Epicor stated at Insights 2026 that on-premises customers cannot access the agentic capabilities it demonstrated. Before a job shop evaluates any of it, the questions worth asking are whether the agent is generally available or only demonstrated, whether it runs on the version the shop actually licenses, and where the approval gate sits. BrixIQ takes a different route: it reads the documents (print, PO, cert, invoice) and drafts the work while the shop's people approve it, connected to the ERP a shop already runs, with no cloud migration in the way.
Every ERP a job shop might run announced something with "agent" in the name this spring. The announcements are written for enterprises with a CIO and an integration team. This is the version for an owner or ops manager at a 10 to 150 person shop who got the email and wants to know whether any of it applies.
What is an ERP AI agent, and what is it being asked to do?
Strip the marketing and an agent is software that takes an action in your system rather than answering a question about it. That distinction matters more than any demo. Three shapes are actually being shipped:
- Assistants that answer questions. "What is the status of order 4417?" Useful, low stakes, and not what the keynotes are about.
- Document capture and matching. Software reads an invoice or a PO, matches it against a record, and flags what does not line up. Narrow, concrete, and the most real category today.
- Agents that act on the workflow. Reprioritizing orders, reconciling invoices, committing changes without a person in the loop. This is the shape in the demos, and it is the one that needs a governance answer rather than a wow moment.
The third shape is where the question stops being "does it work" and becomes "who approves what it does." That question does not appear in any launch video.
Can I run these agents on the ERP version I already have?
Often not, and this is the fact no shop-facing page states plainly. At Epicor Insights 2026, Epicor demonstrated agents that autoprioritize expedited orders and reconcile freight invoices against carrier manifests without human intervention. The same analyst coverage of the event (May 26, 2026) records the availability condition: most of these capabilities require Epicor Kinetic Cloud or Prophet 21 Cloud, and on-premises customers cannot access them.
An Epicor partner writing the same month put it just as plainly: Prism, the agent layer, is cloud-native, so on-premises Kinetic users need a path to the cloud first, and release timing for several of the demonstrated agents is not yet confirmed.
None of that is a criticism. Cloud-first is a normal architecture decision, and Epicor published the condition itself. But the operator translation matters: for an on-premises shop, the announced feature is not a feature. It is a migration project with a feature at the end. If your ERP runs on a server in the back office, the honest answer to "can we have the agent" is "after you move," and that changes what the announcement is worth to you.
What is generally available today versus demonstrated on a stage?
The announced list and the shipped list are different lists. It helps to put the two side by side:
| ECI AI Invoicing (JobBOSS2, Deacom) | Epicor Prism agents | |
|---|---|---|
| Status | Announced April 15, 2026, launched | Demonstrated May 2026, release timing not confirmed |
| What it does | Captures vendor invoices, matches to POs, flags discrepancies | Autoprioritizes expedited orders, reconciles freight invoices, more |
| What it commits alone | Posts only invoices that match 100 percent, with review and audit visibility | Demonstrated acting without human intervention |
| Runs on | The JobBOSS2 and Deacom products it was built for | Kinetic Cloud or Prophet 21 Cloud editions only |
The pattern is worth noticing. The agent that shipped is narrow, document-shaped, and stops at a match: it posts an invoice only when everything lines up, and everything else goes to a person. The agents that were demonstrated are broad and act on their own. And to be fair to ECI, a matched-only posting rule is an approval gate, and a well-chosen one. That is what a responsibly-deployed agent looks like.
What does this cost, and why can't I find out?
Probably nothing you can look up. A pricing transparency check of manufacturing software (June 21, 2026, updated July 27) found that of 34 products surveyed, only 14 publish a starting price without a sales call. For ERP and MRP products it was 5 of 10. For QMS, 1 of 6. For MES, 1 of 9.
Opacity matters more for an agent than for a seat. A seat is a known thing at an unknown price. An agent is an unpriced capability on top of an unpriced platform, possibly behind an unpriced migration. Three unknowns multiply.
For contrast, and because checkable numbers are the point of this article: BrixIQ is $995 per facility per month, unlimited users, no setup fee, plus metered usage with a cap the customer sets. The base tier is print reading and estimating; quality, finance, customer portal, and scan center are add-on modules. The product and the price are the same whether it connects to an ERP or serves as the system of record for a shop that has none.
Where should the approval gate sit?
"How autonomous is it" is the demo question. The operating question is: what is this software allowed to decide alone, and who chose where that line sits?
The analyst note from Insights 2026 makes the same point from the enterprise side: it advises identifying who approves agent actions at each step, and observes that pilots which started with adoption rather than governance failed. If that is true for enterprises with an IT department, it is more true for a shop where the office is two people.
BrixIQ's answer is a product constraint rather than a setting. BrixIQ drafts and people approve. Quotes are not sent automatically. Prices are not committed without an estimator reviewing the number. Invoices are not released without a person releasing them. PO mismatches are queued for a human to clear, not auto-resolved.
One shop's own measurements, from Anodizers Inc, and stated carefully because they are one shop's numbers, not a benchmark or an average: PO tracking and validation went from three people spending an hour or more each to automatic with only mismatches queued for a person. Finding a cert went from 40 minutes to under a minute. Notice what stayed human in both: the mismatch decision and nothing else.
The honest counterpoint is that an approval gate costs a person's time. The argument for it is not caution for its own sake. It is that the shop owns the number it sends a customer, and owning a number you never saw is not ownership.
Four questions to ask your ERP vendor before the next renewal
- Is it generally available today, or demonstrated? Ask for the release note, not the keynote.
- Does it run on the edition and version we license, or does it require a cloud migration first? Get that answer in writing.
- What is it allowed to do without a person, and can we move that line ourselves?
- What does it cost on top of what we already pay, in writing, before the renewal is signed?
If the answer to question 2 is "after a migration," there is a follow-up worth asking yourself: what could be fixed without one? The documents a shop runs on (the print, the PO, the cert, the invoice) can be read by software that connects to the ERP you already have, the same way quote turnaround became the place to look first this year, and the same discipline applies to any purchase: evaluate the software beyond the cost-savings slide.
Common questions
Do I have to move my ERP to the cloud to get AI on my documents?
No. The cloud requirement applies to specific vendors' agent layers, on their stated terms. Reading and drafting work from documents does not require your ERP to move anywhere: BrixIQ connects to the system you already have.
Is BrixIQ an AI agent?
Not in the sense the ERP vendors mean. BrixIQ reads documents and drafts the work, and people approve it. It does not price, send, or bill on its own, and that is a product constraint rather than a configuration.
Can BrixIQ replace my ERP?
For a shop with no ERP, BrixIQ can be the system of record, at the same product and price. For a shop running an ERP, it connects to it with no migration required.
What should I do before my next ERP renewal?
Ask the four questions above, in writing. The answers sort the announcements into three piles very quickly: available to you now, available after a project, and not actually released. Most of what you have read about this year sits in the second and third piles.