Epicor Prophet 21 is an enterprise resource planning (ERP) system built for wholesale distribution.
It is one of the most common ERPs among the distributors we work with, because it does the job it was built for very well: recording every order, invoice, and payment accurately, reconciling inventory across branches, holding contract pricing per customer and per item, and converting units of measure between how you buy and how you sell.
This is unglamorous, load-bearing work. P21 does it for distributors at scale.
But P21 is a backend system. It records what happened, and for many distributors it's the single source of truth.
Its transactional core was built for operational and financial work—not to give every rep a ready-made view of what changed, what matters, and what to do next.
Some of your reps may not have ERP access at all. The ones who do often can't reach it from the road. On ride-alongs, we've watched a rep pull a laptop out in a customer's parking lot, hotspot off their phone, login, and work out what to talk about before walking in.
P21 records the business through operational entities. It tracks orders, invoices, items, bill-to accounts, and ship-to locations. Reps who want to understand a single customer may have to connect several records, reconcile the account structure, and add sales activity from CRM or elsewhere. The data may be in there, but the answer isn’t in a single field or on a single screen.
Some sales questions are about a single account. Others only become visible across a territory. Which of your 800 customers stopped reordering something they used to order every two weeks? Which ones buy pipe from you and fittings from someone else? Which accounts has nobody called this quarter?
The evidence a rep needs may already be in P21’s transaction history. But answering a territory-wide question requires a defined account rollup, product hierarchy, comparison logic, and sometimes activity data from a different system altogether. Assembling and interpreting it takes a lot of work.
It means connecting the pieces together in a central brain.
That's what we built Proton to do. Below, a full guide to P21.
TL;DR
- Prophet 21 is a system of record for orders, inventory, pricing, purchasing, and finance.
- It holds more than most distributors realize: years or decades of buying behavior at line-item resolution, for every account, including the ones nobody has called.
- Single-account visibility matters, and so does the view across your whole book. A book-level view helps surface three patterns: Churn signals, wallet share gaps, and accounts nobody has called.
- P21 has a CRM module. It stores contacts, accounts, and the activity your team enters. A CRM record is not the same as a prioritized workflow that tells each rep where to focus and what to do next.
- Getting the data out is only the first step. What happens next determines if anything changes.
What is Epicor Prophet 21?
P21 is Epicor's ERP for wholesale distributors. It runs inventory, purchasing, order management, pricing, and financials. It was built for distribution from the start rather than adapted from manufacturing, and that shows up in the details: multi-branch inventory, customer-specific pricing, unit of measure conversion, and order entry a counter or inside sales team can actually run.
The core modules distributors typically run:
- Inventory management. On-hand across branches, replenishment, min/max, branch transfers
- Order management. Quotes, sales orders, backorders, returns
- Purchasing. POs, vendor management, receiving
- Warehouse management. Picking, packing, directed workflows
- Pricing. Customer-specific pricing, price books, price matrices
- Financials. AR, AP, GL, the month-end close
- CRM. Contact and account records, activity tracking
- Mobile sales. Field access to inventory and account data
P21 can serve as the authoritative record for the operational and financial transactions captured in it.
What information does Prophet 21 actually hold?
There is data that accumulates as a byproduct of transacting, and data that must be maintained.
Data that accumulates: Every order line, with quantity, price, date, and who placed it; every invoice; every price you've actually charged a customer; branch-level inventory movement and availability; payment history; every quote your team entered in P21, including the ones that never converted.
Data somebody has to maintain: contract terms and price matrices; product hierarchies, the item master, and cross-references between items; contact records; sales rep assignments; and credit terms.
Robust product data can be hard to come by, as descriptions are lifted from varying sources that may or may not be complete.
But understanding the data and acting on it are completely separate things.
Why is an ERP a backend system?
An ERP acts as your source of truth.
Epicor's P21 is built on Microsoft SQL Server. Its transactional core keeps operational records consistent while teams process orders, receipts, inventory movements, and payments.
That structure makes P21 reliable for operational records. Book-wide analysis is a separate workload, handled through reports, analytics tools, read-only replicas, or connected applications rather than transaction screens.
Figuring out what a rep should do with this data is a separate question. It requires defining what normal looks like for each account or peer group, identifying meaningful changes, and ranking opportunities by value and urgency.
What about Epicor Data Analytics (EDA) or reporting tools?
Epicor offers Report Studio and Epicor Data Analytics (EDA). Report Studio supports operational reporting, while EDA provides dashboards and drill-down analysis of P21 data.
The pattern distributors describe to us is consistent. They buy the tool, reps don't use it because reps aren't analysts, so they hire an analyst to build the reports instead. Report requests then queue behind everything else that analyst owns, and once the reports do land, nobody can say whether any of it gets acted on.
Traditional BI tools stop short of execution. They can surface patterns and exceptions, but someone still has to decide who needs a call and what to do next. A system of action takes the busywork out of work: call this customer today, mention this missing category, quote this contract price.
A BI layer on top of P21 gives leadership better visibility, but someone still has to interpret the output and act on it. Salesforce’s fifth State of Sales report found that reps spent 28% of an average week selling. The rest went to deal management, data entry, planning, meetings, training, and other work.
Proton comes with the ability to build reports out-of-the-box, so nothing queues behind an analyst. Then it goes where reporting stops: each rep gets the customer to call and the reason to call them.
What does your P21 data already know that your reps don't see?
Four patterns show up consistently across the distributors we work with. P21 can hold much of the evidence behind them. Turning that evidence into an answer depends on how the data is structured and analyzed.
1. Churn signals begin in transaction history, but they need to be visible to reps. Here’s an example: a customer ordered every two weeks through the winter and is now sixty days out. Their pattern has broken. No rep can monitor 800 accounts by hand, so the change may go unnoticed until the revenue is already at risk.
2. Some accounts underbuy whole categories. A customer buys pipe from you and fittings from someone else. Identifying where an account may be buying elsewhere requires comparing its category mix with similar customers. P21 can supply the transaction data, but the comparison has to be defined and run somewhere.
3. Order history exists for accounts that receive little sales attention. P21 shows what each account buys, while CRM activity shows who has been contacted. Putting the two together reveals accounts that are buying without active sales coverage.
4. “Normal” depends on the account. A 20% drop may be a crisis for one customer and seasonal for another. The comparison may come from the account’s own history or from similar customers. P21 can supply the data, but the benchmark has to be defined.
P21 can hold the evidence, but it still has to be interpreted across the book while there is time to act.
Right now, your reps are the glue holding information together
Distributors have spent years using people to hold their systems together.
A rep opens P21, reads one account, remembers what the last conversation covered, checks a spreadsheet a manager sent over, and assembles a picture of the customer in their head before dialing. That assembly is the integration layer. It runs on memory and effort, and it leaves when the rep retires.
For a long time, this order-taking approach to sales made sense from the inside. Reps work from whatever they can pull together fast enough, so the accounts that call get served.
But it’s a huge time sink. And it eats up margin and costs that could go to better use. What's missing is software that reads all 800 accounts overnight, decides what matters, and puts it in front of a rep before their first call. None of this requires replacing your ERP. P21 stays the system of record.
Proton takes the busywork out of work and becomes your favorite new colleague. It’s the new glue for your systems.
So what should sit on top of your ERP?
Epicor supports several ways to integrate with P21, including APIs and read-only SQL access. The right path depends on what data the integration needs and whether it must write back to P21.
How much work any of this is depends on your deployment, your version, and your licensing, so scope it with your IT team before anyone commits to a timeline.
Five things worth considering before you sign up for any new software:
Does it read across accounts, or just display them? A tool that shows one account at a time in a nicer interface has rebuilt your ERP with better fonts. The value is in the comparison: this account against similar accounts, this month against its own pattern.
Does it produce a decision or a dataset? A clean data feed is a data project. A dashboard that has to be interpreted isn’t the same thing as a specific recommendation for a customer with the reason attached.
Does it keep P21 data current throughout the day? Ask how often the system refreshes pricing and inventory, and what happens before a quote or order writes back. “Real time” should describe a specific data path, not a general promise.
Does it cover accounts that receive less attention? The highest-value accounts are usually already visible. The opportunity may be in the middle of the book, where buying patterns exist but sales coverage is thinner.
Does the ERP stay the system of record? Everything transactional stays in P21. Anything that starts absorbing ERP functionality builds a second source of truth, which is the problem you were solving.
How Proton works with Prophet 21
Proton makes the data held in P21 easy for your reps to use with proactive recommendations about next steps.
People stop being the glue between systems, freeing them up to do better, more interesting work. Proton becomes everyone’s favorite colleague, recommending the next best action and working across all internal systems for a full business view.
Proton connects to P21, then puts agents to work across sales, pricing, purchasing, inventory, and accounts receivable. That happens in three steps.
Connect in real time. Ongoing data retrieval runs on P21's APIs, keeping your data current throughout the day so your team and Proton's agents work from the latest information. Historical loads move by secure file transfer or API, and writeback into P21 is configured separately based on your P21 environment. Those are different mechanisms, and any vendor should tell you which is which.
Build business context. Proton organizes records and relationships from P21 and your other systems, so your team and Proton's agents can actually use them.
Put agents to work. Proton reads P21 transaction history alongside the rest of your business data, then gives each rep a focused call list before the day starts. Each recommendation explains why the customer needs attention, from a broken reorder pattern to a category they may be buying elsewhere. A rep builds a quote or enters an order inside Proton against your real contract terms and never rekeys it into P21 afterward. Agents automate work in pricing, purchasing, and accounts receivable across your internal systems.
Proton is SOC 2 Type II certified, GDPR compliant, and CCPA ready, with SSO and MFA.
P21 stays the system of record. Everything transactional stays where it belongs. Distributors are the only customers we serve.
To see how Proton works with P21, book a demo.
