Pricing & Packaging

The price book is the foundation of everything in Veles. It defines what you sell, how it’s priced, and the guardrails that keep your team quoting accurately. Every quote your reps build pulls from this configuration, so getting it right here means cleaner deals downstream. Your price book is managed in the Admin Console under Admin > Price Books and is composed of six core elements. You don’t need to configure all six to get started — products and pricing models are the minimum. The rest add structure, flexibility, and automation as your catalog and deal complexity grow.

---

​

Products

Products are the individual SKUs in your catalog. Each product has a name, a unique SKU, and one or more pricing plans that define how it’s sold. A product on its own is just metadata. The pricing plan is where the real logic lives — it defines the currency, payment type (recurring or one-time), pricing method (flat, tiered, volume, etc.), and the rep permissions that control what salespeople can modify during quoting. Creating a Product →

---

​

Pricing models

The pricing model determines how Veles calculates the price for a product based on the inputs a rep provides (typically quantity). Veles supports five methods: Each pricing model is configured on the product’s pricing plan. You can combine multiple components within a single plan (e.g., a base license fee plus a percentage-based support fee). Pricing Models →

---

​

Categories

Categories group products into logical families, similar to Product Families in Salesforce. They control how products are organized in the quoting interface and how revenue is reported by product line. Common categories include “SaaS Subscriptions”, “Professional Services”, “Hardware”, and “Add-ons”. When a rep opens the product catalog during quoting, categories appear as filters so they can narrow down a large price book quickly. Categories also serve as criteria for Rules. For example, you could create a rule that requires a “Shipping” fee whenever a product from the “Hardware” category is added to a quote. Product Categories →

---

​

Units of Measure

Units of Measure (UOM) define the input that drives pricing — what exactly is being counted when a rep enters a quantity. For most products, this is straightforward: “Per User”, “Per Seat”, or “Per License.” But for consumption-based or usage-based products, you might define units like “Per GB”, “Per 1,000 API Calls”, or “Per Million Transactions.” Veles gives you two options for managing units:

• Shared UOMs apply a single measure across an entire product category (e.g., every product in “SaaS Subscriptions” is measured “Per User”).
• Unique UOMs define a specialized measure for a single product (e.g., a storage product measured “Per GB”).

Units of Measure →

---

​

Data Sheets

Data Sheets are reference tables that the Veles pricing engine can query at quoting time. They work like spreadsheet tabs — rows and columns of data that you upload once and reference across your pricing formulas and rules. Use Data Sheets when your pricing logic depends on external data that doesn’t belong on the product itself. For example:

• A regional pricing matrix that adjusts list price based on the customer’s geography.
• An ERP uplift table that applies different multipliers depending on which system the customer runs (e.g., SAP = 15%, Oracle = 12%, NetSuite = 5%).
• A discount threshold table that maps customer tiers to maximum allowable discounts.

Data Sheets support copy-paste from Excel or Google Sheets, and once saved, they’re immediately available in the formula builder and rules engine. When a value changes (e.g., the SAP uplift moves from 15% to 20%), you update the Data Sheet in one place and every product referencing it picks up the change automatically. Data Sheets →

---

​

Deal Components

Deal Components control the transactional parameters of how a product is sold — the settings that sit alongside the price itself. Billing frequencies define which payment schedules a rep is authorized to offer for a given product. For example, you might allow Monthly, Quarterly, and Annual billing on a SaaS license but restrict a Professional Services fee to a single upfront payment. Contextual data carries custom field values from the product level directly to quote lines. This is useful for downstream reporting — if a product is tagged with a specific region or vertical, that metadata flows through to the quote line so you can slice revenue data by those dimensions later. Deal Components →

---

​

Product Filters & Custom Fields

Filters and custom fields work together to control which products a rep sees during quoting. Custom fields are metadata tags you define on products — things like Region, Segment, or Vertical. They serve two purposes: filtering the catalog for reps and providing reporting dimensions on quote lines. Product filters use those custom fields (along with categories) to scope the catalog view. When a rep assigned to “Enterprise” and “North America” opens the product catalog, they only see products tagged with those values. This keeps large catalogs manageable and prevents reps from quoting products outside their territory. Product Custom Fields → · Product Filters →

---

​

Multi-currency support

Veles supports pricing in multiple currencies. Your base currency is set during account setup (determined by your company’s country), and you can add additional currencies to support international deals. Each product’s pricing plan specifies a currency, and you can create multiple pricing plans on the same product for different currencies. Adding Currencies →

---

​

How these pieces connect

Here’s how the components work together when a rep builds a quote:

1. The rep opens the product catalog, filtered by their assigned categories, regions, and segments (via filters and custom fields).
2. They select a product. The product’s pricing plan determines the pricing model and the available billing frequencies (via deal components).
3. The rep enters a quantity using the product’s unit of measure.
4. The pricing engine calculates the price, referencing data sheets for any lookup-driven logic and applying rules for validation, discounts, and approvals.
5. The calculated line item, with all its metadata, is added to the quote.

The rest of this section covers each component in detail. If you’re setting up from scratch, we recommend working through them roughly in this order: Products → Categories → Pricing Models → Units of Measure → Deal Components → Data Sheets → Rules.

---

​

All pages in this section