How to add a mobile app to ECI E2 Shop System
Short answer
Pair a small API layer in front of E2's SQL Server data with a phone or rugged-scanner app for scanning, job lookup and approvals. Reads are straightforward; writes should use E2's own data collection or a supported import, with offline queueing for weak Wi-Fi.
E2 is a desktop product, and the shop floor is not a desktop environment. Operators stand at machines, receivers stand at docks, and managers walk the floor. When the only way to see a job traveler, report labor or move material is a PC in an office, the data arrives late or is keyed from paper.
A mobile app does not replace the E2 client. It gives specific roles a narrow screen: scan a job and see its drawing and next operation, start and stop a labor clock, count a bin, or approve a PO from a phone. Narrow is a feature, because each screen can enforce the rules E2 expects.
This page compares the ways to get there, from E2's shop floor data collection to a custom progressive web app, and explains the offline, scanning and write-safety questions that decide the design.
What teams use it for
Job scan and traveler view
Scan the job barcode to see part, revision, quantity, current operation, notes and a link to the drawing, without walking to a terminal.
Labor start and stop
Operators scan their badge and a job operation, then start or stop time, with prompts for quantity completed and scrap reason.
Receiving with scanning
Scan the PO and part labels at the dock, enter counts, print lot labels, and prepare the receipt for posting.
Inventory moves and cycle counts
Move stock between locations and perform counts by scanning bins, with variances held for supervisor review.
Inspection results capture
Inspectors enter measurements and pass or fail against the job, attach a photo, and trigger a nonconformance flag when needed.
Manager approvals and dashboards
A supervisor views late jobs, WIP and shipments due today, and approves overtime or purchase requests from a phone.
ECI E2 Shop System integration surface
- E2's own shop floor data collection offerings: ECI has historically offered modules for labor and production reporting. Names and capabilities vary by version, so ask ECI what your licence includes before building a duplicate.
- SQL Server read access supports job, operation, inventory and PO lookups through your own API layer. Do not connect phones to the database directly.
- Writes such as labor, receipts and moves have business rules in E2. Use a supported integration or the vendor's data collection path rather than raw table inserts.
- Barcodes: you can generate job, part, location and badge barcodes from E2 data. Code 128 and QR are common choices, and the content should be an ID, not a full record.
- Documents and drawings: a file share or document service with authenticated URLs lets the app show PDFs on the floor, if E2 links point to the same store.
How it works
- 1
Decide the roles and screens
List each role and the three or four actions they do daily. Resist building a general E2 clone on a phone.
- 2
Choose the client type
A progressive web app works on iOS, Android and rugged scanners with a browser, while native apps offer deeper hardware access. Many shops pick a PWA with camera or Bluetooth scanner support.
- 3
Build the API layer
Create a small authenticated service on your network that exposes only the needed lookups and actions, using parameterised queries and a service account with limited rights.
- 4
Connect identity
Authenticate operators with badge or PIN and managers with directory login. Map each to the E2 employee or user record for attribution.
- 5
Handle writes safely
Send transactions to a queue, validate them against E2 rules, and post through a supported path. Show the user a clear success or reject message.
- 6
Plan for offline
Cache job lists and queue scans locally with timestamps, then sync when connectivity returns, resolving duplicates by scan ID.
- 7
Pilot on one cell
Run one work center for two weeks, compare app data with E2 totals, and fix mismatches before rolling out.
Example flows
Operator labor reporting
Trigger: An operator arrives at a machine and scans the job traveler.
- The app shows the job and next operation with the drawing.
- The operator taps Start and the time is queued with badge ID.
- At end of run they enter good and scrap quantities.
- The transaction is validated and posted to E2 labor reporting.
Result: Labor and quantities reach E2 in real time instead of from paper at end of shift.
Dock receiving
Trigger: A truck arrives with material for several POs.
- The receiver scans the PO barcode and sees open lines.
- They enter counts, and the app flags overs and shorts against tolerance.
- Lot labels are printed for lot-tracked parts.
- The prepared receipt is posted after supervisor confirmation for exceptions.
Result: Material is available to the floor faster and receipts are more accurate.
Keeping data on-prem
A shop floor mobile app is naturally an on-prem workload, because the devices are inside your Wi-Fi and E2 is inside your network. Host the API and the web app on a server next to the SQL Server, serve it over HTTPS with an internal certificate authority, and avoid any internet exposure. If managers need access from outside, use a VPN or a zero-trust access proxy rather than opening the API. Keep drawings on the internal file share and serve them through the app with authentication. For AI features such as asking for a job by voice or summarising notes, a small local model on a shop server is enough, so audio and ERP data do not go to a third party. Remember Wi-Fi coverage: dead zones near large machines are the usual failure point, so test offline behaviour early.
Security checklist
- Never expose SQL Server to mobile devices; all access goes through an authenticated API.
- Use per-user identity and role checks for each action, and log device, user and timestamp.
- Encrypt traffic with TLS and enforce device management or at least screen locks on phones.
- Limit drawing access by job and role, especially for controlled technical data.
- Rate-limit and validate scans server-side to prevent duplicate or malicious posts.
Ways to get it done
ECI shop floor data collection module
Effort: Licensing and configuration over days to weeks; confirm mobile support for your version.
Shops wanting a supported route for labor and production reporting with minimal custom work.
Third-party shop floor or MES app with E2 connector
Effort: Weeks, with subscription cost and a data mapping exercise.
Shops wanting a packaged scheduling and tracking tool if a connector exists for their version.
Custom PWA with partner support from Netray
Effort: A scoped project of roughly six to twelve weeks, delivered with an E2 specialist.
Shops with specific workflows, offline needs or AI features that packaged tools do not cover.
Pitfalls
- !Building labor capture that duplicates E2's own tracking can create two sources of truth.
- !Poor Wi-Fi leads to lost scans unless you queue and sync with idempotent IDs.
- !Shared logins on a shop tablet destroy labor attribution; require badge or PIN per action.
- !Giant forms on a phone get abandoned; keep each screen to one task.
- !Skipping a pilot means errors are found by operators in production; compare app totals with E2 first.
Frequently asked questions
Does ECI E2 Shop System have a mobile app?
ECI has offered shop floor data collection and other add-ons over the years, but capabilities depend on version and licence. Ask ECI for the current list. If your needs are specific, a custom web app over an API layer is a practical alternative.
Can a phone scan barcodes for E2?
Yes. A phone camera or a Bluetooth scanner can read Code 128 or QR codes in a web app or native app. The barcode should carry an ID, and the app looks up the record through your API.
Is a PWA good enough, or do we need a native app?
A PWA covers scanning, forms and offline caching for most shop needs. Native apps help with advanced hardware, background sync or device management. Start with a PWA and move to native only for a proven limitation.
How do we post transactions without breaking E2?
Use a supported integration or ECI's data collection path, validate on the server, and avoid direct table writes. Test against a copy of the database and reconcile with E2 totals during a pilot.
What about offline use?
Cache the active job list and queue transactions locally with unique scan IDs. When connectivity returns, sync in order and reject duplicates. Show the user clearly which entries are pending and which have been posted.
Want Mobile app working on your ECI E2 Shop System?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment