Skip to main content

Add a Custom Column

Create custom data columns to display additional information such as delivery time or internal references.

Updated this week

You can add custom columns to your pricing tables to show extra information, such as delivery times, SKUs, or internal notes.
Custom columns give you flexibility to tailor your tables to each proposal or contract and can also connect to integrations using a unique key.


Step 1: Open your Pricing Table

  1. Click inside your Pricing Table in the Editor.

  2. Hover between two existing columns until the blue + symbol appears.

  3. Click the + to open the Insert column menu.


Step 2: Add a custom column

  1. From the Insert column menu, select Custom columns β†’ Add new column.

  2. A new column will appear in your table labeled Custom column by default.

This column can be placed anywhere in your table to display extra data fields.


Step 3: Name your column

  1. Click the column header to open the Column menu.

  2. Enter a Column name, for example:

    • Delivery time

    • SKU

    • Notes

  3. Use the menu options to adjust placement or visibility:

    • Move left / Move right – Change column position.

    • Hide column – Temporarily remove from view.

Each row under your new column can now contain any text or number you enter manually.


Step 4: Set an integration key (optional)

If you use integrations like HubSpot, Salesforce, or Pipedrive, you can link this column to a CRM field using a key.

  1. Open the Column menu again.

  2. Select Integration settings.

  3. Add a key following these rules:

    • One word, no spaces or punctuation.

    • Starts with a letter.

    • Can include uppercase/lowercase letters, numbers, or underscores (e.g., customColumn1).

This key allows your custom column data to sync correctly with your integrated pricing setup.


Step 5: Review and test

  • Fill in sample data for your custom column.

  • Preview your document to confirm the column displays as expected.

  • If using integrations, send a test document to verify data mapping.


Best practice

  • Use Custom columns for one-off data that’s specific to a deal.

  • Keep column names short and descriptive.

  • For numeric data you want summarized (like hours or service units), use Product properties instead.


Next step

Continue to Variable Quantity and Optional Products to learn how to make your pricing tables interactive for your recipients.

Did this answer your question?