From the counter to the books.
One restaurant, one system.
For Kesiyos, a full-service restaurant, we built the whole business on open-source Odoo and ran it day to day: the point of sale, kitchen and cost control, payroll and people, accounting and electronic invoicing, ordering over WhatsApp and Instagram, and AI that handles the paperwork while a person approves. Fifty custom modules the team used every day, from the cash register to the accountant.
One sale, followed all the way through.
Order
At the counter, on the website, on WhatsApp or on Instagram.
Payment
Cash, card, or a payment link sent from the register.
Tax invoice
A certified electronic invoice, issued automatically.
Kitchen
The ticket prints. Overnight, the recipe comes out of inventory.
Inventory
Blind counts, par levels and reorder points say what to buy.
Books
Bank matched, margins on the dashboard, daily reports in Slack.
Six parts of the business, on one system.
Point of sale and front of house
- Every sale at the register became a certified electronic invoice, with no retyping.
- Combos with choices (protein, sauce, with or without cream), each one tracked as a real ingredient.
- A sold-out button: an item left the register and the online menu at once. Seasonal and weekly hours too.
- Payment links from the register: the cashier sent a link by WhatsApp or email and kept selling. The kitchen ticket printed when the payment landed.
- Online ordering with tax ID validation and delivery fees by distance. Web orders printed in the kitchen on their own.
- Loyalty points, one-click staff roles, and an alert any time a refund skipped the manager's PIN.
Kitchen, inventory and cost control
- Every recipe costed: food, packaging and labor, with a margin traffic light and a pricing helper.
- Nightly auto-consumption: after closing, the day's sales were broken down into recipes and sub-recipes and taken out of inventory, with an undo button.
- Daily blind cycle counts approved by a manager, and weekly counts against par levels.
- Reorder points recalculated every two weeks from real consumption, ordering cost and supplier minimums.
- Receive first, purchase order after: the way a market run actually works. Spoilage had its own screen.
People and payroll
- Full payroll under local labor law: social security, income tax withholding, legally required bonuses, overtime and severance.
- From the clock-in kiosk to payroll to a payslip the employee signed on their phone.
- A visual schedule builder the whole team could open from a link.
- Contracts, salary advances, final settlements and letters signed with a finger on the phone, each with a tamper-evident record.
- Employee files that filled themselves: the system asked for ID, health cards, background checks and bank details by link, and followed up every 30 days.
- A supervisor panel for cash withdrawals, counts against minimums and a supplier directory one tap from WhatsApp.
Accounting and electronic invoicing
- Electronic invoicing end to end: invoices, voids and credit notes, with the official exchange rate loaded daily.
- The company inbox inside Odoo: 30 rules sorted it and AI classified the rest. Tested on 3,457 real emails with zero errors.
- Supplier invoices collected from email, XML files and the tax authority, matched to purchase orders and bills. AI suggested; the accountant decided.
- Bank statements read straight from the PDF with 40 matching rules, and card, processor and delivery app deposits checked channel by channel.
- Receipts from the phone: a photo and a voice note became a draft bill, already tagged with what it was and who paid.
WhatsApp, Instagram and Messenger
- One ordering assistant across WhatsApp, Instagram and Messenger, connected through Meta's official Cloud API.
- It read the live menu, built the order, sent a payment link, and delivered the receipt and the tax invoice in the same chat.
- Anything it couldn't handle went to a person on WhatsApp.
- Meta-approved message templates for payment links and payment confirmations.
AI that does the paperwork
- Claude read receipts, sorted the inbox, suggested how to book supplier invoices and took orders in chat. Whisper turned voice notes into text.
- A content flow that wrote social posts around a bank of real photos, checked the facts and published to Instagram in one click.
- The rule everywhere: AI proposes, a person approves. Nothing reached the books without a human.
And the numbers, every day
A control dashboard with sales by day and hour, menu engineering (which dishes carry the menu and which don't), costs and margins. Plus four daily reports in Slack: cash-outs, sold vs. consumed, bought vs. consumed, and dishes in the red.
A restaurant can't stop for a software update.
A safe copy to test on
A copy of the system with email, invoicing and payments switched off, so no test ever reaches a real customer or the tax authority.
Tested end to end
Each module shipped with an automated test of the whole flow, run before going live.
Never during service
Updates waited until the cash registers were closed, and always after a backup.
Written down, reversible
Every module has its install steps and its rollback in writing, and the code lives in a private repository.
Spanish and English
New screens, emails and documents in both languages.
Open source, no per-user fees
Odoo Community on the business's own cloud server. The data and the code belong to the business.
"Rodolfo helped us build our business foundation from the ground up. He deployed our full POS system, organized our inventory structure, and established the accounting workflows we use today. Thanks to his guidance, our operations run smoothly and we can focus on serving our customers instead of fighting administrative challenges. His support was essential to launching Kesiyos the right way."
Not a restaurant? The same pieces fit.
Point of sale, recipes and inventory, payroll, electronic invoicing and chat ordering work the same way for:
Anywhere in the U.S. and Latin America
In English and Spanish. Local tax and labor rules are where most systems break; we build them end to end and adapt to yours.
Running on spreadsheets and five different apps?
Tell us how your operation works today. The first conversation is free, and you will leave with a clear idea of what to connect first.
Another case study
A 24-level residential tower controlled from one system: schedule tied to purchases, daily cash and inventory reports, rebar cut plans and AI that reads the invoices.
See the Torelo case study →Rodolfo Kong · ARMKU · rkong@armku.us · +1 713 881 9960 · 650 W Bough Ln #125, Houston, TX 77024