Epicor Prophet 21 Capabilities
What ESS can do in Prophet 21 — and has already done for distributors running it every day. Business rules, web visual rules, DynaChanges, custom portals, labels, reports, a P21 API layer and an incremental migration tool, all built on Epicor's supported extension points.
- P21 business rules in production
- 100+
- Prophet 21 windows automated
- 30+
- Simplified P21 API endpoints
- 150+
- Functional areas covered
- 15
Every Prophet 21 Extension Point, Mastered
We pick the right tool for each requirement — and often combine several in one workflow.
Business-logic extensions
Compiled P21 business rules that fire on the events Prophet 21 exposes — field edits, on-save validation, window open, post-save order updates, message boxes and DataStream form events.
- Converters, validators, on-demand and on-event rules
- Popup + callback flows for guided entry
- Drive any P21 window through the Transaction API
Web visual rules
Rich web screens that open inside P21 at the moment they are needed — search, capture, approve — and hand the result straight back to the window.
- Supplier-catalog item search from Order Entry and PO Entry
- Request & approval forms for items and suppliers
- Sales history and PDF viewers inside P21
DynaChanges
Dozens of simple and complex DynaChanges — screens, tabs, fields and menus tailored by role — plus user-defined fields that carry the data your workflows need.
- Role-based screen and menu layouts
- User-defined fields across dozens of tables
- Hidden fields that carry state between rules
Custom portals
Role-targeted P21 portals that put the exceptions in front of the people who own them — approvers, credit, purchasing and branch managers.
- Approval queues for store and regional managers
- Custom audit-trail portals for orders, POs and customers
- Branch follow-up, open quote and PO review portals
Labels & forms with custom data sources
Complex warehouse labels and forms driven by custom data sources — configured per location and printed from the P21 and WWMS workflows your team already uses.
- Item, bin, pallet and shipping label suites
- Per-location label definitions and WWMS defaults
- Invoice and check forms enriched at print time
Custom reports & portal queries
Purpose-built report and portal queries for the questions standard P21 reports don't answer, plus extra columns in P21's own search and popup windows.
- Discontinued, over-received and unvouchered items
- Open POs by buyer, disputed invoices by territory
- Hot / rush order and approval-queue reporting
API layer — no Epicor API module
150+ simplified, domain-driven P21 endpoints for customers, contacts, items, suppliers, pricing, AR, orders and availability — no Epicor API module required.
- REST, Transaction API, OData and SQL under one API
- JWT auth, per-action permissions and 2FA
- Creates P21 records without the licensed API module
Data migration with incremental updates
An automated migration tool that moves legacy data onto Epicor's conversion layouts and then keeps it in sync — pushing only what changed.
- Master data and open transactions
- Row-level change detection, delta pushes to P21
- Self-service staging screens with Excel upload
What We've Automated in Prophet 21
A catalogue of capabilities already running in production P21 environments — by functional area.
Order & quote approvals
- Tiered store-manager → regional-manager holds on high-dollar, low-margin and price-override orders
- Thresholds per customer with company defaults; approvers resolved by branch and region
- Mandatory approval comments with an audit trail written to order notes
- Only authorized roles can approve; $0-price lines un-approve the order
Pricing & cost governance
- Price-on-request items prompt for supplier cost and a calculated standard cost at entry
- Costs written back to Item Maintenance for every eligible location and supplier
- Automatic RFQ flagging and POR expiration dates
- Bulk linking of price pages to price books
Sourcing, transfers & freight
- Offer the replenishment location's free stock when the source location is out
- Auto-create transfers and default the carrier for transfer lines
- Role-gated approval for transfers into the central DC
- Tasks raised when linked transfers are cancelled or under-shipped
Down-payment invoicing
- Down-payment % → amount, with running DP numbering on the order
- Mandatory DP notes routed to the right screens and printouts
- DP numbers printed on invoice forms at print time
- DP history surfaced in Customer Master Inquiry
Cash receipts & AR disputes
- Dispute reason and notes per invoice line across all Cash Receipts windows
- Invoice disputed flag set automatically in P21
- Defaults and naming conventions for quick entry and cash drawers
- Invoices pushed to third-party AR & collections platforms
Finance & GL controls
- Inactive GL accounts blocked across six GL entry and maintenance windows
- Balanced, unapproved journals routed to accounting leads
- GL-impact confirmation with undo on sensitive customer settings
- Two-printer check printing that saves check stock
Purchasing & receiving
- PO acknowledgement cascades to lines and locks once acknowledged
- Alerts on expected ship-date changes and discontinued items on POs
- Store managers notified when a receipt completes a PO
- Order Entry blocked from creating POs for restricted suppliers
Item & supplier master governance
- Create items on the fly from a supplier catalog — without importing the catalog
- Discontinuation rules with branch-manager notification
- New-item completeness checks and content-team review
- Duplicate supplier / vendor prevention and auto-generated supplier notes
Customer & contact data quality
- Phone and fax normalization on any window
- Duplicate phone / email prevention and required contact methods
- Contact-belongs-to-customer checks with auto-fill in Order Entry
- New-customer defaults and payment-terms sync
Inventory, RMA & warehouse
- Inventory adjustments default to unapproved with created-by audit
- Store-manager approval tasks for adjustments
- RMA approval restricted by role
- WWMS putaway and production-order completion guardrails
Tasks, notes & alerts
- P21 Tasks routed by role, location or order owner — with multiple assignees
- Mandatory special-order line notes flowed to purchasing screens
- Supplier return-policy notes generated automatically
- Confirmation and guidance messages at the right moment
Prompts & usability
- Global rule that auto-answers routine P21 prompts
- Silent prompts for API service accounts so automation runs unattended
- Print-window defaults and required-input guards
- Previously requested items re-priced automatically
Migrate Once, Then Stay in Sync
Our migration tool loads legacy data onto Epicor's P21 conversion layouts, cleans and validates it in staging, and pushes it into Prophet 21 through the Transaction API. Every row is fingerprinted, so re-runs push only what is new or changed — ideal for parallel running and phased cut-overs.
- Customers, ship-tos, contacts, sales reps and part numbers
- Items with locations, suppliers, UOMs, accessories, substitutes and assemblies
- Suppliers and vendors with terms and purchase accounts
- Open sales orders, POs, AR invoices, AP vouchers, GL journals and counts
- Self-service staging screens with list, detail and Excel upload
How We Deliver It
Custom work should compound across releases, not block them. Every capability on this page follows the same delivery discipline.
- Built on P21's supported extension points — business rules, visual rules, DynaChanges and portals
- One extension per concern, so each can be piloted, tested and upgraded on its own
- Environment-aware builds that deploy unchanged across dev, play, live and import
- Every rule traceable to the requirement that asked for it
- Retested as part of every Prophet 21 upgrade we run
Related Reading
Go Deeper
FAQ
Epicor Prophet 21 Capabilities — FAQ
Almost anything P21's extension framework can reach. ESS has put 100+ Prophet 21 business rules into production across 30+ windows and 15 functional areas — order and quote approvals, price-on-request costing, sourcing and transfers, down-payment invoicing, cash receipts and AR disputes, GL controls, purchasing, item and supplier governance, contact data quality, inventory, RMA and warehouse. Alongside those rules we build web visual rules, DynaChanges, custom portals, labels and forms with custom data sources, custom reports, a P21 API layer and an incremental data migration tool. Most new requests start from a pattern we have already delivered.
Business rules are compiled extensions that run inside Prophet 21 on events such as a field edit, a save or an order update — they validate, default, calculate, route approvals and call P21's APIs. Web visual rules open a web screen inside P21 when a richer interaction is needed, such as searching a supplier catalog or completing a request form, and pass the result back to the window. DynaChanges tailor the screens themselves — fields, tabs, menus and layouts by role — and add user-defined fields. ESS uses all three together, with custom portals surfacing the exceptions to the people who own them.
No. ESS's API layer exposes 150+ simplified, domain-driven Prophet 21 endpoints — customers, contacts, items, suppliers, pricing, AR, orders and availability — without licensing the Epicor API module. Under the hood it combines P21's REST and Transaction APIs, OData views and database access behind one secured API with JWT authentication, per-action permissions and two-factor sign-in, and it can create P21 records directly. The same layer powers our visual rules, integrations and ESS Fusion AI.
Legacy data is extracted and loaded onto Epicor's P21 conversion layouts in a staging database, where transform, correction and validation scripts clean it up. Every staging row is fingerprinted, so each record is classified as new to P21, changed since the last push, or already in sync. Only new and changed records are pushed into Prophet 21 through its Transaction API — items with locations, suppliers, units of measure, accessories and substitutes, as well as customers, suppliers and assemblies. Open sales orders, POs, AR invoices, AP vouchers, GL journals and stock counts migrate too, and business users can review and upload staging data through self-service screens.
Yes. Everything is built on P21's supported extension points rather than core modifications, and each capability ships as its own small, versioned extension. During an upgrade ESS revalidates each extension individually against the new release, so custom work carries forward instead of blocking the upgrade — and because the same team builds, supports and upgrades, nothing gets lost between projects.
Tell Us What P21 Should Do Next
A manual step, a missing guardrail, a report nobody can get — with 100+ rules already in production, we can usually show you something close within one call.
