Skip to Content

Commodity Base

by
Odoo

$ 6.88

v 19.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 3403
Technical Name grev_od_commodity_base
LicenseOPL-1
Websitehttps://www.grevlin.com
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 3403
Technical Name grev_od_commodity_base
LicenseOPL-1
Websitehttps://www.grevlin.com

🌱 Commodity Base

Domain-Agnostic Master Data for Commodity Types, Grades, Quality Parameters & Reference Configuration

✓  Odoo 19.0 Community and Enterprise  |  OPL-1 License

🎯 Value Proposition

Commodity Base is the foundational hub of the Grevlin Commodity Procurement Suite. It provides a single, domain-agnostic configuration layer for commodity types, quality grades, quality parameters, forms/cuts, origin regions, packaging types, regulatory standards, and quality profiles — serving as the master data backbone consumed by all downstream commodity modules including supplier management, contracts, delivery, quality inspection, warehousing, and settlement.

🌎

6 Commodity Domains

Grains, meat, fish, dairy, oils, and industrial — all pre-configured with seed data
⭐

Grade-Based Pricing

Price adjustment percentages on every grade, consumed by downstream settlement engines
🔬

Quality Parameters

Reject thresholds and per-unit penalties that drive auto-reject and deduction logic

🌟 Key Benefits

📌

Single Source of Truth

Define commodity types, grades, and quality parameters once. Every downstream module — supplier management, contracts, delivery, quality inspection, warehouse, and settlement — references these shared definitions automatically.

🌱

Domain-Agnostic Design

Works across all commodity sectors: grains and cereals, meat and poultry, fish and seafood, dairy, edible oils, and industrial commodities. The domain model adapts to any procurement vertical without code changes.

⚖

Regulatory Compliance Ready

Quality standard profiles map regional compliance requirements (EU, EAC, USDA, Codex) to per-commodity parameter thresholds. Switch between export standards and domestic standards with a single profile selection.

🔒

Centralized Security Groups

Defines the three-tier security model (User / Officer / Manager) that all commodity modules inherit. One set of groups governs access across the entire commodity procurement chain — no per-module group sprawl.

⚙ Core Features

🌱 Commodity Domains & Types

  • Pre-configured domains: grains, meat, fish, dairy, oils, industrial
  • Hierarchical categories within each domain
  • Commodity types linked to product.product and uom.uom
  • Unique code per company with SQL constraint
  • Chatter tracking on all type-level changes

⭐ Quality Grades

  • Per-commodity grade definitions with sequencing
  • Accepted/rejected flag for purchase eligibility
  • Price adjustment percentage (premium or discount)
  • Minimum quality score threshold
  • Used by settlement module for final price calculation

🔬 Quality Parameters & Test Methods

  • Parameter definitions with min/max acceptable ranges
  • Reject threshold for automatic rejection
  • Penalty per unit of deviation for settlement deductions
  • Linked test methods (lab procedures, equipment)
  • Consumed by commodity_quality for inspection results

📦 Forms, Cuts & Presentations

  • Hierarchical form types: whole → primal → sub-primal → retail
  • Expected yield percentage from parent form
  • Per-form cold chain requirements and shelf life
  • Storage temperature ranges (min/max °C)
  • Critical for meat, fish, and processed commodity procurement

⚖ Regulatory Standards & Quality Profiles

  • Standard registry: EAC, EU, USDA, ISO, Codex Alimentarius
  • Export/import requirement flags per standard
  • Quality profiles override parameter thresholds per standard
  • Multi-country applicability with res.country links
  • Effective and expiry dates for regulatory lifecycle

📍 Reference Data & Configuration

  • Origin regions for provenance tracking
  • Procurement seasons with start/end dates
  • Packaging types (bags, bulk, drums, containers)
  • Price basis (Incoterms) for cost calculations
  • Unit conversion factors between commodity-specific UoMs
  • Storage conditions: temperature, humidity, fumigation, aeration

👥 Who Is This For?

🌽

Commodity Traders & Agribusinesses

Standardize commodity definitions across grains, livestock, fish, dairy, and oils. Ensure consistent grading, quality testing, and pricing rules across all procurement operations.

📊

Quality & Compliance Managers

Define quality parameters, reject thresholds, and regulatory standard profiles. Map regional compliance requirements to commodity-specific acceptance criteria.

🛠

System Administrators

Set up the master data foundation before deploying supplier, contract, delivery, quality, warehouse, or settlement modules. Centralized security groups simplify user access management.

🗒 Changelog

Version 2.0.0 — March 2026

Full Master Data Platform — Major Release

  • Commodity domains with cold chain and food safety flags
  • Hierarchical categories within each domain
  • Forms / cuts / presentations with yield hierarchy (whole → primal → retail)
  • Quality standard profiles with per-parameter threshold overrides
  • Regulatory standard registry with country and import/export flags
  • Storage conditions: temperature, humidity, fumigation, aeration, incompatibilities
  • Test method definitions linked to quality parameters
  • Origin regions, procurement seasons, packaging types, price basis (Incoterms)
  • Unit conversion factors between commodity-specific UoMs
  • Centralized security groups (User / Officer / Manager) for all commodity modules
  • Multi-company record rules on all primary models
  • Pre-loaded seed data across all six commodity domains

Version 1.0.0 — January 2026

Initial Release

  • Commodity type registry with product and UoM links
  • Quality grades with price adjustment percentages
  • Quality parameter definitions with reject thresholds and penalty rules
  • Three-tier security groups (User / Officer / Manager)
  • Multi-company record rules
  • Basic seed data for grain and cereal domains

📞 Need Help?

🎁 30 Days Free Support Included
📧

Email

odoo@grevlin.com
🐦

X (Twitter)

@GrevlinGlobal

Grevlin Commodity Procurement Suite

Enterprise-Grade Commodity Procurement Solutions for Odoo

© 2026 Grevlin Global Corp. All Rights Reserved.

Compatible with Odoo 19.0 | Licensed under OPL-1

Commodity Base

The Commodity Base module is the foundational hub of the Grevlin Commodity Procurement Suite. It provides domain-agnostic master data for commodity types, quality grades, quality parameters, forms/cuts, origin regions, procurement seasons, packaging types, regulatory standards, and quality profiles — consumed by all downstream commodity modules.

Overview

This module defines the shared configuration layer that every other commodity module depends on: supplier management, contracts, delivery, quality inspection, warehousing, and settlement all reference Commodity Base for their master data.

Key Capabilities

  1. Commodity Domains — six pre-configured sectors (grains, meat, fish, dairy, oils, industrial) with cold chain and food safety flags.
  2. Hierarchical Categories — multi-level category trees within each domain for fine-grained classification.
  3. Commodity Types — the core entity, linked to product.product and uom.uom, with mail tracking and unique codes per company.
  4. Quality Grades — per-commodity grade definitions with accepted/rejected flags, price adjustment percentages, and minimum quality score thresholds.
  5. Quality Parameters — measurable attributes with min/max acceptable ranges, reject thresholds, per-unit penalties, and linked test methods.
  6. Forms / Cuts / Presentations — hierarchical form types (whole, primal, sub-primal, retail, processed) with yield percentages, cold chain requirements, and shelf life.
  7. Regulatory Standards — standard registry (EAC, EU, USDA, ISO, Codex) with country applicability and import/export flags.
  8. Quality Standard Profiles — per-commodity parameter threshold overrides mapped to a governing standard for regional compliance.
  9. Reference Data — origin regions, procurement seasons, packaging types, price basis (Incoterms), unit conversion factors, and storage conditions.
  10. Centralized Security Groups — User / Officer / Manager groups inherited by all commodity modules.

Note

This is a pure master data module — no workflow states, no transactional logic. All models are configuration records.

Configuration

Commodity Domains

Six commodity domains ship as seed data. To add a custom domain:

  1. Go to :menuselection:`Commodity --> Configuration --> Domains`.
  2. Click :guilabel:`Create`.
  3. Set :guilabel:`Domain Name`, :guilabel:`Code`, and flags:
  4. Click :guilabel:`Save`.

Commodity Types

  1. Go to :menuselection:`Commodity --> Configuration --> Types`.
  2. Click :guilabel:`Create`.
  3. Fill in required fields:
  4. Optionally link a :guilabel:`Linked Product` from the Odoo product catalog.
  5. Click :guilabel:`Save`.

Important

The commodity code must be unique within the company. The SQL constraint code_company_uniq enforces this at the database level.

Quality Grades

  1. Open a commodity type and navigate to the :guilabel:`Grades` tab.
  2. Click :guilabel:`Add a line`.
  3. Set :guilabel:`Grade Name`, :guilabel:`Code`, and:
  4. Click :guilabel:`Save`.

Tip

The price_adjustment_pct value is consumed downstream by the settlement module to calculate the final purchase price. Set it once here and it applies across all settlement computations.

Quality Parameters

  1. Open a commodity type and navigate to the :guilabel:`Quality Parameters` tab.
  2. Click :guilabel:`Add a line`.
  3. Define the parameter:
  4. Click :guilabel:`Save`.

Quality Standard Profiles

Profiles override the default parameter thresholds for a specific regulatory standard or market requirement.

  1. Go to :menuselection:`Commodity --> Configuration --> Quality Profiles`.
  2. Click :guilabel:`Create`.
  3. Select :guilabel:`Commodity Type` and :guilabel:`Governing Standard`.
  4. In the :guilabel:`Parameter Thresholds` tab, add lines with per-parameter min, max, reject threshold, and penalty overrides.
  5. Click :guilabel:`Save`.

Storage Conditions

  1. Open a commodity type and navigate to the :guilabel:`Storage Conditions` tab.
  2. Click :guilabel:`Add a line`.
  3. Select :guilabel:`Storage Type` (ambient, chilled, frozen, controlled atmosphere, liquid tank).
  4. Set temperature range, humidity, max storage days, and fumigation/aeration requirements.
  5. Optionally specify :guilabel:`Incompatible Commodities` that cannot share storage.
  6. Click :guilabel:`Save`.

Security Groups

The module defines three centralized groups under the Commodity Procurement category. All other commodity modules reference these groups — they do not define their own.

Commodity User (group_commodity_user)

  • Read-only access to all commodity master data.
  • Cannot create or edit records.

Commodity Officer (group_commodity_officer)

  • Create and edit commodity types, grades, parameters, and all reference data.
  • Cannot delete records.
  • Inherits Commodity User permissions.

Commodity Manager (group_commodity_manager)

  • Full CRUD including delete on all commodity models.
  • Can manage security-sensitive configuration.
  • Inherits Commodity Officer permissions.

Note

Multi-company record rules apply to all models using the pattern ['|', ('company_id', '=', False), ('company_id', 'in', company_ids)].

Usage

Setting Up a New Commodity

The typical setup sequence for a new commodity:

  1. Verify or create the commodity :guilabel:`Domain` and :guilabel:`Category`.
  2. Create the :guilabel:`Commodity Type` with product and UoM links.
  3. Add :guilabel:`Grades` with price adjustments.
  4. Add :guilabel:`Quality Parameters` with test methods, reject thresholds, and penalties.
  5. Add :guilabel:`Forms / Cuts` if applicable (especially for meat and fish).
  6. Add :guilabel:`Storage Conditions` if the commodity has specific temperature or fumigation requirements.
  7. Optionally create a :guilabel:`Quality Standard Profile` for each target market (domestic, EU export, etc.).

Tip

Complete this setup before deploying downstream modules (supplier, contract, delivery, quality, warehouse, settlement). They all depend on the master data defined here.

Technical Details

Data Model

Model Type Description
grev.commodity.domain Model Commodity sector (grains, meat, fish, dairy, oils, industrial).
grev.commodity.category Model Hierarchical category within a domain.
grev.commodity.type Model + mail.thread Core commodity definition with product and UoM links.
grev.commodity.grade Model Quality grade with price adjustment and acceptance flag.
grev.commodity.quality.param Model Quality parameter with thresholds and penalties.
grev.commodity.form Model Form / cut / presentation with yield hierarchy.
grev.commodity.origin Model Origin region for provenance tracking.
grev.commodity.season Model Procurement season with date range.
grev.commodity.packaging Model Packaging type definitions.
grev.commodity.price.basis Model Price basis (Incoterms) reference.
grev.commodity.conversion Model Unit conversion factors between UoMs.
grev.commodity.test.method Model Laboratory test method definitions.
grev.commodity.standard Model Regulatory standard registry.
grev.commodity.quality.profile Model Standard-mapped parameter threshold overrides.
grev.commodity.quality.profile.line Model Per-parameter override lines within a profile.
grev.commodity.storage.condition Model Storage requirements per commodity type.

Dependencies

  • base — core framework
  • product — product catalog integration
  • uom — unit of measure definitions
  • mail — chatter tracking on commodity types

See Also

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.