产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $199.00 USD
- Odoo 版本
- 17, 18, 19
- 设置时间
- 30分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
POS Restaurant Floor Plan Designer Pro
A build-to-order Odoo POS extension that gives multi-floor venues a true drag-and-drop floor designer with custom table shapes, seat capacities, visual merge/split, and a live occupancy and turn-time heat-map. ECOSIRE builds, installs, and supports it for Odoo 17, 18, and 19.
$199.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
OWL drag-and-drop floor editor embedded in the POS frontend with grid snapping and per-table rotation
Extends native `pos.floor` and `pos.table` models rather than patching core, keeping upgrades clean
Custom table shapes (round, square, rectangular, booth, bar-stool, L-shaped) with configurable width/height
Per-table seat capacity as a real `fields.Integer` used in occupancy and party-size validation
Multi-floor and multi-room layouts with named sections and independent background images per floor
Live occupancy heat-map computed via `@api.depends` on active `pos.order` links per table
Turn-time tracking per table with color-graded thresholds (fast / normal / slow) set at config time
Visual merge of tables — drag one onto another to combine open orders, with consistent `pos.order` linkage
Visual split back into separate tables and orders when a party divides
Role-scoped access via `ir.model.access.csv` and record rules: managers edit layouts, cashiers get read-only state
Section-level occupancy and turn-time QWeb reports for shift and daily review
Optional `ir.cron` nightly roll-up of turn-time analytics into a reporting model
Live table state exposed over XML-RPC/JSON-RPC for host tablets, reservations, or BI integration
Version-pinned builds for Odoo 17.0, 18.0, and 19.0 with edition-aware (Community vs Enterprise) implementation
关于此产品
Larger restaurants, food halls, and multi-room venues quickly outgrow Odoo's stock POS floor editor. Odoo Point of Sale ships with a basic pos.floor and pos.table model set and a simple background editor, but it assumes a handful of rectangular or round tables on a single flat plane. Once you run two or three floors, a rooftop, a private dining room, and a bar with irregular booths, the native editor runs out of road: you cannot model a real seat count per table shape, you cannot see which sections are turning fast versus sitting idle, and merging two parties across tables is a clumsy, error-prone operation for your floor staff during a Friday rush.
为什么选择 POS Restaurant Floor Plan Designer Pro
OWL drag-and-drop floor editor embedded in the POS frontend with grid snapping and per-table rotation
Extends native `pos.floor` and `pos.table` models rather than patching core, keeping upgrades clean
Custom table shapes (round, square, rectangular, booth, bar-stool, L-shaped) with configurable width/height
Per-table seat capacity as a real `fields.Integer` used in occupancy and party-size validation
Multi-floor and multi-room layouts with named sections and independent background images per floor
Live occupancy heat-map computed via `@api.depends` on active `pos.order` links per table
POS Restaurant Floor Plan Designer Pro is the layer we build on top of native POS to close that gap. We extend pos.floor and pos.table with new fields and compute methods (models.Model, fields.Integer seat capacity, fields.Selection for shape, @api.depends computed occupancy state) and ship an OWL-based drag-and-drop editor that runs inside the POS frontend. Managers lay out multi-floor and multi-room plans visually, snap tables to a grid, assign custom shapes and sizes, and set exact seat counts per table. On the live POS screen, a color-graded heat-map overlays each table with its current occupancy and turn-time so a host can read the room at a glance and seat the next party into the fastest-turning section. Merge and split are handled visually — drag one table onto another to combine orders, split them back apart when the party separates — with the underlying pos.order links kept consistent.
Technically the module is a clean, upgrade-safe addon: a proper __manifest__.py declaring the POS dependency, ORM extensions rather than core patches, ir.model.access.csv plus record rules so floor-plan editing is limited to manager roles while cashiers get read-only occupancy, XML/OWL views for the editor and heat-map, and optional QWeb reports for section-level occupancy and turn-time summaries. Automated actions or ir.cron jobs can roll up turn-time analytics nightly, and every new model is exposed over Odoo's XML-RPC/JSON-RPC API so a host-stand tablet, a reservations system, or a BI tool can read live table state. It targets Community and Enterprise alike; where Enterprise-only POS features exist we note the difference during scoping and never assume an edition you do not run.
Because this is build-to-order, nothing is a black-box download. After a short scoping call we confirm the exact floors, table shapes, seat rules, and heat-map thresholds you need, then build the version pinned to your Odoo release (17.0, 18.0, or 19.0). Typical delivery is 2 to 4 weeks from confirmed scope. We install it on a staging database first, run UAT with your team against real layouts, then deploy to production with a rollback plan and hand over the full git repository. You own the source, the docs, and a post-go-live support window — no per-seat lock-in and no dependency on a marketplace listing.
你得到什么
- Installable module source code built and pinned to your exact Odoo version (17.0 / 18.0 / 19.0)
- Installation and configuration on your environment, including floor, shape, and heat-map threshold setup
- Technical documentation: model/field reference, security matrix, and API endpoints
- End-user guide plus a live training session for managers and floor staff
- UAT on a staging database against your real layouts, with a documented rollback plan
- Post-go-live support window for bug fixes and configuration adjustments
- Full git repository handover — you own the source and history
- Compatibility notes covering Community vs Enterprise POS behavior for your edition
这是给谁的
Multi-Floor Restaurant Owner
Runs a venue with two or more floors, a rooftop, or private rooms and needs one accurate visual plan of every section instead of the flat single-floor stock editor.
Front-of-House / Floor Manager
Seats parties during peak service and wants a live heat-map of occupancy and turn-time to route guests to the fastest-turning tables and merge or split parties without cashier errors.
Hospitality Group Operations Lead
Standardizes POS across multiple locations and needs consistent, role-scoped floor-plan tooling plus API access to feed reservations and BI dashboards.
Odoo Administrator / IT Manager
Owns the Odoo deployment and wants an upgrade-safe addon that extends `pos.floor`/`pos.table` cleanly, ships with proper access rules, and comes with source and docs they control.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 POS Restaurant Floor Plan Designer Pro 模块 ZIP。
上传至Odoo
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中（或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传）。
安装模块
激活开发者模式，打开应用程序，单击更新应用程序列表，搜索 POS Restaurant Floor Plan Designer Pro，然后按安装。
配置设置
打开新菜单，粘贴您的 ECOSIRE 许可证密钥，连接任何外部凭据（Shopify、Amazon、Stripe 等），然后保存。
验证并上线
运行内置连接测试，同步前 10 条记录，并安排定期 cron。如果出现任何问题，请联系支持人员。
POS Restaurant Floor Plan Designer Pro 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Multi-floor / multi-room layouts | Built in, unlimited floors and named rooms | Possible but you design it from scratch | Often single-floor or capped | |
| Custom table shapes & seat counts | Configurable shapes with real per-table capacity | Whatever you build and maintain | Limited preset shapes | |
| Live occupancy & turn-time heat-map | Color-graded, computed from live orders | Build and tune the logic yourself | Rarely offered | |
| Visual merge / split tables | Drag-to-merge with consistent order linkage | Complex to get order links right | Basic or manual only | |
| Odoo version fit | Pinned build for 17/18/19, edition-aware | Depends on your developer | May lag new releases | |
| Access control | Role-scoped via access CSV + record rules | You implement the security model | Varies, often coarse | |
| API / integration | New models exposed via XML-RPC/JSON-RPC | You expose and document it | Usually closed | |
| Ownership & support | Full source + git handover + support window | You own it and all maintenance | Vendor-locked, per-listing updates |
关于POS Restaurant Floor Plan Designer Pro的常见问题
+How long does delivery take?
This is a build-to-order module, so there is no instant download. After a short scoping call to confirm floors, table shapes, seat rules, and heat-map thresholds, typical delivery is 2 to 4 weeks from confirmed scope. Complex multi-location or integration requirements can extend that, and we tell you the realistic timeline before you commit.
+Which Odoo versions do you support?
We build against Odoo 17.0, 18.0, and 19.0, and pin the module to the exact release you run. It works with both Community and Enterprise POS; where a capability depends on Enterprise-only features, we flag it during scoping and design around your edition.
+How do support and updates work after go-live?
Every build includes a post-go-live support window for bug fixes and configuration tweaks, and you receive the full git repository so nothing is locked to a marketplace listing. Beyond the included window, or to port the module to a future Odoo version, we offer ongoing support and version-upgrade engagements.
+Will this break when I upgrade Odoo or reinstall POS?
We extend the native `pos.floor` and `pos.table` models through the ORM and add our own models rather than patching core files, which keeps the addon upgrade-safe. When you move to a new major Odoo version we rebuild and retest against it; the git handover means you or your own team can maintain it too.
+Can the live table data connect to other systems?
Yes. Every new model is exposed over Odoo's XML-RPC and JSON-RPC API, so live occupancy and turn-time can feed a host-stand tablet, a reservations platform, or a BI tool like Power BI. We scope the exact fields and endpoints you need as part of the build.
+Who can edit the floor plan versus just view it?
Access is role-scoped with `ir.model.access.csv` and record rules. Managers can create and edit layouts, shapes, and thresholds, while cashiers and hosts get read-only access to the live occupancy heat-map. We tailor the exact permission matrix to your team structure.
+Do we own the code, or is it licensed per seat?
You own it. There is no per-seat license and no dependency on an apps.odoo.com listing. We hand over the full source and git history, so your team can read, extend, or maintain the module independently.
申请报价
POS Restaurant Floor Plan Designer Pro
A build-to-order Odoo POS extension that gives multi-floor venues a true drag-and-drop floor designer with custom table shapes, seat capacities, visual merge/split, and a live occupancy and turn-time heat-map. ECOSIRE builds, installs, and supports it for Odoo 17, 18, and 19.
- OWL drag-and-drop floor editor embedded in the POS frontend with grid snapping and per-table rotation
- Extends native `pos.floor` and `pos.table` models rather than patching core, keeping upgrades clean
- Custom table shapes (round, square, rectangular, booth, bar-stool, L-shaped) with configurable width/height
- Per-table seat capacity as a real `fields.Integer` used in occupancy and party-size validation