Product Properties vs Custom Columns | GetAccept Help Center
Product Properties vs Custom Columns
Learn when to use Product Properties or Custom Columns to customize your pricing tables.
June 1, 2026
Product Properties and Custom Columns
Product Properties and Custom Columns both add information to pricing tables, but they store data differently and serve different purposes. Understanding when to use each ensures your pricing tables stay organized, data stays consistent, and your pricing behavior remains predictable.
What are Product Properties?
Product Properties are predefined fields attached to products in your Product Library. They are part of the product itself and travel with the product wherever it is used.
Standard Product Properties include:
- Name
- Price
- Description
- SKU
- Product image
You can also create custom Product Properties to store additional structured data on every product, such as license type, plan tier, included support hours, or usage limits. When you update a Product Property in the Product Library, all pricing tables using that product automatically reflect the change.
What are Custom Columns?
Custom Columns are additional columns added directly to a pricing table that aren't tied to the Product Library. They exist only in that single pricing table and contain deal-specific or table-specific information.
Custom Columns are useful for information such as:
- Delivery timeframe for this specific deal
- Internal reference codes or project numbers
- Deal-specific notes or terms
- Custom approval labels
When you add or edit a Custom Column in a pricing table, the change affects only that table. It does not update other pricing tables or the Product Library.
Key Differences at a Glance
| Aspect | Product Properties | Custom Columns |
| Data Location | Stored in Product Library; reused across deals | Stored only in this pricing table |
| Scope | Global, applies to the product everywhere | Local, applies only to this table |
| Updates | Changes in Product Library auto-sync to all tables | Changes affect only this single table |
| Consistency | Guaranteed consistency across all deals | No automatic consistency |
| CRM Integration | Integrations Key for reliable CRM sync | Can use Integrations Key but requires manual setup per table |
| Aggregation | Numeric properties can be summarized | No aggregation support |
When to Use Product Properties
Use Product Properties when the data is part of the product definition and should remain consistent everywhere that product is used.
Product Property use cases:
- Data that belongs to the product itself (e.g., license type, plan tier, included features)
- Information that should be the same across all customer proposals
- Values you want to maintain centrally in the Product Library
- Numeric data you want to aggregate or summarize in pricing table summaries
When to Use Custom Columns
Use Custom Columns when the information is specific to a single deal, proposal, or pricing table and does not apply consistently to the product across all uses.
Custom Column use cases:
- Deal-specific terms or conditions
- Values that vary from one proposal to another
- Information that does not belong in the Product Library
- Data that should not auto-update when the product changes
Accessing and Managing Column Settings
When you edit a pricing table in the Editor, you can access column settings by clicking the breadcrumb for any column. The Column Settings panel provides:
- Column Name: The label for the column as it appears in the table
- Move Column: Reorder columns by dragging them to a new position
- Integrations Key: A unique identifier used when syncing data with your CRM. Click the copy button to copy the key for use in integrations
- Hide Column: Remove a column from display without deleting it
- Add Column: Create a new Custom Column directly in this pricing table
Understanding the Integrations Key
The Integrations Key is a unique identifier that connects a column to your CRM system. When you set up data sync with Salesforce, HubSpot, or another platform, the Integrations Key tells the system which column to populate with which CRM field.
Product Properties come with predefined Integrations Keys that are consistent across all pricing tables. Custom Columns require you to configure an Integrations Key manually for each table where you want CRM sync to work. This makes Product Properties the more reliable choice if CRM integration is important to your workflow.
Impact on Pricing Calculations
Neither Product Properties nor Custom Columns affect how pricing is calculated. They are display-only data fields and do not modify:
- Unit prices
- Quantity calculations
- Discounts
- Taxes
- Line totals or table totals
Use these columns purely to provide additional context or information to buyers viewing your pricing table.
Decision Framework
Ask yourself these questions to decide which to use:
Should this data follow the product everywhere it is used? If yes → use a Product Property. If no → use a Custom Column.
Do I want this value to stay consistent across all deals? If yes → use a Product Property. If no → use a Custom Column.
Should my CRM automatically sync this data? If yes → use a Product Property (more reliable for integrations). If no → use a Custom Column.
Do I need to summarize this data in a pricing summary? If yes → use a numeric Product Property. If no → either option works, but Product Properties are better for consistency.