Prophet 21 integration: APIs, SISM, data extraction and reports

Prophet 21 integrates through four API layers exposed by the P21 middleware server (OData for reads, Entity for master records, Transaction for postings, Interactive for screen-style flows) and through SISM, the Scheduled Import Service Manager, for batch file imports. API access is a separately licensed asset. P21 data sits in Microsoft SQL Server, which is why reporting and extraction tools work well. Integration moves structured data between systems; it does not read customer emails or chase suppliers. Morsa does that work and writes the results into P21 through the same APIs.

Morsa publishes this guide. Epicor facts were read on epicor.com and partner facts on each partner’s site on 21 October 2026. Epicor’s own API documentation sits behind customer login, so the API detail below comes from named Epicor partners and integrators.

Part of our Epicor Prophet 21 guide.

Where Prophet 21 data lives

P21 runs on Microsoft SQL Server, whether it is hosted on premises or in Epicor’s Azure cloud [1]. Customer, item, price, order, purchase order, inventory and ledger tables all live in that one database. Around it sit the P21 middleware server, which exposes the APIs [3], and extension tools: the SDK and DynaChange, which tailor screens and rules without changing source code [1].

The other half of a distributor’s data is not in P21 at all: customer POs in inboxes, supplier confirmations in email threads, delivery promises made on the phone. Every integration project should list both halves.

The ways to integrate with Prophet 21

OData (Data Services)

• What it does: Fast, read-only queries

• Best for: Dashboards, reporting, syncing data out

• Watch for: Read only

• Source: [2][3]

Entity API

• What it does: Create, read, update master records

• Best for: Customers, items, contacts

• Watch for: License required

• Source: [2][3]

Transaction API

• What it does: Posts transactions with P21’s business rules, no screen prompts

• Best for: Orders, vouchers, receipts

• Watch for: License required; more build effort

• Source: [2][3]

Interactive API

• What it does: Drives a live P21 session and answers the prompts a screen would show

• Best for: Complex, branching flows

• Watch for: Most build effort

• Source: [2][3]

SISM (Scheduled Import Service Manager)

• What it does: Imports template files on a schedule; errors land in “Import Suspended” for review before commit

• Best for: High-volume, predictable loads: EDI-like files, price updates, invoice imports

• Watch for: Strict layouts; no branching logic

• Source: [2]

Bulk Data API

• What it does: New in P21 2026.1

• Best for: Large data moves

• Watch for: New; check your version

• Source: [4]

Direct SQL read

• What it does: Reports and extraction straight from the database

• Best for: BI tools, data warehouses

• Watch for: On-premises or with Epicor’s agreement; never write directly

• Source: [1][5]

iPaaS and connectors

• What it does: Pre-built syncs to ecommerce, CRM, shipping

• Best for: Standard apps (Shopify, Salesforce, marketplaces)

• Watch for: Usually polling, not real time

• Source: [5][6]

EstesGroup, which describes itself as an Epicor Platinum Partner, gives a simple rule: predictable, batched writes go through SISM; interactive, branching or mixed read and write work goes through an API [2].

Licensing and setup

Airdev reports that P21 API access is “a separately licensed add-on”, sold as “the P21 API asset in your Epicare asset list”, and that integrations built without it fail with a security exception [3]. EstesGroup lists “licensing costs, version changes, and higher development effort” as the API watch-outs [2]. Before any project, confirm three things with Epicor in writing: the API asset is on your contract, any transaction limits, and whether your hosting (cloud or on premises) exposes the middleware server to the integration.

Known patterns from integrators: iPaaS.com syncs with P21 by scheduled polling and uses no webhooks [5]. Optimizely’s B2B commerce connector needs the P21 APIs reachable over port 443 [7]. Documentation is thin enough that many teams rely on the epiusers.help community [3].

Prophet 21 automate data extraction: getting data out

Three routes, from cheapest to most flexible:

1. Built-in reporting. Epicor Report Studio and Epicor Grow build reports and dashboards that export to Excel, “no database or coding skills needed” [8].

2. OData queries. Pull tables into Power BI, Excel or a data warehouse on a schedule, with the API license [2][3].

3. ETL connectors. Tools such as Fivetran list an Epicor Prophet 21 connector that copies P21 tables into a warehouse [9].

Epicor P21 reports

For daily operations reports (open orders, backorders, open POs by vendor, stock below minimum), start with Report Studio. For cross-system reports, such as P21 orders against carrier delivery data, use OData or an ETL connector into one warehouse. Keep one rule: reports read P21, they never change it.

What integration does not fix

Integration moves data that is already structured. It does not:

• read a customer’s PDF PO and decide which of your items they mean;

• notice that a supplier’s email moves a ship date by two weeks;

• chase the supplier who has not confirmed;

• answer “where is my order” in the customer’s thread.

That is why P21 shops with good integrations still employ people to type orders and chase suppliers. EstesGroup’s own reference architecture for “smart” P21 integrations adds AI for loosely structured data and human review via Teams or Slack before posting to P21 [2].

Where Morsa fits: the work integration leaves behind

Morsa is an AI operations layer that runs on top of Prophet 21 and does the unstructured work, then writes clean transactions into P21 through the APIs above.

• Order entry. Morsa reads customer orders from email, PDF and phone photos, matches customer part numbers to your P21 items, asks before guessing, and enters the order in P21. See AI order entry for distributors.

• Supplier dates. Morsa chases suppliers from the buyer’s own mailbox, reads the replies, and updates the promise date on the P21 purchase order. See how to automate supplier follow-up on open purchase orders.

• Shortages. When a slip hits, Morsa lists the customer orders affected and proposes the fix for one-tap approval.

• Where is my order. Morsa answers from P21 status plus carrier tracking.

People approve; Morsa does the typing and chasing. It runs in Morsa’s cloud, a private cloud or fully on premises, and across two ERPs at once during a migration. At J4S, a 120-person glass plant, on-time completion rose from about 30% to about 75% in four weeks [10]. Start with a pilot on one live problem; no per-seat licences, live in days, and “We’ll catch a shortage in your plant, or you don’t pay.”

Book a demo: https://cal.com/morsa

Sources

1. Epicor, Prophet 21 Technology: https://www.epicor.com/en-us/products/enterprise-resource-planning-erp/prophet-21/technology/ (read 21 October 2026)

2. EstesGroup, P21 Integrations: Smart AI, SISM, and API Strategies (August 13, 2025): https://www.estesgrp.com/blog/p21-integrations-smart-ai-sis-and-api-strategies/ (read 21 October 2026)

3. Airdev, Prophet 21 Integrations and API Guide: https://www.airdev.co/erp/prophet-21/integrations (read 21 October 2026)

4. Epicor blog, Prophet 21 2026.1 Is Now Available (June 2, 2026): https://www.epicor.com/en/blog/supply-chain-management/prophet-21-2026-1-is-now-available/ (read 21 October 2026)

5. iPaaS.com, Epicor Prophet 21 integration known limitations: https://support.ipaas.com/en/articles/15693675-epicor-prophet-21-integration-known-limitations (read 21 October 2026)

6. Mind Harbor, Epicor Prophet 21 Integrations: https://www.mindharbor.com/epicor-prophet-21-integrations (read 21 October 2026)

7. Optimizely, Overview of InsiteConnect for Prophet 21: https://webhelp.optimizely.com/latest/en/b2b-commerce-sdk/connectorsandintegrations/erps/overviewprophet21.htm (read 21 October 2026)

8. Epicor, Epicor Prophet 21 product page: https://www.epicor.com/en-us/products/enterprise-resource-planning-erp/prophet-21/ (read 21 October 2026)

9. Fivetran, Epicor Prophet 21 connector: https://www.fivetran.com/connectors/epicor-prophet-21 (read 21 October 2026)

10. Morsa, J4S customer story: https://morsa.ai/customers/j4s (read 21 October 2026)