Don

Context

A small cookie bakery tracks purchases, ingredients, recipes, production and sales across scattered spreadsheets. Without a single source of truth, inventory drifts out of balance and decisions get made blind.

What I built

A web application that integrates the whole operation, with three roles administrator, worker and buyer:

• Purchasing and batch inventory of ingredients, with cost and expiration date.
• Recipes per cookie: ingredients, quantities and measurements.
• Production that starts from a recipe, deducts ingredients and generates cookie inventory.
• Counter sales and orders from registered buyers, with PDF receipts.
• Waste tracking and reports on sales, expenses, profit and best-selling products.

Technical decisions

• A Flask monolith with Jinja2 views and the business logic concentrated in a service layer, so controllers don't carry the calculations.
• FEFO inventory (first-expired, first-out): production and sales draw first from the batches that expire soonest a key decision for a perishable product.
• Stored procedures (SP_CrearCompra, SP_InsertarReceta) for compound write operations.
• PDF receipts with ReportLab; interface with Tailwind and Flowbite.

Result

A working system covering the full purchase → production → sale flow, with perishable inventory control and operational reports. It solves an entire domain that of a bakery with real business rules.

It is an academic project, not commercial: the pending items for production out of scope here would be per-environment secret management, versioned migrations and automated tests.