// Prophet 21 · Sales order automation
P21 Order Entry, drafted from the POs your inside sales team already keyed.
For distributors whose reps key emailed and PDF POs into the Order Entry window in Prophet 21. From copies of 20 to 30 of those POs, AI drafts each order: customer, ship-to, PO number, lines, and what happens to a line the branch can't fill. Your reviewer, the person on your team who knows P21 order entry best, checks every draft against the order in P21. We never log in to P21.
- Keyed POs
- 20 to 30
- P21 users we need
- None
- Before anything moves
- An NDA
// The one job
From an emailed PO to an order in P21, drafted for review
A rep opens Order Entry, starts the order for the customer, picks the ship-to, types the PO number and adds the lines. Some POs answer a quote already sitting in P21. Others ask for items the branch doesn't have, so the rep chooses between a backorder, a direct ship from the vendor and a transfer from another location.
For the test, AI does that reading on copies of POs your team already keyed and drafts each order the way P21 holds it, header first, then each line with its disposition, giving a reason for every choice. It enters nothing in P21. Your reviewer then goes line by line, draft against order, and marks every field that differs.
P21 order terms
// Inside Prophet 21
Where P21 order entry asks a rep to decide
The header: customer, ship-to, PO and taker. An order in P21 starts with the customer, then the ship-to, the customer's PO number and the taker, the rep who entered it. Customers sometimes want one order sent to a job site instead of their default ship-to, and Epicor's training shows that change made on the single order, along with one-time delivery instructions. When a PO says same as last time, reps reach for the Previous Requests tool to pull items off earlier orders. The draft picks a Ship To ID when the address matches one you export, marks job-site addresses and delivery notes as changes for this order only, and pulls repeat items from the order history you send.
Quotes live in the same window. P21 builds a quote in Order Entry, the window that holds orders, and a rep turns it into an order with Convert to Order on the right-click menu. Reps can also copy a quote from one customer to another, so near-identical quotes can sit under several accounts, and a PO that says per our quote has to be matched to the right one. The draft points to the quote it believes the PO answers, shows each line that drifted from it on item, quantity or price, and leaves Convert to Order to your rep.
Approval and credit hold come before the warehouse. Epicor's own videos describe two gates. A company can require that orders be reviewed and approved before the warehouse picks them or anyone invoices them. And when a customer goes on credit hold, every one of that customer's orders goes on hold too, until someone validates the open orders and stock is allocated again. Some P21 shops add business rules of their own on top, such as a manager's approval for certain product groups, and reps attach notes to the order header or a single line for the warehouse or billing to read. Each draft names the gate it would hit, and it carries the PO's instructions as header or line notes.
Short on stock: a PO, a transfer or a backorder. When the branch can't fill a line, P21 lets the rep act from Order Entry itself: create a purchase order to the vendor, or create a transfer from another location on the fly. Each line carries a disposition code; D, for example, marks a direct ship from the vendor. Which one your team picks turns on the customer, the date and the vendor, none of it printed on the PO. The draft suggests the disposition your team chose on similar lines in the sample, labels it as a suggestion, and never raises a purchase order or a transfer.
Prices, revised POs and what your reviewer watches. P21 prices a line from price pages, which reach a customer only through a price book in a price library, and each page can carry an effective date and an expiration date. A buyer quoting last quarter's number may be right about the past and wrong today, and reps check where a number came from in Sales Pricing Inquiry. Revised POs bring their own trap: canceling a line and deleting it differ in P21, and depending on settings a canceled item can still print on pick tickets and invoices at a quantity of zero. Your reviewer looks hardest at dispositions, ship-tos and dropped lines, because those reach the warehouse floor and the customer's invoice.
// What you send
Exports from P21, never a P21 user
20 to 30 keyed POs with their orders
Each PO as the customer sent it, with the order your rep saved, exported with header, lines and dispositions. A PO that answered a quote and one with a direct-ship line belong in the sample.
Items, customer part numbers and ship-tos
Your item list with units, the customer part numbers for the accounts in the sample, and their Ship To IDs and addresses. Spreadsheet exports are fine.
Quotes, prices and the rules behind them
The quotes those POs answered, a price export or Sales Pricing Inquiry printouts for the sample lines, and your approval and credit hold rules written in plain words.
An NDA, and no P21 access
The NDA is signed before any file moves. We never get a P21 user, a web client login or a key to its APIs. If POs must stay inside, your reviewer helps us build look-alikes with the same problems in them.
// Before it starts
Agreed with the owner before any PO is shared
The owner settles these with us first, so the test is scored on rules set in advance.
- Your reviewer
- Named by the owner, usually a senior inside salesperson or the order desk lead
- Success criteria
- Written: which header fields, lines and dispositions must match
- Sample
- Chosen by your reviewer, with quotes and direct ships in it
- Price
- A range for running it live
- NDA
- Signed ahead of the first file
// How it's judged
The rep's order on one side, the draft on the other
| Checked on the same 20 to 30 POs | What your rep saved in P21 | The AI draft |
|---|---|---|
| Customer ID, Ship To ID and PO number | From your POs | From your POs |
| Job-site addresses and one-time delivery instructions | From your POs | From your POs |
| The quote each PO answers, and lines that drifted from it | From your POs | From your POs |
| Item ID found from the customer's part number | From your POs | From your POs |
| Disposition on lines the branch couldn't fill | From your POs | From your POs |
| Unit price against your rep's entry and the price export | From your POs | From your POs |
| Orders that would need approval or sit on credit hold | From your POs | From your POs |
| Lines canceled or deleted after a revised PO | From your POs | From your POs |
// After a yes
A month of new POs, each one approved by a rep
When the drafts meet the success criteria, the job runs on incoming POs for about 30 days.
A rep approves, edits or turns back every draft before an order exists in P21, and dispositions, purchase orders and transfers stay their call. Your P21 administrator decides how approved drafts get in: keyed by a rep, or brought in through import tools your company already has. The same scoring sheet stays in use for the month.
// Later, one at a time
What could follow in a P21 shop
- 01Next
Quote requests
RFQs from contractors and buyers drafted as quotes from your item list and price exports, for a salesperson to finish in P21.
- 02Then
Direct-ship follow-up
Vendor confirmations and tracking for direct-ship lines matched to the customer's order, with late or short lines marked for the rep.
- 03After that
Orders on credit hold
Held orders summarized for your credit manager with the customer's open balance and recent payments, so a person can decide what to release.
// By industry
The full job page for your industry
// One hard limit
Nothing is keyed into P21, and we never sign in to it.
The proof of concept reads copies and exports and returns drafts on a review sheet. We hold no P21 user, no web client login and no API access, and we claim no integration, partnership or certification with Epicor. Prophet 21 is named here only because your team runs it. Epicor and Prophet 21 are trademarks of Epicor Software Corporation.
One job, one price: a range before the proof of concept, a fixed price before you sign.
What sets the range: how many POs your reps key into Order Entry each month, how many answer a quote, and how many lines need a disposition decision.
// Questions
Questions from P21 order desks
Is this a P21 add-on or an Epicor integration?
Our reps convert quotes all day. Does the test cover that?
Will a draft decide on backorders, direct ships or transfers?
We have business rules and order approval turned on in P21. Do the drafts know?
Could approved drafts load through P21's own import?

Rob Eason, founder
// Book a call with Rob
Pull 30 POs your reps keyed into P21, then book the call.
Half an hour with Rob. Booking asks for your company and your role, the job you'd test, and roughly how many POs your reps key into P21 in a month. Hold every PO until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
