Integrations
STRYKE and ProShop ERP
We hold no public API specification for ProShop ERP, so STRYKE starts from what your shop has: the API documentation and your keys, built and tested before anything is written, or the desktop runner keying into ProShop's own screens.
How the connection works
Tell us your ERP, or the desktop runner.
- You point STRYKE at ProShop's API documentation: a link, a PDF or pasted text
- STRYKE builds the connection from it and your keys, then tests it by reading only
- Nothing is written until that test passes
- Without an API you can use, STRYKE's desktop runner on one shop PC keys the entry into ProShop's screens
What a PO becomes in ProShop ERP
A sales order, with the checks every STRYKE entry gets.
- A sales order with the customer PO number, lines, quantity, price and due date
- Every line matched to your part number and checked against your quote before it is written
- 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
- Vendor invoices go to your books as Bills
What to have ready
One of these, depending on the door.
- ProShop's API documentation, the address it answers at and the keys it names
- Or one shop PC that stays signed into ProShop, for the runner
Read the vendor's own pages
ProShop ERP publishes these; they are its pages, not ours.
- ProShop ERP
- Product names describe compatibility only; STRYKE is not affiliated with ProShop ERP.
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.
