How to Automate Order Entry in Epicor Prophet 21
How distributors turn emailed customer purchase orders into Prophet 21 orders: the ship-to, customer part numbers, quotes and contract prices, checked before an order exists.
Gonzalo Nuñez
Chief Technology Officer
To automate Order Entry in Epicor Prophet 21, have software read each customer purchase order, resolve the ship-to, the customer and every item against your live P21 data, and draft the order your inside sales team would key, with anything it could not settle named for a person to review. Fluent does this through P21's own APIs with nothing installed inside Prophet 21. It converts the customer's open quote when the order answers one, applies the customer's job contract, flags an existing order on the same customer PO, and saves nothing until a person approves the draft.
What makes P21 order entry slow
A distributor's inside sales team spends little of its day typing. It spends it working out who the order is for and what the customer means. The PO names a delivery address, and the order taker has to find the ship-to and the customer that owns it. Lines carry the customer's own part numbers, and someone has to find the matching items. Units on the PO may not match how the item is sold. Prices have to be checked against the quote or the contract the customer was given. And when the same PO is emailed twice, someone has to notice.
Ways to automate it
EDI into P21
Prophet 21's EDI module turns a customer's EDI 850 into a sales order, and orders that fail import are held for someone to fix. For customers who already trade EDI, it is the most direct path. Most distributors still receive a large share of orders as PDFs, spreadsheets and plain email from customers who will never set up EDI. The guide to EDI and AI order entry for Prophet 21 compares the two.
Order capture platforms
Conexiom, under an expanded Epicor partnership announced in July 2026, converts emailed orders for Prophet 21, with checks on ship-to, contract price and cross-references and review in Conexiom's own platform. Esker reaches P21 through a connector built by an Epicor partner. Confirm with each vendor which P21 version and which order fields they cover.
A custom build
Some distributors have a developer, or a firm such as Airdev, build an order reader on P21's Transaction API. That gives full control, and also leaves your team owning the code, the prompts and the upkeep as P21 versions change.
An agent that drafts the order in P21
Fluent reads each order (PDF, spreadsheet or email body) and resolves it against your live P21 data:
- Ship-to first, which settles the customer the way your order takers work.
- Items, including the customer's own part numbers.
- Units the item actually carries.
- Quotes: the customer's open quote is converted into the order, so the order stays tied to it. A cancelled or completed quote, or another customer's, is never converted.
- Contracts: the customer's job contract for the ship-to is applied, so P21 prices the lines from it.
- Duplicates: an existing order on the same customer PO is flagged.
The result is a draft in Fluent's review queue with every unresolved item named on its line. When it is approved, Fluent saves the order through P21's own interfaces and reads back what P21 committed: an order that comes back missing a line is cancelled and reported, never left half-written. User-defined fields on the header and lines can be filled from the document, and when you turn it on, Fluent raises the purchase orders for special-order and direct-ship lines after the order is saved.
Side-by-side
| P21 EDI | Order capture platform | Custom build | Fluent | |
|---|---|---|---|---|
| Formats | EDI 850 | Email attachments; confirm with the vendor | What you build | PDFs, spreadsheets, email bodies |
| Customer setup | A trading partner per customer | Confirm with the vendor | What you build | None; written instructions |
| Where review happens | Failed imports, in P21 | In the vendor's platform | What you build | A draft in Fluent's review queue |
| Quotes and job contracts | Confirm with Epicor | Confirm with the vendor | What you build | Quote converted, contract applied |
| Upkeep | Maps per trading partner | The vendor | Your team | Fluent |
How to decide
Test with a batch of your own orders, the ones that cost your team the most today:
- A customer who orders by their own part numbers.
- An order shipped to one of many ship-tos.
- An order that answers a quote you sent.
- A customer on a job contract.
- A PO emailed twice.
Then compare how many lines arrive resolved against your P21 data, how each option shows what it could not resolve, and how long a person spends on each order.
Automate Prophet 21 Order Entry with Fluent
The Prophet 21 order entry automation page explains the agent in detail, and the Prophet 21 integration page covers the connection and the access your administrator grants. To see it on your own customer orders, book a demo.
Frequently Asked Questions
Yes. Fluent reads each customer purchase order, resolves the ship-to, the customer and every item against your live P21 data, and drafts the order in Prophet 21 Order Entry. A person reviews the draft, and nothing is saved until they approve it.
Yes. Items are matched including the customer's own part numbers, and the unit on the PO is checked against the units the item carries in P21. An item it could not match is named on its line for a person to settle.
Yes. When the customer's PO answers an open quote, Fluent converts the quote into the order, the way your team would, so the order stays tied to it. A quote that is cancelled, completed or belongs to another customer is never converted.
Yes. When the customer holds a job contract for the ship-to, Fluent puts it on the order so Prophet 21 prices the lines from the contract, and prices on the PO that disagree are shown before the order is saved.
It covers the orders EDI does not: the PDFs, spreadsheets and emails from customers who will never set up a trading partner. Customers already on EDI can stay there. The two work side by side.
Yes. User-defined fields on the order header and its lines can be filled from the document, with rules your team writes in the agent's settings rather than a customization inside P21.
