At work · OMIC USA
QUOLims and the 2026 price update
The lab's quoting system, rebuilt, and a price change across three production databases.
The internal product report I wrote for the rebuild
What it is
QUOLims is how 20 staff turn a customer's request into a quote, and a quote into a work order the lab runs. The original is an ASP.NET WebForms app I helped build as part of a three-person team.
The rebuild
I rebuilt it on my own from an approved spec in Blazor on .NET 10. It keeps using the existing stored procedures, so the old and new versions always agree on a price.
I added what people had been asking for in the team's request tracker: bulk Excel import to build a quote, soft delete and restore, exports, analyte counts and generated PDF quotes in place of hand-built report layouts. The rebuild runs on our development server, and the original stays in daily use until cutover.
The price update
The source was a business spreadsheet of about 1,650 prices with live formulas where values should have been, product codes missing their dollar signs, name and code columns swapped, and duplicates throughout.
I staged it into SQL tables and reconciled it row by row until every gap in the counts traced to an exact row. I wrote a one-page decision brief for lab leadership with the impact of each option, rehearsed the whole update twice on fresh copies of production with staff acceptance testing and sign-off, and ran it in transactions with backup and rollback tables.
When something went wrong
The same week, two price profiles were wiped. I wrote a plain-language post-mortem that proved, with two independent pieces of evidence, that a long-standing bug in the old editor caused it, not the update. Both profiles were restored from backup with nothing else lost.