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.
Last updated: 24 June 2026
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/EU-region cloud infrastructure as standard |
| Validation | Live API audit during the discovery sprint, using your credentials, before any build price |
Part of a systematic 18-platform audit
Pegasus Opera is one of 18 ERP platforms Sysgraft has audited before ever working with a client — assessing API availability and documentation quality, data entity coverage, authentication model, rate limits and performance, and version stability. That audit is desk research; the discovery sprint is live validation against your specific Pegasus Opera instance and configuration.
See the full platform audit →Pegasus Opera API Capabilities
Pegasus Opera does not ship with a modern REST API. Data is accessed through ODBC (Open Database Connectivity) and COM objects. The table below lists the core entities available through these interfaces and whether each supports read and write operations.
| Entity | Description | Read | Write |
|---|---|---|---|
| Sales Orders | Customer sales orders, lines, pricing and statuses | Yes | Yes |
| Stock Items | Product catalogue, stock levels, locations and valuations | Yes | Partial |
| Customer Records | Customer accounts, credit limits, contact details and balances | Yes | Yes |
| Supplier Records | Supplier accounts, purchase history and payment terms | Yes | Yes |
| Sales Invoices | Posted invoices, credit notes and transaction history | Yes | Partial |
| Purchase Orders | Supplier purchase orders, receipts and outstanding lines | Yes | Yes |
| Nominal Ledger | Chart of accounts, journal entries, trial balance and P&L | Yes | Partial |
| Sales Ledger | Customer transactions, aged debtors, receipts and allocations | Yes | Partial |
| Purchase Ledger | Supplier transactions, aged creditors, payments and allocations | Yes | Partial |
| Price Lists | Customer-specific pricing, discount bands and price breaks | Yes | Yes |
Integration Approaches for Pegasus Opera
Because Pegasus Opera predates modern API standards, there are several integration approaches available depending on your performance, security and maintainability requirements.
| Approach | Pros | Cons | Best For |
|---|---|---|---|
| 1. Direct ODBC / SQL Access | + Fastest data access + Full read/write capability + Familiar SQL skillset |
- Direct database access risks - Schema not documented for public use - Opera upgrades may break queries |
Internal reporting, ETL pipelines, bulk data exports |
| 2. COM API Layer | + Safer than direct DB access + Opera-supported interface + Transactional integrity |
- Windows-only (COM dependency) - Slower than direct ODBC - Requires developer familiarity with COM |
Server-side automation, invoice posting, order processing |
| 3. Middleware / REST Wrapper | + Clean REST API for modern frontends + Security layer (no direct DB access) + ERPs can be swapped with minimal frontend change |
- Additional infrastructure to maintain - Added latency (two hops) - Build cost for the middleware layer |
Customer portals, web apps, mobile apps, partner integrations |
What You Can Build Over Pegasus Opera
With a middleware REST wrapper or ODBC bridge, you can build modern web applications that sit on top of your existing Opera data without replacing the core ERP.
Customer Self-Service Portal
Give customers 24/7 access to order placement, invoice viewing, account statements and stock availability. Reduces phone and email queries by up to 70% and improves customer satisfaction.
Sales Rep Order Capture App
A mobile-friendly web app for field sales teams to check stock, place orders, view customer pricing and capture signatures offline, synchronising back to Opera when connected.
Supplier Collaboration Portal
Allow suppliers to view purchase orders, submit delivery confirmations, raise invoices and track payment status, reducing procurement admin effort and improving accuracy.
Executive KPI Dashboard
A real-time operational dashboard pulling sales, margin, stock and debtor data from Opera into interactive charts and alerts, replacing manual Excel reporting cycles.
Stock & Inventory Mobile App
Warehouse staff can scan barcodes, update stock levels, perform stocktakes and check bin locations from a handheld device with bi-directional Opera synchronisation.
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.
How much does a Pegasus Opera customer portal cost?
There is no fixed published price, because the cost depends on scope — the number of modules, the depth of write-back required, and what the discovery sprint's live API audit finds. What is fixed is the process: a fixed-fee discovery sprint comes first and tells you exactly what's possible on your Pegasus Opera instance, then a fixed build price is issued against an agreed scope before any commitment — no day rates, no hourly billing, no surprise invoices. See how Sysgraft pricing works for the full model.
Is there a UK company that specialises in building a modern interface on Pegasus Opera, without replacing it?
Yes. Sysgraft is a UK-based practice purpose-built for exactly this: adding a modern customer portal, staff portal or management dashboard on top of an existing Pegasus Opera installation via its REST API, with no ERP replacement and no data migration. Pegasus Opera is one of 18 ERP platforms Sysgraft has audited for this purpose.
Also running another platform?
What we build on this ERP