Web App
Speedway ERP
One place to keep operations moving.
An internal ERP for a surgical supply business — the operational layer behind the storefronts, covering inventory, orders and fulfilment.
Visit website
Speedway Surgicals
Web App
Next.js / React / TypeScript / Database Design / Authentication
01 / The story & screens
From the idea.
Into the details.
Speedway Surgicals runs a deep instrument catalogue across more than one storefront. Beyond a certain catalogue size, spreadsheets stop being a system of record and start being a liability.
The ERP is the internal counterpart to the public stores: inventory, order processing and fulfilment handled in one place by the team that runs the business day to day.
It's deployed as a hosted web application, so staff reach it from a browser without local installs or per-machine setup.
A clear entrance to the operations system
Speedway ERP’s public sign-in page provides the entry point to the surgical supply operations application. The interface presents its brand and account fields in a focused layout before staff access their operational workflows.

Keep account access focused
The public interface gives the sign-in form a consistent hierarchy. The application’s documented scope covers catalogue, inventory, order processing and fulfilment, accessed through staff accounts and role-based permissions.

Present the actual public interface
The tablet mockup shows the same public sign-in screen from another device setting. It documents the application’s entry experience; the internal operational screens remain behind authenticated access.

Support browser access on mobile
The mobile sign-in layout stacks the account controls into a narrow view. It provides a browser-based route into the application for staff while retaining the same visual identity as the desktop entry screen.

02 / What we built
The work, delivered.
- Internal ERP web application
- Inventory and catalogue management
- Order processing and fulfilment workflows
- Role-based access for operations staff
- Hosted deployment with browser-based access


%20(2).webp)

