Your Odoo 19 Point of Sale is running on your own server, and the vibe-code agent is sitting in the Open WebUI chat next to it. It can read your Odoo configuration, query the Postgres database, write scripts, and restart services. You describe the job in plain language, it does the work, and it tells you what it changed. Here are ten everyday POS jobs you can hand to it instead of clicking through the backend yourself.

1. Add a new product to the POS menu

New menu item or shelf product? Give the agent the details and it creates the product template, sets the sale price and tax, attaches a barcode if you have one, and files it under the right POS category so it appears on the right touch-screen button. It will confirm the change by reading the record back from the database, not just by saying it saved. If the item comes in sizes, it can set them up as product variants so each size gets its own price and button label. Try: Add a flat white to the Drinks POS category at $4.50, tax included, barcode 7612345000012, available in all sessions.

2. Rebuild your floor plan

Restaurants and bars change layouts constantly — patio season, a booked event, two tables pushed together. The agent can add or rename tables on a floor, move seats, or create a whole new floor in your restaurant POS config. It checks the existing floors first so you don’t end up with duplicate names. Try: Add four two-seat tables to the Terrace floor named T7 to T10, and mark T5 as inactive for repairs.

3. Run the end-of-day cash check

Closing the register should take minutes, not an archaeology session. The agent pulls the session totals from pos.session — expected cash by payment method, sales by product — and compares them against the counted amounts you give it. If the drawer is short, it lists the orders most likely to explain it instead of making you dig. It can also produce the closing report you would otherwise hunt for in the backend, with payments split by method. Try: Here’s tonight’s session: I counted $1,843.50 in the drawer and $912 on the card terminal. Show me what the system expected and flag any difference.

4. Rescue orders stuck in offline mode

Your POS keeps selling when the internet drops, then auto-syncs when it comes back. Usually. If orders sit unsent, they pile up in a rescue session and your backend numbers drift. This is worth fixing the day you notice it — the longer unsent orders wait, the harder they are to match against stock and payments. The agent finds those stuck orders, checks why they failed to sync, fixes the cause, and pushes them through. Try: Two orders from this morning never showed up in the backend. Find the rescue session, sync the missing orders, and tell me why they got stuck.

5. Set up happy hour pricing

Time-based pricing is a pricelist with a rule, but the setup screens bury it. Describe the deal and the agent builds the pricelist — 20% off cocktails from 5 to 7 pm, for example — ties it to your bar’s POS config, and sets the start and end dates. It will also check for conflicts with any other pricelist already on that config. Try: Create a happy hour pricelist for the Bar POS: 20% off all drinks in the Cocktails category, weekdays 5–7 pm, starting Monday.

6. Fix kitchen orders going to the wrong printer

If drinks are printing in the kitchen or food never prints at all, the cause is almost always the category-to-printer routing in the restaurant settings. The agent reads your kitchen printer setup, checks which categories each printer serves, and corrects the mapping. Try: Bar orders are landing on the kitchen printer. Route everything in the Drinks POS category to the bar printer only, and leave food on the kitchen printer.

7. Handle a refund without the guesswork

Refunds in POS work best when they reference the original order, so stock, payments, and accounting all stay consistent. Give the agent the receipt number or the approximate time and table, and it locates the original order, explains what a refund will reverse, and can walk you through doing it at the till with the right reason code. The same lookup works weeks later, when a customer brings something back without the receipt. Try: Table 12’s ribeye at 8:15 pm came back cold — find that order and tell me exactly what a refund will undo before I process it.

8. See what is running low before the rush

POS sales drain stock in real time, so the low-items list is the honest one. The agent queries current quantities against recent sales velocity and gives you a restock shortlist — what will run out first, based on how fast it has been selling. Try: Which products sold through POS this week will run out first at current stock levels? Give me the top ten with a suggested reorder quantity.

9. Chase down a card terminal mismatch

When the terminal payout does not match the POS card total, the answer lives in the payment records. The agent compares the POS payment journal against your terminal report line by line and isolates the transactions on the wrong side — a duplicate tap, a failed capture retried at the till. Most of the time it is one duplicated tap or a tip recorded against the wrong method. Try: Card takings in Odoo say $2,104 but Adyen settled $2,064. Compare the payments for today’s sessions and find the forty-dollar difference.

10. Export today’s numbers for your accountant

Your accountant wants taxes split out, totals by payment method, and the invoice list — not a screenshot of the dashboard. The agent generates the sales details from the day’s sessions and exports it as a spreadsheet or a clean summary in the chat. Run it the same way every week and the year-end handoff becomes one archive instead of a panicked export. Try: Give me yesterday’s POS sales as a spreadsheet: net sales by tax rate, totals per payment method, and any orders that still need an invoice.

These ten are the daily grind, and none of them need you to learn the Odoo backend. If the agent ever isn’t sure what you meant, it will show you what it found and ask before changing anything. When you are ready to hand off the bigger, multi-step work, move on to the workflow automations. Odoo Point of Sale on OpenSysLab