Operational use
Opbase
Built an industrial order operations platform with more than six active clients, as reported by its operator.
- Engineering impact
- Made the order record the place to check status, ownership and partial deliveries. That gave staff a shared record for day-to-day operations, documentation and analysis.
- Business impact
- Opbase has more than six active clients, as reported by its operator. In one operation using it, the team reported zero missed orders and zero missed compliance steps, with routine coordination down to a minimum. Annual documentation and analytics work fell from several weeks to about two days.
Problem
Orders came in across channels. Staff had to reconcile handoffs, partial deliveries and records across messages and spreadsheets, then reconstruct that history for reporting.
My role and ownership
Designed the workflow and built the operational software linking order intake, catalog, inventory and fulfillment.
Architecture and tradeoffs
NestJS and PostgreSQL support a shared order record and explicit transitions. React gives owners, store managers and order managers different views of the same work. Webhooks and notifications connect channel events and operational handoffs.
Workflow in use
Capture an incoming order, assign it, track status and partial deliveries, and surface open items to the next owner.
Scope and constraints
The active client count is a firsthand report from November 2026. The operating improvements describe one deployment.