Creating Custom Data Items for a Specific Template or Document

Template- or document-specific custom data items are user-defined fields that exist only within a single QuoteCloud template or document. They let you add unique, one-off fields (for example a project-specific option or client-only term) without adding those fields to your global dataset or exposing them to other templates in your sales quoting software.

Use a template-specific custom data item when the field is relevant only to one proposal or narrowly scoped document — for example, a one-off service option, special pricing for a single client, or a project-specific clause. This keeps the global interface uncluttered and prevents niche fields from showing up across other templates in your quote software or proposal software.

The page explains the concept but does not list exact UI clicks. In QuoteCloud you typically create template- or document-scoped items from the template or document editor when adding or configuring fields. For precise step-by-step instructions (menu names, buttons, and configuration options), consult the guides on global custom data items and contact data items or reach out to QuoteCloud support.

Yes. Once created, template-specific custom data items behave like system data items (such as customer name or proposal ID). They can be embedded in text blocks and will be dynamically merged into generated documents. They can also be used inside price tables where QuoteCloud supports data-item merging, helping you build interactive sales proposals and pricing tables within your proposal software.

No — by design these custom data items are scoped only to the template or document where they were created. They do not modify global settings or appear on other templates, so your global data set and other documents remain unchanged.

The digest does not provide an automatic conversion workflow. In many systems you would recreate the field in the global data area if you need it available across templates, or recreate it as template-scoped if you need it limited. For the definitive method in QuoteCloud — and to avoid accidental data loss — consult the related guides or contact QuoteCloud support for instructions.

Template-specific items are scoped to a single template/document and are primarily used for document generation and merging. Integration behavior can vary — some integrations rely on global or contact-level fields. If you plan to sync fields with accounting or CRM systems (for example QuickBooks Online), check the integration documentation or contact QuoteCloud support to confirm which data items are synced.

Keep these best practices in mind: use template-specific fields only for one-off or narrowly scoped data to avoid cluttering your global dataset; give fields clear, descriptive names; test merged fields in a draft document before sending to clients; document any template-specific fields your team needs to use; and consult integration docs if you expect those fields to flow into external systems. These practices help you maintain clean quote software and proposal software workflows while leveraging the flexibility of custom data items.