商品詳細は英語で表示されます。翻訳は近日公開予定です。
簡単な事実
- 価格
- $399.00 USD
- Odoo のバージョン
- 17, 18, 19
- セットアップ時間
- 20160分
- ライセンス
- ワンタイム永続
- 言語
- 11 言語
一回購入
Pharmacy & Retail Pharmacy POS
Build-to-order Odoo pharmacy POS with batch/expiry FEFO, controlled-drug register, prescription dispensing and insurance co-pay.
$399.00USD
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
主な機能
Batch and lot tracking on every medicine using Odoo stock lots, with mandatory expiry dates captured at goods-in and enforced through dispensing.
FEFO (First-Expiry-First-Out) dispensing logic that computes each batch's days-to-expiry via @api.depends and auto-suggests the correct lot at the POS so near-expiry stock leaves first.
Prescription capture and dispensing workflow: a custom prescription model linking patient, prescriber, drug, dosage and quantity, with a draft-to-dispensed status flow before the sale is completed.
Controlled/narcotic drug register maintained as its own Odoo model, auto-appending an immutable entry (in/out balance, batch, prescriber, dispensing pharmacist) on every controlled-item movement.
Compliance and audit logs with record-rule-protected register entries and QWeb-printable narcotic register reports formatted for regulatory inspection.
Multi-branch pharmacy stock transfers built on Odoo internal transfers, with per-branch warehouses, min/max reorder rules and lot-level traceability across locations.
POS with insurance co-pay: a computed split between patient-payable and insurer-payable amounts per line, capturing scheme, member ID and approval reference at the till.
Salt/generic substitution: link brands by active ingredient (salt) so cashiers can offer an equivalent generic and log the substitution against the original prescription line.
Near-expiry and expired-stock alerts via scheduled automated actions that raise activities or emails to branch managers and block sale of expired lots.
Role-based security through ir.model.access.csv and record rules for cashier, pharmacist, branch manager and compliance-officer profiles, restricting who can dispense controlled drugs or edit the register.
Dispensing labels and receipts via QWeb: patient-name label with dosage instructions, batch and expiry printed at point of dispense.
XML-RPC / JSON-RPC endpoints kept open for integration with e-prescription systems, national drug databases, insurance eligibility checks or a patient-facing app.
Supports Odoo 17, 18 and 19 on Community or Enterprise, delivered as a proper module with its own __manifest__.py and clean dependency declarations.
この製品について
Pharmacy & Retail Pharmacy POS is a build-to-order Odoo module that ECOSIRE designs, builds, installs and supports for your retail, hospital or chain pharmacy — this is not an off-the-shelf apps.odoo.com download you install yourself. After you purchase, our Odoo engineers scope your dispensing rules, regulatory register format and insurance mix, then deliver a production-ready module on your Odoo 17, 18 or 19 instance (Community or Enterprise) within a typical 2–4 week lead time.
Pharmacy & Retail Pharmacy POSを選ぶ理由
Batch and lot tracking on every medicine using Odoo stock lots, with mandatory expiry dates captured at goods-in and enforced through dispensing.
FEFO (First-Expiry-First-Out) dispensing logic that computes each batch's days-to-expiry via @api.depends and auto-suggests the correct lot at the POS so near-expiry stock leaves first.
Prescription capture and dispensing workflow: a custom prescription model linking patient, prescriber, drug, dosage and quantity, with a draft-to-dispensed status flow before the sale is completed.
Controlled/narcotic drug register maintained as its own Odoo model, auto-appending an immutable entry (in/out balance, batch, prescriber, dispensing pharmacist) on every controlled-item movement.
Compliance and audit logs with record-rule-protected register entries and QWeb-printable narcotic register reports formatted for regulatory inspection.
Multi-branch pharmacy stock transfers built on Odoo internal transfers, with per-branch warehouses, min/max reorder rules and lot-level traceability across locations.
Standard Odoo POS and inventory were never built for pharmacy. A pharmacy needs strict batch and expiry control so the oldest safe stock leaves first, a legally defensible controlled-drug register, a prescription workflow that ties a dispense to a prescriber and patient, and a till that understands insurance co-pay and generic substitution. This module layers all of that onto Odoo's proven stock, point_of_sale and product foundations rather than replacing them — so accounting, purchasing, valuation and multi-company all keep working the way Odoo intends.
Under the hood we extend Odoo's ORM cleanly: custom models built on models.Model for the controlled-drug register, prescription and dispensing records; computed fields with @api.depends for days-to-expiry, FEFO priority and co-pay splits; access control through ir.model.access.csv plus record rules so a cashier, pharmacist and branch manager each see only what their role permits; OWL/XML views and POS screen extensions for the dispensing and substitution flow; and QWeb reports for the narcotic register, dispensing labels and expiry reports. Automated actions and scheduled server actions flag near-expiry batches and reconcile the controlled-drug register, and the JSON-RPC/XML-RPC API stays fully available for e-prescription gateways, national drug databases or a patient app.
You get more than code. ECOSIRE hands over the installed module, a configured pharmacy environment matched to your branches and drug schedules, admin and pharmacist documentation, live training, and a warranty support window — with paid support and Odoo version-upgrade options after that. Everything is scoped to your jurisdiction's controlled-substance rules and your insurer contracts, so what ships fits how your pharmacy actually dispenses.
得られるもの
- The complete build-to-order Odoo module source (models, views, security, QWeb reports, POS extensions) with a clean __manifest__.py, installed on your Odoo 17/18/19 instance.
- A configured pharmacy environment: your branches as warehouses, drug schedules, controlled-substance categories, reorder rules and insurance schemes set up to match your operation.
- ir.model.access.csv and record rules pre-configured for your cashier, pharmacist, branch-manager and compliance roles.
- QWeb report templates for the controlled-drug register, dispensing labels and expiry/stock reports, styled and ready to print.
- Admin and pharmacist user documentation plus a short configuration/runbook guide for your IT team.
- Live training session(s) for pharmacists, cashiers and managers, with a recording for future staff onboarding.
- A post-go-live warranty support window for defect fixes, with an optional ongoing support and Odoo version-upgrade retainer.
- A scoping/requirements document confirming your jurisdiction's controlled-drug rules and insurer setup, signed off before build begins.
これは誰のためのものですか
Independent retail pharmacy owner
Runs one or two community pharmacies and needs a till that enforces expiry control, prints compliant dispensing labels and keeps a defensible controlled-drug register without paying for a heavyweight hospital system.
Hospital pharmacy manager
Manages inward and outpatient dispensing where prescription-to-patient traceability, batch recall readiness and narcotic register accuracy are non-negotiable for audits and accreditation.
Pharmacy chain operations director
Oversees many branches on one Odoo backend and needs inter-branch stock transfers, per-branch FEFO discipline, consolidated controlled-drug reporting and role-based access across the whole estate.
Compliance / inspection officer
Responsible for regulatory readiness; needs immutable register logs, printable narcotic reports and clear evidence of who dispensed which batch to whom, on demand.
インストールの概要
ECOSIREからダウンロード
ecosire.com でライセンスを購入し、アカウント ダッシュボードから Pharmacy & Retail Pharmacy POS モジュールの ZIP をダウンロードします。
Odoo にアップロードする
ZIP をサーバー上の Odoo カスタム アドオン フォルダーに抽出します (または、[アプリ] > [Odoo.sh / runbot のファイルからインストール] を介してアップロードします)。
モジュールをインストールする
開発者モードをアクティブにし、アプリを開き、「アプリリストの更新」をクリックして、「Pharmacy & Retail Pharmacy POS」を検索し、「インストール」を押します。
設定を構成する
新しいメニューを開き、ECOSIRE ライセンス キーを貼り付け、外部認証情報 (Shopify、Amazon、Stripe など) を接続して保存します。
検証して公開する
組み込みの接続テストを実行し、最初の 10 レコードを同期し、定期的な cron をスケジュールします。何か問題が発生した場合はサポートにお問い合わせください。
Pharmacy & Retail Pharmacy POS の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Batch/expiry FEFO dispensing built for pharmacy | Enforced FEFO with per-batch days-to-expiry and expired-lot blocking | Possible but you design and maintain the logic yourself | Varies; often generic lot tracking without FEFO enforcement | |
| Controlled/narcotic drug register with immutable logs | Dedicated model, record-rule protected, printable QWeb register | Build and validate from scratch | Rarely included or not localized | |
| Prescription capture & dispensing workflow | Patient/prescriber-linked prescription-to-dispense flow | Fully bespoke build | Sometimes basic, seldom prescriber-linked | |
| Insurance co-pay & salt/generic substitution at POS | Computed patient/insurer split plus salt-linked substitution logging | Custom POS screen work required | Uncommon in generic modules | |
| Multi-branch pharmacy stock transfers | Per-branch warehouses, lot-level transfers, FEFO per branch | Configurable but unstructured | Depends on module | |
| Built, installed & configured for you (not self-install) | ECOSIRE builds, installs, configures and trains | You hire and manage the developers | You install and configure the download yourself | |
| Support, warranty & Odoo 17/18/19 upgrade path | Warranty window plus optional retainer and version upgrades | Your own team owns all maintenance | Vendor-dependent, often per-version paid | |
| Fit to your jurisdiction & insurer contracts | Scoped to your regulations and insurers before build | Achievable but all effort is on you | Generic, rarely localized to your rules |
Pharmacy & Retail Pharmacy POS に関するよくある質問
Is this an instant download I can install myself?
No. This is a build-to-order module that ECOSIRE designs, builds, installs and configures for you — it is not an apps.odoo.com download. After purchase we scope your dispensing rules, controlled-drug schedules and insurance mix, then deliver a production-ready module on your own Odoo instance.
How long does delivery take?
Typical lead time is 2–4 weeks from the scoping sign-off, depending on how many branches, insurers and regulatory register formats are involved. We confirm a firm timeline in the requirements document before build begins, and complex chain rollouts are phased so your first branches go live sooner.
What support and updates do I get after go-live?
Every build includes a warranty support window for defect fixes plus training and documentation. After that, an optional support-and-maintenance retainer covers enhancements, new insurer or regulatory changes, and Odoo version upgrades (for example moving your instance from Odoo 17 to 18 or 19) so the module keeps working as your Odoo evolves.
Which Odoo versions and editions does it work with?
It supports Odoo 17, 18 and 19 on both Community and Enterprise. We build against Odoo's standard stock, point_of_sale and product apps and declare them as dependencies in the module manifest, so it coexists cleanly with your accounting, purchasing and inventory rather than replacing them.
Will it handle our country's controlled-drug and narcotic regulations?
Yes — the controlled-drug register, dispensing logs and QWeb register reports are configured to your jurisdiction's schedules and required fields during scoping. The register entries are protected by record rules so they can't be silently edited, giving you a defensible audit trail. We tailor the exact register format to your regulator's expectations.
Can it connect to insurance eligibility systems or e-prescription gateways?
Yes. The module keeps Odoo's XML-RPC and JSON-RPC APIs available and we can build integration points for insurer eligibility/co-pay checks, e-prescription intake or national drug databases. The specific integrations are scoped as part of the build based on the systems you use.
How does FEFO dispensing actually work at the till?
Each medicine is tracked by lot with an expiry date captured at goods-in. A computed field derives days-to-expiry per batch, and the POS suggests the earliest-expiring safe lot first (First-Expiry-First-Out). Expired lots are blocked from sale and near-expiry batches raise alerts to the branch manager.
関連モジュール
見積もりを依頼
Pharmacy & Retail Pharmacy POS
Build-to-order Odoo pharmacy POS with batch/expiry FEFO, controlled-drug register, prescription dispensing and insurance co-pay.
- Batch and lot tracking on every medicine using Odoo stock lots, with mandatory expiry dates captured at goods-in and enforced through dispensing.
- FEFO (First-Expiry-First-Out) dispensing logic that computes each batch's days-to-expiry via @api.depends and auto-suggests the correct lot at the POS so near-expiry stock leaves first.
- Prescription capture and dispensing workflow: a custom prescription model linking patient, prescriber, drug, dosage and quantity, with a draft-to-dispensed status flow before the sale is completed.
- Controlled/narcotic drug register maintained as its own Odoo model, auto-appending an immutable entry (in/out balance, batch, prescriber, dispensing pharmacist) on every controlled-item movement.