Your QAD system,
finally speaking
plain English.
qadAI is Either answering questions about QAD in general, like module behavior, error codes, how a transaction is supposed to flow, OR about the exact data sitting inside your own QAD environment, cited back to the record it came from.
qadAI works with any QAD version. Extra benefit if you are on a version, QAD itself has stopped investing in, here's an AI layer that adds modern capability without forcing a disruptive migration.
Two things to ask it
Some questions are about how QAD works. Some are about how your QAD is behaving right now. qadAI handles both, and it's always clear which kind of answer you're getting.
Ask about QAD itself
Error codes, module behavior, how a document is supposed to move through MFG/Pro or QAD Cloud ERP — answered from documentation and support history, without touching your database.
- What does reason code SEG-ERR-2110 actually mean?
- What's the difference between a firm and planned MRP order?
- What fires an 856 versus an 810 in a drop-ship flow?
Ask about your QAD
Connected read-only to your own QAD or Progress OpenEdge database, so the answer comes from your actual transactions, exceptions, and history — never a guess, always sourced.
- Which MRP exceptions today actually need a human?
- How many pallets cleared receiving on second shift?
- Which trading partner rejected the most ASNs this month?
The questions that eat your day
These are the tickets that usually land on whoever knows QAD best. qadAI takes the first pass.
EDI reject triage
Groups 856/810 rejections by partner and reason code, so you fix the segment mapping once instead of re-sending the same ASN four times.
MRP exception noise
Separates the exceptions that change a shipment date from the ones that are just planning catching up with itself.
WMS & pallet counts
Shift totals, dock-to-stock timing, and forklift throughput questions, answered without opening a report builder.
New hire QAD questions
The "how does this module actually work" questions a new planner or CSR would otherwise ask a senior teammate five times a day.
How it connects
Set up once by someone who's spent years inside QAD and Progress OpenEdge — not a generic connector.
Connect, read-only
qadAI reads from a replica or a read-only credential on your QAD database. It never has write access — not during setup, not ever.
Ask in plain language
Type the question the way you'd ask the person next to you. No report names, no table joins, no query language.
Get a sourced answer
Every answer that touches your data names the table, the date range, and the records behind it, so you can check it in a click.
Read-only, on purpose
The architecture is built around one rule: qadAI can look, and it can never touch.
No write path exists
The connection is provisioned as read-only at the database level, not just disabled in the app. There's no code path that can issue a write.
Built for Performance
Your own separate server, not interfering with QAD servers. Replication either with underlying Progress OpenEdge database, or QAD Cloud ERP.
Scoped to your environment
Each deployment is configured for one company's QAD instance. Nothing is pooled, shared, or used to answer anyone else's questions.
Bring qadAI to your QAD environment
Tell us how your QAD is set up — MFG/Pro, QAD Cloud ERP, whatever's under it — and we'll show you what it looks like connected to your own data.