Mama R's
Internal Bakery Operations System
Mama R's is a custom internal operations system built for a local bakery to replace manual paper records with one browser-based workflow for orders, payments, inventory, expenses, reporting, and end-of-day cash reconciliation. It also supports printable receipts and stock-history tracking.

Project Links
The deployed application is restricted to internal business use. The implementation is available publicly for code review.
The bakery did not need another dashboard. It needed one place to run the day.
The bakery previously relied on manual records for day-to-day operations. Mama R's brings customer orders, payment progress, stock levels, expenses, receipts, and end-of-day reconciliation into one working record.
The goal was not simply to digitize separate forms, but to keep the operational pieces connected as an order moves through fulfillment.
An order stays useful from booking to fulfillment
Order and payment state
Each order keeps the customer and order details, line items, quantities, prices at the time of order, target date, and amount paid. Payment status distinguishes unpaid, partial, and paid commitments.
Fulfillment and inventory
Stock is not deducted when an order is created. When it enters fulfilled status, the backend checks the relevant product, verifies enough stock, reduces it, and records the movement in stock history. Updating an already fulfilled order does not deduct stock again.
Knowing the stock count is useful. Knowing why it changed is better.
The catalog supports products and variants, stock quantities, low-stock thresholds, and restocking. Relevant changes such as restocks, adjustments, and fulfillment create stock-history entries, so the current count is accompanied by an operational trail.
The digital total still has to match the cash drawer
End-of-day reconciliation turns the day's operational records into a practical closing check.
Expected
Recorded payment amounts from today's fulfilled orders, minus recorded expenses.
Actual
The physical cash count entered at closing. The interface shows whether the register is balanced, over, or short, alongside a daily order-and-expense ledger that can be printed as a Z-report.
The same records become the reporting layer
Fulfilled-order records feed dashboard and report views for daily and monthly sales and sales over time, alongside low-stock counts from inventory. Sales data can also be exported as CSV when it needs to leave the interface.
As the workflow grew, loose data contracts stopped being enough
The project began with a looser JavaScript implementation, then grew to cover orders, expenses, stock history, and reconciliation. Moving to TypeScript made the contracts between the React frontend, Express API, and MongoDB models explicit. The detailed migration story is in A Typo, a Timeout, and TypeScript.
Built for the people running the bakery, not public traffic
The application routes unauthenticated visitors to login and exposes its operational screens only after authentication. Passwords are hashed, and JWT checks protect the operational API routes. The deployed system is intended for the people running the bakery.
Turning daily bakery operations into one consistent record
Mama R's started with a practical goal: replace paper-based operational tracking with something the bakery could use from a browser. Connecting fulfillment to inventory, expenses to reconciliation, and daily records to reporting turned separate manual tasks into one working system.

