OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured APIs across the declared product scope
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
Epicor describes structured REST service access to business objects, processes, reports and BAQs. Tenant/version coverage needs installed help.
Kinetic Open REST API ↗
Complete ERP Coverage Through REST · Checked 2026-10-16
Bulk delivery -
-
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
Iterable collection paging and a complete bulk extraction contract are not established by the reviewed public capability page.
Kinetic Open REST API ↗
OData-Compliant Query And Metadata · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
The public API overview documents OData v4 query parameters and metadata; arbitrary operational SQL is not credited.
Kinetic Open REST API ↗
OData-Compliant Query And Metadata · Checked 2026-10-16
Access cost barrier -
-
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation.
Kinetic Open REST API ↗
Kinetic Open REST API · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
Eligibility for a chosen third-party application, beyond the documented technical authorization, remains unestablished.
Kinetic Open REST API ↗
Kinetic Open REST API · Checked 2026-10-16
Downstream permission -
-
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
Applicable downstream processing, redistribution and AI-use conditions remain unestablished for the declared route.
Kinetic Open REST API ↗
Kinetic Open REST API · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface -
-
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
The public overview describes update capability but provides no named create/update operation contract. Installed REST help is needed before assigning a write score.
Kinetic Open REST API ↗
Open REST API overview · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
The REST architecture supports customer external applications within API scopes and ERP permissions. Contractual third-party eligibility remains separate.
Kinetic Open REST API ↗
Secure external integration support · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism -
-
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
A general updated-record extraction contract is not established for every assessed object.
Kinetic Open REST API ↗
Kinetic Open REST API · Checked 2026-10-16
Limit visibility -
-
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
The reviewed interface does not establish a universal numeric request quota and recovery contract.
Kinetic Open REST API ↗
Kinetic Open REST API · Checked 2026-10-16
CDC and deletion capture -
-
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
Complete deletion identity coverage is not established on this assessed route.
Kinetic Open REST API ↗
Kinetic Open REST API · Checked 2026-10-16
Replay and gap recovery -
-
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
A retained replay window, durable consumer checkpoint and gap-recovery contract are not established for this route.
Kinetic Open REST API ↗
Kinetic Open REST API · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
External services expose structured ERP data suitable for a scoped record copy; full export completeness is unresolved.
Kinetic Open REST API ↗
Structured data and methods · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination.
Kinetic Open REST API ↗
Kinetic Open REST API · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
Service records are portable, while a complete product/native backup is not established.
Kinetic Open REST API ↗
Platform-Level API For Extending ERP · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 7.5/10
Customer-authored native scripts or custom APIs
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
Customer-defined Epicor Functions are reusable server-side logic invoked through the API.
Kinetic tools and technology ↗
Epicor Functions · Checked 2026-10-16
Rights to custom logic -
-
Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded.
Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished.
Kinetic Open REST API ↗
Kinetic Open REST API · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Epicor documents API keys, access scopes and existing ERP user/data permissions for external integrations. Exact credential provisioning and chosen-third-party contractual eligibility must be confirmed for the deployed version.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
The product describes OData v4 queries and metadata plus business-object and BAQ endpoints. The installed interactive REST help remains the authoritative inventory for a customer’s exact services and methods.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-enabled Kinetic REST services | API key | Customer | Not confirmed | product and contract scope | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The current public product documentation does not establish the minimum licensed plan or a universal fixed API surcharge. API entitlement, deployment and implementation charges need a current quote.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The public overview describes updates and configured Function execution, but a named write operation contract remains unverified. Inspect installed REST help before choosing any mutation.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
REST reads can be repeated, but the reviewed public material does not establish a universal update/deletion feed or retained recovery window. Validate each selected BAQ or business-object interface before scheduling sync.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. Complete deletion identity coverage is not established on this assessed route. | Kinetic Open REST API ↗Kinetic Open REST APIChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. A retained replay window, durable consumer checkpoint and gap-recovery contract are not established for this route. | Kinetic Open REST API ↗Kinetic Open REST APIChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Service responses can support a scoped structured record copy. A complete native backup, attachment inventory and executable customization restore are not established by the public REST overview.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can define Epicor Functions and expose them through REST. Their native runtime and independent reuse rights still need verification (remote invocation is not portable execution).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured APIs across the declared product scopeEpicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. Epicor describes structured REST service access to business objects, processes, reports and BAQs. Tenant/version coverage needs installed help. | Kinetic Open REST API ↗Complete ERP Coverage Through RESTChecked 2026-10-16 |
| How can customers retrieve data in bulk? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. Iterable collection paging and a complete bulk extraction contract are not established by the reviewed public capability page. | Kinetic Open REST API ↗OData-Compliant Query And MetadataChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersEpicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. The public API overview documents OData v4 query parameters and metadata; arbitrary operational SQL is not credited. | Kinetic Open REST API ↗OData-Compliant Query And MetadataChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. Eligibility for a chosen third-party application, beyond the documented technical authorization, remains unestablished. | Kinetic Open REST API ↗Kinetic Open REST APIChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation. | Kinetic Open REST API ↗Kinetic Open REST APIChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. Applicable downstream processing, redistribution and AI-use conditions remain unestablished for the declared route. | Kinetic Open REST API ↗Kinetic Open REST APIChecked 2026-10-16 |
| Which external write operations are documented? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. The public overview describes update capability but provides no named create/update operation contract. Installed REST help is needed before assigning a write score. | Kinetic Open REST API ↗Open REST API overviewChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionEpicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. The REST architecture supports customer external applications within API scopes and ERP permissions. Contractual third-party eligibility remains separate. | Kinetic Open REST API ↗Secure external integration supportChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. A general updated-record extraction contract is not established for every assessed object. | Kinetic Open REST API ↗Kinetic Open REST APIChecked 2026-10-16 |
| How are integration limits disclosed? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. The reviewed interface does not establish a universal numeric request quota and recovery contract. | Kinetic Open REST API ↗Kinetic Open REST APIChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsEpicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. External services expose structured ERP data suitable for a scoped record copy; full export completeness is unresolved. | Kinetic Open REST API ↗Structured data and methodsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination. | Kinetic Open REST API ↗Kinetic Open REST APIChecked 2026-10-16 |
| How can customers define their own business logic? | Customer-authored native scripts or custom APIsEpicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. Customer-defined Epicor Functions are reusable server-side logic invoked through the API. | Kinetic tools and technology ↗Epicor FunctionsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Epicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished. | Kinetic Open REST API ↗Kinetic Open REST APIChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedEpicor Kinetic customer-enabled Open REST API and BAQ/business-object services; licensed deployment/version, object grants and API scopes remain prerequisites. Other Epicor products are excluded. Service records are portable, while a complete product/native backup is not established. | Kinetic Open REST API ↗Platform-Level API For Extending ERPChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Bulk delivery: Iterable collection paging and a complete bulk extraction contract are not established by the reviewed public capability page.
- Third-party eligibility: Eligibility for a chosen third-party application, beyond the documented technical authorization, remains unestablished.
- Access cost barrier: The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation.
- Downstream permission: Applicable downstream processing, redistribution and AI-use conditions remain unestablished for the declared route.
- Write interface: The public overview describes update capability but provides no named create/update operation contract. Installed REST help is needed before assigning a write score.
- Refresh mechanism: A general updated-record extraction contract is not established for every assessed object.
- Limit visibility: The reviewed interface does not establish a universal numeric request quota and recovery contract.
- Post-cancellation access: The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination.
- Rights to custom logic: Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished.
- CDC and deletion capture: Complete deletion identity coverage is not established on this assessed route.
- Replay and gap recovery: A retained replay window, durable consumer checkpoint and gap-recovery contract are not established for this route.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.