Enterprise Order Management: Modernizing a Legacy Legal-Services Operation into a Secure Web Platform

August 31, 2026

Enterprise Order Management (EOM) is a custom web application Odyssey built to run the day-to-day operations of a mid-sized legal support services firm in San Diego. The company coordinates a wide range of attorney-facing services, including service of process, court filings, medical and business record retrieval, research, photocopying, and copy-centre work, each with its own workflow, billing rules, and compliance requirements. Odyssey replaced the firm’s aging terminal-based system with a secure, intuitive, browser-based platform, without losing the operational depth the business had built up over decades.

The Challenge: Decades of business logic trapped in a green-screen system

The firm had been running on a legacy terminal-based application, a text-only, keyboard-driven system accessed over a Telnet connection. It was robust and deeply embedded in the business, but it came with real limitations: it was difficult to learn, offered no self-service for clients, and could not provide the real-time visibility that both staff and customers increasingly expected.

Replacing it was not a simple screen refresh. The old system encoded countless edge cases across service types, billing codes, and check handling, knowledge accumulated over many years of real operations. The goal was to modernize the experience while preserving that hard-won business logic exactly.

Three challenges defined the project:

  • Deep, decades-old business logic that had to be surfaced and understood before it could be rebuilt.
  • Multiple departments on one platform, each operating independently but cooperatively, with different permissions and notification needs.
  • Sensitive legal data, including subpoenas, proofs of service, and confidential records, demanding security and accountability from the outset.

Objectives

The engagement was shaped by a clear set of goals agreed with the client at the outset:

  • Deliver all functionality required to manage orders internally end-to-end, including client management and full accounting.
  • Modernize the operation through a web-based implementation for a more efficient, scalable enterprise.
  • Provide a secure interface appropriate to the sensitive nature of legal documentation and services.
  • Enable customers to submit orders conveniently over the web, removing friction from a traditionally tedious process.
  • Give customers real-time access to order status and progress.

Discovery: Grounding the design in real cases

Because EOM was replacing a system that encoded years of operational know-how, discovery was intensive and highly collaborative. The work was informed by an ongoing dialogue between Odyssey’s design team, the agency managing the engagement, and the client’s own domain experts, who knew every edge case of the existing workflows.

Working sessions walked through the legacy screens one by one, capturing not just what each screen did but why, and where the current process created unnecessary work. Meeting notes, annotated screenshots, and real order documents, such as subpoenas, proofs of service, and billing sheets, were used so the new designs were grounded in genuine cases rather than idealized examples.

A key insight: eliminating duplicate data entry

One of the most valuable discoveries concerned how new orders were entered. In the legacy process, an order might be placed by a client, then reviewed by a research team who added the correct codes and locations, before being handed to yet another person who created the final order, effectively re-keying the same information more than once.

The redesigned workflow removed this redundancy by letting each role build on the same evolving record:

  1. The client enters the order online, creating an initial pre-order record.
  2. The research team reviews “New Orders,” then adds the correct codes and locations.
  3. The order advances to “Ready Orders” once research is complete.
  4. The operations team picks up “Ready” orders and finalizes each one, without re-entering anything already captured.

This single change reduced data entry, cut the risk of transcription errors, and gave every team a shared, always-current view of where an order stood.

The Solution: Two connected portals, built around real workflows

EOM was delivered in two connected parts: a powerful internal administration portal for staff to process and track orders, manage clients, and run accounts receivable; and a client-facing portal that lets customers submit and track orders, search records, download documents, and request updates online.

Role-driven navigation instead of an “admin” catch-all

A central design question was how to serve many departments, each with different responsibilities and permissions, without overwhelming any single user. Rather than a traditional “Admin” section, Odyssey adopted a role-driven model: features simply do not appear for users who lack the right role.

Navigation was organized around the core service lines and business functions, Photocopy, Process, and Copy Centers, each with its own orders, document prep, billing, and reports, alongside Accounting, Field Agents, and a cross-cutting Clients reference. A guiding principle emerged: give users access to the same data from different starting points, so a user can begin from a client record, an order list, or a specific location and still reach the detail they need, with every action gated by role and changes logged for accountability.

Guided, multi-location order entry

Orders frequently span multiple locations, for example, several hospitals from which records must be obtained. Odyssey designed a guided flow in which the number of locations is known up front. After completing the main sections, a step-by-step “add location” modal, headed “Location 1 of 5,” presents the next location each time one is saved. Users can skip, add, or correct locations, and the order’s location count updates automatically.

Smart inputs that reduce effort

The interface was designed to make dense operational data scannable and actionable, and to remove the small frictions that slowed staff down:

  • Searchable custodian lookup. Custodians are pre-entered, so users pick from a searchable dropdown and the address auto-fills.
  • Multi-select record types. A single order can request multiple record types (for example, Billing and Medical) at once, something the legacy system could not do.
  • Auto-filled request notes are pre-populated based on the record type and remain editable, with a deliberately larger notes area after the team observed staff working around the old system’s limits.
  • Context-aware activity logging, all those activity entries default to the current user but stay editable, with a searchable code-and-description dropdown.
  • Order-bound client details of an existing client record can be pulled in, but the name stays bound to that order so future client changes never rewrite historical records.

Accounting and Billing that mirror how the business reconciles money

Accounting was one of the most intricate areas, and its rules were documented in detail during discovery so they could be carried faithfully into the new system. All sales, receipts, and adjustments are recorded in an accounts-receivable transaction file reflecting each client’s aged balance; invoices are marked paid as payments are applied, and overpayments are flagged.

A particularly detailed requirement concerned the working-account check database, which tracks every check issued. When a location is billed, any unbilled check generates an invoice line item, a check charge is computed where applicable, and the check record is stamped with the invoice number and date, the mechanism that ensures every check is eventually billed. The database is reconciled against cleared-check data from the bank so outstanding checks are always visible. Because billing accuracy is central to the business, where a single missed check has real financial consequences, documenting these rules during design rather than discovering them mid-build was essential.

Technology

EOM was built on a modern, enterprise-grade Microsoft and Angular stack, chosen for security, scalability, and long-term maintainability, exactly the qualities a system handling sensitive legal data demands. Security was engineered in from the ground up, with role-based access control and multi-factor authentication underpinning the role-driven design described above.

  • Front end: Angular, TypeScript, HTML5 / CSS3 / SCSS, Angular Material, RxJS
  • Back end: .NET 6, ASP.NET Core Web API, C#, Entity Framework Core, AutoMapper, Swagger / OpenAPI
  • Database: Microsoft SQL Server
  • Security & authentication: ASP.NET Core Identity, JWT authentication, OpenID Connect / OAuth 2.0, role-based access control (RBAC), multi-factor authentication, HTTPS / TLS
  • Reporting and documents: ActiveReports (PDF and Excel generation), CsvHelper (CSV export), secure file upload / download
  • Cloud and infrastructure: Microsoft Azure App Service, Azure Functions, Azure Blob Storage
  • Integration and communication: SendGrid (transactional email), FTP (FluentFTP)
  • DevOps and testing: Git / Bitbucket, Bitbucket Pipelines (CI/CD), Docker, MSTest, Moq, FluentAssertions

The Outcome

EOM replaces a friction-heavy, terminal-based operation with a modern web platform that streamlines order management for a more efficient enterprise while giving customers the convenience they expect.

  • Internally, staff gain compact, sortable order views, guided data entry, role-appropriate access, and accounting tools that mirror the real reconciliation process.
  • Externally, clients can submit and track orders, search the database, view or download records, and request updates entirely online.
  • Operationally, the shared, status-driven order record removes redundant re-keying and gives every department a single, current view of each order.

By taking the friction out of what has traditionally been a challenging and tedious process, the platform supports the business in delivering outsourced attorney services faster, more accurately, and with far greater transparency for everyone involved.

Why This Project Matters

Modernizing a legacy system is one of the hardest things a business can undertake, precisely because the old system usually works, and quietly holds years of irreplaceable operational logic. EOM shows how Odyssey approaches that challenge: intensive discovery to surface the real rules, designs grounded in genuine cases, a security-first architecture for sensitive data, and an interface that respects how people actually work.

If your business is running on an aging system that has become a bottleneck, we can help you modernize it without losing what makes it work. Learn more about our Web App Development and Enterprise Software Development services, or read our guide to legacy system modernization.

Ready to modernize your operations? Contact Odyssey Computing for a free consultation.

Useful Articles

Software Development

Legacy System Modernization: When It’s Time to Replace Aging Business Software

Plenty of successful companies put off legacy system modernization even as their software is...

Read More
August 28, 2026
App Development

AI Code Maintainability: Can AI Write Your Code and Still Maintain It?

The hidden risks of AI-generated codebases and the sustainable model that prevents them AI...

Read More
August 25, 2026
Software Development

Is Your Custom Software Ready for 2026? 

If you are relying on custom software to run your business today, you are already ahead...

Read More
April 14, 2026
Software Development

Agentic Workflows for Software Development in 2026 

Software teams are entering a new era where automation is no longer limited to simple scripts or...

Read More
March 25, 2026

We can't wait to hear all your ideas!