Overview
Voltage Analytics started as a way to organize live-selling shows, but it grew into shared infrastructure for several of our internal tools. It connects show assignments, inventory sources, product feeds, and commission information so each part of the operation can work from related records.
The problem
Scheduling a show isn't just putting a name on a calendar. Host availability, inventory, and sales data all affect what happens before, during, and after a show. I wanted one place where that information could connect instead of leaving each tool to manage its own version.
My role
I built this application as the sole developer, owning the workflow design, implementation, integration, and testing. I defined the business rules and how the applications needed to share information, using Codex during implementation and refinement. I specified what the dashboards should show, how inventory sources should contribute to investment totals, and what hosts and operators needed from the commission views. I also kept track of which features were actually in use, rather than treating every available screen as a proven result.
How I built it
The application was rebuilt with React, TypeScript, Vite, and Firebase, using the earlier project as a reference for its data structures and business rules. Scheduling covers show assignments, host availability, requests, and conflict checks.
On the inventory side, the documented workflow combines Shopify API updates, FBT inventory CSV imports, and tech inventory entered through the refurbishment team's application. The dashboard brings these sources together for investment reporting.
Voltage Analytics also provides a product-feed Cloud Function used by our Whatnot Copilots. Instead of having every extension build its own catalog mapping, they use the shared feed and cache the returned data.
For commissions, show and host identity connect activity to the right records. Overstock and Refurb have different commission plans, so I kept their rules separate rather than trying to force them into one calculation.
The tricky part
Once other applications depend on a system, a small change can affect a lot more than the page you're editing. A Firestore collection, product feed, or access-rule change can impact a warehouse screen and a browser extension at the same time.
That made compatibility a priority. The project includes shared Firestore rule tests, and commission logic needs careful handling of show ownership, time windows, and repeated updates. A dashboard number isn't useful if it comes from the wrong records or appears for the wrong person.
The result
Voltage Analytics links show planning to what happens during a show and what gets reviewed afterward. Inventory maintained elsewhere can reach the host through the shared feed, while show activity supports reporting and commission views.
Its biggest contribution is giving several focused applications a common operational foundation.
What I learned
When software becomes shared infrastructure, you have to think about downstream effects before making changes. I'd like to make data freshness more obvious: when each inventory source last updated, which sales are awaiting reconciliation, and which commission numbers are final.