Purchase contracts and info records

This page describes two sub-modules of src/cluster_erp/modules/procurement/: purchase_contracts/, the outline agreements with a vendor for a period, and info_records/, the price master per vendor and product breakdown with its price history. Supplier quotations that feed both are described on the purchasing quotations module.

Scope and source¶

• Defined in: models.py, services.py, routes.py, and metadata.py of purchase_contracts and info_records.
• Count: 4 tables; 16 contract routes and 8 info record routes (@router. decorators); 5 ActionMeta entries, all on contracts.

Contract fields¶

Contract items (PurchaseContractItem, table procurement_purchase_contract_items) carry line_no, the product breakdown, description, target_qty, released_qty, net_unit_price, and unit_id (src/cluster_erp/modules/procurement/purchase_contracts/models.py:83-109).

Contract statuses and actions¶

The service maps each action to a target status and the allowed source statuses (src/cluster_erp/modules/procurement/purchase_contracts/services.py:39-45).

stateDiagram-v2
 [*] --> draft
 draft --> active: activate
 active --> closed: close
 active --> expired: expire
 draft --> cancelled: cancel
 active --> cancelled: cancel
 cancelled --> draft: reopen

In prose: activate needs a complete draft: at least one item, a validity period with from not after to, and a target value for a value contract (src/cluster_erp/modules/procurement/purchase_contracts/services.py:234-256, src/cluster_erp/modules/procurement/purchase_contracts/services.py:308-346). Every transition checks the record version for concurrent edits (src/cluster_erp/modules/procurement/purchase_contracts/services.py:213-232).

Contract routes¶

Info record fields¶

Price history rows (PurchasingInfoRecordPrice, table procurement_info_record_prices) keep unit_price, currency, valid_from, source, source_ref_code, and recorded_at (src/cluster_erp/modules/procurement/info_records/models.py:94-121).

Info record routes¶

Constraints and validation¶

• A contract changes only in draft; only draft or cancelled contracts can be deleted (src/cluster_erp/modules/procurement/purchase_contracts/services.py:36, src/cluster_erp/modules/procurement/purchase_contracts/services.py:198-210).
• One live info record exists per vendor and product breakdown; a manual duplicate is refused (src/cluster_erp/modules/procurement/info_records/models.py:33-41, src/cluster_erp/modules/procurement/info_records/services.py:160-173).
• upsert creates a record or updates the price, reactivates the record, and appends a history row when the price changed (src/cluster_erp/modules/procurement/info_records/services.py:229-292).
• On SupplierQuotationAwarded, the module upserts one info record per awarded line that carries a full breakdown, each line in its own savepoint (src/cluster_erp/modules/procurement/module.py:813-862).
• CreateFollowOnFromSupplierQuotation creates a purchase order or a contract from an awarded supplier quotation; text lines become text items (src/cluster_erp/modules/procurement/module.py:711-810).
• Purchase order items take their default unit price from lookup_price with the full breakdown (src/cluster_erp/modules/procurement/purchase_orders/services.py:297-303).

Discrepancies¶

Terms introduced¶

Related pages¶

• Procurement module
• Purchase orders
• Purchasing quotations module

Verified against commit 92f8051 on 2026-11-13.