ProShop with DigiOS.
ProShop's work orders reach the floor, and what people do on them, their time and their quantities, goes back against the operation.
What moves each way
- Work orders and operations: Into DigiOS
- Parts: Into DigiOS
- Workcells and users: Into DigiOS
- Time tracking: Out of DigiOS
- Operation completion: Out of DigiOS
| What | Direction | Documents and data | When |
|---|---|---|---|
| Work orders and operations | In | Open work orders with their operations, due dates and quantities | On a schedule you set |
| Parts | In | Parts and their part numbers, so a work order's material and output are named correctly | On a schedule you set |
| Workcells and users | In | Workcells and the people who run them | On a schedule you set |
| Time tracking | Out | Clock in and out times, the person, good and scrapped quantities and notes against a work order operation | When a person closes a job step |
| Operation completion | Out | An operation marked complete once its quantity is done | When the last step closes |
On your floor
Orders and item lists in. Receipts and stock levels out.
RESTLast exchange 10:40Charges for the work out, to be invoiced.
RESTLast exchange 10:15Orders in. Shipment confirmations and stock levels out.
RESTWebhooksLast exchange 10:41Orders in. Shipment confirmations out.
RESTLast exchange 10:39Labels and pickup bookings out. Tracking numbers back.
RESTLast exchange 10:42Labels and pickup bookings out. Tracking numbers back.
RESTLast exchange 10:36Purchase orders and advance notices in. Shipment notices out.
X12 850, 856, 945AS2Last exchange 09:58The 09:58 purchase order (850) was turned back: ship-to code 4471 is not in your list of retailer stores.
Sam can actOpen the orderJobs out to each handheld. Scans back. Labels printed in ZPL.
ZPLLast exchange 10:42Scale weights and line signals in. Sort instructions out.
EtherNet/IPOPC UALast exchange 10:42How DigiOS works with ProShop
DigiOS connects to your ProShop instance through its GraphQL API, signed in with an OAuth 2.0 client that your ProShop administrator creates. Work orders come down to the floor, and what people do on them goes back as time tracking entries against the operation.
- Where it stands
- Planned1 Nov 2026
- About ProShop
- ProShop is an ERP and quality system built for machine shops and other job-based manufacturers.
- Your account
- You keep your ProShop license and its administrator. DigiOS uses the access your administrator creates for it, and you can take that access away at any time.
- If a document is rejected
- A time or material entry that ProShop refuses goes to one queue with ProShop's message. Fix it there or in the mapping and send it again, and hours are never counted twice.
Questions about ProShop
Does DigiOS replace ProShop?
No. ProShop keeps the work orders, the quality plans and the books. DigiOS puts the work in front of people and machines and sends back what they did.
What if an operation has no workcell in ProShop?
It shows on the floor under a default workcell you name, so a person can still pick it up.
Is a repeat send a problem?
No. A time entry that is sent again updates the same entry rather than adding hours twice.
Ask about ProShop.
Tell us what you run and what you want ProShop to do. A person answers in writing.