Address
An Address in the stock context is a physical location record linked to a partner — used to identify farms, storage facilities, processing sites, and logistics contacts involved in stock transactions. A single partner can have multiple addresses serving different roles: a farm's field location (where goods are collected), a separate office address (for correspondence and invoicing), and one or more warehouse addresses (where goods are delivered or received).
Article
An Article is the item master data record for a tradeable commodity or processed product — the specific thing being weighed, contracted, and stored in the stock management system. In the agricultural context this could be a particular crop type (e.g. "Soft Wheat" or "Sunflower Seeds"), a processed derivative, or a packaging material. Each article carries an identifier, a name, and a set of classification attributes that determine how it is handled throughout the system.
CoPos (Contract Position)
A CoPos is a single agreed line item within a contract, specifying what has been committed: which article, in what quantity, at what quality level, for what unit price, and under which conditions. Together, the CoPos entries of a contract define its entire substantive content — the contract header provides the administrative and commercial framework, while the positions carry the actual trading commitments.
Contract
A Contract in the stock management context is the legally and commercially binding agreement that defines the terms for the delivery and receipt of goods between two parties. It records which partner is buying or selling, under what price conditions, for what delivery and transport terms, and within which time window the exchange is expected to take place. All of this administrative and commercial context lives on the contract header, while the actual commodity commitments — article, quantity, quality, and price per line — are captured in the associated contract positions (CoPos).
ContractType
A ContractType is the top-level classification that defines the fundamental direction and purpose of a contract within the stock management workflow. The most common distinction is between a purchase contract — goods arriving from a producer or supplier — and a sales contract — goods leaving toward a buyer or processing facility. This classification is not merely a label: the type determines which set of workflow states are valid for contracts of that kind, since a purchase agreement and a sales agreement follow different lifecycle steps even though they share the same underlying data structure.
ContractVersion
A ContractVersion is a versioning layer beneath a ContractType that allows the same kind of contract to exist in multiple named variants. In practice this is used when a contract type — for example a purchase agreement — covers several slightly different forms depending on the trade relationship: a standard grain purchase contract, a special organic grain contract, or a contract with different clause sets for export markets.
MarketingProj (Marketing Project)
A MarketingProj is an organizational grouping entity that bundles product groups and articles under a common marketing initiative, product season, or campaign context. In the stock management context, a marketing project typically represents a trading season or a specific commodity program — for example "Grain Season 2024/25" or "Organic Oilseeds Program". Product groups are assigned to a marketing project, which means that every article belonging to those groups is implicitly part of that project's scope.
PGVariant (Product Group Variant)
A PGVariant is a specific variety or sub-type within a product group — used to identify goods at a finer level of detail than the product group alone allows. In an agricultural stock context, a PGVariant typically represents a crop variety (e.g. "Pannonikus" for wheat, "PR45D03" for rapeseed) or a quality grade designation. This granularity is important because different varieties of the same commodity can command different prices, carry different quality profiles, and require separate stock balances for accurate inventory management.
Partner
A Partner in the stock management context is a business entity involved in the physical flow of goods — primarily the farms and producers delivering commodities, the trading companies and buyers receiving them, and the logistics providers moving them in between. Partners are the who behind every contract, every transaction, and every payment in the stock system.
ProductGroup
A ProductGroup is the top-level commodity category under which articles (individual products) are organized. In an agricultural trading context, typical product groups represent broad commodity classes such as "Cereals", "Oilseeds", "Pulses", or "Specialty Crops". Every article belongs to exactly one product group, and this membership drives a range of downstream behaviors throughout the system.
StorePeriod
A StorePeriod is a named time window — such as a harvest season or a marketing year — used to categorize stock and contracts by the period in which goods were produced or stored. In the stock context this distinction is critical because the same commodity can exist in multiple periods simultaneously: last year's grain and this year's grain may both be physically present in the same warehouse but must be tracked, priced, and reported separately.
Trans (Transaction)
A Trans is the header document for a physical stock movement event — a goods receipt at intake, a goods issue on dispatch, or another warehouse operation that changes the inventory position. It acts as the organizational container under which all individual weighed or measured positions (TransPos) are grouped. A single transaction might represent a full truck delivery containing multiple positions with different articles, quality grades, or lot identifiers — all belonging to the same physical event at the weighbridge.
TransPos (Transaction Position)
A TransPos is a single weighed or measured item within a stock transaction — the line-level record of a physical goods movement. While the Trans header describes the overall event (who, when, which contract), each TransPos records the specifics of one particular batch or delivery unit within that event: which article, in what quantity, under what quality classification, and with what lot identifier. A single truck delivery might result in one Trans header and five TransPos records if five different lots or articles were weighed separately at the intake.