My in-house ERP, built with PHP 8, Alpine JS, and htmx, has a data-processing fault: new or edited records are failing to persist to the database. The problem shows up only in two modules—Inventory Management and Financial Transactions—while all other areas work as expected. The core workflow: a user edits a record, htmx issues an async POST, the PHP controller validates and writes through an ORM to MySQL. The front-end confirms success, yet the row never appears (or reverts on refresh). No errors are thrown in the browser console, but MySQL slow-query logs stay clean, so I suspect a logic or transaction issue in the controller or model layer. I will grant repository access (Git) and a staging URL. The schema and seed data are documented in README. Deliverables • Diagnose the root cause in both modules • Patch the PHP/ORM logic so records save reliably • Test with at least 20 sample transactions per module and supply a short test report • Commit clean, commented code and push via pull request Acceptance criteria 1. After the fix, every create/update in Inventory Management and Financial Transactions writes to the correct tables with full rollback safety. 2. Page confirms “Saved” only when the commit is actually persisted (verified by a live DB query). 3. No regression introduced elsewhere; automated tests still pass. 4. All changes conform to PSR-12 style. If you’re comfortable tracing htmx requests through Alpine bindings into PHP controllers and MySQL transactions, you’ll find everything you need in the repo. Let’s get these records saving again.