Early access
Epicor Prophet 21 sales order automation
Prophet 21 is the distribution standard, OrderPier turns inbound PDFs into P21 sales orders, touchless. The connector is built and tested end to end against the vendor's REST API. We are onboarding pilot customers now. Book a slot and we validate it against your own instance during onboarding, before any live order flows.
Acme Distribution
Order attached, need it by May 30
Every field read & scored
ValidatedPosted to Epicor Prophet 21
SO-10238Early access
Epicor Prophet 21 order creation, validated in your pilot
0
templates to maintain
A few days
onboarding
Why Epicor Prophet 21 teams still re-key orders
Epicor Prophet 21 is built to manage orders once they're in the system, but it can't read the PDF a customer just emailed. So a CSR opens the attachment, finds the customer and items in Epicor Prophet 21, and types the order in by hand, line by line.
OrderPier closes that gap. It reads the inbound purchase order, matches it to your Epicor Prophet 21 records, and creates the sales order directly, so the document arrives as a ready-to-fulfill order, not a task in someone's inbox.
How OrderPier posts into Epicor Prophet 21
- Capture the PO from a forwarded email or shared mailbox.
- Extract every field and line item with confidence scoring.
- Match customers, items, and price levels against your Epicor Prophet 21 data.
- Create the Epicor Prophet 21 sales order. Route exceptions to a review queue.
- Log every step for a complete audit trail.
How OrderPier maps a PO to a Prophet 21 order
OrderPier connects to your P21 middleware as a dedicated API user (a token request to /api/security/token/v2) and works entirely through P21's standard REST and OData surface. Nothing is installed inside P21 and no custom development is required.
Customer and item resolution run against your live master data before anything is written. The extracted bill-to and ship-to are matched to your customer records via OData against the customer data object, and each line's part number resolves against your item master, including customer-specific part numbers.
The order is written as a native P21 order transaction: an oe_hdr header carrying the PO number, customer, ship-to and requested date, plus an oe_line for every line with item id, quantity ordered, unit price and unit of measure, exactly the fields a CSR keys into Order Entry. Anything the model is not confident about routes to a review queue before the order posts.
Because it is early access, we point the connector at your own P21 instance during onboarding and confirm a live order end to end before it handles real volume.
Epicor P21 questions
- Does this require custom Epicor Prophet 21 development?
- No. Order creation goes through Epicor Prophet 21's standard REST API, nothing to install and no per-customer template work. You authorize OrderPier once during your pilot onboarding.
- Will it match customer part numbers to our Epicor Prophet 21 items?
- Yes. Line items are matched to your Epicor Prophet 21 item master, including customer-specific part numbers, with pricing and availability validated before the order is created. CSR corrections in the reviewer feed a per-customer alias table so the same raw string auto-resolves next time.
- What if an order can't be matched cleanly?
- It routes to an exception queue with the flagged field and the source document side by side. A CSR resolves it in seconds and the order posts to Epicor Prophet 21, nothing is ever guessed into Epicor Prophet 21.