The catalog unit price and the price stored on the deal are two different numbers, and reading only one can misstate the weekly total.
Key takeaways
- Check the unit price stored in the product catalog against the price stored on the specific deal before reading the weekly total.
- A product can have a unit price of €45 in euros and $50 in US dollars, according to Pipedrive. These figures are Pipedrive's example of two currency prices, not your firm's rate.
- Custom prices created in the deal window apply only for that deal and are not saved as a price entry in the product’s detail or list view, according to Pipedrive. If you type a custom price while linking a product, that price does not write back to the product catalog.
- When importing line items or updating them through the API, the associated deal amount will not be updated, according to HubSpot. This rule applies to HubSpot's line items; importing them does not change the deal amount.
According to Pipedrive, the price and currency will default to the price you have saved in your product, but you can customize this to another currency and price before linking it to the deal. This distinction matters because the number displayed on the deal record may differ from the standard catalog entry.
The catalog unit price and the price stored on the deal are two different numbers
When you link a product to a deal, the system pulls the standard price from the product library. The price and currency can be customized before the product is linked to the deal. This creates a deal-specific price that may diverge from the catalog unit price.
HubSpot handles this separation by creating a distinct record for each line item. According to HubSpot, when a product is added from the product library to a contract, deal, invoice, payment link, quote, legacy quote, or subscription, it becomes a line item specific to that record, with its own line item record ID. This means the line item on the deal is a separate entity from the product in the library. See Deal and quote line-item rules from 4 publishers.
Because these are separate records, the price on the deal does not automatically update the catalog. If you read only the catalog price, you might miss a custom currency and price set before linking. If you read only the deal price, you might miss the standard rate that applies to other deals using the same product.
To avoid misstating the weekly total, you must verify both numbers. See Product catalog: 7 rules for the weekly forecast. Check the product library for the standard unit price. Then check the specific deal record for the line item price. If these two numbers differ, the deal price is the one that counts for that specific transaction. If they match, the catalog price is the one that counts.
A filled reference table of the price each publisher stores
The table below lists the price rules for Pipedrive and HubSpot based on their published documentation. It distinguishes the catalog price stored in the product library from the price behavior on specific deals.
| Publisher | Catalog Price Rule | Deal Price Behavior | Publisher Example |
|---|---|---|---|
| Pipedrive | A product can have a unit price for each currency. | The deal price is distinct from the catalog unit price. | A product could have a unit price of €45 in euros and $50 in US dollars, according to Pipedrive. |
| HubSpot | A flat price can be stored in the product library for a service. | The line item on a deal is a copy of the product. | If you sell a one-off consultation service for $99, you'd set a flat price of $99 in your product library, according to HubSpot. |
These examples are specific to the cited publishers and do not represent your firm's pricing. The €45 and $50 figures are Pipedrive's example of two currency prices, not your price. The $99 figure is HubSpot's example of a flat service price, not your price.
Use this table to verify which price field your system stores for the catalog and the deal. Check the deal record for the price stored on that specific transaction. Do not assume the two numbers are identical.
Pipedrive's currency price, one price for each currency, and the 1,000 product cap
When you link the product to a deal, Pipedrive uses whichever price matches that deal’s currency, according to Pipedrive. This selection happens at the moment of linking, so the catalog price applied is the one stored for that specific currency code.
Note: You can only add one price entry for each currency, according to Pipedrive. This restriction means a product cannot hold two different values for the same currency. The catalog remains the single source of truth for that currency’s unit price.
Note: You can add up to 1,000 different products to a single deal, according to Pipedrive. This limit applies to the number of distinct product lines, not the total quantity of units. A deal can hold a large variety of items, but the count of unique products is capped at this number.
Note: Each deal can only have products in one type of currency (USD or CAD, not both), according to Pipedrive. This rule prevents a single deal from mixing line items priced in different currencies. The deal’s currency setting dictates which product prices are available for linking. If a product has prices in multiple currencies, only the one matching the deal’s currency will be used.
A custom price typed while linking a product applies only to that deal. It does not write back to the product catalog. The catalog price remains unchanged. This isolation ensures that a one-off negotiation does not alter the standard price for future deals. The deal-specific price is stored on the deal record, separate from the product record.
A price typed on the deal does not write back to the product
When a sales rep links a product to a deal and types a custom price in that window, that number applies only to that specific deal. It is not saved as a price entry in the product’s detail or list view, according to Pipedrive. The catalog unit price remains unchanged. This isolation means the deal-specific price does not overwrite the standard catalog value. You can treat the deal price as a transaction-level figure that exists only for that record.
Because the custom price does not write back to the product, the catalog retains its original unit price. If you read the catalog price later, you will see the standard rate, not the custom amount entered during the deal. This separation is critical when reconciling the weekly total. The deal amount reflects the custom price, while the product catalog reflects the standard rate. Do not assume that editing the price on one deal updates the product for all other deals.
Consider the status of the product itself. A deactivated product can no longer be linked to deals, according to Pipedrive.
Deleting a product follows a similar rule regarding existing deal values. Deleting does not change the value of deals it is already linked to, according to Pipedrive. The dollar amount on the deal persists even after the product record is removed. This means the deal total is not zeroed out or recalculated to a default rate when the source product is deleted. The deal retains its specific value independent of the product's existence in the catalog.
HubSpot's line item is a copy, and an import does not change the deal amount
When a product moves from the library to a specific record, the system creates a distinct entry. According to HubSpot, adding a product from the product library to a contract, deal, invoice, payment link, quote, legacy quote, or subscription makes it a line item specific to that record. This new line item receives its own unique line item record ID. The line item acts as a separate copy tied to the specific transaction.
The pricing structure for these line items can vary based on the product type defined in the library. For instance, a one-off consultation service might have a flat price stored in the product library. According to HubSpot, if you sell a one-off consultation service for $99, you would set a flat price of $99 in your product library. This $99 figure is an example from the publisher’s documentation, not a market rate or a price specific to your firm.
According to HubSpot, a customer buying 6,000 GB pays $0.06/GB for all 6,000 units, resulting in a $360 total. These figures—$0.06 for each GB and the $360 total—are examples from the publisher’s documentation. They demonstrate how unit pricing scales with quantity but do not represent the actual costs or revenue of your specific software deals.
A critical distinction exists when data is added to the system through bulk operations. While adding a product manually creates a line item linked to the deal, importing data behaves differently. According to HubSpot, when importing line items or updating them through the API, the associated deal amount will not be updated. This means that if you import a set of line items for a deal, the total amount field on the deal record itself does not automatically recalculate to match the sum of those imported line items. See Sales data imports: 5 field checks before upload.
Illustrative example of a price changed before linking
A catalog lists 80 for one currency and 60 for a second currency. The deal uses the first currency, so the matching price is 80. Before linking, that price is changed to 60. The weekly total uses 60. The catalog still lists 80, and the typed 60 stays on this deal only. The deal does not add the second currency.
Check both prices on one open deal today
Use this worksheet to record the two price fields on one open deal today, before you read the weekly total. The first column names the field you are checking. The second column is for the value stored on the deal itself. The third column is for the value stored in the product catalog. The final column is for your own notes on any mismatch or context.
Write the catalog unit price in the third column exactly as it appears in your product list. Do not estimate it or convert it to another currency unless your tool stores a separate price for each currency. Write the deal-specific price in the second column exactly as it appears on the deal record. If the deal has a custom price typed into it, that number belongs in the second column, not the third.
Close defines Total Value as the amount the sales rep has listed in the Opportunity on the Lead page, according to Close. This means the deal-side amount is what the rep entered.
Microsoft notes that when you select Close as Won, you enter the Actual Revenue (the final sales amount), the Close Date, and any notes about the deal, according to Microsoft.
Deal price FAQ
Does Pipedrive keep a separate price for each currency?
Yes, Pipedrive allows one price entry for each currency. According to Pipedrive, you can only add one price entry for each currency.
Does a price typed on the deal change the product?
No, custom prices created in the deal window apply only to that specific deal. These custom prices are not saved as a price entry in the product’s detail or list view. According to Pipedrive, any custom prices created in this window will only apply for that deal and not be saved as a price entry in the product’s detail/list view.
How many products can one Pipedrive deal hold?
Pipedrive allows up to 1,000 different products on a single deal. This limit applies to the number of distinct product items that can be added to one deal record. According to Pipedrive, you can add up to 1,000 different products to a single deal.
Does a HubSpot line-item import change the deal amount?
No, importing line items or updating them through the API does not update the associated deal amount. The deal amount remains unchanged even when line items are modified through these methods.
What amount does Close call Total value?
Close defines Total Value as the amount the sales rep has listed in the Opportunity on the Lead page. This value represents the specific figure entered by the sales representative for that opportunity. According to Close, Total Value is the amount the sales rep has listed in the Opportunity on the Lead page.