イメージプレビューConfigurable combo meals and forced/optional modifiers with upsell pricing and kitchen-ready tickets
— built for your Odoo POS.
POS Combo Meals & Modifiersとは？
Configurable combo meals and forced/optional modifiers with upsell pricing and kitchen-ready tickets — built for your Odoo POS. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
主な機能
受注生産、すべておまかせ
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
- 1
ご注文
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
- 2
構築とインストール
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
- 3
本番稼働 + サポート
約1週間（営業日ベース）で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
技術仕様
- Odoo互換性
- Odoo 17, Odoo 18, Odoo 19
- エディション
- Enterprise＆Community
- ライセンス
- ライセンスの確認が必要です
- Python要件
- Python 3.10+
- データベース
- PostgreSQL 12+
この製品について
Selling meal deals and made-to-order items in Odoo Point of Sale usually means a wall of near-duplicate products, manual price math, and kitchen tickets that never show what the customer actually asked for. POS Combo Meals & Modifiers is a build-to-order Odoo module that ECOSIRE designs, develops, installs, and supports specifically for your QSR operation — no generic download, no guesswork.
At the core is a combo builder that lets a single POS product represent a whole meal deal. You define component slots (main, side, drink) as new models.Model records, each pointing at a group of eligible products, with min/max choices and per-choice price deltas resolved by @api.depends computed fields. Cashiers pick one main, one side, one drink from an OWL-based selection screen, and the order line price is calculated automatically — deposit pricing, "any two for" bundles, and fixed-price combos are all supported.
Modifiers work the same way. Forced modifier groups (for example, "choose your bun" or "spice level") block the line until a valid selection is made; optional groups (extra cheese, add bacon, no onions) attach cleanly with per-modifier price adjustments that flow through to the receipt, the journal entries, and your sales analytics. Because modifiers are stored as structured records rather than free-text notes, they report correctly, cost correctly, and print correctly.
That last point matters most in the kitchen. The module writes full combo composition and every modifier onto the KDS and the printed kitchen ticket via a customized QWeb receipt/order template, so expo and line cooks see "Combo #2 — no pickles, extra cheese, large fries" instead of a bare SKU. Upsell prompts (size up, add a dessert, make it a meal) fire at the moment of selection to lift average ticket without slowing the line.
ECOSIRE builds the module against your exact Odoo edition and version. It targets Odoo 17, 18, and 19, works on Community or Enterprise POS, respects your access model through ir.model.access.csv and record rules, and — where your workflow needs it — exposes the combo/modifier data over Odoo's XML-RPC/JSON-RPC API for kiosks, aggregators, or your own front end. You get a clean, upgrade-safe addon in its own __manifest__.py, not a pile of studio hacks.
This is a fixed-scope engagement with a typical one working week lead time from confirmed requirements to installed, tested, and trained. You are buying the build and the handover, not an instant download.
得られるもの
- Custom Odoo addon module (source code) with its own __manifest__.py, models, security rules, OWL POS screens, and QWeb kitchen/receipt templates, built for your Odoo 17, 18, or 19 edition
- Installation and configuration on your environment (staging first, then production) with your real combo and modifier menu loaded
- Configured combo definitions, modifier groups, and upsell prompts reflecting your actual menu and pricing
- Kitchen ticket / KDS template tailored to your outlet layout and printer setup
- Technical documentation: data model overview, configuration guide, and how to add or edit combos/modifiers yourself
- Staff training session for cashiers and POS managers (recorded on request) covering ordering flow and menu maintenance
- Source-controlled handover (Git repository access) so you own the code outright
- Post-launch support window (two weeks included) for bug fixes and configuration adjustments
これは誰のためのものですか
QSR / Fast-Food Operator
Runs one or more quick-service outlets selling meal deals and customizable items. Needs combos priced and rung up in seconds without a product SKU explosion, and wants the kitchen to see exactly what was ordered.
Restaurant Operations / Franchise Manager
Oversees menus and pricing across multiple locations. Needs consistent combo and modifier definitions, reliable upsell prompts to lift average ticket, and clean sales reporting on which combos and add-ons actually sell.
Odoo Administrator / IT Lead
Owns the Odoo instance and cares about upgrade safety and access control. Wants a clean, documented addon with proper ir.model.access.csv and record rules — not Studio patches — that survives version upgrades and integrates with kiosks via the API.
POS Combo Meals & Modifiers の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Odoo 標準機能 |
|---|---|---|---|---|
| Combo meals as a single POS product (no SKU explosion) | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Forced + optional modifier groups with per-modifier price deltas | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Full combo + modifier detail on KDS / printed kitchen ticket | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Size / add-on upsell prompts at point of selection | 付属 | 部分的なサポート | 含まれていない | 含まれていない |
| Built and tested for your exact Odoo 17/18/19 edition | 付属 | 付属 | 部分的なサポート | 付属 |
| Menu, pricing, and kitchen layout configured to your real operation | 付属 | 部分的なサポート | 含まれていない | 含まれていない |
| Structured records for accurate costing + POS analytics (not free-text notes) | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Clean addon with __manifest__.py, ir.model.access.csv, record rules (upgrade-safe, no Studio hacks) | 付属 | 部分的なサポート | 部分的なサポート | 含まれていない |
| Included training, documentation, and post-launch support window | 付属 | 含まれていない | 含まれていない | 含まれていない |
POS Combo Meals & Modifiers に関するよくある質問
How long until the module is delivered and installed?
Typical lead time is one working week from the point your requirements (menu structure, combo rules, modifier groups, pricing, and kitchen ticket layout) are confirmed. This is a build-to-order engagement — ECOSIRE develops the module for your Odoo instance, tests it on staging, then installs it on production. It is not an instant apps.odoo.com download. Simpler menus land nearer two weeks; complex multi-outlet or API-integrated builds land nearer four.
What support and updates do I get after launch?
Every build includes a two-week go-live support window for bug fixes and configuration adjustments. You receive full source code and Git access, so your team can maintain it, and ECOSIRE offers optional ongoing support/maintenance retainers. When you upgrade Odoo (for example 18 to 19), we can provide a paid compatibility pass — because the module is a clean addon with its own __manifest__.py and no Studio hacks, upgrades are straightforward.
Which Odoo versions and editions does this support?
We build against Odoo 17, 18, and 19, on either Community or Enterprise Point of Sale. Tell us your exact version and edition at kickoff and the module is developed and tested specifically for it, using the OWL POS architecture and QWeb templates native to that release.
Will the combo and modifier details actually reach the kitchen?
Yes. That is a core part of the build. Full combo composition and every modifier (including negatives like 'no onions') are written to the printed kitchen ticket and the Kitchen Display System via a customized QWeb order/receipt template — so the line sees 'Combo #2, extra cheese, no pickles, large fries', not a bare SKU. The exact layout is tailored to your outlet during the engagement.
Do modifiers and combos report and cost correctly, or are they just notes?
They are stored as structured Odoo records (via proper models.Model definitions and computed price fields), not free-text order notes. That means per-modifier price adjustments flow into the receipt, the accounting journal entries, and POS sales analytics, and component products can be tracked against inventory. You get real reporting on which combos and add-ons sell — something free-text approaches cannot give you.
Can we edit combos and modifiers ourselves after handover?
Yes. Configuration lives in back-office records secured by ir.model.access.csv and record rules, so authorized POS managers can add or change combos, modifier groups, and prices without a developer. Your documentation and training session cover exactly how. If you prefer, ECOSIRE can also manage menu changes for you under a support retainer.
関連モジュール
POS Block Incognito
A build-to-order Odoo Point of Sale guard that detects and blocks private/incognito browsing sessions before the POS loads, protecting the offline order cache and local storage from silent data loss. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 estate.
POS Combo Meals & Modifiers
Configurable combo meals and forced/optional modifiers with upsell pricing and kitchen-ready tickets — built for your Odoo POS.
- Combo/meal-deal builder: one POS product spans multiple component slots (main, side, drink) with configurable min/max choices per slot
- Component product groups: each slot draws from a curated set of eligible products so cashiers only see valid choices
- Fixed-price, delta-price, and bundle pricing ('any 2 for', 'make it a meal') resolved by @api.depends computed fields on the order line
- Forced modifier groups that block the POS order line until a valid selection is made (bun, spice level, cook temperature)