I’m sitting on roughly 1,600 individual Excel workbooks—each one a complete recipe of its own. I want them living in a single, query-friendly database instead of scattered across folders. Here’s the workflow I’d like you to build: • Import every recipe sheet once, capturing its ingredients, quantities, and any existing notes. • Read a separate set of Excel files that hold current ingredient prices. • Tie each recipe line to the correct price record, calculate the total cost, and store that result in the database. • Watch for price changes: whenever someone updates a price sheet (or drops in a fresh one), the system should recalculate the affected recipe costs automatically—no manual triggers. I’m open on the underlying database (MySQL, PostgreSQL, SQLite—use what fits best for reliability and speed) but the import/update logic must be seamless and repeatable. A straightforward UI or script that lets me kick off an import, see status messages, and confirm that costs have refreshed would be perfect. Deliverables 1. Database schema and populated database containing all 1,600 recipes. 2. An Excel-to-database loader that can be run again for future batches. 3. Automatic cost-recalculation mechanism linked to the ingredient price workbooks. 4. Brief setup guide so I can run the whole process on my own machine or server. If you’ve worked with Python (pandas, SQLAlchemy), .NET, or similar ETL tools, mention it—speed of development matters to me as much as accuracy.