Odoo POS & Retail
Odoo POS is the under-rated jewel of the suite. It runs in a browser, works offline when WiFi dies, syncs inventory across shops in real time, and integrates with the same accounting and inventory used by the back office. For Belgian retail and F&B operations it's a serious contender to dedicated POS systems.
We've deployed Odoo POS for fashion shops, restaurants, specialty retail and a few hybrid e-commerce + brick-and-mortar operations. The integration story is the killer feature — what sells in the shop updates inventory, accounting and the e-commerce site at the same instant. Standalone POSes can't match that without painful synchronisation.
For Belgium specifically, Odoo POS works with the GKS/SCE fiscal data module required for restaurants, and integrates with the major payment terminals (CCV, Worldline). The operational simplicity for shop staff is genuinely good — training a new cashier takes hours, not days.
What Odoo POS is — and what it isn't
Odoo POS is a browser-based or PWA point-of-sale that runs on any device with a browser — Windows tablet, iPad, Android tablet, dedicated POS hardware. It supports barcode scanners, receipt printers, cash drawers, customer screens and payment terminals. It works offline, syncing when connectivity returns.
What it isn't: a hyper-specialised POS for very specific verticals (e.g., pharmacies with strict drug interaction checking, very large grocery chains with deep loyalty ecosystems). For 90% of SME retail and F&B in Belgium, it's more than enough.
- Browser-based POS — runs on tablets, dedicated hardware, any browser device
- Supports barcode, receipt printer, cash drawer, customer screen, payment terminal
- Works offline, syncs when connectivity returns
- GKS/SCE fiscal data module supported for Belgian restaurants
- Integrates with CCV, Worldline payment terminals natively
Multi-shop, inventory sync and the central console
For multi-shop retail, Odoo gives you per-shop configuration (prices, products, payment methods) and central visibility (stock across shops, sales by shop, transfers). Inventory syncs in real time when online, queues when offline. Shop managers see their P&L; head office sees everyone's.
Pricing per shop, promotions per shop, regional product variants — all native. The central console makes managing 10-20 shops genuinely easy, and we have clients managing more. Above 50 shops with very heavy customisation per shop, you'd evaluate a dedicated retail platform.
- Per-shop config: prices, products, payment methods, promotions
- Central visibility: stock, sales, transfers across all shops
- Inventory syncs real-time when online, queues offline
- Shop managers see local P&L; head office sees all
- Native handling of 10-20 shops easy; 50+ may need evaluation
Hardware and the offline story
Odoo POS works with most standard retail hardware. Receipt printers (Epson, Star), barcode scanners (any USB or Bluetooth HID), cash drawers (any standard), customer displays, payment terminals (CCV, Worldline directly; others via integrations). The IoT box bridges legacy serial hardware to the modern POS.
Offline mode is the unsung hero. WiFi dies? POS keeps selling, queues transactions, syncs when connectivity returns. We've had clients sell through entire afternoon outages without losing a single sale. The reconciliation when back online is automatic.
- Works with standard retail hardware: printers, scanners, drawers, displays
- Payment terminals: CCV, Worldline native; others via integrations
- IoT box bridges legacy serial hardware
- Offline mode = sells through outages, queues, syncs automatically
- Reconciliation on reconnect is automatic and reliable
Restaurant and F&B specifics
Odoo POS Restaurant adds table management, kitchen printer routing per category, course/round management, split bills, tipping, and table transfers. The kitchen sees orders by course; bar sees drinks immediately; dessert prints at the right time.
For Belgian restaurants the GKS/SCE black box requirement is supported: Odoo writes the legally-required transaction log to the certified fiscal data module, satisfying the Belgian tax authority. We've certified many Belgian restaurants on Odoo POS.
- Table management, kitchen routing, courses, split bills, tipping
- Kitchen printer per category routes orders correctly
- GKS/SCE black box supported for Belgian restaurant compliance
- Many Belgian restaurants certified on Odoo POS
- Table transfers, course timing, bar drinks all native
Loyalty, promotions and customer-facing features
Odoo POS integrates with the eCommerce loyalty program — same customer, same points, same discounts whether they buy in shop or online. Promotions, coupons, discounts and gift cards are managed centrally and applied at any POS. Customer lookup at the till is instant.
For loyalty depth (tiers, complex earning rules, predictive marketing) you'll layer a dedicated loyalty platform. For the 90% case (points, occasional promotion, customer history), Odoo native is more than enough.
- Loyalty integrated with eCommerce — same points, same customer
- Promotions, coupons, gift cards managed centrally
- Customer lookup at the till instant via barcode or phone number
- Native handles points, promotions, customer history
- Deep loyalty programs may need dedicated platform layered on
POS mistakes we keep correcting
These patterns turn POS go-live into a rough first month.
- Skipping offline mode testing — first WiFi outage exposes config gaps painfully.
- Wrong receipt printer model — slow or unreliable printing kills cashier productivity.
- Loose product master in inventory — wrong prices at the till, customer disputes.
- Skipping cashier training on the close-of-day flow — money handling errors at start.
- GKS/SCE not configured for Belgian restaurants — legal risk, fines.
Metrics that prove POS is healthy
We watch these weekly with retail managers in the first months.
- Daily POS uptime above 99% — including offline mode handling.
- Cashier transaction time under target — speed reflects training and hardware.
- Stock variance under 1% per shop per month — inventory sync is healthy.
- Cash variance under €5 per cashier per shift — handling discipline is solid.
- Loyalty redemption rate above target — customers value the program.
How we run POS implementations at Flydoo
We always test the full POS workflow — sale, return, void, discount, payment, close-of-day — on the real hardware in the real shop before go-live. Lab testing isn't enough; the WiFi, the printer, the terminal all have shop-specific quirks.
We always train cashiers on the close-of-day flow first, then on sales. Cashiers who can confidently close the day feel safe; cashiers who can't always live in low-grade panic. Confidence at close-of-day = confidence all day.
- Test the full workflow on real hardware in the real shop before go-live
- Train cashiers on close-of-day first, then on sales
- Validate offline mode with a deliberate WiFi outage during testing
- GKS/SCE configured and tested for Belgian restaurants from day one
- Hardware (printers, terminals) selected with the shop manager
Practical checklist before going live with Odoo POS
Walk this list with your shop manager and head office. Most ticked = healthy POS go-live.
- POS hardware (printer, scanner, drawer, terminal) tested in real shop
- Offline mode validated with deliberate WiFi outage
- Cashier training on close-of-day completed before training on sales
- GKS/SCE configured for Belgian restaurants (if applicable)
- Product master clean, prices verified
- Loyalty program (if any) configured and tested
- Multi-shop transfer flows tested if relevant
- First week of go-live has on-site or remote support coverage
Key takeaways
- Odoo POS is browser-based, works offline, integrates tightly with inventory and accounting
- Multi-shop with central visibility is native and works for 10-20 shops easily
- GKS/SCE fiscal compliance for Belgian restaurants supported and certified
- Hardware = standard retail (printers, scanners, terminals); IoT box bridges legacy
- Train cashiers on close-of-day first — confidence there cascades to all-day confidence
- Test on real hardware in the real shop before go-live — labs miss shop-specific quirks
Frequently asked questions
Does Odoo POS work for Belgian restaurants with the black box requirement?
Yes — Odoo POS Restaurant supports the GKS/SCE black box (fiscal data module) required by the Belgian tax authority for restaurants above the turnover threshold. We've implemented and certified many Belgian restaurants on Odoo POS. The setup involves the certified hardware module and a validation pass with the FOD Financiën / SPF Finances.
What happens when WiFi dies in the middle of the day?
Odoo POS keeps selling. Transactions queue locally on the device. When connectivity returns, everything syncs automatically — inventory updates, accounting entries, customer history. We've had clients sell through hours of outage without losing a single sale or a single inventory update. The reconciliation on reconnect is solid and tested.
Can Odoo POS replace a dedicated retail POS like Lightspeed or Shopify POS?
For most Belgian SME retail, yes — and you get the integration to inventory, accounting, e-commerce, CRM for free. Lightspeed and Shopify POS have richer retail-specific features (some loyalty depth, specific apparel/grocery features) but force you to synchronise data with your back office. The integration value of Odoo usually wins for SMEs.
How fast is Odoo POS at the till?
Fast enough for any normal retail or restaurant pace. Selecting products, scanning, applying promotions, taking payment — all snappy on modern hardware (any 2020+ tablet works). The bottleneck is usually receipt printing or payment terminal speed, not Odoo. We benchmark on real hardware before sign-off.
Can we run Odoo POS on existing POS hardware?
Often yes. If your hardware is standard (USB or network printers, USB or Bluetooth scanners, standard cash drawers), it'll work. For older serial-only hardware, the Odoo IoT box bridges them to the modern POS. For very specialised hardware (kiosk units, integrated all-in-ones), we test compatibility before commitment.
Need help applying any of this to your own context? We're happy to talk.