For distributors running Epicor Prophet 21
Stop quoting away your margin on Prophet 21.
PIE connects to the Epicor Prophet 21 book you already run, reads the trading history in it, and checks every new quote line against your own margin floor before it goes out — then reports the margin that held. Your ERP keeps the records; PIE decides nothing you did not set a policy for.
One sign-in, checked when you save it
A token sign-in as an API-enabled Prophet 21 user, against your middleware's OData views, re-minted hourly and paged 500 rows at a time. The form asks for the middleware URL, that user's credentials and your company code — and, where your site keeps its views under a non-default path or prefix, for those too. The connection is checked when you save it, so a wrong value fails there rather than on the first nightly sync.
What your administrator does first
Two things have to be true before the form connects: the API user is enabled for API access in P21 (Maintain Users → API), and each view above is exposed on the middleware and readable by that user — a view that is not exposed answers 404, which reads like a wrong URL rather than a missing grant. And because a P21 middleware usually sits on your own network, it has to be reachable on a public hostname: PIE refuses a source address that resolves inside a private range, when you save it and again on every fetch.
What the first pull reads
The first pull is offered from the first day of the month 18 months back, and you choose the date before it starts. It runs as a background job that commits as it goes, so you can watch it move rather than wait on a spinner — and what the screens then report is the span the rows actually cover, not the window that was asked for.
Exactly this, and nothing else
The list below is not a summary of the integration — it is the integration. Each line is a permission the Prophet 21 connector declares and a method that reads it, and a test holds the two against each other in both directions, so a capability cannot be claimed here and missing in the code.
- Customerscustomer
- Supplierssupplier
- The item masterinv_mast
- Invoices, with their linesinvoice_hdr · invoice_line
- AP invoices, with their linesapinv_hdr · apinv_line
- Sales ordersoe_hdr
- Purchase orderspo_hdr
PIE writes nothing to Prophet 21
The Prophet 21 connector is read-only: there is no method in it that creates anything, and the platform refuses to send a quote to a Prophet 21 customer rather than pretending it can. A quote is built and approved in PIE and entered in Prophet 21 by whoever enters them today.
What PIE does not read from Prophet 21
- Customer payments are not read from Prophet 21. Payment timing, the collections worklist and days-to-pay have nothing to read on a P21 book, and they say so rather than estimate around it.
- AP invoices booked against PO receipts rather than item lines arrive as payables with no cost lines. Each one is named on the sync report rather than averaged into a cost figure nobody could trace.
- Stock levels are not read from Prophet 21 in this version, so the stock and GMROI screens stay empty on a P21 book.
- Quotes are not imported from any ERP, P21 included, so a win rate has no denominator until you start quoting here.
- Vendor payments are not read from any ERP, so what has actually been paid out is outside what PIE can see on this book.
- Credit notes are not read from Prophet 21 in this version, so a returned or credited line still counts as sold until you say otherwise.
- Salespeople are not imported, so every decision routes to management until accounts are assigned inside PIE.
Three things, on your own numbers
Every figure is deterministic arithmetic over the rows above, stamped with the version of the margin policy that judged it. The AI on this platform reads those numbers and phrases them; it never produces one.
Every quote line, against your own floor
Your P21 invoice and AP-invoice lines are what a floor is computed from: what you sold, to whom, and what it cost you. PIE checks each new line against the policy you set and routes a breach for sign-off — the platform holds it, not the salesperson, and the sign-off is on record.
Margin drift, per customer and item
Computed from the line-level history P21 already holds and compared across windows, with every figure stamped with the version of the policy that judged it. The arithmetic is deterministic and the operands come with it, so any number on the screen opens into the rows it came from.
The accounts that went quiet
Decline is read from the invoice history the first pull brings in, so it works on a P21 book from the first sync — no quotes to record first, no payments needed, nothing to configure.
Why it can be trusted
The AI never computes a single number.
Your Prophet 21 data and your rules determine the number. AI explains it.
Same inputs, same answer, every time — with a paper trail.
- Deterministic calculations — every figure is arithmetic on your own records; turn AI off and every number still works
- Auditable decisions — each number names the policy that produced it, so a price you quoted last quarter still explains itself
- Your data — read from your own books, used for you alone, exportable and erasable on request; AI runs on your own account
- Your rules — you set the floors and thresholds, and PIE holds every quote to them
- Provenance — every row carries the connector, the connection and the id it came from, so nothing in PIE claims a source it did not have
Your Prophet 21 book already knows where the margin went.
30–45 minutes, your own numbers on the screen, and an honest answer about what PIE can and cannot see in Epicor Prophet 21.