EDI vs AI Order Entry for Epicor Prophet 21
Which customer orders belong on EDI and which on AI order entry in Prophet 21, how each reaches Order Entry, and how distributors run the two side by side.
Gonzalo Nuñez
Chief Technology Officer
For a distributor on Epicor Prophet 21, EDI and AI order entry are not rivals. EDI suits the customers who already send structured EDI 850 orders and will keep doing so. AI order entry suits everyone else: the customers who email a PDF, a spreadsheet or a few lines of text and will never set up a trading partner. Most distributors need both. Fluent covers the second group, reading each order, resolving it against live P21 data and drafting it in Prophet 21 Order Entry for a person to approve, while EDI customers stay on EDI.
How EDI reaches Prophet 21
Prophet 21's EDI module turns a customer's EDI 850 into a sales order, and sends acknowledgements, advance ship notices and invoices back (855, 856 and 810). Orders that fail import are held for someone to fix. Many distributors connect through a provider such as Epicor EDI, 1 EDI Source, SPS Commerce or TrueCommerce, which handles the network and the maps.
EDI works well when both sides agree a format and keep it. Each customer is a trading partner with its own map, set up and tested before the first order flows. That makes sense for a large customer who orders every day. It rarely makes sense for the long tail of customers who order a few times a month by email.
How AI order entry reaches Prophet 21
AI order entry reads the order the way a person would, whatever its layout. Fluent reads PDFs, spreadsheets and email bodies, then resolves each one against your live P21 data:
- Ship-to first, which settles the customer.
- Items, including the customer's own part numbers.
- Units the item actually carries.
- Quotes converted into the order when the PO answers one, and job contracts applied so P21 prices from them.
- Duplicates: an existing order on the same customer PO is flagged.
The result is a draft in Fluent's review queue with anything unresolved named on its line. When a person approves it, Fluent saves the order through P21's own interfaces and reads it back. There is no map per customer: a new customer's first PO is read the same day.
Side-by-side
| EDI | AI order entry with Fluent | |
|---|---|---|
| Best for | Large customers who already trade EDI | Customers who email PDFs, spreadsheets or text |
| Setup per customer | A trading partner and a map, tested | None; written instructions where needed |
| Input | EDI 850 | PDFs, spreadsheets, email bodies |
| When the data is wrong | Import fails and is held in P21 | Named on the draft line before saving |
| Customer part numbers and units | Mapped per partner | Resolved against P21 on each order |
| Who reviews | Exceptions only | A person approves each draft |
| Outbound documents | 855, 856, 810 | Not covered; keep EDI for these |
Where each fits better
EDI fits better when a customer requires it, sends high volume every day, and needs acknowledgements and ship notices back. Keep those customers on EDI.
AI order entry fits better for customers who will not or cannot trade EDI, which for most distributors is the majority by count. It also suits new customers, one-off orders and customers whose POs change shape.
How to decide
List your customers by order count and by how they send orders today. Then:
- Leave customers already on EDI where they are.
- Take the customers who email orders, and pick the ones that cost your team the most: their own part numbers, many ship-tos, quotes or contracts.
- Run a batch of their real POs through AI order entry and compare the drafts with the orders your team keyed.
Automate Prophet 21 order entry with Fluent
The Prophet 21 order entry automation page explains the agent, the guide to automating Order Entry covers the process, and the Prophet 21 integration page explains the connection. To see it on your own customers' orders, book a demo.
Frequently Asked Questions
Usually both. Keep customers who already trade EDI 850 on EDI, and use AI order entry for the customers who email PDFs, spreadsheets and plain text, which for most distributors is the larger group by count.
For customers who will not set up EDI, yes. Fluent reads their emailed orders, resolves the ship-to, the items and the units against live P21 data, and drafts the order in Prophet 21 Order Entry for a person to approve, with no map per customer.
No. Fluent drafts inbound customer orders from documents and email. It does not send the 855 acknowledgements, 856 ship notices or 810 invoices that EDI customers expect, so keep EDI for the customers who require it.
The difference is named on the line it belongs to, such as an item that could not be matched or a price that disagrees with the contract, and the order is saved only after a person approves the draft.
There is nothing to set up per customer. A new customer's first purchase order is read and resolved against your P21 data the same way as any other, and written instructions can be added if a customer needs special handling.
Fluent does not. It calls Prophet 21's own APIs from outside through an integration user your administrator sets up, and restricted networks allowlist Fluent's fixed egress IPs.
