Product Properties and Custom Columns both add additional information to pricing tables, but they serve different purposes and live in different systems. Understanding the difference ensures consistent data, accurate summaries, and predictable behavior.
Core difference
The key difference is where the data lives and how it is reused.
Product Properties store structured data on products in the Product Library and are reused across all deals.
Custom Columns store deal-specific data directly in a pricing table and apply only to that document.
Product Properties
Product Properties are predefined fields attached to products.
They are used when information:
Should stay consistent across proposals
Belongs to the product itself
Needs to be reused across multiple deals
May need to be summarized when numeric
Product Properties are managed centrally and automatically populated wherever the product is used.
Custom Columns
Custom Columns are free-form columns added directly to a pricing table.
They are used when information:
Is specific to a single deal
Varies per proposal
Does not belong to the product definition
Should not be reused automatically
Custom Columns exist only in the pricing table where they are created.
Editing behavior
Product Property values are edited on the product in the Product Library.
Custom Column values are edited directly in the pricing table on each row.
This separation ensures product data integrity while allowing deal flexibility.
Summary and aggregation
Number-type Product Properties can be added to pricing summaries and automatically aggregated.
Custom Columns do not support aggregation or summary calculations.
Pricing behavior
Neither Product Properties nor Custom Columns affect pricing calculations.
They do not modify:
Unit prices
Discounts
Taxes
Totals
They are display-only data fields.
Integrations and data consistency
Product Properties provide structured, reusable keys that support consistent integrations.
Custom Columns can use integration keys but require manual configuration per table and do not guarantee consistency across deals.
When to use each
Use Product Properties when the data is part of the product and should stay consistent across deals.
Use Custom Columns when the data is specific to a single proposal or contract.
Common examples
Product Properties:
Plan tier
License type
Included support hours
Usage limits
Custom Columns:
Delivery time
Internal reference
Deal-specific notes
Custom approval labels
Decision guideline
If the data should follow the product everywhere it is used, use a Product Property.
If the data should exist only in one pricing table, use a Custom Column.