How Catalog attributes apply to Inventory in Dutchie POS

Learn about the attributes that inventory items inherit from products in the Catalog in Dutchie POS.

In Dutchie POS, each inventory item (identified by a package ID, lot number, serial number, etc., depending on the market) is assigned to one product in your Catalog. Importantly, it automatically inherits certain attributes from that product.

For example, this Catalog product for Wedding Cake Bulk Flower includes basic product information such as its name, SKU, and category. It’s configured to be sold by weight in grams, and it’s a cannabis product. These attributes will be the same for every package assigned to this product because they are inherited from the Catalog product.

bo_catalog product example.png

By contrast, this is a package of Wedding Cake Bulk Flower that has attributes specific to this package that do not necessarily apply to other packages of Wedding Cake Bulk Flower, such as its package ID, the cultivation batch it originated from, its current remaining quantity, its current Room location, lab results, and other production details. Note how fields like SKU and Category are greyed out because they are inherited from the Catalog and can only be edited at the Catalog level.

bo_inventory item example.png

This article provides an overview of which attributes an inventory item inherits from the Catalog, where and how you can change an attribute, and what system-level configurations can affect these inheritance rules.

Catalog products never inherit any attributes from inventory items, and changes at the inventory level do not affect Catalog products. Inheritance is strictly from the Catalog to inventory items.

catalog product and inventory items diagram.png

Not all of these attributes apply to all users or locations. You can customize many of these attributes to be shown or hidden or make them required fields. Others are market-specific or only appear for locations with certain optional features.

Inventory attributes controlled at the Catalog level

All of the following attributes apply to inventory in some way but are controlled entirely at the Catalog level. Associated inventory items will inherit the Catalog value, and any changes at the Catalog level will also apply at the inventory level. For example, if you change the name of a Catalog product, the names of all associated inventory items will automatically update to the new name.

  • Name
  • SKU
  • Category
  • Master category
  • External category
  • Cannabis product (Yes/No)
  • Brand
  • Size (appears as Product Size in inventory search results table)
  • Alternate name (appears as Alternate Description in inventory search results table)
  • Available on point of sale
  • Taxable
  • Is additive
  • Ingredients
  • Allergens
  • Instructions
  • Days supply

Inventory attributes with defaults controlled at the Catalog level

For these attributes, the Catalog value is applied by default to new inventory during receiving or when you create a new package. These default Catalog values can be overidden on individual inventory items without affecting the Catalog value or other inventory items.

  • Grams/concentration (appears as “Grams per concentration” on inventory detail pages)
  • Vendor
  • Producer (also known as a Manufacturer)
  • Net weight
  • Available for [customer types]

Catalog-only attributes

These attributes either do not apply at the inventory level or have no direct equivalent at the inventory level.

  • Abbreviation
  • NDC
  • GTIN
  • OCS item number
  • Provincial SKU
  • UPC
  • Administration Method
  • Non-cannabis weight
  • Oil volume
  • Allow automatic discounts
  • DoH Approved (WA state only)
  • High CBD (WA state only)
  • Tax categories
  • Serving size
  • Servings per unit
  • Lineage
  • Distillation
  • Flavor
  • Dosage
  • Test product
  • Is finished
  • THC content (note that this value does appear in the inventory grid as “Calculated THC (mg)”)
  • CBD content
  • Low inventory threshold
  • Use SKU as package ID
  • Default pricing tier
  • Max quantity per transaction
  • External ID
  • MN medicine ID
  • Sales account
  • Expiration days
    • The value in this field affects the Expiration date field at the inventory level and reflects the number of days from receiving at which inventory is considered expired.
    • For example, if a product’s Expiration days = 100, inventory assigned to that product and received on July 1 will have a calculated Expiration date of October 9.
  • Regulatory category
  • Unit THC Content Dose
  • Unit CBD Content Dose

Attributes with unique or configuration-dependent behavior

Price

Whether inventory items inherit price information from the Catalog depends on whether your location uses product-level pricing or inventory-level pricing. This configuration can only be changed by Dutchie Support and is usually set during implementation.

  • If you use product-level pricing, inventory inherits the Catalog-level Price.
    • Price is displayed in inventory details and search results but can only be changed at the Catalog level.
    • All inventory items of the same product have the same price.
    • If you also specify a location-specific price at the Catalog level, packages associated with that product will inherit the location-specific price for that location only.
  • If you use inventory-level pricing, the Catalog-level Price is the default applied to new inventory during receiving, but you can override the inventory-level Price at any time without affecting the Catalog value or other inventory items.

Cost

Inventory items typically inherit their Cost from the Catalog, though this is not always the case.

When receiving inventory, the Cost per unit field is pre-populated with the Catalog-level cost value, though users can change this as needed for individual packages. Changes to a package's cost will never affect the Catalog-level cost.

When creating or converting packages or when creating recipe batches, you have three options for entering the Cost of the new package(s)/output(s):

bo_inventory_create packages_cost.png

  • If you select Catalog, the new package(s)/output(s) use the Catalog-level cost.
  • If you select Calculated, the cost of the new package(s)/output(s) is calculated based on the cost of the source package(s)/input(s).
  • If you select Other, you can manually enter a cost for the new package(s)/output(s).

The default selection for Cost when creating or converting packages or creating recipe batches depends on your Which unit cost setting under Settings > Location.

Flower equivalent

Flower equivalency is typically set at the inventory level because it may vary between packages and batches and is used to enforce allotments and purchase limits.

However, a Flower equivalent field also exists at the Catalog level, and when new packages are received or created, the inventory-level Flower equivalency field will use the Catalog value by default unless you override it by entering a different value.

Depending on your configuration and local requirements, you may have separate Med and Rec flower equivalency fields at both the Catalog and Inventory level. This is controlled by the Use Both Med and Rec Flower Equiv option under Settings > Location.

You can define standard calculations for flower equivalency based on purchase limit category. This allows Dutchie POS to calculate and fill in flower equivalency values for you automatically. 

Type and Default unit

Type (Quantity, Weight, or Volume) and Default unit (Gram, Ounce, Milliliter, etc.) are Catalog-only attributes, but they do affect the units of measure for the Available, Allocated quantity, and Quantity (including allocated) values shown in the Inventory grid.

If Type or Default unit is changed at the Catalog level, the change is not retroactively applied to the existing inventory, which retains its original unit of measure. The change will only be applied to new inventory.

Tags

New inventory inherits tags from the assigned Catalog product only upon receiving. If you add a tag to a Catalog product, its existing inventory does not inherit that tag. If you create new packages from existing inventory, new packages do not inherit the tags from the source package or the Catalog product.

Strain

Strain exists at both the Catalog and Inventory levels. However, the inventory-level Strain is inherited from the associated Batch, not from the Catalog.

Actions that trigger inheritance

  • When you Receive inventory, the new inventory inherits data from the assigned Catalog product.
  • When you use the Convert or Create package actions or when you receive inventory, any new inventory items will inherit data from the associated Catalog product.
  • However, when you Sublot or Create a lab sample, the new inventory item inherits data from the source package.

Learn more

Was this article helpful?