Duration: 19:42
PART 1 — Analytical Summary 🚀
Context and why it matters 💼
Robin, a business analyst and expert in Point of Sale at Odoo, delivers a step-by-step walkthrough on configuring the Belgian fiscal “blackbox” with Odoo Point of Sale for restaurants. The session focuses on the practical hardware and network setup needed to achieve compliance, reliability, and smooth daily operations. This matters because in Belgium, any restaurant doing more than €25,000 in annual turnover must use a certified fiscal data module (“blackbox”) so the government can verify sales. The talk demystifies how Odoo Point of Sale, the Odoo IoT layer, and the blackbox fit together—what to buy, how to wire it, and which network choices prevent headaches.
Core ideas and innovations 🧠
At the heart of the setup is the Odoo IoT bridge, which connects physical devices (printers, scales, payment terminals, the blackbox) to the Odoo database. There are two deployment models. The Physical IoT is a Raspberry Pi (recommended models 3/4; 5 for kiosk usage) running Odoo’s IoT image with Odoo-maintained drivers and an embedded print server; it’s ideal for multi-device, multi-station environments because devices on the local network can be shared by many terminals. The Virtual IoT runs as a Windows 10/11 service (Windows Server is possible) and uses the PC’s own drivers; it’s free and works best when a single Windows machine hosts all devices locally. The trade-off is simple: physical adds network-level flexibility and shared access; virtual adds driver compatibility on a single host.
Printer support hinges on the ESC/POS protocol. Odoo recommends Epson TM‑T20 (USB) and Epson TM‑T30 (USB/Wi‑Fi). Cash drawers do not connect to Odoo directly; they plug into the receipt printer via an RJ‑11 cable, and the printer triggers the opening. Once the basic stack (IoT + printer + cash drawer) is proven with a test sale and receipt, you add the blackbox: it links to the IoT via a serial-to-USB adapter. Odoo supports BMC3 and BMC4 fiscal modules. Certification covers Odoo versions 13–18; Odoo’s official support focuses on the two latest major versions (currently 18 and 19), including 18.x minors. A key architectural note: the blackbox signs each receipt to certify legal compliance.
On the network side, the presentation emphasizes reliability and simplicity over cleverness. Use static IPs assigned at the router, prefer Ethernet where possible, and avoid unnecessary secondary routers. VLAN segregation for IoT is not supported today. For browser clients, avoid mobile App Store builds—use a PWA so the browser’s configuration and device permissions are preserved. For device connectivity beyond the local network, Odoo is moving from long-polling to WebSockets (notably around v19) to make remote printing feasible; this is arriving or arriving soon depending on the exact release.
Impact and takeaways ⚙️
The message is pragmatic: get your foundation right, test early, then add compliance. The Physical IoT (priced at €25/month per unit) is the robust choice for multi-station restaurants; the Virtual IoT (free) is best when everything is tethered to a single Windows machine. Always validate printers before the blackbox step, standardize on ESC/POS models, and keep drivers consistent with the IoT you’ve chosen. For payment terminals, plan capacity—many setups require one IoT per terminal due to direct IP callbacks. Keep modules aligned with hardware: install the necessary payment integrations and use pos_blackbox_be for Belgian fiscalization. For migrations (e.g., Odoo 15 to 18+), refresh the IoT to the latest image/build, remove the prior IoT from the Odoo IoT app, and re-pair cleanly.
The Q&A clarified scope and constraints. The blackbox requirement is Belgian-specific. Windows Server is supported for Virtual IoT in larger contexts (e.g., warehouses). Have a plan to find the IoT’s IP (attach a screen or scan the network) and remember that printers link to the IoT, not directly to the blackbox. Loyalty and gift cards with Belgian fiscalization are not yet re-certified but are expected to return later. For scales, the IoT-supported models (e.g., ML2‑ARS) work like any other device. Finally, stability between physical and virtual IoT is comparable; the main difference is driver availability and sharing across multiple POS stations.
Bottom line 💬: Odoo’s IoT layer turns a complex compliance stack into a manageable one—provided you standardize your devices, choose the right IoT flavor for your topology, lock down your network, and test incrementally before going live.
PART 2 — Viewpoint: Odoo Perspective
Disclaimer: AI-generated creative perspective inspired by Odoo’s vision.
Compliance should never make your workflow harder. Our goal with the IoT layer is to hide complexity behind a simple, integrated experience so restaurants can focus on service, not cables and drivers. The blackbox is a legal requirement in Belgium, but in Odoo it becomes a predictable step in the POS journey: configure, test, certify, and run.
We’ll keep pushing on standards like PWAs and WebSockets because they scale better across devices and networks. And as always, we listen to integrators on the front line—your feedback helps us reduce setup time, improve device compatibility, and keep the platform both powerful and approachable.
PART 3 — Viewpoint: Competitors (SAP / Microsoft / Others)
Disclaimer: AI-generated fictional commentary. Not an official corporate statement.
Odoo’s hardware story is pragmatic and cost-conscious, which resonates with SMB restaurants. The Physical vs. Virtual IoT distinction is clear, and the emphasis on ESC/POS and PWAs keeps the stack accessible. Where we’ll watch closely is enterprise depth: VLAN isolation, advanced device fleet management, and centralized policy enforcement are areas where larger groups often demand more governance.
The move to WebSockets is the right direction for remote device workflows. At scale, customers will still expect robust change control, compliance auditability, and lifecycle management across many sites and terminals. If Odoo continues tightening its network posture and multi-location device operations while preserving its UX advantages, it will remain a strong challenger in hospitality POS.
PART 4 — Blog Footer Disclaimer
Disclaimer: This article contains AI-generated summaries and fictionalized commentaries for illustrative purposes. Viewpoints labeled as "Odoo Perspective" or "Competitors" are simulated and do not represent any real statements or positions. All product names and trademarks belong to their respective owners.