Orders with payment links, table bookings and menu answers.
Votel built an ambitious restaurant assistant: take orders and send a Stripe payment link, confirm payment to the customer and kitchen, book tables and answer menu questions. The source shipped with embedded payment secrets, dead webhooks, a hard-coded catalog and no booking. The corrected version keeps every feature, repairs it and adds the promised table booking.
Open the level of detail you need.
Original audit
Source inventory, the order, reservation and payment chains and 22 findings, unchanged.
Open audit →02Remediation
Each feature, what was broken, what changed and how it was checked.
View corrections →03Final audit
Rebuilt inventory, test results and the launch decision.
Open final audit →04Snapshot guide
What the finished snapshot does, what it installs and how to check it.
Open guide →05Owner setup center
Menu, Stripe catalog and key, webhook, booking, messaging and acceptance tests.
Start setup →Orders get paid, tables get booked, the kitchen gets the details.
With texts and emails bypassed for the test, 17 simulator runs: orders ran 20 to 23 steps and scored 90 to 96 across pickup, delivery, unmatched items and failed links. With the placeholder catalog every priced order correctly went to staff.
Owner-supplied restricted key, payment link by text and email, webhook confirmation to customer and kitchen.
A table was booked in the conversation (98 after the booking fix); a failed booking creates a staff task (96); a menu question alone scored 96.
No embedded secrets; unknown items go to staff; allergy notes flagged, never guaranteed.
11 of 11: allergies asked and never guaranteed, no card numbers, no invented menu items, no false confirmations, no table promised before booking, do-not-contact respected.