Epicor Prophet 21
Planned: look up orders and draft sales orders in Prophet 21 by text.
Todavía no está disponible. Esta página describe lo que tenemos planeado para Epicor Prophet 21. Pregunta en tu chat y te avisamos por mensaje cuando esté listo.
Esta página todavía no está traducida. Te mostramos la versión en inglés.
Status: planned — not available to connect in Tack yet. These steps prepare the integration; creating vendor credentials does not enable it in the app.
Planned workflows
Section titled “Planned workflows”Planned for Epicor Prophet 21:
| You text | What would happen in Epicor Prophet 21 |
|---|---|
| “What did Dale’s Hardware order last quarter?” | Reads order history |
| “Reorder the same” | Drafts an order |
These are intended workflows, not a guarantee that every operation is exposed by the vendor. Each must pass the API and permission checks below before release.
Before you start
Section titled “Before you start”This is an administrator/implementation-partner setup, not a self-service OAuth connection. Obtain the customer’s Prophet 21 version and approved middleware/API documentation before choosing an authentication flow. Epicor provides customer resources through EpicCare and EpicWeb.
Developer setup — once
Section titled “Developer setup — once”- Ask Epicor or the customer’s partner to confirm the supported API for customer lookup and sales-order creation, required licenses and compatible middleware version.
- Obtain the authenticated developer guide, endpoint schema, authentication/token instructions and transaction examples for that deployment. Public middleware documentation may require a login; do not infer the protocol from its login form.
- Implement the documented transaction workflow and validation rules. A read-only reporting endpoint is not sufficient for order creation.
Customer setup — repeat for each deployment
Section titled “Customer setup — repeat for each deployment”- The P21 administrator identifies the test company, middleware HTTPS base URL and network-access requirements.
- The administrator or Epicor partner installs/enables the supported middleware and confirms API licensing. Do not expose a database or admin service directly to the internet.
- Create a dedicated API identity and any consumer key required by that version’s official guide. Confirm customer/order permissions and company/location restrictions.
- Store credentials through the secure setup process; record the version, company, location and endpoint URLs separately.
- Provide a test customer, item, warehouse, price setup and order type. Agree on an uncommitted/draft transaction path before writes are enabled.
Verify write access
Section titled “Verify write access”Read the test customer and item, run the documented order-entry sequence and inspect validation messages. Verify the resulting test order in P21 with an operator. Confirm retries do not duplicate it and that no stock is shipped or invoice posted.
Disconnect and unresolved details
Section titled “Disconnect and unresolved details”The administrator must revoke the API identity/consumer key using the procedure supplied for the installed middleware. Stop queued work and verify subsequent calls fail. Exact token endpoints, key-management screens and transaction methods remain blocked on the customer’s official version-specific guide; they are intentionally not invented here.
Who completes the work?
Section titled “Who completes the work?”An agent/developer can implement the connector, field mappings and automated checks. A customer administrator must authorize account access and permissions; the vendor must approve any restricted partner access. A business operator verifies the test records before production use. Follow the shared setup and release checklist for credential handling, approval gates and launch checks.
Setup guidance reviewed October 23, 2026. Vendor menus and entitlements can change; unresolved details are called out above.