Products reference - Zenskar Documentation

This page is a field-level lookup. For task steps, see how to add a product and how to manage products. For the reasoning behind these fields, see products: concepts and features: concepts.

Product fields

Field	Required	Description
Product Name	Yes	Name of the product, shown on invoices and reports. Labeled Product Bundle Name if the product is a bundle.
Description	No	Internal description of the product.
SKU	No	Stock keeping unit, useful for syncing with an ERP or inventory system.
Tax Code	No	Determines how the product is taxed. Not shown for bundles, since tax resolves at the level of each product inside a bundle.
Custom attributes	Depends	Shown only if your organization has defined custom attributes for the Products module.
Type	Yes	Standalone product, or bundle (a group of other products).
Status	Yes	Active or inactive. Defaults to active.

Type

Type	Description
Standalone	A product priced and sold on its own.
Bundle	A product that groups several other products together under one catalog entry.

Pricing models

A product’s pricing is configured separately from the product itself, through one or more pricing models attached to it.

Pricing model	What it does
Per-unit	A fixed rate multiplied by quantity.
Flat fee	A fixed price agreed upfront, independent of quantity.
Percent	A percentage of a transaction value or of usage, rather than a fixed per-unit rate.
Tiered	Usage is split across tiers, and each tier is billed at its own rate.
Tiered pricing with flat fee	A flat base fee plus usage billed per tier, each tier at its own rate.
Volume	The total quantity determines a single rate applied to every unit.
Volume pricing with flat fee	A flat fee plus usage billed across volume tiers, with each tier carrying its own flat fee.
Step	Usage is divided into tiers, and each tier is billed at its own flat fee rather than a per-unit rate.
Package	Sold as a fixed-size bundle at a fixed price.
Matrix	The rate depends on two dimensions, for example usage and region.
Two-dimensional tiered	Tiers are set across two independent factors at once, rather than one.
Custom tiered	Mixes tiered, package, and per-unit rates within the same tier structure.

Feature types

These are the feature types available at the product level. Payment terms and service fees aren’t among them, those are contract-level features instead. See contracts reference: feature types for that set.

Feature	What it does
Discount	Reduces the charge. Fixed, percent, or quantity-based.
Tax	Applies a tax rate, either entered manually or resolved through Avalara.
Free units	Grants a number of units the customer isn’t charged for.
Commitment	Sets a minimum spend the customer is held to.
Grants	Issues an entitlement, a pool of usage triggered by an event you choose.
Consumptions	Defines how usage draws down a grant.

How product changes affect contracts

Change	Effect on contracts already using the product
Editing name, description, SKU, tax code, or custom attributes	Not blocked. Existing contracts are flagged as needing a refresh rather than updated automatically.
Setting status to inactive	Not blocked. Existing contracts keep working.
Deleting the product	Blocked while any contract, plan, or bundle still references it.
Deleting a pricing model	Blocked while any contract still references that specific pricing model.