Pegasus Opera Customer Portal & Staff Portal — Without Replacing Pegasus Opera
Yes — you can add a modern customer portal, staff portal and management dashboard to Pegasus Opera without replacing it. Sysgraft connects to the Pegasus Opera API and builds a bespoke interface layer on top, for UK manufacturers and distributors. No ERP replacement, fixed-price build, UK-hosted.
A long-established UK ERP/finance system with a loyal SME base in manufacturing and distribution.
Where Pegasus Opera slows your people and customers down
Opera's interface is firmly desktop-era and version-dependent; customer self-service is absent and management reporting leans on exports. The biggest variable is how much the installed version exposes programmatically.
Built for the way Pegasus Opera data is actually used
- A customer portal for orders, statements and invoices
- A management dashboard over Opera financial and sales data
- A staff portal for order entry and stock lookup
Opera can support interface layers, but feasibility depends on version and configuration more than most platforms — which is exactly what the discovery sprint exists to confirm before any build commitment.
Connecting to Pegasus Opera
| API model | API coverage varies by version (Opera 3 vs Opera SE); access is via the Pegasus SDK / web service layer and is confirmed per deployment. |
| Authentication | SDK / service-layer authentication; staff SSO via Entra at the portal. |
| Key entities | Sales Orders, Stock, Customers, Nominal, Invoices (version dependent) |
| Hosting | UK data residency — AWS eu-west-2 or Azure UK South |
| Validation | Live API audit during the discovery sprint, using your credentials, before any build price |
Pegasus Opera interface layer FAQ
Can you add a customer portal and staff portal to Pegasus Opera without replacing it?
Yes. Sysgraft builds a modern interface layer over Pegasus Opera via its API, leaving the ERP exactly as it is. API coverage varies by version (Opera 3 vs Opera SE); access is via the Pegasus SDK / web service layer and is confirmed per deployment. SDK / service-layer authentication; staff SSO via Entra at the portal.
Does Pegasus Opera have an API we can use?
Yes. API coverage varies by version (Opera 3 vs Opera SE); access is via the Pegasus SDK / web service layer and is confirmed per deployment. The discovery sprint includes a live API audit against your instance using your credentials before any build price is issued.
Will it work with our version of Opera?
That is the key question for Opera specifically, because API coverage varies between Opera 3 and SE and by configuration. We confirm feasibility in the discovery sprint before issuing any build price.
How is the build priced?
Every project starts with a fixed-price discovery sprint that scopes and prices the build. The build itself is fixed price, followed by a cancellable monthly subscription for hosting, support and ERP API monitoring.
Also running another platform?