# Salesforce Price Book: When a Small Team Needs a Second One

https://salesbond.app/blog/salesforce-price-books-small-team-manager-check/
Published: 2026-10-22 · Updated: 2026-10-22

A price book in Salesforce is a list of products with a price against each one. The standard price book is always there and holds the base price of every product you sell; a custom price book is a second list you create when the same product has a different price for a segment, a currency or a partner. A team of five to fifteen people needs a second price book only when that difference exists. Once a month the manager looks at which price book the lines of the open deals came from and whether the Sales Price a rep entered sits below the list price, and that is the whole management side of it.

This article is the decision, not the dictionary: whether you need the second book at all, who owns it, and what to check so it stays honest.

## What a price book is, in one minute

Products and prices are two separate things in Salesforce, and the price book is the join between them. In the Trailhead exercise you create a product, open its Related tab, click Add Standard Price and enter the amount. If the org has multiple currencies active, you enter a standard price per currency: the same product gets USD 450, EUR 397 and GBP 355 ( [Trailhead: Create and Customize Products](https://trailhead.salesforce.com/content/learn/projects/manage-products-prices-quotes-orders/create-customize-products)). Multi-currency itself is a separate switch, “Activate Multiple Currencies”, on the same page.

We treat that standard price as the floor. A custom book changes the number for one group of customers, and the standard price is what every such change gets measured against. That is also why the [CPQ versus standard quotes article](https://salesbond.app/blog/salesforce-cpq-vs-standard-quotes-small-team/) starts its ladder with the standard book.

Noca, a consultancy that wrote up the Pricebook object in 2025, puts the operational rule in one line: an opportunity must be assigned a price book before products can be added to it ( [noca.ai](https://noca.ai/salesforce-pricebook-object/)). With one book that choice is invisible. With two, it is where things go right or wrong.

## Standard vs custom: what the second price book is for

A custom price book exists for one reason: the same product, a different price, and a rule that says which price applies. Not a different product. Not a one-off discount. A rule.

Trailhead’s version makes two custom books, Nonprofit and Enterprise, and adds a Region picklist to the Price Book object so each book carries where it applies. Products go into a custom book through Price Book Entries and Add Products, “taking care to select the correct currency”, and the custom price comes out lower than the standard one: JPY 250,000 becomes 100,000 in the Enterprise book, GBP 1,000 becomes 701 in the Nonprofit one ( [Trailhead: Create Custom Price Books](https://trailhead.salesforce.com/content/learn/projects/manage-products-prices-quotes-orders/create-custom-price-books)). Notice what that structure says. The nonprofit discount is not something a rep remembers; it is a number sitting in a list the rep selects.

One line on a thing you may have seen in search results: Salesforce Pricing, inside Agentforce Revenue Management, ships with its own predefined standard price book ( [Trailhead: Explore Salesforce Pricing](https://trailhead.salesforce.com/content/learn/modules/price-management-with-revenue-cloud/explore-salesforce-pricing)). That is Revenue Cloud, not the Sales Cloud price book a small team has.

## Three reasons a five-to-fifteen-person team needs one, and three signs it doesn’t

Three reasons hold up at this size.

**A segment with its own price list.** Nonprofits, education, a startup tier: a group of customers that always gets a different number for the same product, and you could write the rule on a card. The Trailhead Nonprofit book is exactly this.

**A second currency.** The standard book can already hold a price per currency, so a second currency alone does not force a custom book; it forces you to maintain the currency entries in the book you have. It becomes a second-book reason when a segment and a currency stack, say European partners.

**A partner or reseller channel.** Partners buy at partner prices, and that is a list, not a discount. This is the the case where two books in a small org is normal, and also the case where a rep selling direct picks the partner book by mistake, which is the first line of the monthly check.

Now the three signs you are about to create a book you do not need.

The first is a discount pretending to be a segment. “Our Q4 book” is not a price list, it is a discount policy. Ask a chatbot when to add price books and promotions and volume discounts will be on the list; at this size we disagree. A discount belongs on the deal line as a Sales Price below list with an approval behind it, and the [approval process for discounts](https://salesbond.app/blog/salesforce-approval-process-discount-deal-gate/) is built for that. A second price book is not.

The second is one currency, one market, one kind of customer. If every customer gets the standard price and the only variation is how hard they negotiated, you have one book. Keep it that way for as long as you can.

The third is “this one client has a special price”. One client is a deal, not a segment. Give the rep the agreed Sales Price on that opportunity and a note on the account. The day the same price goes to the fifth similar client, you have a segment, and then you create the book. Until then every extra book is a list somebody has to keep current, and the one that gets forgotten is the custom one.

## List price vs sales price on the deal line

How a rep picks a book and adds products is covered in our [opportunity products article](https://salesbond.app/blog/salesforce-opportunity-products-amount-manager-check/). Two details matter here. The products come in the currency of the deal, so a JPY opportunity gets the JPY entries ( [Trailhead: Create an Opportunity and Add Products to It](https://trailhead.salesforce.com/content/learn/projects/manage-products-prices-quotes-orders/create-opportunity-add-products)). And each line then carries two prices that look alike and mean different things.

The list price is what came from the price book. The rep did not type it. The Sales Price is what the rep entered for this deal, and ScienceSoft describes it the way we do: the seller’s price on the opportunity, as opposed to the price in the book ( [scnsoft.com](https://www.scnsoft.com/blog/salesforce-price-books)). When the two match, the deal is at list. When Sales Price is lower, the gap is a discount whether anyone called it that or not.

![A deal line with a long List Price bar from the price book and a shorter Sales Price bar typed by the rep; the gap is the discount](https://salesbond.app/wp-content/uploads/2026/10/salesforce-price-books-small-team-manager-check-2.png)

That is the manager’s reading of the line: the book it came from and how far below list it landed. ScienceSoft also mentions restricting reps’ ability to edit the Sales Price. We have not tested how far that goes in a standard org, so take it as a consultant’s suggestion. We would rather leave the field open and look at the gap. A gap with an approval behind it is a decision; a gap without one is the thing to ask about on Monday.

## Who gets to use the price book, and who gets to change it

Access to price books is a sharing question, and Trailhead’s setup is the one we would copy: the organization-wide default for Price Book is View Only for internal users, and each specific book is then shared through its Sharing settings to roles and subordinates with the “Use” access level ( [Trailhead: Control Access to Price Books and Products](https://trailhead.salesforce.com/content/learn/projects/manage-products-prices-quotes-orders/control-access-price-books-products)). Trailhead’s own comment on the View Only default is that after it “no one can actually use them” until a book is shared with Use.

So can a rep use any price book? Only the books shared to their role with Use. If the direct sales role has no Use on the Partner book, the partner-book mistake becomes impossible rather than discouraged.

Changing the prices inside a book is a different job from using it, and the Trailhead project stops at Use, so we will not describe the edit permission here. The team rule needs no permission screen anyway: one person owns price changes, usually the sales manager or the admin, never the rep who is mid-negotiation. Every change to an entry gets a date and a reason wherever you keep decisions, because “why is the Enterprise price lower than standard” will be asked six months from now by somebody who was not in the room.

People do automate the book choice with a flow that reads deal data; a Reddit thread near the top of results for this query does exactly that. With two books and fifteen people, we would not. Sharing with Use does most of the work, and a [record type for new versus renewal deals](https://salesbond.app/blog/salesforce-record-types-new-vs-renewal-opportunities/) does the rest if your books split along that line.

## The monthly check: five things a manager looks at

A short check, once a month, from a report or list view of open opportunities with their products, done before the pipeline review so that review stands on real prices.

1. **Lines from the wrong book.** Group open deals by the price book on the opportunity. A direct deal on the Partner book means a direct customer is about to see partner prices on their quote. Fix teh book before the quote goes out.
2. **Sales Price below list with no approval.** List the product lines where Sales Price is lower than list and compare against the discount approvals of the same period. Anything in the first list and not in the second is a discount somebody gave on their own.
3. **Sales Price above list.** Rare, and almost always a typo or a currency mix-up.
4. **Products missing from the custom book.** A product with a standard price and no entry in the segment’s book means reps selling that segment skip it or improvise.
5. **Books and entries nobody has touched.** A book for a channel you no longer sell through, or a custom price that did not move when the standard one did. Deactivate or update; a stale list is worse than no list, because it looks authoritative.

Items one and two change behaviour; by the third month the list is short. The weekly question of whether a late-stage deal has products at all is a different check, and the [opportunity products article](https://salesbond.app/blog/salesforce-opportunity-products-amount-manager-check/) has that one.

A disclosure, since the monthly list is the kind of thing a tool can keep watching between your checks: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It reads deal data from Salesforce and the other CRMs we support and flags the deals that break the team’s rules, with the reason, so the exception shows up when it happens and not on the first of the month. Whether the second book is justified is still your call. If you want to see what it finds in your pipeline, [check your CRM with SalesBond](https://salesbond.app/).

And if after all this you still have one book, one currency and one kind of customer, good. Keep the standard price book current, ask about every gap between list and Sales Price that has no approval behind it, and let the second book wait until the segment shows up on its own.