E2 Shop System API
JobBOSS2 (E2) has a real API and SDK, but everything lives behind ECI's gated customer portal. There is no public endpoint reference, OpenAPI spec, sandbox, or documented auth flow; third party platforms like Makini exist mainly to wrap the surface for customers.
Frequently asked questions
E2 Shop System scores D on Supergood's API Report Card. JobBOSS2 (E2) has a real API and SDK, but everything lives behind ECI's gated customer portal. There is no public endpoint reference, OpenAPI spec, sandbox, or documented auth flow; third party platforms like Makini exist mainly to wrap the surface for customers.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
E2 Shop System (originally 'E2 SHOP' from Shoptech Industrial Software, since 2021 sold and rebranded as JobBOSS2 by ECI Software Solutions) is a shop-floor-first ERP for small and mid-sized discrete manufacturers, primarily job shops, machine shops, fabrication shops, tool & die shops, stamping and screw shops, assembly shops, and other custom and make-to-order manufacturers.
Vertical: Enterprise/HR/ERP, specifically shop-floor / job shop ERP for SMB discrete manufacturers. Front office uses E2 SHOP / JobBOSS2 to build estimates and quotes for incoming RFQs, including material, labor, outside processing, and markup logic; sales then converts accepted quotes into sales orders and work orders.
Within North American job shop ERP, E2 SHOP / JobBOSS2 is a tier-1 incumbent.
Yes, for an E2 SHOP / JobBOSS2 customer, the platform is the canonical operational system of record.
E2 SHOP originated at Shoptech Industrial Software, a Cleveland, Ohio-based job-shop ERP vendor founded in the mid-1980s; JobBOSS itself was first developed in 1984 by a job-shop manager in the Minneapolis area as a custom in-house shop management system.
No public, self-serve developer portal, API documentation lives behind the ECI customer portal (resource.ecisolutions.com / customerportal.ecisolutions.com), so prospective integrators and ISVs cannot evaluate the API surface without an active JobBOSS2 customer relationship. No published OpenAPI/Swagger spec, no public endpoint reference, no documented rate limits, no public sandbox, third-party integration vendors (Makini, Sellbery) explicitly position their products as wrappers because customers cannot easily integrate themselves. Full sourced list under Sources below.
Common alternatives include Global Shop Solutions, Epicor Kinetic, Infor CloudSuite Industrial (SyteLine), Cetec ERP, MIE Trak Pro, Genius ERP. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official E2 Shop System MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. E2 Shop System doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.