Commodity Items

Commodity Items

Purpose and when to use this record

Configure an item’s commodity-specific units, pricing, grading, or settlement behavior.

At a glance

Before you begin

You need the Brisk permission for the action you are taking on commodity items. If a Create, Edit, or Delete control is absent, do not work around it with another user’s account; ask an administrator to review your role.

Have valid Expense Account, Cogs Account, Revenue Account, and Default Tax records ready first. Those selections determine where this Commodity Item belongs and which later screens can find it.

Create a Commodity Item

Brisk Commodity Items create screen displayed with fictional documentation-demo data.
The Commodity Items create screen in the Brisk documentation demo.

Create a Commodity Item after searching for the person, organization, item, location, or resource under alternate names and identifiers. Merge or correct an existing master record instead of creating a duplicate.

  1. Select the business context first: Purchase Uom, Sales Uom, Expense Account, Cogs Account, Revenue Account, and Default Tax.

  2. Enter the required identifying and operational values: Name, Cost, Sales Price, Expense Account, Cogs Account, and Revenue Account, plus the remaining screen fields.

  3. Review Description, Item Code, and Memo against the source document or approved setup decision.

  4. Save the Commodity Item, then confirm Name, and Item Code on its detail page before continuing.

After saving: Verify this Commodity Item in Commodity Invoices, and Item Rows before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Delete a Commodity Item

Delete this Commodity Item only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

Before confirming, check for related Commodity Invoices, and Item Rows. Brisk may refuse deletion when another record depends on this one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Name, and Item Code. After confirmation, return to the Commodity Items list and make sure only the intended Commodity Item was removed.

Review Commodity Item details

Use the detail page as the shared record of what this Commodity Item currently means. Verify Name, Description, Item Code, and Cost before relying on it for a decision.

Follow Purchase Uom, Sales Uom, Expense Account, Cogs Account, Revenue Account, and Default Tax to determine whether the issue is on this Commodity Item or on one of those linked records.

Next check: Verify this Commodity Item in Commodity Invoices, and Item Rows before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Edit an existing Commodity Item

Edit this Commodity Item to keep the same real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.

  1. Open the detail page. Compare Purchase Uom, Sales Uom, Expense Account, Cogs Account, Revenue Account, and Default Tax with the supporting document or approved request.

  2. Recheck Cost, Sales Price, Expense Account, Cogs Account, and Revenue Account. These values are most likely to change material demand, production status, output quantity, and cost.

  3. Save the change, return to the list, and confirm that the Commodity Item now appears under the expected Name, and Item Code.

After the change: Verify this Commodity Item in Commodity Invoices, and Item Rows before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Find and review commodity items

Brisk Commodity Items list screen displayed with fictional documentation-demo data.
The Commodity Items list screen in the Brisk documentation demo.

Use the Commodity Items list to find the correct record before opening or changing it. Compare Name, and Item Code. Records with similar names or numbers can still belong to different Purchase Uom, Sales Uom, Expense Account, Cogs Account, Revenue Account, and Default Tax.

Open the Commodity Item whose Name, and Item Code match the task. If it is missing, clear the list filters and recheck the identifying information shown on the screen rather than creating a replacement immediately.

Fields and business rules

Brisk stores 12 user-relevant fields for this Commodity Item, including 6 linked-record selections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this full reference.

Field Required What it controls
Name Yes Human-readable name for this commodity item.
Description No Description of this commodity item.
Item Code No Short code used to identify this commodity item.
Cost Yes Represents the current average cost for this product in inventory. For FIFO and LIFO settings, individual transactions will use the actual cost of the inventory that is being used. Under the Average value system, this field will update automatically upon receiving. In Manual and Market settings, this field will never update automatically and will always be used for financial calculations.
Sales Price Yes The sales price value recorded for this commodity item.
Purchase Uom No Unit of measure used when purchasing the item from a vendor.
Sales Uom No Unit of measure used when selling the item to a customer.
Expense Account Yes The expense account associated with this commodity item.
Cogs Account Yes The cogs account associated with this commodity item.
Revenue Account Yes The revenue account associated with this commodity item.
Default Tax Yes The default tax associated with this commodity item.
Memo No The memo recorded for this commodity item.

What happens next

Verify this Commodity Item in Commodity Invoices, and Item Rows before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Common mistakes and troubleshooting


Revision #3
Created 2026-08-10 16:08:59 UTC by Brisk
Updated 2026-08-10 20:28:21 UTC by Brisk