Skip to main content
Before your team can build a quote, you need at least one product in your catalog. Products are the building blocks of every deal in Veles — they contain the SKU, pricing logic, and configuration that drive the quoting engine. There are two ways to populate your catalog: importing from Stripe (fastest) or creating products manually (most control).

​
Option A: Import from Stripe

If you’ve already connected your Stripe account, you can pull in your existing price book and skip most of the manual setup.
  1. Navigate to Admin > Price Books > Products.
  2. Click Import from Stripe.
  3. Select the products you want to sync. Veles imports the SKU, name, and pricing structure for each selected product.
  4. Review the imported products and make any adjustments (categories, custom fields, rep permissions).
Imported products are immediately available in the catalog. You can edit their pricing plans, add categories, or adjust permissions after import.
Stripe import requires an active Stripe connection. See Account Setup if you haven’t connected Stripe yet.

​
Option B: Create a product manually

​
Step 1: Product details

Navigate to Admin > Price Books > Products and click the + New Product button.
FieldRequiredDescription
NameYesThe display name as it appears in the catalog and on quotes.
SKUYesA unique identifier for the product. Must be unique across your entire Veles environment. Used for reporting, CRM sync, and ERP integration.
CategoryNoGroups the product into a logical family (e.g., “Software”, “Professional Services”, “Hardware”). Categories control how products are organized in the quoting interface.
DescriptionNoInternal notes or customer-facing details about the product.
Custom fieldsNoOrganizational fields like Region, Segment, or Vertical. Used as filters during quoting so reps only see relevant products.
StatusToggleSet to Active to make the product available to reps. Inactive products are hidden from the catalog.
Click Save to create the product. You’ll be redirected to the Product Details page.
Set up categories first. If you’re building a catalog with many products, create your Product Categories before creating products so you can assign them during setup rather than going back to edit each one.

​
Step 2: Add a pricing plan

From the Product Details page, click Add Pricing Plan. A pricing plan defines how the product is sold and how the price is calculated. Currency: Select the currency for this plan. If you sell in multiple currencies, you can add additional pricing plans later. See Adding Currencies. Payment type: Choose the billing structure:
  • Recurring — for products billed on a repeating schedule (e.g., annual license, monthly SaaS seat).
  • One-time — for products billed once (e.g., implementation fee, onboarding service).
Pricing floor (optional): Set a minimum price. This can be a fixed dollar amount or a formula. Useful for preventing reps from discounting below cost.

​
Step 3: Configure components and pricing method

A pricing plan is built from one or more components. Most products need only one component (e.g., “Base License”), but complex products can have multiple components that are summed together. Name your component, then select a pricing method:
A single fixed price regardless of quantity. The quantity defaults to 1 — the product is either included or not.Best for: Implementation fees, one-time services, fixed-price add-ons.Example: A “Standard Implementation” fee of $5,000. The price doesn’t change based on other deal factors.
A single rate applied to the entire quantity, based on which tier that quantity falls into. All units are priced at the same rate.Best for: Per-seat licensing, ACV-based pricing.Example:
  • Tier 1 (0-5 users): $50/user
  • Tier 2 (6-10 users): $40/user
If a rep enters a quantity of 8, the total is **320∗∗(320** (40 x 8). All 8 units are priced at the Tier 2 rate.
Units are priced progressively based on the tier they fall into, like tax brackets. Each tier’s units are priced at that tier’s rate, and the results are summed.Best for: Usage-based billing, consumption models.Example:
  • Tier 1 (0-5 users): $50/user
  • Tier 2 (6-10 users): $40/user
If a rep enters a quantity of 8, the first 5 units cost 250(5x250 (5 x 50), the remaining 3 units cost 120(3x120 (3 x 40). Total = $370.
A fixed dollar amount for anything within a tier’s range, regardless of the exact quantity. No per-unit multiplication.Best for: Platform packages, bucket pricing (e.g., “0-50 employees” plan).Example:
  • Tier 1 (0-5 units): $500 flat
  • Tier 2 (6-10 units): $800 flat
A quantity of 4 costs 500∗∗.Aquantityof∗∗9∗∗costs∗∗500**. A quantity of **9** costs **800.
Price is calculated as a percentage of the value of other products in the same pricing option.Best for: Support plans, success fees, platform fees tied to deal value.Example: A 10% support fee on a 100,000dealadds100,000 deal adds 10,000.You can set tiered percentages (e.g., 10% for deals under 100k,7100k, 7% over 100k), and optionally exclude one-time fees to calculate the percentage against recurring revenue (ARR) only.
For a detailed comparison of all pricing methods with additional examples, see Pricing Models.

​
Lookup drivers

The lookup driver defines what input drives the price calculation.
  • Quantity (default): The number of units sold. This is what you’ll use for most per-seat or per-unit products.
  • Custom drivers: Used for transactional or consumption-based pricing. For example, “Transaction Value” or “Annualized Construction Volume” might define the price per unit without being the quantity of SKUs.

​
Input scale

Input scale simplifies data entry for reps working with large numbers. Set the scale to Singles, Hundreds, Thousands, or Millions so a rep can enter 42.5 instead of typing 42,500,000.

​
Step 4: Define pricing tiers

For any lookup-based pricing method (Volume, Graduated, or Stair-step), you’ll define tiers using the boundary table. Veles uses upper boundaries to set ranges.
  1. Enter the upper boundary for each tier (e.g., Tier 1 upper boundary = 5, Tier 2 upper boundary = 10).
  2. Set the price for each tier.
  3. Veles displays a live calculation preview as you build the table, so you can verify the math in real time.
Start with 2-3 tiers and add more as needed. You can always edit the tier structure after the product is live without affecting existing quotes.

​
Step 5: Set rep permissions

At the bottom of the pricing plan, toggle the permissions that control what sales reps can modify during quoting:
PermissionWhat it controls
List Price EditableAllows reps to manually override the calculated list price. Use only for products without fixed pricing (legacy SKUs, unpriced items). Manual edits override automatic calculations — to recalculate after a quantity change, the rep must clear the List Price field.
Disable DiscountingWhen ON, reps cannot apply discretionary discounts. Only automated rules or promotions will apply.
Name EditableAllows reps to rename the product on customer-facing documents. The underlying SKU and system name remain unchanged for reporting. Note: when synced to a CRM or Stripe, the product name reverts to the original system name.
Quantity EditableAllows the rep to change the unit count, even if a default quantity was set.
TransactionalMarks the SKU as billed in arrears (e.g., a percentage of transaction volume). Transactional SKUs are excluded from Total ARR calculations and displayed as a rate to the buyer.
Products using custom pricing drivers (transaction value, construction volume, credit consumption) should typically have their quantity fixed at 1. The driver determines the price; the quantity represents the SKU count on the order.

​
Organizing your catalog

As your product catalog grows, use these tools to keep it navigable: Categories group products into logical families (e.g., “SaaS Subscriptions”, “Professional Services”, “Hardware”). Categories appear as filters in the quoting interface, so reps can quickly narrow down a large catalog. Create categories at Admin > Price Books > Categories before adding products. See Product Categories. Custom fields like Region, Segment, or Vertical let you tag products with metadata that drives filtering and reporting. When a rep builds a quote, custom field values on the product can carry over to the quote line for granular downstream reporting. Filters combine categories and custom fields to control which products a specific rep sees based on their assigned segment, region, or vertical. See Product Filters.

​
What’s next

Pricing Models

Deep dive into each pricing method with detailed examples and comparison tables.

Deal Components

Configure billing frequencies and contextual data for your products.

Data Sheets

Upload custom datasets to drive dynamic pricing (e.g., price-by-zip-code matrices).

Units of Measure

Define the inputs that drive pricing: per-user, per-API-call, or custom units.