# Prophet 21 and Epicor Kinetic compared

> How Prophet 21 and Epicor Kinetic software line up concept by concept, for people who know one and need the other, and for leaders weighing where each fits.

Source: https://docs.lumina-erp.com/reference/prophet-21-and-kinetic-compared/

**In short.** Epicor positions Prophet 21 software for distributors and Kinetic software for manufacturers, with supply chain capabilities of its own. Most ideas carry across, but the names, the layers and where logic runs differ, so map the concept before you assume the tool.

Prophet 21 and Epicor Kinetic are both Epicor ERP products, and people move between them more often than you might expect. An administrator changes jobs, a developer picks up a second client, a leadership team inherits a sister company on the other system. The two share plenty of ideas, but the names, the customization layers and the places where logic runs are different enough to trip up anyone who assumes the tool they know has a twin.

Use the concept map below to orient in the product you know less well. It also gives leaders a plain view of how Epicor positions each one.

:::note[What this page is not]
This is not a migration guide, a feature comparison or a recommendation to move from one product to the other. Capabilities depend on version, licensing and deployment, so treat every row here as a starting point to confirm in your own environment. Lumina ERP is an independent consultancy and is not affiliated with, sponsored by or endorsed by Epicor. See [About these docs](/about/).
:::

## How Epicor positions each product

As of 2026-09-28, the public Epicor product pages describe the two products this way. The wording below is our paraphrase. Follow the links in Sources for the originals.

| | Prophet 21 software | Kinetic software |
|---|---|---|
| Built for | Distributors. Epicor presents it as a distribution-specific ERP | Manufacturers. Epicor presents it as a cloud ERP for manufacturing, aimed mainly at discrete and make-to-order production |
| Industries Epicor lists | Distribution verticals such as industrial, electrical, fasteners, fluid power, HVAC, plumbing, medical supply and paper and packaging | Manufacturing verticals such as aerospace and defense, industrial machinery, fabricated metals and medical devices, plus metal service centers |
| Supply chain and distribution capabilities | Inventory, warehouse management, purchasing and order management are core to the product | A supply chain management suite covering purchasing, inventory, shipping and receiving, fulfillment and warehouse work, alongside production and planning |
| Deployment | On-premises or hosted. In January 2026 Epicor announced a schedule of final on-premises feature releases | Cloud-focused, with on-premises and hybrid options |
| Technology Epicor names | Microsoft SQL Server, .NET, a browser client, an SDK and the DynaChange extensibility suite | Application Studio, Epicor Functions, BPM, BAQs and REST APIs that follow OData |

On the Epicor distribution industry page, Prophet 21 appears among the featured distribution products and Kinetic does not. That fits the rest of the positioning, in which **Prophet 21 is the distribution product, and Kinetic is the manufacturing product that also moves and stores goods.** A business that both makes and distributes can reasonably look at either, and the answer depends on which side of the business carries the complexity.

## The concept map

Each row names a concept once and shows where it lives in each product. Cells marked "Confirm in your version" are ones this site and the public sources above do not settle.

| Concept | In Prophet 21 | In Epicor Kinetic |
|---|---|---|
| Where the data lives | Microsoft SQL Server, one database per live system, a conventional relational schema | Confirm in your version |
| Company scoping | Most tables carry a company key, so join and filter on it | The company ID is part of every REST v2 URL, so calls are always company-scoped |
| Everyday user interface | The web client in a browser, though some installs still run the Windows desktop client | The Kinetic browser interface. Systems from earlier versions may carry Windows-client customizations that do not run in the browser as is |
| Screen changes without code | DynaChange Designer: hide, relabel, move, require or default fields, assigned to users or roles | Application Studio layers saved over the base screen |
| Server logic on events | DynaChange Business Rules: compiled .NET code that runs on window events such as a field change or a save | BPM method directives (pre, base or post processing on a business object method) |
| A rule that must hold however data arrives | Business Rules run on window events. Confirm whether your import and API paths trigger them | BPM data directives, which fire on table changes whatever method made them |
| Reusable server operation | Confirm in your version | Epicor Functions, grouped in published libraries and callable from BPMs, layers, other functions and REST |
| Ad hoc queries | Read-only SQL against the database, reporting tools and in some shops SQL Server Reporting Services | BAQs built in the query designer, which feed dashboards, reports, grids and REST callers |
| Printed transactional forms | Generally Crystal Reports designs, changed through a custom copy of the shipped form | Report tooling (confirm in your version) |
| REST APIs | Entity, query (OData style) and transaction endpoints on the middleware tier. Some capabilities may need extra licensing | REST v2 with OData conventions. Every call carries user authentication plus an API key (x-api-key header) that an access scope can narrow |
| Exposing custom logic over REST | Confirm in your version | Publish an Epicor Function and call it under the efx path |
| File-based loads | Import layouts, and scheduled imports that watch a folder | Confirm in your version |
| Sales order levels | Header and line (oe_hdr and oe_line) | Header, line and release, with the release below the line |
| Item records | Item master (inv_mast) plus item-location records (inv_loc) | Part records identified by part number. Confirm how site-level data is held in your version |
| Server tier | The middleware tier, typically on IIS, serving the web client and APIs, plus background services | Confirm in your version |
| Non-production copy | Commonly called the play environment, refreshed from production | A test environment. Plan how libraries, directives and layers are promoted to production |

Two rows matter more than the rest. The **order level** row changes how you total anything on an order, because a Kinetic query that joins to releases repeats line values once per release. The **rule that must hold** row changes where you put controls: in Kinetic the standard answer is a BPM, and in Prophet 21 you need to check which entry paths your rule covers.

## Moving your thinking across

Pick the product you already know. The tab shows how to translate that experience into the other one.

**Prophet 21**

If you know Prophet 21, map your habits to Kinetic this way:

- **Designer becomes Application Studio.** Screen changes are layers over the base screen. Treat them as presentation, the same way you treat a Designer design.
- **A business rule splits into two ideas.** Reacting to something the system is doing is a BPM. A packaged operation that several places call is an Epicor Function. Long BPMs should hand their body to a Function.
- **Stop reaching for SQL first.** The everyday query tool is the BAQ. It is SQL assembled in a designer, so your join and grain instincts carry straight over.
- **Add a level to every order.** Lines have releases. Before you sum anything, decide whether a row is an order, a line or a release.
- **Two credentials on every API call.** A user identity decides permissions, and an API key identifies the calling application. Plan one key per integration.
- **Expect the company in the URL.** Company scoping is explicit in every REST v2 call rather than a column you remember to join on.

**Epicor Kinetic**

If you know Kinetic, map your habits to Prophet 21 this way:

- **Layers become DynaChange Designer.** Designs change what a window shows and requires, and they can be assigned to users or roles.
- **BPMs and Functions become DynaChange Business Rules.** Rules are compiled .NET code tied to window events. Check which entry paths a rule covers before you rely on it as a control.
- **BAQs become SQL.** Prophet 21 runs on SQL Server, and much reporting reads it directly. Use a dedicated read-only login, filter out logically deleted rows and join on the company.
- **Drop a level from every order.** Orders are header and line. Totals that needed release-level care in Kinetic are simpler here, but logically deleted and canceled orders still need filtering.
- **Forms are Crystal.** Printed documents are generally Crystal Reports designs. Change a custom copy, never the shipped design.
- **Files are a first-class integration path.** Scheduled imports that watch a folder are a normal, reliable way to load data in batches.

## What carries over unchanged

Some habits are product-neutral and hold in both systems:

- Choose the lightest tool that solves the request. A setting beats a screen change, and a screen change beats code.
- Keep controls on the server. A check that lives only on a screen can be bypassed by an import or an integration.
- Know the grain before you total. Fan-out from a parent-to-child join produces wrong totals in both products.
- Write through the application. Direct writes to ERP tables bypass business logic in either system.
- Keep an inventory of every customization. At upgrade time, that list is your test plan.

## Sources

- [Epicor Prophet 21 (Epicor)](https://www.epicor.com/en-us/products/enterprise-resource-planning-erp/prophet-21/)
- [Prophet 21 Technology (Epicor)](https://www.epicor.com/en-us/products/enterprise-resource-planning-erp/prophet-21/technology/)
- [Distribution industry solutions (Epicor)](https://www.epicor.com/en-us/solutions/industries/distribution/)
- [Epicor Kinetic (Epicor)](https://www.epicor.com/en-us/products/enterprise-resource-planning-erp/kinetic/)
- [Kinetic Supply Chain Management (Epicor)](https://www.epicor.com/en-us/products/enterprise-resource-planning-erp/kinetic/supply-chain-management/)
- [Kinetic Tools and Technology (Epicor)](https://www.epicor.com/en-us/products/enterprise-resource-planning-erp/kinetic/tools-and-technology/)
- [Epicor announces schedule of final on-premises feature releases (Epicor, 2026-01-06)](https://www.epicor.com/en-us/newsroom/news-releases/epicor-announces-schedule-of-final-on-premises-feature-releases/)

---

Epicor, Prophet 21, P21 and DynaChange are trademarks or registered trademarks of Epicor Software Corporation registered in the United States and other countries. Kinetic is a trademark of Epicor Software Corporation. Lumina ERP is an independent consultancy and is not affiliated with, sponsored by or endorsed by Epicor.