Most teams running Odoo eventually hit the same wall: product data lives inside the ERP, but the people who most need it — warehouse staff scanning a shelf, a technician on-site, a customer holding the physical item, a reseller checking specs — have no way to see it without a login. Odoo core gives you product.template/product.product, a barcode field, and the eCommerce controller, but out of the box that eCommerce page is a shop page (add-to-cart, pricing, checkout), not a neutral public spec sheet. There is no built-in, print-ready label that carries a scannable QR pointing at a curated, catalog-agnostic information page. So teams end up hand-building website pages, exporting to third-party label tools, and reconciling two sources of truth that drift apart the moment a product changes.

Product Public QR is the app we build to close that gap. We add a controller and QWeb-rendered public route (for example /p/<slug>) that renders a read-only information page per product — description, attributes, key specifications, documents, and images — driven entirely by fields on product.template, with a computed slug and an access-scoped published flag so only products you explicitly mark public are reachable. A compute/@api.depends method derives the canonical public URL, and we generate both a 1D barcode (EAN-13/Code128 from the existing barcode field) and a 2D QR code that encodes that URL, using Odoo's report/barcode rendering so no external service is required. Labels are delivered as QWeb (PDF) report templates you can print in batch from the product list — Avery-style sheets or roll labels sized to your printer — and every label's QR resolves to the live page, so a scan in the aisle always shows current data.

Because it is built on the standard ORM and reporting stack, the app stays inside Odoo's security model: ir.model.access.csv plus record rules govern who can publish and edit, the public controller uses sudo() narrowly and only exposes fields flagged as public, and nothing bypasses multi-company boundaries. We can wire an automated action or server action so newly created or updated products auto-generate their slug and QR, expose the published page and label rendering over the XML-RPC/JSON-RPC API for your other systems, and localize the public template and label formats. It ships as a proper module with its own __manifest__.py, is packaged separately for Odoo 17.0, 18.0, and 19.0, and works on both Community and Enterprise (the public page and reports use Community-available primitives; any Enterprise-only touchpoints are called out during scoping).

Delivery is build-to-order: after a short scoping call we confirm the exact fields, page layout, label dimensions, and publishing rules, then build against your version, test on a staging copy of your database, run UAT with you, and deploy with a rollback plan and a git repository handover. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company publishing, deep localization of the public page and labels, custom label designs, and integration with external label printers or downstream systems increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise.