Integrations
STRYKE and E2 Shop System
E2 Shop System is the name JobBOSS² had before ECI renamed it; in ECI's words, "JobBOSS², formerly known as E2." A shop that has moved to JobBOSS² connects by its API. A shop still on a classic E2 install uses an import file or the desktop runner.
How the connection works
It depends on which E2 you run today.
- On JobBOSS²: ECI's public API, with your own keys, exactly as on the JobBOSS² page
- On a classic E2 install: an import file STRYKE writes for each entry, or the desktop runner keying into E2's own screens
- Through an import file or the runner, STRYKE cannot ask the ERP whether a PO is already in, so that check waits for a person's one click
What a PO becomes in E2 Shop System
An Order and its Jobs, as your order desk enters them.
- An Order with the customer PO number, lines, quantity, unit price and due date
- On JobBOSS², the Jobs it cuts from the Order, one per line
- Every line matched to your part number and checked against your quote before it is written
- Vendor invoices go to your books as Bills
What to have ready
One of these, depending on your install.
- On JobBOSS²: the ECI host, client id, client secret, API key and company code
- On classic E2: your import map, or one shop PC that stays signed into E2, for the runner
Read the vendor's own pages
ECI publishes these; they are its pages, not ours.
Starting at $500 a month*
Every document, every system you connect. No seats, no per-system fees, month to month. *Plans scale with your document volume. How pricing works.
