Prophet 21 automation
Runtara automates the operations work around Epicor Prophet 21: customer orders, supplier invoices and product data move into Prophet 21 automatically, and your team handles only the exceptions. Our team has integrated Prophet 21 for distributors.
Add-onCommon among electrical and industrial distributors, the segment we work with first. Electrical distributors
01 / Workflows
What you can automate.
Customer orders into Prophet 21
Customer orders that arrive by email, PDF, EDI or API become Prophet 21 sales orders, with exceptions held for a person.
Supplier invoice processing
Supplier invoices matched against purchase orders and receipts in Prophet 21, with variances held for approval before they are posted.
Product data and pricing
Supplier price changes from letters, spreadsheets or files go into Prophet 21 price lists and items, with unclear changes held for review.
EDI with trading partners
Orders, invoices and ship notices exchanged with customers and suppliers over EDI or SFTP, connected to Prophet 21 by our team.
02 / Connection
How the connection works.
Runtara connects to Prophet 21 through its API, over EDI, or by file exchange, whichever fits your setup and your trading partners. Our team scopes the connection with your Prophet 21 administrator during implementation.
If Prophet 21 runs on your own servers, Runtara needs network access to it, for example through a VPN. That is part of the access checklist that starts the two-week clock.
Each workflow step declares the connection it uses, and the runtime denies anything else. There is no custom code for your team to own or maintain.
03 / Approval
Exceptions wait for a person.
In the illustrative order PO-58213, five lines match the customer, items and contract prices. Line 04 is priced $26 above contract and is held. Inside sales approves the contract price, and the workflow creates the sales order in Prophet 21.
Everything else posts automatically. One query against the instance database returns the order, the match, the approval, and the ERP response.
04 / Availability
An add-on integration.
Prophet 21 is an add-on, sold separately on request. It is not included in any plan or in the open-source engine. Ask about Prophet 21
- Open-source engineAGPL-3.0, run and operate it yourself.Not included
- CloudWe host and manage your instance.Add-on
- EnterpriseYour cloud or on-premises, supported by our team.Add-on
05 / Questions
Common questions.
Has your team integrated Prophet 21 before?
Yes. Our team has integrated Epicor Prophet 21 for distributors, so the connection behind the workflow is work we have done before.
How long until it is live?
Live in two weeks once access is in place: API keys, system URLs and endpoints, credentials, the specs for your files and EDI documents, and network access for Runtara.
Is Prophet 21 included in my plan?
No. Prophet 21 is an add-on, sold separately on request, and not included in Cloud, Enterprise or the open-source engine. Our team quotes it together with the connection and field mappings for your setup.
Can a person approve before anything is written to the ERP?
Yes. A workflow holds an exception for approval and writes to Prophet 21 only after the person decides. The run keeps the source, the decision, who made it, and the ERP response together.
Which other ERPs do you work with?
Our team has integrated Odoo, QuickBooks, Business Central, Infor CSD/SX.e, Epicor Eclipse. Other ERPs that expose an API, EDI or file exchange are scoped during implementation.
Bring your Prophet 21 process.
Start with a paid pilot of one real process, such as order intake. Our team builds and runs it, live in two weeks once access is in place.
All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.