A manufacturing management system that puts SYSPRO on the shop floor.
Flexible Metal, part of the Hyspan group, makes metal bellows, hose and tubular assemblies for Tier-1 automotive and off-highway customers. Its ERP processes were disconnected from the floor: inventory updates were manual, PO status was opaque, and scrap reporting needed SYSPRO access most staff didn't have. We built a Power Apps manufacturing management system that posts to SYSPRO through a .NET API and a WCF bridge. It's live and still being enhanced, and a person approves every PO and every supervisor transaction.
| Before | With the Power Apps system | |
|---|---|---|
| Inventory updates | Manual entry, with errors | Floor staff post their own transactions |
| PO status | Opaque, chased by phone and spreadsheet | Visible in real time |
| Scrap reporting | Needed direct SYSPRO access | Captured at source with a standard reason code |
| Defect data | Recorded on paper, nobody could analyse it | Defect trends analysable for the first time |
| Transfers and cycle counts | Queued behind someone with ERP access | Posted by the operator who does the work |
| ERP integration | Workarounds creating a second version of the truth | One bridge into SYSPRO business objects |
Operators sign in with Microsoft SSO and see only the modules they're permitted. They pick a transaction on a tablet or desktop, and the app calls a .NET REST API. The API turns the call into SYSPRO business-object XML and posts it through a WCF bridge.
Staff record transactions in the app, with warehouse and bin lookups, instead of keying them twice. The project team saw fewer manual entry errors.
Inventory and PO status are visible across all production lines, replacing phone calls and spreadsheet chasing.
Data consistency is maintained with SYSPRO, because every transaction goes through the business-object bridge rather than around the ERP.
Scrap is reported against eight standard defect reasons, which makes defect trends analysable for the first time.
PO inspection uses multi-point checklists, with disposition tracking for non-conforming material.
Transfers, scrap and cycle counts no longer wait for someone with ERP access.
SYSPRO exposes WCF business objects and XML, not REST. The API translates between the two, so the ERP's configuration and data structures stay untouched.
POs route through Power Automate for approval, supervisor transactions are limited to supervisors, and admins grant module access per user.
A browser-based app on tablets means operators don't need ERP expertise or licences, and no separate IT ticket is needed to grant access.
Yes. It's in production and still being enhanced.
Power Apps calls a .NET Web API. The API sends SYSPRO business-object XML through a WCF bridge to SYSPRO e.net, in both directions, without changing the existing ERP configuration or data structures.
POs are routed for approval through Power Automate. Supervisor-only transactions are limited to supervisors, and admins decide which modules each person can use.
Tell us which transactions your operators can't reach today. We'll show you how a Power Apps layer can post them to your ERP.

Founder and CEO

Chief Sales Officer
Thanks, we’ve got your details. A named member of our team will reply within one business day.
Talk to a QServices solutions architect about your ERP. You'll leave with two or three automation ideas you can act on, even if you never work with us.