Skip to main content

Manage your cooperators

Project description

Beta License: AGPL-3 OCA/cooperative Translate me on Weblate Try me on Runboat

Manage cooperators of a cooperative.

A basic flow can be the following:

  • Create subscription request for a person (moral or physical)

  • Validate subscription request, a capital release request (an invoice: account.move). This invoice is sent to the future cooperator.

  • Payment of the cooperator is registered and the capital Release request is marked as paid.

  • A new cooperator (a special partner) is created, and the right type and amount of share is linked to this new cooperator.

  • The new cooperator appears in the Cooperator Registry.

Features:

  • Manage several share types

  • Manage share subscription request

  • Cooperators can be individuals or companies

  • Get an up to date Cooperator Registry

  • See shares of a cooperator on the partner view

  • Manage departure of cooperators

  • Manage conversion between different share type

  • Send automatic mail to the future cooperator during the procedure

  • Can be used with multi-company configuration

  • Generate Cooperator Certificate and several reports about cooperators

Configurations:

  • on the company, set a default payment term for the capital release requests.

  • on the company, set the cooperator account.

Table of contents

Usage

See the documentation (not available in english ATM).

A localization module is needed with this module.

Known issues / Roadmap

Gather and consolidate all cooperator settings in the application parameters.

Consider a refactoring for:

  1. removing a potential redundancy between the boolean field “representative” and the address type “representative”.

  2. prevent new contacts to have the representative address type, if they are not representative.

See this issue.

Known caveat: the cooperator localization modules will have to be split in order to install the cooperator module without the cooperator_website module.

A “Cooperative Memberships” page should be added to the res.partner form, displaying all the cooperative memberships of the partner (cooperative_membership_ids). The page should only be visible for users that are both in the cooperator_group_user group and in the base.group_multi_company group (how to do this?). Should it display the memberships of all companies or only the ones in which the user is “logged in” (checked in the menu)? If all companies, there would be a conflict with the cooperative_membership_rule_company ir.rule.

Changelog

16.0.1.0.2 (2024-03-12)

Bugfixes

  • Remove duplicated member field in res.partner form view. (#47)

16.0.1.0.0 (2023-11-29)

Features

  • Add a “Share Type” column to the cooperator register report. (#86)

  • Add a new “Registers” menu entry and move the “Subscription Register” menu entry there. (#86)

  • Use default filters instead of domains in contact views. (#86)

  • Merge the confirmation email template for individuals and companies into one. (#86)

  • Rename some files and XML IDs to improve consistency. (#86)

  • Update email templates to the default Odoo layout (what also makes them shorter). (#86)

  • Add a description to email templates. (#86)

  • Move the “Cooperator Candidates” menu entry to the “Cooperators” menu. (#86)

  • Add a new “Cooperator Register” view (and menu entry) to display the cooperative memberships and allow to print the cooperator register (report that was previously on the partner model). (#86)

  • Make the capital release request report inherit from the invoice report instead of copying and modifying it. (#86)

Bugfixes

  • Ensure that only shares related to the current company appear on the cooperator certificate. (#86)

  • Ensure reversals of capital release requests use a name prefix to not clash with normal entries (“RSUBJ” instead of “SUBJ”). (#86)

  • Fix subscription requests created by transfer operations: ensure that no confirmation email is sent, that they don’t appear in the list of subscription requests and cannot be erroneously validated. (#86)

  • Fix the display of the first name in email templates and add tests to cover this. (#86)

  • Fix error when creating a new partner from the normal partner form. (#86)

  • Fix the layout of all reports by rewriting them from the default invoice layout. (#86)

  • Ensure creating a cooperator for a non-current company works (when a capital release request is paid). (#86)

  • Ensure that share.line.share_number cannot be negative. (#86)

  • Don’t send a cooperator certificate if there are no remaining shares after an operation. (#86)

  • Fix the company name in confirmation email template: display the name of the company that made the subscription request instead of the name of the cooperative. (#86)

  • Ensure that the company_type value of a subscription request is copied to the legal_form field of the created partner. (#86)

  • Add unique per-company constraints on the cooperator register number and the operation register number. (#86)

  • Fix copyright statements: add missing ones and use the same format everywhere. (#86)

  • Fix consistency of XML files: XML declaration, spacing. (#86)

  • Display an error message instead of failing when trying to create a subscription request from a partner and no default share product is found. (#86)

  • Rename internal string value of “Blocked” subscription request state from block to blocked. (#86)

  • Ensure per-company sequences are used (for the cooperator register number and the operation register number). (#86)

  • Prevent to create a subscription request where Email and Company Email have the same value, to avoid trying to create a recursive partner hierarchy when validating the subscription request (the partner being the parent of itself). (#86)

  • Fix the footer layout to add company logos: wrap the original layout instead of overwriting it. (#86)

  • Fix required company fields on subscription request form. (#86)

Deprecations and Removals

  • Remove the extra columns in the contacts list view; they can now be found in the cooperator register. (#86)

  • Remove deprecated subscription.request.create_comp_sub_req(). Use the normal subscription.request.create() instead. (#86)

  • Remove the useless “subscription” operation request type. (#86)

14.0.2.0.0 (2023-07-25)

Features

  • Each company now has their own mail templates for cooperator-related e-mails. If no template is set, the default (global) template is used. (#73)

  • ir.sequences used by this module are no longer global; each company has its own sequence for cooperator memberships. (#74)

  • Create subscription journal per company. (#75)

  • Improve multi-company consistency by setting company_id on records where needed and adding the check_company flag on Many2one fields. (#77)

  • ir.rules for multi-company usage added. Users cannot access records of this module if they are not members of the relevant company. (#78)

  • Move cooperative membership properties from res.partner to new cooperative.membership model and add company-dependent computed fields on res.partner for backward compatibility. (#82)

14.0.1.6.0 (2023-02-23)

Features

  • Removed all selection widgets. (#55)

12.0.5.3.0 (2022-09-05)

Improved Documentation

  • Adding USAGE.rst to inform that localization modules are necessary. (#346)

12.0.5.0.0 (2022-06-23)

Deprecations and Removals

  • When no cooperator account is defined on the company, this module previously defaulted to the account with code ‘416000’. This behaviour has been removed because the code is Belgian-only. The functionality has been moved to l10n_be_cooperator. (#314)

12.0.3.3.2 (2022-06-20)

Bugfixes

  • Fix name computation crash (#330)

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Coop IT Easy SC

Contributors

  • Coop IT Easy SC:

    • Houssine Bakkali

    • Robin Keunen

    • Rémy Taymans

    • Victor Champonnois

    • Vincent Van Rossem

    • Manuel Claeys Bouuaert

    • Carmen Bianca Bakker

    • hugues de keyzer

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/cooperative project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

File details

Details for the file odoo_addon_cooperator-16.0.1.1.1.3-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_cooperator-16.0.1.1.1.3-py3-none-any.whl
Algorithm Hash digest
SHA256 4fbb577ad220cc3baf3b197873f4b6d1cbf394fff3dde17a23656ba79bd80522
MD5 16a059769f6748554579e260ce72f093
BLAKE2b-256 d774e29d9bf5635e3035311fe4fb1e091cb5bf64a82d7eb4a9df10b245a4baa6

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page