--- schema_version: "1" id: 7f49b519b09087605cedeeaf38bac97d53a2ebc4d8d3d2e10dc2f93c7b98ce11 title: Managing Quote and Order Templates in Industries CPQ collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_cpq_managing_quote_and_order_templates.md canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_cpq_managing_quote_and_order_templates.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 7c29d4f1e2b856cebb379edda46770f8b581379f75c38e358c62a867dc23f6b5 description: Sales Config Templates are reusable, pre-configured Quote or Order models designed to standardize complex product bundles and accelerate the quoting process. By capturing complete configurations—including line items and pricing—they eliminate repetitive manual work while ensuring quality through built-in approval governance and automation. products: - Communications - Media - Energy and Utilities release: "264" --- # Managing Quote and Order Templates in Industries CPQ Sales Config Templates are reusable, pre-configured Quote or Order models designed to standardize complex product bundles and accelerate the quoting process. By capturing complete configurations—including line items and pricing—they eliminate repetitive manual work while ensuring quality through built-in approval governance and automation. ### Required Editions
Available in: Classic and Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions for CME managed package
## Benefits - Standardize common product bundles into approved, reusable configurations. - Accelerate quoting by applying preconfigured templates instead of configuring from scratch. - Organize templates that use tags for easy discovery and categorization. - Automate template operations through Salesforce Flow and Agentforce that use Invocable Actions. - Govern template quality with a built-in approval workflow (Draft, In Review, Approved, Obsolete). ## Template Status Values Find the description of the picklist value for the template: Draft Create a template in Draft status. You can edit or delete it freely. In Review When you submit the template when waiting for approval. The status transitions are managed through Salesforce Approval Processes or custom logic. Approved The template is ready to use. Approved templates are protected from accidental deletion (requires forceDelete=true). Obsolete Retired templates that are kept for reference but no longer be apply to new carts. ## Template Operations See the Template details listed in the [Standard Cart API Usage Examples](https://developer.salesforce.com/docs/industries/cme/guide/stdcart-api-examples.html). Save Template Creates a Sales Config Template by cloning an existing Quote or Order. For more information, see [Save Template](https://developer.salesforce.com/docs/industries/cme/guide/std_comms-save-template.html). Get Template Retrieves a single Sales Config Template by ID, including its metadata, associated tags, and cart totals. For more information, see [Get Template](https://developer.salesforce.com/docs/industries/cme/guide/std_comms-get-template.html). Search Templates Searches, filters, sorts, and paginates Sales Config Templates. Supports field-level filtering (AND logic), free-text search (OR logic), tag-based filtering, and multi-field sorting. For more information, see [Search Template](https://developer.salesforce.com/docs/industries/cme/guide/std_comms-search-template.html). Apply Template Applies an existing Sales Config Template to a target Quote or Order by cloning the template cart's line items. For more information, see [Apply Template](https://developer.salesforce.com/docs/industries/cme/guide/std_comms-apply-template.html). Delete Template Deletes a Sales Config Template with optional deletion of the underlying template Quote or Order. For more information, see [Delete Template](https://developer.salesforce.com/docs/industries/cme/guide/std_comms-delete-template.html). ## Functional Constraints & Requirements for Template APIs Find the operational boundaries and strict requirements for managing Quote and Order template with the API. | Limitations | Requirements and Behaviour | | --- | --- | | Account-Based Context Rules Not Supported | Template APIs use a global account, making account-based Context Rules unsupported. As a result, account-specific rules from the source cart don't pass over or function. | | Cart Type Must Match | Quote templates apply only to Quotes, while Order templates apply only to Orders. Cross-type applications, such as applying a Quote template to an Order, are unsupported. | | Discounts Not Supported | Carts containing Order, Account, or Contract discounts can't be saved as templates and will trigger a TEMPLATE\_DISCOUNT\_NOT\_SUPPORTED error. All discounts to be removed from the cart before the save operation can proceed. | | No Qualification or Eligibility Validation | Product validation checks—including eligibility, qualification, and effectivity—aren't performed during template operations. Users to manually verify product eligibility after applying a template, as original constraints no longer be valid. | | No Status Change API | Status updates for templates lack a dedicated API. Transitions to be performed manually via the Salesforce Object Viewer or standard record update mechanisms. | | No Tag Linking API | Template-tag linking lacks a dedicated API. These associations to be created manually through the Salesforce Object Viewer or standard Salesforce data tools. | | No Tag Management API | No dedicated API exists for managing template tag records. They are created, updated, or deleted manually via the Salesforce Object Viewer or standard data tools. | | No Template Management via Custom Permissions | Template management is restricted to the Admin Profile, while all other profiles are limited to read-only access. | | Price List Must Match | Source and target carts should share the same Price List; mismatches will trigger an error. | | Price List Required on Target Cart | The target cart should have an assigned Price List before a template can be applied. | | Source Order Status Restriction | Source Orders should be in a non-activated state (for example Draft) to be saved as templates. | | Target Cart Status Restriction | Target Quotes or Orders are in "Draft" status; applying templates to non-draft or activated records is unsupported. | ## Technical Constraints & Requirements for Template APIs Here are the technical requirements and boundaries for managing Quote and Order templates via API. | Limitations | Requirement and Behaviour | | --- | --- | | Approved Template Protection | An Approved templates can't be deleted without forceDelete=true. | | Async Mode | Async calls return a jobId for custom tracking, as the API does not provide built-in polling. | | One Cart Per Template | Templates link exclusively to either a Quote or an Order; dual-referencing is unsupported. | | Pagination Maximum | Standard Salesforce SOQL offset limits apply (maximum offset of 2,000 records). | | Search Field Types | Non-filterable fields, such as Long Text Areas, are unsupported in filter criteria and will be skipped with an API warning. | | Supported Cart Types | Template operations are restricted exclusively to Quote and Order objects for both source and target carts. | - **[Custom Hooks for Template Operation](https://help.salesforce.com/s/articleView?id=ind.comms_cpq_custom_hooks_for_template_operation.htm&release=264.0.0&type=5)** All five Sales Config Template APIs support Pre and Post invoke hooks via the standard CpqAppHandlerHook framework. This allows you to inject custom Apex logic before and after each template operation without any platform code changes. - **[Sales Configuration Template Access and Security](https://help.salesforce.com/s/articleView?id=ind.comms_cpq_sales_configuration_template_access_and_security.htm&release=264.0.0&type=5)** Sales Configuration Templates use a permission-set-based security model to control who can create, manage, apply, and delete templates. Three pre-defined permission sets map to distinct user personas, each with a specific level of access enforced at both the record and API levels. Trigger-based guards protect template deletion and that require all deletions to go through the official delete API.