> ## Documentation Index > Fetch the complete documentation index at: https://docs.qwoty.io/llms.txt > Use this file to discover all available pages before exploring further. # Key CPQ concepts > Learn the core CPQ concepts you'll meet throughout Qwoty — from catalogs to quotes to contracts. CPQ stands for Configure, Price, Quote. It describes the process of assembling the right products, applying the right pricing, and generating a proposal — accurately and quickly. In Qwoty, CPQ is the foundation of a longer flow that continues through e-signature, order generation, and buyer collaboration. Understanding the core concepts makes every part of the platform easier to use. ## The quote-to-revenue flow ```mermaid theme={null} graph LR A[Template] --> B[Quote] B --> C[Approval] C --> D[Publish] D --> E[Dealroom] E --> F[Signature] F --> G[Order] G --> H[Contract] ``` A Template defines the starting configuration for a Quote. The Quote goes through approval if required, then gets published to a Dealroom where the buyer reviews and signs. Signature triggers automatic Order generation. The Order is grouped under a Contract alongside any related quotes. ## Core concepts ### Catalog A Catalog is a group of products available to sell. You create separate catalogs to reflect different markets, regions, or business units — for example, "France Catalog" or "Enterprise Software." Catalogs define *what* your reps can sell. Pricing is handled separately in a Pricebook. ### Product and variant A Product is an item, service, or subscription in your catalog. Variants let you define different configurations of the same product — such as different sizes, durations, or tiers — without creating separate products for each. ### Bundle A Bundle is a pack of products sold together as a single line item. Bundles simplify quoting for common product combinations and can carry bundle-level pricing or discounts. ### Pricebook A Pricebook is a price list applied to a catalog. You can maintain multiple pricebooks for the same catalog — for example, one per customer segment, region, or channel. A Quote uses exactly one Pricebook. Products not listed in that Pricebook won't appear when building the Quote. ### Template A Template is a funnel configuration that combines a Catalog, a Pricebook, payment terms, and a Contract Model into a reusable starting point. Reps select a Template when creating a Quote — it sets the rules for the entire deal. Templates are the primary tool for standardizing your sales process across products, regions, or customer types. ### Quote A Quote is a priced proposal sent to a customer. It lists selected products and variants, applies the Pricebook, and carries the payment terms and contract model from its Template. Quotes move through a defined set of statuses from `Draft` to `Accepted`. See [Quote statuses](#quote-statuses) below. ### Approval workflow An Approval Workflow is a set of rules that determine when a Quote needs manager validation before it can be published. Rules can trigger on discount level, deal size, product category, or custom conditions. Approval workflows protect margin and ensure commercial policy is enforced consistently. ### Dealroom The Dealroom is the client-facing space where buyers view the quote, ask questions, and sign. It replaces static PDF attachments with a live, interactive environment. Every comment, view, and signature is recorded and visible to your team in real time. ### Order An Order is generated automatically when a Quote reaches `Accepted` status. It captures the final products, quantities, pricing, and payment terms — and becomes the source of truth for fulfillment and revenue recognition. ### Sales Agreement A Sales Agreement is a framework contract that governs an ongoing commercial relationship. It captures volume commitments, negotiated pricing, and special terms that apply across multiple quotes and orders over time. ### Contract A Contract is a container that groups related Quotes and Orders for the same deal. It provides a single reference for the full engagement — including amendments, renewals, and multi-phase projects. The Contract Model selected in the Template populates the legal document with live quote data using variables like `{{customer.name}}` and `{{quote.total}}`. ## Quote statuses | Status | What it means | | ------------------- | -------------------------------------------------------------------- | | `Draft` | The Quote is being built by the Sales Rep | | `Pending Approval` | The Quote has been submitted and is waiting for manager review | | `Changes Requested` | The approver has sent the Quote back for revision | | `Approved` | The manager has authorized the Quote for delivery | | `Published` | The Quote is live in the Dealroom, visible to the buyer | | `Pending Signature` | The buyer has reviewed and is in the process of signing | | `Accepted` | The Quote is signed and closed — an Order is generated automatically | | `Expired` | The Quote passed its expiration date without being accepted | | `Lost` | The deal did not close | | `Canceled` | The Quote was withdrawn before acceptance | ## Dive deeper Statuses, approval flows, and quote management in detail Products, variants, bundles, and pricebooks Configure your sales funnels The buyer experience from publish to signature