Every system STRYKE enters into
STRYKE gets into an ERP one of three ways: its API with your own keys, an import file your ERP takes in, or the desktop runner keying the entry into its screens. The books take one sign-in at Intuit. Here is the way each system goes, and what it asks of you.
-
JobBOSS²
ECI's public API, with your own keys. A PO becomes an Order and its Jobs.
STRYKE and JobBOSS² -
Odoo
Odoo's external API, with an API key you make. A PO becomes a confirmed sales order.
STRYKE and Odoo -
Epicor Kinetic
Built from your instance's own REST API documentation, with your keys, tested before any write.
STRYKE and Epicor Kinetic -
Global Shop Solutions
From the API documentation your shop holds, or an import file, or the desktop runner.
STRYKE and Global Shop Solutions -
ProShop ERP
From the API documentation your shop has, with your keys, or the desktop runner.
STRYKE and ProShop ERP -
E2 Shop System
E2 is JobBOSS² under its old name: its API on JobBOSS², an import file or the runner on classic E2.
STRYKE and E2 Shop System -
NetSuite
In pilot: a connection drafted from Oracle's SuiteTalk REST documentation, tested with your keys.
STRYKE and NetSuite -
QuickBooks Online
One sign-in at Intuit. Vendor invoices become Bills with the PDF, shipments Invoices, remittances Payments.
STRYKE and QuickBooks Online
Tell us your ERP in the first of the five questions. If it has an API, STRYKE builds the connection from its documentation and your keys and tests it before anything is written; if it has an import or only screens, the import file or the runner is the way in. Product names describe compatibility only; STRYKE is not affiliated with these vendors.