How to Import Customer Orders into Epicor Prophet 21
Manual entry, CSV import, EDI, API and AI order automation — the ways to get customer orders into Epicor Prophet 21, and when each one fits.
"Import customer orders into Prophet 21" can mean several different things, because orders arrive in several different shapes. The right method depends far more on how the order comes in than on Prophet 21 itself. Here are the common approaches and where each one fits.
Manual entry
Still the default for most distributors: someone reads the order and types it into Prophet 21. It handles any format a human can read, which is its strength and its cost. It does not scale — volume is capped by how fast people can type — and it is where most order-entry errors come from.
CSV and spreadsheet import
Useful when a customer can send a clean file in a fixed layout, or for bulk one-offs. The catch is the word fixed: an import expects the data already structured in the columns it wants. Real customer spreadsheets rarely match, so someone ends up reformatting them first — which is manual entry wearing a different hat.
EDI
For structured, high-volume trading relationships, EDI is hard to beat. Once a partner is set up, orders flow in as standardised transactions with little human touch. The limitation is reach: EDI only helps with customers who trade over EDI, and setting up each partner takes effort. Most distributors have a long tail of customers who will never send an EDI order. We cover this trade-off in EDI vs AI order automation for Prophet 21 distributors.
API and integration
If an order already exists as structured data in another system, an API integration can move it into Prophet 21 directly. This is the right tool for system-to-system flows. It does not, by itself, solve the problem of an order that arrives as a PDF or an email — something still has to turn that into structured data first.
AI order automation
This is the method for everything that arrives unstructured: email bodies, PDF purchase orders, varied spreadsheets, messaged orders. Instead of requiring the data to be pre-formatted, it reads the order as sent, extracts the fields, and matches each line to your Prophet 21 part numbers and pricing before preparing the sales order. It complements EDI and API rather than replacing them — it covers the customers those methods cannot. That is what ManualOut does for Prophet 21 order automation.
Most distributors use more than one
There is no single winner. A practical setup routes EDI partners over EDI, system flows over an API, and the large remainder — the email-and-PDF customers — through AI order automation, with a person reviewing exceptions. To see the AI path on your own orders, book a demo.
Epicor and Prophet 21 are trademarks of Epicor Software Corporation. ManualOut is an independent product and is not affiliated with or endorsed by Epicor Software Corporation. Specific Prophet 21 import and API capabilities depend on your Epicor version and modules.
Frequently asked questions
What is the best way to import orders into Prophet 21?
It depends on how the order arrives. Structured, high-volume trading partners suit EDI or API; one-off spreadsheets suit a CSV import; email, PDF and messaged orders suit AI order automation that reads and matches them. Most distributors use more than one.
Does Prophet 21 have an order import?
Prophet 21 supports structured integration methods, and specific import and API capabilities depend on your version and modules. Confirm the exact options with your Epicor setup; the approach in this article is about which method fits which kind of order.
How does AI order automation differ from a CSV import?
A CSV import needs the data already structured in the columns it expects. AI order automation reads unstructured orders — email, PDF, varied spreadsheets — and does the matching first, so it handles the orders an import cannot.