Context
From production file to workshop use
The need is concrete: distribute pizza production across several distributors, validate imported quantities and then guide preparation variety by variety. A spreadsheet provides the data, but it is not an interface designed for the production workflow.
Solution
A guided local business workflow
Version 1.2 brings the Excel plan closer to workshop practice: adjust quantities, recover imported values and follow assembly steps in pictures.
Production dashboard
Excel import excludes Kit Pizza rows and groups quantities by pizza and location. Quantities can be adjusted with recalculated totals. Changes are highlighted in yellow, saved locally and can be reset to the imported values after confirmation.
Workshop flow
Ordered recipes and an assembly gallery: photos play at an adjustable pace, with pause, navigation and access to the final image. Zero-quantity pizzas are skipped; the next pizza stays visible to help prepare ahead.
Business settings
Local management of the catalogue, recipes and locations. Up to 20 photos per pizza can be added, reordered or removed with confirmation; the last one represents the finished result.
Update · 1.2.0
Adjust, illustrate, prepare
This iteration addresses three practical needs: adjust a plan without losing the Excel reference, make assembly steps visible and improve readability during production. The dark theme is now permanent and images stay uncropped.
Architecture
A full-stack chain packaged with Electron
The Excel file remains the source of the production plan.
React and TypeScript power the interface and presentation rules.
Express exposes a strictly local API bound to 127.0.0.1.
SQLite stores the business catalogue and recipes on the machine.
Electron starts the backend on an available port and provides the desktop application.
Decisions and trade-offs
Make local use reliable before expanding the scope
Local operation
Data, pictures and settings remain on the machine. The server is not designed to be exposed directly to the Internet.
Separated persistence
The catalogue and photos remain outside the installation files. Gallery migration preserves existing images and backs up the existing database; plan adjustments are saved separately in local storage.
Verifiable delivery
As of 2 October 2026, the v1.2.0 release log reports 67 automated tests, a packaged macOS build and an in-app check. Windows acceptance testing remains pending. Version 1.1.4 had been validated in the workshop on a 43-inch screen.
Current limitations
A deliberate scope
- Excel remains the initial source of the plan, with traceable local adjustments; Adial integration is not included.
- The application targets trusted local use and does not include the authentication required for network exposure.
- The Windows and macOS test releases are not signed yet.
- Version 1.2.0 is an acceptance-test build: Windows packaging and workshop feedback are still pending.
Stack
Core technologies
- React
- TypeScript
- Electron
- Express
- SQLite
- Vite