What API2Cart Is Evaluating for ECI M1 Integration
Candidate workflow
Connect digital inquiries or orders with customers, parts, jobs, inventory, and shipments. Final entity and method coverage will follow verified vendor interfaces and customer requirements.
Operational outcome
The intended result is to retain plant, job, operation, material, lot, cost, and due-date relationships. Identity rules and idempotency would be defined before transactional writes are enabled.
ERP safeguards
The design must support shop-floor workflows without creating incomplete production demand. Customers, products, sales orders, fulfillments, invoices, and production records would keep their distinct lifecycle roles.
Develop Integrations Faster and Save Up to 9x on Costs
Trusted by
What We Know About ECI M1 So Far
Based on ECI M1’s own documentation and API2Cart’s discovery process — not a promise of a release date.
API & Integration. M1 is served by ECI's shared, product-agnostic "ECI Manufacturing API" (also covering Deacom, Macola, and JobBOSS²) rather than having its own standalone API. It includes a versioned Authentication API (authentication-v1) that issues an access token required on all subsequent calls, and some endpoints are restricted to hosted/cloud-deployed customers only. Public OpenAPI/reference documentation is not generally available; access and detailed specs are typically arranged through ECI's product support or partner channel.
ECI M1 integration is not live yet. Authentication, modules, entities, fields, writes, events, limits, editions, and release timing remain subject to technical discovery and demand.
Background. M1 is ECI Software Solutions’ manufacturing ERP for small and midsize producers. It connects quoting, order entry, bills of material, production, purchasing, inventory, shipping, invoicing, and financial processes in one operational system.
Where it specializes. ECI positions M1 for discrete manufacturers, including make-to-order, engineer-to-order, configure-to-order, and mixed-mode environments. Its strongest integration context is therefore not a simple catalog: parts can carry revisions, routings, material requirements, labor operations, job status, costing, and links between customer demand and shop-floor execution.
Integration challenge. ECI documents an M1 Public API that can read, create, update, and delete ERP data and connect CRM, ecommerce, IoT, and other applications. Availability still has to be verified for the customer’s exact M1 version, deployment, license, and security configuration. API2Cart discovery must identify exposed entities and custom fields, company and warehouse scope, part revisions and units, job and order state transitions, pagination and throttling, and which writes trigger costing, purchasing, production, or shipping workflows.
Technical validation. Engineering must confirm API or integration services, authentication, cloud/on-prem topology, and supported objects. Unsupported modules and operations would remain outside the public scope.
Roadmap evaluation considers API maturity, sandbox access, operational correctness, commerce relevance, scale, customer demand, maintenance cost, deployment variants, and overlap with existing connectors. This page records a candidate, not a promised release date.
Primary sources: ECI M1 manufacturing ERP features · ECI M1 integrations and Public API · ECI M1 product overview
Related planned integrations: Global Shop Solutions ERP integration · Cetec ERP integration · MRPeasy integration · Genius ERP integration
Interested in ECI M1 Integration?
Let us know you’re interested, and we’ll notify you as soon as ECI M1 support becomes available.
