Skip to main content

Add a Custom Column

Updated yesterday

Custom columns let you add extra information to pricing tables, such as delivery time, SKUs, or internal references. They are flexible fields designed for deal-specific data that does not affect pricing calculations.


What a custom column is

A custom column is a manually editable column inside a pricing table.

Custom columns:

  • Can contain text or numbers

  • Do not affect pricing calculations or totals

  • Are specific to the pricing table where they are added

  • Can be shown or hidden without removing data

Custom columns are best used for contextual or informational data.


Where custom columns appear

Custom columns can be placed anywhere in a pricing table.

They appear alongside default columns such as Name, Price, Units, and Amount, and apply to all product rows within the table or Pricing Group.


Naming and managing custom columns

Each custom column has a configurable column name.

You can:

  • Rename the column to match the data it contains

  • Reorder the column within the table

  • Hide the column from view without deleting it

Changes to column layout apply to the entire pricing table.


Integration keys for custom columns

Custom columns can optionally be linked to CRM integrations using an integration key.

Integration keys:

  • Allow data to sync with connected CRM systems

  • Must be unique within the pricing table

  • Follow a strict format to ensure correct mapping

Setting an integration key does not change how the column behaves inside the editor.


Custom columns vs Product properties

Custom columns are intended for free-form, deal-specific data.

Product properties should be used when:

  • The data should be reusable across deals

  • Values need to be standardized

  • The column should support summaries or calculations

Choosing the correct column type ensures consistent pricing behavior.


Recipient experience

Recipients can view custom column data but cannot edit it.

Custom columns are always read-only for recipients.


Best practices

Use custom columns for one-off or descriptive information.

Keep column names short and clear.

Avoid using custom columns for numeric data that needs to be totaled or calculated.

Did this answer your question?