Configuration
This section is the starting point for Cotiza CPQ administrators. Use the guides below in recommended order for a new implementation.
Implementation sequence
| Order | Task | Guide |
|---|---|---|
| 1 | Assign admin permissions | Permissions |
| 2 | Copy configuration between orgs (optional) | Sandbox Seed Data |
| 3 | Create System Settings | System Settings |
| 3 | Configure products and pricing | Products and Pricing |
| 4 | Design playbooks | Playbook Design |
| 5 | Build scenarios and rules | Scenarios, Rules Cookbook |
| 6 | Configure approvals | Approvals |
| 7 | Build proposals | View Sections |
| 8 | Set field mappings | Field Mappings |
| 9 | Configure contracts | Contracts Lifecycle |
| 10 | Assign users and power users | Power Users |
For a minimal first Quote, start with the Quick Start.
Configuration layers
System Settings
Org-wide defaults for tables, actions, contract behavior, and proposal options. One record per org implementation.
Playbook
The core configuration container—questions, rules, approvals, and view sections all belong to a Playbook linked to a Price Book.
Product catalog
Products, price books, price book entries, and optional pricing sets/thresholds.
Custom metadata
Deploy field mappings for Quote sync and contract entitlement creation.
Key admin objects
| Object | Role |
|---|---|
| System Settings | Org-wide CPQ defaults |
| Playbook | Operating motion container |
| Playbook Question | User input |
| Playbook Scenario | Conditions |
| Playbook Rule | Automation |
| Playbook Approval | Approval requirements |
| Playbook View Section | Proposal/email layout |
| Pricing Set | Tiered pricing |
See Object Model Overview for the complete reference.
Design decisions
- How Many Playbooks? — single vs. per-price-book strategy
- Rule Evaluation — timing and execution order
- Pricing Rules — pricing automation patterns