Skip to Content

Tests

pmis_base_website pmis_theme_base pmis_website_readme pmis_website_sale_private_prices pmis_website_sale_product_brand_fix pmis_website_theme_oca_assortment pmis_website_theme_oca_checkout pmis_website_theme_oca_document_counter pmis_website_theme_oca_hide_price pmis_website_theme_oca_loyalty pmis_website_theme_oca_payment_fee pmis_website_theme_oca_secondary_unit theme_pmisuite

Coverage

pmis_base_website pmis_theme_base pmis_website_readme pmis_website_sale_private_prices pmis_website_sale_product_brand_fix pmis_website_theme_oca_assortment pmis_website_theme_oca_checkout pmis_website_theme_oca_document_counter pmis_website_theme_oca_hide_price pmis_website_theme_oca_loyalty pmis_website_theme_oca_payment_fee pmis_website_theme_oca_secondary_unit theme_pmisuite

PMISuite Website

Odoo 18.0 PMISuite Website

English · Slovenščina

PMISuite Website provides 20 addons for Odoo 18 Community: independent website tools, customer pricing and quotation checkout, a six-addon storefront bundle, a visual theme, and optional OCA integration bridges.

Capabilities · Setup · Module index · Integration and limits

What you can do

Sell through customer prices and signable quotations

Public visitors browse without commercial prices. Signed-in buyers use their assigned company-compatible pricelist. Checkout creates a sent quotation for portal signature, without requiring an online payment provider. Signing rechecks purchase readiness while retaining the sent prices.

Products need a positive final price and must not be marked On Request Only to enter the cart. For unpriced or request-only variants, the customer can submit a product request that creates an unassigned CRM opportunity. It does not create a sales quotation, reservation, or payment transaction.

Help customers discover and save products

Use whole-term synonym groups, autocomplete, recorded search keywords, shared product tabs, and product-specific content. Saved collections retain product variants and desired quantities. Theme PMISuite adds quick views, product and category snippets, wishlist presentation, and enhanced OCA attribute controls. Brand data and filtering use OCA's product-brand implementation.

Show stock and delivery information

Stock displays and purchase controls use inherited OCA available-to-promise quantities in the applicable fulfillment warehouse. Editable carts follow carrier warehouse settings and native pickup behavior. Free-shipping progress uses the selected carrier's threshold, currency, amount basis, and quoted fee; there is no independent website threshold.

Add a website app and publish documentation

Website PWA extends OCA's web_pwa_customize with app branding and shortcuts and reuses Odoo's service worker. Offline mode shows a public fallback rather than cached private shopping pages.

The independent documentation addon publishes selected local repository and addon READMEs, linked guides, images, and referenced PDFs. Translated source files supply live SEO metadata. The independent base website addon changes Odoo's protected default website designation without transferring content or changing domain routing.

How it fits together

pmis_theme_base installs six addons: pmis_website_sale_core, pmis_website_search, pmis_website_pwa, pmis_website_product_content, pmis_website_collections, and pmis_website_sale_delivery. It supplies their combined Theme PMISuite website settings tab. Core depends on pmis_website_sale_private_prices and owns the shared storefront resources.

theme_pmisuite adds presentation on top of the bundle. Installing the bundle and applying the theme to a website are separate actions. Collection controls, quick-view placeholders, and dynamic mega menus need the matching theme markup. The base website and documentation addons depend on website and can be used without the storefront bundle.

OCA bridges extend the installed dependencies' behavior. Their manifests define the exact automatic-installation conditions. Some depend on sale core, some on the theme, and the secondary-unit bridge depends on collections. The loyalty bridge installs the OCA promotion-incompatibility dependency when triggered by sale core and website loyalty.

Start here

  1. Choose the scope. Select independent tools, individual feature addons, the complete storefront bundle, or optional OCA bridges from the index.
  2. Provide dependencies. Put this repository and the required OCA addons on addons_path. Consult requirements.txt, oca_dependencies.txt, and the selected manifests. Documentation publishing requires the Python packages Markdown and docutils.
  3. Install and apply. For the full storefront, install pmis_theme_base and apply Theme PMISuite to the intended website through Odoo's theme workflow.
  4. Configure customer prices. Enable native Pricelists and assign each buyer an active company-compatible or shared pricelist in the website company's context. Keep the feature enabled; disabling it archives pricelists.
  5. Configure the website. Use its Theme PMISuite tab for search, display, countries, stock, and PWA options. Configure shipping thresholds and warehouses on the carriers. Follow each module guide for access roles and prerequisites.

Modules

Module Purpose License
pmis_base_website Change the protected default website while retaining standard deletion safeguards. LGPL-3
pmis_website_readme Publish selected local repository and addon documentation with translations, images, PDF downloads, and source SEO metadata. LGPL-3
pmis_website_sale_private_prices Hide public prices, enforce customer pricelists, hand checkout to signable quotations, and create CRM requests for unpriced or request-only variants. LGPL-3
pmis_theme_base Install the six shared storefront addons and expose their combined website settings; applying the visual theme is separate. AGPL-3
pmis_website_sale_core Provide shared catalog, cart, configurator, account and product-file policies, quantity-price tables, menus, labels, and frontend resources. AGPL-3
pmis_website_search Expand whole search terms through synonym groups, enrich autocomplete, and record eligible shop searches. AGPL-3
pmis_website_pwa Add website-specific app manifests, branding, shortcuts, and worker lifecycle with a public offline fallback. AGPL-3
pmis_website_product_content Manage shared HTML product tabs and product-specific overrides with publication and website restrictions. AGPL-3
pmis_website_collections Save named collections and quantities, add items to the cart, and queue sharing emails; see the documented access limitation. AGPL-3
pmis_website_sale_delivery Use OCA stock availability and carrier warehouses for fulfillment, stock displays, and carrier-based free-shipping progress. AGPL-3
theme_pmisuite Apply storefront layouts, styling, editor options, product and category snippets, quick views, collection controls, and enhanced attribute filters. AGPL-3
pmis_website_theme_oca_assortment Extend PMIS catalog, cart, collection, and sitemap policies with OCA no-show and no-purchase assortments. AGPL-3
pmis_website_theme_oca_secondary_unit Select eligible OCA sales units when adding collection items while retaining saved primary-unit quantities. AGPL-3
pmis_website_theme_oca_document_counter Validate product-document relationships and visitor access before delegating counted downloads to OCA. AGPL-3
pmis_website_theme_oca_hide_price Combine OCA website, customer, and product hidden-price rules with PMIS catalog and checkout eligibility. AGPL-3
pmis_website_theme_oca_filter_manual Preserve existing-value visibility on OCA mobile manual-submit attribute filters in Theme PMISuite. AGPL-3
pmis_website_theme_oca_loyalty Retain native rewards and OCA promotion incompatibilities, checking reward eligibility before quotation signing. AGPL-3
pmis_website_theme_oca_checkout Keep OCA skip-payment completion within the PMIS quotation-signing workflow. AGPL-3
pmis_website_theme_oca_payment_fee Preserve inherited provider-fee processing while preventing provider selection from charging unsigned website quotations. AGPL-3
pmis_website_sale_product_brand_fix Guard OCA brand shop-response postprocessing while preserving inherited brand and attribute filtering. AGPL-3

All 20 addons have English and Slovenian module guides. Licenses below come from the manifests; individual source notices remain applicable.

Integration scope and limits

Catalog, cart, product-file, and quotation checks retain visitor, website, and company context. Product documents require their own publication and catalog checks; sale-portal documents use separate order entitlements. Optional bridges add OCA assortment, hidden-price, loyalty, fee, download-counting, and checkout behavior through inherited extension points.

Collections are partner-owned and have no website/company field. Their displayed products follow the current catalog. Most collection operations check ownership, but the item-removal endpoint currently lacks that check. Email sharing queues introductory text; it grants no recipient access and contains no itemized product list. Native cart additions reject fractional saved primary-unit quantities. See the collection guide.

PWA does not support offline account, cart, or checkout use. Another application's root service worker requires separate integration. See the PWA guide.

Personalized storefront responses are private and non-cacheable; shared sitemaps use the public visitor. Public price privacy and purchase checks apply independently of B2B presentation toggles. Backend and ordinary portal payment workflows retain their inherited processing. Custom controllers and themes must respect the same catalog and pricing hooks.

Maintenance and documentation

Keep compatible bundle, feature-addon, theme, and bridge versions together on addons_path. Use each manifest for its current dependencies and version. Apply module and asset updates through the installation's maintenance workflow. Theme application remains a separate website operation.

Module guides contain configuration, usage, access rules, and limits. Shared implementation and assets live in the feature addons; the bundle retains compatibility imports and its combined settings view. Theme-specific fragment routes live in theme_pmisuite/controllers/main.py. Asset declarations belong to each feature manifest and its loaded ir.asset data.

These READMEs and the theme's static/description/index.html are maintained directly. Update English and Slovenian companions together. Source SEO metadata belongs at the beginning of each document; see documentation publication and SEO.

Project checks

Repository test and coverage badges

Badges show the last published local results for the displayed addons. They do not establish current results for all 20 modules; README updates do not refresh them.

Tests

pmis_base_website pmis_theme_base

pmis_website_readme

pmis_website_sale_private_prices pmis_website_sale_product_brand_fix

pmis_website_theme_oca_assortment pmis_website_theme_oca_checkout pmis_website_theme_oca_document_counter

pmis_website_theme_oca_hide_price pmis_website_theme_oca_loyalty pmis_website_theme_oca_payment_fee pmis_website_theme_oca_secondary_unit theme_pmisuite

Coverage

pmis_base_website pmis_theme_base

pmis_website_readme

pmis_website_sale_private_prices pmis_website_sale_product_brand_fix

pmis_website_theme_oca_assortment pmis_website_theme_oca_checkout pmis_website_theme_oca_document_counter

pmis_website_theme_oca_hide_price pmis_website_theme_oca_loyalty pmis_website_theme_oca_payment_fee pmis_website_theme_oca_secondary_unit theme_pmisuite

Issues and maintainers

Report bugs and scoped enhancement proposals through PMISuite Repository Issues. Include reproduction steps and expected and actual results. Use synthetic examples and redact sensitive information.

Credits

Authors: Luxim d.o.o., Matmoz d.o.o., and PMISuite. Contributor: Matjaž Mozetič. Individual module credits remain in the module READMEs.

LUXIM MATMOZ

Maintainer: sysadminmatmoz.

sysadminmatmoz

Luxim is an independent R&D and deployment company focused on solving complex problems in the Odoo ecosystem and an active member of the Odoo Community Association.

Addon documentation