Sometimes the stock Odoo Point of Sale setup does not match how your shop actually runs. The vibe-code agent on your server can change that: it edits configuration, writes small custom modules, adjusts data models, and tightens the server’s security. You describe the behavior you want, it implements it on your own box, and explains what it touched. Here are ten customizations worth asking for.
1. A receipt that looks like your shop
The default receipt is plain. The agent can override the receipt template in a small custom module so every printout carries your trading name, VAT number, address, return policy, and even your Wi-Fi password — the things customers actually ask about. Because it is a module, the change survives upgrades instead of being wiped by an update. Ask it to show you a preview line before it deploys, so the wording is right the first time. Try: Put our logo, VAT number, and a 30-day return policy line on every POS receipt, and add the Wi-Fi password at the bottom.
2. Modifier quick-notes for the kitchen
Typing extra hot, oat milk, no onion
on a busy till is slow. The agent can add preset line-note buttons — your common modifiers — so a tap attaches the note to the order line and it prints on the kitchen ticket in the right place. The notes also show on the customer receipt, so the till and the kitchen always read the same order. Try: Add quick-note buttons for Extra hot, Decaf, Oat milk, No onion, and Allergy flag, and make sure the notes print on the kitchen ticket.
3. A POS screen laid out for speed
Seconds at the till come from layout: the right categories in the right order, colors that separate food from drink at a glance, and the right number of buttons per screen for your tablet’s size. The agent reviews your category tree and grid density and proposes a cleaner arrangement before changing anything. Try: Our bartenders fumble the drinks screen. Reorder POS categories so Beer, Wine, Spirits, Softs come first, and make the buttons bigger for our 8-inch tablets.
4. Combo products with real choices
Lunch deals and tasting menus are combo products: a base price, then the customer picks one starter, one main, one drink. The agent builds the combo with your exact choices and pricing rules, and verifies each combination totals correctly at the till. Try: Build a Lunch Combo at $16.90 — any sandwich, any side, any soft drink — with a $2 surcharge for milkshakes.
5. Custom product fields on the POS card
Allergens, spice level, or a shelf location do not exist on the default product card. The agent extends the product model with the fields you need, adds them to the backend form so your staff can maintain them, and shows the important ones on the POS screen so the till sees contains nuts
before the kitchen does. Keep the list short — three or four flags people actually act on beat ten that everyone ignores. Try: Add allergen flags to products — nuts, gluten, dairy — editable in the backend and shown on the POS product card.
6. Lock down what cashiers can change
Open discounts and free price edits leak money slowly. The agent tightens the access groups: cashiers can sell and take payments, but price changes need a manager PIN and refunds are restricted to managers. It maps the changes to Odoo’s POS groups so the audit trail still shows who did what. Test it at the till before go-live: the agent can walk you through exactly what a cashier can and cannot do now. Try: Stop cashiers from editing prices or giving discounts without a manager PIN, and make refunds manager-only.
7. Dine-in and takeaway that tax themselves
Food to eat in and food to take away often carry different tax rules. With presets and fiscal positions, the agent sets it so the till applies the right tax automatically based on order type — no cashier deciding tax at the counter. The same trick works for delivery orders, which can carry their own preset, journal, and receipt wording. Try: Set up presets so Dine-in applies the standard food tax and Takeaway switches to the reduced fiscal position automatically on the restaurant POS.
8. Reports the backend does not ship
The built-in reports answer generic questions. Your questions are yours: sales by hour to plan staffing, margin by product to fix the menu, average spend per table to see which section earns its floor space. The agent builds these as saved backend views or SQL-backed reports you can rerun any time. Because it lives in your database, you can slice it further later — by floor, by cashier, by product category. Try: Build me a weekly report of POS sales by hour of day, split by weekday, so I can see when to roster more staff.
9. Loyalty rules that match your regulars
The default loyalty program is a starting point, not a strategy. The agent tunes the earn rate, reward thresholds, gift card rules, and expiry to your margin reality — points per visit for a coffee shop, points per dollar for a bar — and shows you the cost of the program per hundred dollars sold. Start conservative — generous points are easy to give and painful to claw back. Try: Change our loyalty program to 1 point per dollar, with a free coffee at 60 points, points expiring after 6 months, and gift cards that work in both retail and restaurant modes.
10. Harden the server behind the till
Your POS only works if the box it runs on behaves. The agent audits and fixes the boring essentials: a rotated Odoo master password, two-factor on admin accounts, fail2ban watching the Odoo port, automatic nightly database dumps to a folder off the container, and a quick rollback note if an upgrade goes wrong. It writes a short audit note of everything it changed, so any future operator can see the setup at a glance. Try: Audit the server: rotate the Odoo admin password, enable 2FA for administrators, set up nightly database dumps, and add fail2ban protection for Odoo.
Customizations like these used to mean a developer on retainer. On your own server they are a chat message, a tested change, and a clear explanation of what moved. Start with the receipt and the cashier locks — they are quick and you will feel them every shift. Odoo Point of Sale on OpenSysLab
