This module introduces a membership concept called "primeship" for partners.
Primeship functions as a straightforward, user-friendly membership system that activates automatically when a sale order containing a primeship activation product is confirmed. The membership duration is customizable and defined in months.
The system automatically deactivates the primeship when the specified duration expires. Users can easily verify a customer's active primeship status and implement conditional actions based on this membership state.
Key features:
- Simple membership management for partners
- Automatic activation through sales orders
- Configurable duration in months
- Automatic expiration handling
- Easy status verification for conditional business logic
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Sell time-limited "primeship" memberships to customers: confirming a sale order with a primeship product automatically creates a membership period for the customer, and Odoo tracks when it is active or expired.
This module adds a simple membership system called a primeship to customers. On a service product you can tick "Activates primeship" and set a "Primeship duration (in months)" (12 by default). When a sale order containing such a product is confirmed, Odoo automatically creates a primeship record for the customer's company (commercial partner), starting today and ending after the configured number of months. If the customer already has a primeship, the new period is placed after the existing one so periods never overlap.
On the customer form you get a "Primeships" smart button showing how many memberships the customer has, plus an "active_primeship" indicator. A dedicated Primeship screen (list and form) lists start date, end date, related sale order and whether the membership is currently active; it can be searched by dates, customer or current status.
Business rules: the end date cannot be before the start date, and two primeships for the same customer cannot overlap. A sale order line can only have one primeship. Cancelling the sale order deactivates its primeship. When a primeship product is invoiced, the invoice line inherits the membership start and end dates. A daily scheduled job refreshes the active status of customers so expired memberships stop counting as active.
Depends on
Models and fields (5)
- sale.order · extends an existing model
- res.partner · extends an existing modelprimeship_ids, primeship_count (Primeships Count), active_primeship
- sale.primeship · new modelname, active, current (Currently Active), end_date, order_id (Sale Order), partner_id, start_date, order_line_id (Sale Order Line)
- sale.order.line · extends an existing modelprimeship_id (Primeships), primeship_ids
- product.template · extends an existing modelprimeship_duration (Primeship duration (in months)), primeship_activation (Activates primeship)
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/sale-workflow.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0To configure a product that activates primeship upon sale order confirmation:
- Edit the desired product and set its type to "Service"
- Navigate to the "Sales" tab in the product form
- Enable the "Activates primeship" checkbox
- Define the primeship duration (in months)
You can easily view a customer's current primeship status directly from their partner record:
Clicking on the primeship status widget will redirect you to a detailed list view showing all primeship records for that specific customer:
This interface allows you to track membership history, expiration dates, and manage customer primeship records efficiently.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.