Skip to main content
Custom fields let you extend the Product object with your own data beyond the built-in fields. Use them to tag products with metadata like cost basis, vertical, deal type, or any dimension your team needs for filtering, reporting, or pricing logic. Custom fields are managed in the Object Explorer, which is the central place to view and extend the data model across all Veles objects.

​
Built-in fields

Every product in Veles comes with these fields out of the box. Built-in fields cannot be edited or removed. These built-in fields cover the core product attributes. Custom fields extend the model for anything specific to your business.

​
Adding custom fields

Navigate to Pricebook > Object Explorer and select Product from the sidebar. You’ll see the built-in fields table and, below it, the Custom Fields section. Click Add Custom Field and configure: Click Save and the field is immediately available on every product in your catalog.

​
Editing and deleting custom fields

Custom fields can be edited or deleted from the Object Explorer. Click Edit to update the name, key, or kind, or Delete to remove the field entirely.
Deleting a custom field removes its value from all products and any Product Filters or Rules that reference it may stop working. Review dependencies before deleting.

​
Pulling fields from your CRM

If you’ve connected a CRM (Salesforce or HubSpot), you can pull custom fields from your CRM into Veles rather than recreating them manually. This is managed through the CRM Proposal Fields section in the Object Explorer sidebar. CRM-sourced fields stay synced with your CRM, so data entered or updated in Salesforce or HubSpot flows into Veles automatically. This is especially useful for fields that are already maintained by your CRM admin (e.g., product line, cost center, revenue type) — pulling them in avoids double data entry and keeps a single source of truth.
Use CRM-sourced fields when the data already exists and is maintained in your CRM. Use manually created custom fields when the data is specific to Veles and doesn’t need to live anywhere else (e.g., a pricing-specific cost basis or a Veles-only product tier).

​
How custom fields are used

Custom fields on products flow through the platform in several ways:

​
Filtering

Custom fields are the product-side target for Product Filters. When you create a filter, you match a source field (from the user’s profile or CRM) against a product field. Custom fields give you the product-side dimensions to match against. For example, if you add a “Vertical” custom field to products and tag each product with its target industry, you can create a filter that matches the rep’s assigned vertical against the product’s vertical — so a Healthcare rep only sees Healthcare products.

​
Reporting

Custom field values carry through to quote lines when a product is added to a quote. This means you can slice deal data by any custom dimension you define. For example, a “Cost per User” number field lets you report on margin by comparing the quoted price against the cost basis.

​
Rules and formulas

Custom fields can be referenced in Pricing Rules, Validation Rules, and Formula Rules. For example, a pricing rule might reference a product’s “Implementation Tier” field to automatically adjust the implementation fee based on the product’s complexity level.

​
Deal Components

Custom field values can flow from the product to the quote line via Deal Components, carrying contextual metadata through the deal lifecycle for downstream reporting and billing.

​
The Object Explorer

The Object Explorer isn’t limited to products. It’s the central place to view and extend the data model across all Veles objects. The sidebar includes:
  • Company — customer account fields
  • CRM Proposal Fields — fields pulled from your CRM for use in proposals
  • Product — product catalog fields (this page)
  • Option — pricing option fields
  • Quote Line — line item fields on quotes
  • User — user profile fields
The same pattern applies to all objects: built-in fields are fixed, and you can add custom fields to extend any object. This gives your team full control over the data model without requiring developer intervention. For more on the Object Explorer, see the Object Manager documentation.

​
What’s next

Product Filters

Use custom fields as the product-side target for catalog visibility filters.

Creating a Product

Full reference for product setup, including assigning custom field values.

Rules & Approvals

Reference custom fields in pricing, validation, and approval rules.

Connect your CRM

Set up CRM sync to pull fields into Veles automatically.