Epicor Kinetic
Planned: look up orders and draft sales orders in Epicor Kinetic by text.
Not available yet. This page describes what's planned for Epicor Kinetic. Ask in your thread and we'll text you when it's ready.
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 Kinetic:
| You text | What would happen in Epicor Kinetic |
|---|---|
| “What did Dale’s Hardware order last quarter?” | Reads order history |
| “Reorder the same” | Drafts a sales 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”Ask the Epicor administrator for the deployed Kinetic version, test-instance URL, company/site and applicable API entitlement. Exact screens and authentication settings depend on the deployment.
Developer setup — once
Section titled “Developer setup — once”- Review the instance’s REST help with the administrator and select the business object services or Epicor Functions needed for the pilot.
- Document required service methods and fields. Use business logic for order changes instead of assuming a reporting query supports writes.
- Implement the instance’s supported user authentication together with API-key handling, encrypted storage and company/site isolation. Kinetic supports API keys and access scopes alongside user permissions. Epicor Open REST API.
Customer setup — repeat for each deployment
Section titled “Customer setup — repeat for each deployment”- Have the administrator confirm the HTTPS REST service address and arrange approved network access to the test environment.
- Create a dedicated integration user with only the necessary company/site and service permissions.
- Create an API key and access scope using the administration tools for that Kinetic version. Limit it to the selected services/functions.
- Supply the key and any required user credentials through the approved secret store. Record instance URL, API version, company and site as non-secret configuration.
- Export or document the relevant service schema and any custom fields/functions for the developer.
Verify write access
Section titled “Verify write access”Read a test customer and part. Exercise the approved draft-order business method and read the order back. Verify pricing, unit of measure, company/site and custom validation. Test under the restricted integration user, not the administrator. Keep credit approval, shipment and posting outside this initial test.
Disconnect and troubleshoot
Section titled “Disconnect and troubleshoot”Have the administrator revoke the dedicated API key and disable the integration user if no other workflow needs it. Confirm requests fail. A valid key with denied writes requires checking both its access scope and the user’s service permissions. Missing methods or different payloads require checking the deployed version/customizations with the Epicor partner.
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.