Integration
Epicor Prophet 21 order entry automation
OrderDrafter is built P21-native from day one — not a generic ERP connector. Emailed POs become draft sales orders your CSR confirms in one click, written through Prophet 21's own APIs.
Item master and customer sync via OData
On connection we read your customers, ship-tos, item master, customer part numbers, and contract pricing through P21's OData services. No exports, no spreadsheets, no stale copies — matching always runs against current data.
Native order creation via the Transaction API
Confirmed orders are written as real oe_hdr and oe_line records through Prophet 21's Transaction API, and the returned P21 order number appears in the review screen immediately. Your pick/pack/ship flow continues exactly as it does today.
You control the credentials
Your team provisions the API user and consumer key inside your own P21 instance, scoped to what the integration needs. Revoke access anytime from your side. We never ask for database access.
Defensive against P21's quirks
The Transaction API can report failure inside an HTTP 200 response, block writes on DynaChange popups, and throttle concurrent sessions. Our client parses every result summary, retries safely with idempotency keys, and surfaces real errors to a human instead of silently dropping orders.
Batch-import fallback
P21 REST API access is a separately licensed Epicor add-on that not every site has. If yours doesn't, we support a scheduled batch-import path so you can start automating now and switch to the API when licensing is sorted.
Audit trail down to the payload
For every order: source document, extracted fields with confidence, every correction, the exact JSON written to P21, and the returned order number. Immutable and searchable.
Onboarding in under a week
- 1
Day 1: your P21 admin creates the API user; we run the connection test and sync your item master, customers, and pricing via OData.
- 2
Day 2: set the forwarding rule on your orders mailbox; optionally backfill recent POs so the alias tables start pre-trained.
- 3
Days 3–5: run in shadow mode on live POs; your CSRs compare drafts to source documents and correct anything the AI missed.
- 4
Go live: flip the switch — confirmed orders start writing to Prophet 21 with full audit logging.
Prophet 21 integration FAQ
Do I need a P21 API license?
For native write-back, yes — Epicor licenses REST API access separately, and many sites already have it for e-commerce or reporting integrations. If your site doesn't, our batch-import fallback works without it, and we can help you ask Epicor the right questions about the entitlement.
Which Prophet 21 versions are supported?
Current cloud and on-premise releases with the middleware/API layer enabled, including the 2026.1 API changes. During onboarding we run a connection test against your instance before anything else.
Does it work with our DynaChange rules and business logic?
Orders created through the Transaction API pass through P21's business logic like any other order. Rules that raise interactive popups can block API writes, so during onboarding we identify them and configure popup suppression for the dedicated API user, leaving your CSR-facing rules untouched.
Can it read our contract pricing?
Yes. Contract and customer-specific pricing sync via OData, and extracted PO prices are validated against them — so an outdated or off-contract price on the customer's PO gets flagged before the order is created, not discovered at invoicing.
What about multiple branches and ship-tos?
Ship-to resolution handles branch addresses, jobsite addresses, and will-call. Ambiguous ship-tos are flagged for the CSR with the closest matches pre-selected rather than guessed.
Stop keying purchase orders by hand
Design-partner spots are open for Prophet 21 distributors. Go live in under a week — no consultants, no IT project.