Deal and quote line-item rules from 4 publishers

• HubSpot clones the line item: The deal line item record ID will be different from the quote line item record ID, as stated in HubSpot.
• Published quotes freeze: Once a quote is published, its line items are frozen, meaning later deal edits do not alter the quote, according to HubSpot.
• Microsoft auto-associates products: Any products added to an opportunity are automatically associated with quotes generated from the opportunity, according to Microsoft.
• Close defines status, not IDs: Closed/Won indicates the Opportunity has been Closed and a deal has been won, which is a status rule rather than a line-item identifier, as described in Close.
• Check your tool’s help page: Verify whether your specific system assigns separate record IDs to deal and quote line items before making changes to a quoted deal.

When you create a quote from a deal, HubSpot clones the deal's line items into the quote as new, independent line items, according to HubSpot.

Any time there's a conversion between tools (such as deal to quote or invoices automatically created from a contract, payment link, quote, or subscription), the line items are cloned to the new record, according to HubSpot. The quote does not reference the original deal line item by ID; it holds its own copy.

Because the line items are cloned, the quote contains independent records. Editing the deal's line items does not change the quote's line items. The two records maintain separate identities from the moment the quote is created.

The table below lists the specific rule each publisher states regarding how line items or products relate to quotes.

The sequence begins when the system creates a quote from an existing deal. The line item on the quote is a clone of the line item on the deal. Because it is a clone, it receives its own distinct record ID. The deal line item keeps its original ID, while the quote line item holds a new one. This separation happens at the moment the quote is generated.

According to HubSpot, once a quote is published, its line items are frozen. This freeze applies to the specific line items on that published quote. It does not apply to the deal line items, which remain editable in the deal record.

According to HubSpot, later changes to the deal's line items won't affect the quote. If you edit the quantity, price, or product on the deal after the quote is published, the quote retains its frozen values. The deal and the quote diverge at that point. The deal reflects the new edits, while the quote remains unchanged.

You can see this separation in how payment terms are handled. The quote can have specific due dates for its line items. According to HubSpot, for example, line item 1 is due at checkout, and line item 2 is due in 30 days. This example shows that the quote holds its own specific terms.

Discount calculations also stay fixed on the quote. The system applies rounding rules to the quote line items. According to HubSpot, for example, if a line item is $11.90 USD and a 15% discount is applied, the $1.785 discount is rounded to $1.79. This rounding happens on the quote.

A related walkthrough is Line-item rounding rules in 4 sales tools.

The freeze is a hard stop for the quote record. It does not sync with the deal. The deal is a living record that you can edit. The quote is a static snapshot of the line items at the time of publishing. When you edit the deal, you are changing the deal’s line items. You are not changing the quote’s line items. The quote’s line items are frozen and separate.

Suppose a deal line is priced at 50. Creating the quote stores a separate line, also at 50. A 10 percent discount on the quote line comes to 5, so that quote line shows 45. A second quote line stays at 20. After publishing, the deal line is edited from 50 to 30. The quote lines stay at 45 and 20. The deal now shows 30, and the quote does not change.

When you add products to an opportunity in Dynamics 365 Sales, the system handles the link to future quotes automatically. According to Microsoft, any products added to an opportunity are automatically associated with quotes generated from the opportunity. This rule applies specifically to the Dynamics 365 Sales environment described on that page. It does not imply that other vendors use the same automatic association logic for their quote records.

The product selection process offers two distinct paths for adding items. You can add a product that already exists in the Dynamics 365 Sales product catalog or add a Write-in product, according to Microsoft. Both methods feed into the same opportunity record.

Price list selection filters the available catalog items. According to Microsoft, only the products associated with the selected price list are shown in this field. This filtering mechanism ensures that the products you see match the pricing structure you have chosen for the opportunity. If a product is not linked to the active price list, it will not appear in the selection field. This constraint is part of the product-catalog instruction for Dynamics 365 Sales.

For a revenue leader editing a deal, the key takeaway is that the association is automatic upon quote generation. You do not need to manually re-select products when creating a quote from an opportunity. The system carries the products forward based on the initial opportunity setup. However, this automatic association does not mean the quote line items share the same record ID as the opportunity line items.

Pipedrive explains how product data moves into a quote document. This rule is found in the "Products - Knowledge Base" article.

According to Pipedrive, once a product is linked, you can also generate quote documents that pull in its data.

For example, a product could have a unit price of €45 in euros and $50 in US dollars, according to Pipedrive. These figures illustrate how the system handles multi-currency pricing within the product record. This example demonstrates the data structure Pipedrive uses for product pricing, showing that the unit price is a stored attribute on the product record itself.

If a product is deleted, the system retains it for a limited period before permanent removal. After 30 days, the items are permanently deleted and can’t be accessed or restored, according to Pipedrive. This 30-day window applies to deleted product items, providing a short buffer for recovery if a product is removed by mistake. It is important to note that this restore window relates to the product record's lifecycle, not the quote document's validity or expiration.

See Recover deleted sales records: 4 CRM restore rules when a product record is removed.

The status definitions in the Opportunity Pipelines & Statuses | Close Help Center page define how pipeline records are categorized, not how line-item records are duplicated or linked. According to Close, "Closed/Won: Indicating that the Opportunity has been Closed, and a deal has been won." This label describes the final state of the opportunity record itself. Similarly, the page states that "Marking Opportunities with a ‘Lost’ status removes the value from any expected revenue." This action modifies the revenue calculation for the opportunity record.

The structure of these statuses is defined by specific requirements for the pipeline. According to Close, "Each new Status is required to have a name (unique within the given Pipeline) and an Opportunity Status Type (Active, Won, or Lost)." This requirement governs the details of the status label within the pipeline. It does not describe a cloning mechanism for line items. The "Active," "Won," or "Lost" types are classifications for the opportunity's lifecycle stage. They are not identifiers for cloned data objects.

The status type tells you where the opportunity sits in the pipeline. It does not tell you whether the line items on a quote are linked to the deal's line items or are independent copies. The "Won" status indicates the deal is closed. The "Lost" status indicates the deal is lost and its value is removed from expected revenue. Neither status name describes a cloned line item. They are pipeline status definitions.

See Open, won, and lost stage rules in 4 sales tools when a status name is unclear.

Open the quote and the deal side by side. Pick one line that appears on both, and compare the record on each side. If you need the buyer to see a new price, edit the quote line itself before you change the deal.

Why does HubSpot say the deal and quote line-item IDs differ?

The deal line item record ID will be different from the quote line item record ID because the line item is cloned into the quote as a new, independent line item, according to HubSpot. This separation occurs when the line item is cloned into the quote. The distinct identifiers confirm that the quote holds a separate record from the original deal entry.

What freezes when a HubSpot quote is published?

Once a quote is published, its line items are frozen, according to HubSpot. Later changes to the deal's line items won't affect the quote after this state is reached. The frozen status prevents the quote from reflecting subsequent edits made to the source deal record.

Does Microsoft associate opportunity products with the quote?

Any products added to an opportunity are automatically associated with quotes generated from the opportunity, according to Microsoft. This automatic association happens within Dynamics 365 Sales. The system links the products to the generated quotes without requiring manual re-entry of each item.

What does Pipedrive pull into a quote document?

Once a product is linked, you can also generate quote documents that pull in its data, according to Pipedrive. The euro and dollar unit-price figures are a product-page example and not quote record IDs. This data pull allows the quote document to include specific product details from the linked items.

Does Close describe a cloned line-item ID?

Close's page describes opportunity status types and their effects on expected revenue, but it does not describe a cloned line-item record ID, according to Close. The Closed/Won status indicates that the Opportunity has been Closed, and a deal has been won. These status names are pipeline definitions and do not refer to separate line-item identifiers.