Epicor Prophet 21 Customization & Enhancements
We bend Prophet 21 to your workflows instead of the other way around. ESS has built 100+ P21 business-logic extensions and web visual rules across every module — from creating items on the fly in Order Entry to two-printer check printing — using Epicor's own supported framework and a native API layer that needs no Epicor API module.
100+ Prophet 21 extensions across 10 functional areas — each a small, upgrade-safe module, none requiring the Epicor API module.
Customizations That Pay for Themselves
Real Prophet 21 enhancements ESS has built — the kind that remove manual steps, stop costly mistakes and save real money.
Add catalog items on the fly from Order Entry
A P21 user searches a supplier catalog directly from Order Entry through a web visual rule — without ever importing the supplier's catalog into Prophet 21 — and places the item on the order. Our API layer creates the item in P21 on the fly, so reps quote and sell from a full catalog while P21 stays clean.
Two-printer check printing that saves check stock
Check stationery prints on the dedicated check printer while addendum / remittance sheets route to a regular printer — so expensive pre-printed check paper is never wasted on overflow pages.
Auto-create transfers & replenishment on save
Order and demand events automatically generate the right transfer or replenishment in P21, removing a manual step that distribution teams otherwise repeat hundreds of times a week.
Territory-based approval & credit workflows
Orders route to the correct regional manager by territory, with credit-review and approval gates enforced in P21 — so the right people sign off before an order or RMA proceeds.
Order-entry guardrails & alerts
Rules catch zero-price lines, COD or unapproved orders, ship-date changes and discontinued items at the moment of entry — and can auto-send an RFQ to suppliers — so problems are stopped before they ship.
Third-party AR & payment integrations
Invoices and PO documents are pushed to external AR / collections and payment platforms automatically, keeping P21 and your money-movement systems in lockstep without re-keying.
Customizations Across Every P21 Module
Deep knowledge of Prophet 21 business rules, applied everywhere your team works.
Order Entry
Workflow automation, validation and guardrails — auto-RFQ, price and approval checks, on-save transfers.
Approvals
Regional-manager routing by territory, credit review, RMA and inventory-adjustment sign-off.
Cash Receipts & AR
Quick entry, dispute-at-line handling, paid-in-full and default-check logic.
Inventory & Transfers
Transfer requirements, cancelled / under-shipped handling, replenishment and putaway.
Purchasing & Suppliers
PO acknowledgement, ship-date alerts, discontinued-item blocks, supplier / vendor validation.
Item & Catalog Maintenance
New-item task rules, discontinued-item handling, default product groups, legacy part lookup.
Customer & Contact Data
Default values and validation, phone / fax formatting, direct phone-or-email contact tabs.
Invoicing & Billing
Email invoice on shipping, down-payment counts on reports, one-line service-order billing.
Notes & Documents
Mandated notes, order-line notepads, supplier notepad generation and note-area rules.
UX Personalization
Guided or suppressed popups, on-screen totals and order numbers — fewer clicks, fewer mistakes.
On Epicor's Framework — Not Fighting It
ESS builds enhancements on Prophet 21's own supported extension points — business-rule events, dynachanges and web visual rules — backed by a native on-premises API layer for everything that has to read from or write to P21. That combination is what lets us automate deep workflows, and even create records on the fly, without the Epicor API module and without unsupported hacks.
- Business-logic extensions on P21 business-rule events (on edit, on save, pre/post)
- Simple and complex web visual rules, inside P21 and to outside partners
- Dynachanges to tailor screens, fields and data behavior
- Native on-premises API layer — no Epicor API module required
- One extension per concern — modular, testable and upgrade-safe
100+ Built
Across every P21 module
No API Module
Native on-prem API layer
Upgrade-Safe
Supported extension points
Modular
One extension per concern
Need documents to flow into P21 too? See AI document processing for Prophet 21 and our Prophet 21 integrations & API.
Epicor Prophet 21 Customization — FAQ
What kinds of customizations can ESS build for Epicor Prophet 21?
Just about anything P21's business-rule framework can reach. ESS has built 100+ Prophet 21 extensions spanning order entry, purchasing, accounts receivable, inventory and transfers, item and customer maintenance, invoicing, approvals and UI personalization. Examples include creating catalog items on the fly from order entry, two-printer check printing that saves check stock, territory-based approval routing, and automatic transfer and replenishment creation on save.
Do Prophet 21 customizations require the Epicor API module?
No. ESS provides a native on-premises API layer purpose-built for P21, so customizations and integrations work on both Epicor Cloud and legacy on-prem installs without licensing the Epicor API module. That is how we can do things like create items in P21 on the fly directly from order entry.
What are dynachanges and web visual rules?
They are Prophet 21's supported extension points. Dynachanges customize screens, fields and data behavior; web visual rules (both simple and complex) let us enforce logic and automate workflows inside P21 — and connect them to outside partners. ESS uses these alongside custom business-logic extensions so enhancements ride on Epicor's own framework rather than fighting it.
Can you really add an item to P21 on the fly from order entry?
Yes. A rep can search a supplier's catalog from within Order Entry — without importing that catalog into Prophet 21 — and place the item on the order. Our API layer then creates the item in P21 automatically, so you sell from a full catalog while keeping the item master clean.
Will customizations survive a Prophet 21 upgrade?
We build on P21's supported business-rule events and extension points rather than unsupported hacks, and we version and retest extensions as part of any upgrade. Because the logic is modular — one extension per concern — upgrades are a matter of revalidating each rule, not untangling a monolith.
How do you deliver and support these enhancements?
Each enhancement is a small, independently deployable extension, so we can pilot one workflow, prove it, and roll out more without disrupting the rest of P21. ESS maintains them over time and folds them into your upgrade and support cycle.
Have a Prophet 21 Workflow That Should Be Easier?
Tell us the manual step or the rule you wish P21 enforced. With 100+ extensions already built, chances are we have done something close — and can show you.