Got a process that lives in a spreadsheet, a WhatsApp group and someone's head? That's exactly the kind of problem I like to solve.
Online ordering, kitchen, delivery, inventory and driver settlement in one system. ~500 orders a month in production.
It started as the in-house system for a pizzeria with delivery: orders came in through the website, WhatsApp and the phone, and had to reach the kitchen, the driver and the till without anyone retyping them. Today it also covers purchasing, stock, recipe costing and accounting, and it's sold to other venues as Vialika.
I audited the Redsys payment flow and found eight holes: charges with no order, duplicate orders when two notifications arrived at once, mismatched amounts silently ignored. Web and WhatsApp moved onto a single payment engine, with a unique key per transaction and a watchdog that asks Redsys again when a notification never arrives.
The assistant never writes on its own: every change is a card with Accept or Dismiss, and everything can be undone. It calls the same server actions as the screens, so it inherits their permissions, and numbers come from tools, not from the model.
No check ever looks at the role. Every request passes three locks: the proxy blocks the route, the page checks again, and the server action, which is the one that counts, checks once more.
Closing the till pushes a draft invoice to Holded on its own, with the VAT breakdown and payments per account. The second version of the integration was validated against the first until it matched to the cent, with 135 tests.