Products, Price Books and Price Book Entries

Why This Topic Matters

Products, Price Books and Price Book Entries form the backbone of how Salesforce represents what a company sells and how much it charges. Every Opportunity Product, Quote Line Item and Order Product ultimately depends on this data model. Because the Advanced Administrator exam tests your ability to configure Sales Cloud for real-world selling scenarios, you will almost certainly see questions that involve products that cannot be found, prices that are wrong, price books users cannot access, or opportunities whose price book cannot be changed. If you understand the relationships between these three objects and the rules that govern them, these questions become some of the easiest points on the exam.

This topic falls under the Advanced Cloud Applications section of the exam and is frequently combined with questions about Opportunities, Quotes, Forecasting, multi-currency, sharing, and validation rules. Think of it as a hub topic: it connects to many other areas, so mastering it pays off repeatedly.

What It Is: The Three Core Objects

1. Products (API name: Product2)
A Product is an item or service your company sells. Key standard fields include Product Name, Product Code, Product Description, Product Family (a picklist used to group products for reporting and forecasting), and the Active checkbox. A product record on its own has no price. Price information lives in a separate object, which is the key design concept to remember.

2. Price Books (API name: Pricebook2)
A Price Book is a list of products together with their prices. There are two kinds:
- The Standard Price Book: Every org has exactly one. It is created automatically, cannot be deleted, and holds the standard (or list) price for every product you intend to sell. It can be renamed and can be deactivated, but it must exist.
- Custom Price Books: You create these to offer different prices to different customer segments, regions, channels, or sales teams. Examples include a Government Price Book, a Partner Price Book, a European Price Book, or a Holiday Promotion Price Book. You can have many custom price books, and each has its own Active checkbox and Description.

3. Price Book Entries (API name: PricebookEntry)
A Price Book Entry is the junction record that links one Product to one Price Book and stores the price for that product in that price book. Key fields are List Price (UnitPrice), Active, Use Standard Price (a checkbox that tells the entry to simply mirror the standard price), and, in multi-currency orgs, Currency. A product can appear in a given price book only once per currency.

The relationship is therefore: Product (one) to Price Book Entries (many) to Price Books (many). The Price Book Entry is the many-to-many junction, and the price is a property of the entry, not of the product.

How It Works: Setup and Rules

Step 1: Create the Product
An administrator or a user with Create permission on Products creates the Product record and marks it Active. Optionally assign a Product Family. If product schedules are enabled in the org, you can also enable quantity or revenue scheduling on the product.

Step 2: Add a Standard Price
Before a product can be added to any custom price book, it must first have a standard price in the Standard Price Book. This is one of the most heavily tested rules. If a question describes a product that cannot be added to a custom price book, the most likely cause is a missing standard price.

Step 3: Add the Product to Custom Price Books
Create a Price Book Entry in each custom price book where the product should be sold. You can either enter a specific list price or check Use Standard Price. Each entry must be Active for users to select it on an opportunity.

Step 4: Use the Price Book on Opportunities, Quotes and Orders
When a user adds the first product to an Opportunity, Salesforce prompts them to choose a Price Book (if more than one is available to them). After the price book is selected, the user can only pick products that have active entries in that price book (and, in multi-currency orgs, entries in the opportunity currency). The List Price on the Opportunity Product is copied from the Price Book Entry and is read-only. The Sales Price defaults to the List Price but can be edited by the user unless you restrict it. Once products exist on the opportunity, the Amount field becomes a read-only roll-up of the line items.

Important Behavioral Rules to Memorize
- A product must have a standard price before it can be added to a custom price book.
- A product can be in a price book only once per currency.
- An opportunity can use only one price book at a time.
- To change the price book on an opportunity that already has products, you must delete all opportunity products first (Salesforce warns that changing the price book removes the products).
- Inactive products and inactive price book entries do not appear in the product selection list, but existing opportunity products referencing them remain intact.
- Inactive price books cannot be selected on new opportunities, but opportunities already using them are unaffected.
- Once a Price Book Entry is created, you cannot change which product or which price book it belongs to; you can only edit the price and the Active flag. To move a product, create a new entry.
- Deleting a price book deletes all of its entries. You cannot delete a price book or product that is referenced by opportunities or quotes; instead you must archive it (or deactivate it). Archiving keeps historical data intact.
- In multi-currency orgs, a product needs a price book entry in each currency in which it will be sold. The opportunity shows only products with entries in the opportunity currency. Dated exchange rates affect opportunity products based on the Close Date.

Product Schedules
Product schedules allow a single opportunity product to be split into installments. A Quantity Schedule spreads units over time (for example, delivering 12 licenses, one per month). A Revenue Schedule spreads the amount over time (for example, recognizing a 12,000 annual contract as 1,000 per month). Schedules must be enabled at the org level in Product Schedule Settings, then enabled on each individual product, and finally established on the opportunity product by the sales user. Schedules are relevant to forecasting and revenue reporting questions.

Product Families
The Product Family picklist groups products into categories such as Hardware, Software, Services. Beyond reporting, Product Family is used in Collaborative Forecasts when the Opportunity Revenue by Product Family or Opportunity Quantity by Product Family forecast types are enabled. If a question asks how to forecast separately on hardware versus services, the answer involves the Product Family field.

Sharing and Security
Price Books have their own Organization-Wide Default setting with three options:
- Use (default): All users can view price books and use them on opportunities.
- View Only: Users can see the price book but cannot add its products to opportunities unless granted access via sharing.
- No Access: Users cannot see or use the price book unless shared with them.
Price books support manual sharing and sharing rules, so you can give a partner price book only to the partner sales team, for example. Products and Price Book Entries are controlled through object permissions on Products and Price Books in profiles and permission sets. To create or edit price book entries, a user needs Edit permission on Price Books and Read permission on Products. Field-level security and page layouts also apply, so hiding the Sales Price field or making it read-only on the Opportunity Product layout is a legitimate configuration option.

Lightning Experience Considerations
In Lightning, the Add Products flow lets users search, filter, and multi-select products, then edit quantity, sales price, date and line description on a single screen. The Opportunity Product object in Lightning includes a Discount field. Administrators can customize search layouts and the fields displayed during product selection. Price books can also be cloned in Lightning. List views on Products and Price Books can be customized like any other object.

Common Business Scenarios and the Correct Configuration

Scenario: Different customers pay different prices for the same product.
Create custom price books (Retail, Wholesale, Government) with the appropriate price book entries. Do not create duplicate products.

Scenario: A sales rep cannot find a product when adding it to an opportunity.
Check, in order: Is the product Active? Does it have an active Price Book Entry in the price book selected on the opportunity? Is the entry Active? In multi-currency orgs, is there an entry in the opportunity currency? Does the user have sharing access to the price book?

Scenario: A rep selected the wrong price book and needs to change it.
Remove all opportunity products, then change the price book and re-add the products.

Scenario: Reps are discounting too aggressively.
Use a validation rule on Opportunity Product comparing Sales Price to List Price (for example, preventing a discount greater than 20 percent), or make Sales Price read-only on the page layout for certain profiles. Approval processes on the Opportunity can also require approval for large discounts.

Scenario: Management wants revenue spread across months for subscription products.
Enable Product Schedules in Setup, enable revenue schedules on the specific products, and have reps establish schedules on the opportunity products.

Scenario: A product is discontinued but has historical opportunities.
Deactivate or archive the product; do not attempt to delete it. Deleting is blocked when the product is referenced, and archiving preserves historical reporting.

Scenario: Only the EMEA team should use the EMEA price book.
Set the Price Book OWD to No Access or View Only, then create a sharing rule granting Use access to the EMEA role or public group.

Exam Tips: Answering Questions on Products, Price Books and Price Book Entries

Tip 1: Always remember where the price lives. The price is on the Price Book Entry, never on the Product. If an answer option suggests adding a price field to the Product object or creating separate products for each price, it is almost always wrong.

Tip 2: Standard price first, always. Any question about adding a product to a custom price book and failing points to the missing standard price. This is a favorite exam detail.

Tip 3: One price book per opportunity. If a scenario requires products from two price books on the same deal, the correct approach is to consolidate the products into a single price book, not to allow two price books on the opportunity (which is impossible).

Tip 4: Changing the price book requires deleting products. Watch for distractor options that say the rep can simply change the price book or that an admin must edit the field directly. The products must be removed first.

Tip 5: Active flags are a three-layer check. The Product, the Price Book, and the Price Book Entry each have an Active checkbox. When troubleshooting why something is not visible, mentally check all three, plus currency and sharing.

Tip 6: Know the three Price Book OWD options. Use, View Only, No Access. Questions about restricting which teams can sell from which price book are sharing questions, not permission-set questions. Note that Use is the default.

Tip 7: Archive, do not delete. Whenever historical opportunities or quotes reference a product or price book, the exam expects you to archive or deactivate it. Deletion is blocked and would also destroy reporting history.

Tip 8: Multi-currency doubles the entries. In a multi-currency org, each product needs an entry per currency in each price book. If a rep in Europe cannot see a product, the most likely gap is a missing EUR entry.

Tip 9: Connect Product Family to forecasting. If the question mentions forecasting by product category, the answer involves populating the Product Family picklist and enabling a product family forecast type in Collaborative Forecasts.

Tip 10: Connect schedules to installments. Words like installments, recurring, spread over time, or monthly recognition signal Product Schedules. Remember the two-level enablement: org setting plus per-product setting.

Tip 11: Sales Price versus List Price. List Price comes from the entry and is read-only. Sales Price is what the rep actually charges and is editable by default. Questions about enforcing pricing discipline are answered with validation rules on the Opportunity Product, page layout read-only settings, or approval processes, not by locking the Price Book Entry.

Tip 12: Read for the actual problem. Exam scenarios often bury the real issue in a story. Identify whether the problem is visibility (sharing or active flags), data model (standard price or duplicate entries), process (changing price books or discounting), or reporting (product family or schedules). Classify first, then eliminate options that address a different category.

Tip 13: Eliminate solutions that over-engineer. If a declarative feature of price books solves the problem, options involving custom objects, Apex, or duplicating products are distractors. The Advanced Administrator exam rewards knowing the native capability.

Quick Reference Summary
- Product = what you sell (no price).
- Price Book = a named list of products and prices; one Standard, many Custom.
- Price Book Entry = junction record holding the price for one product in one price book in one currency.
- Standard price required before custom price book entries.
- One price book per opportunity; remove products to change it.
- Three Active flags: Product, Price Book, Entry.
- Price Book OWD: Use (default), View Only, No Access; supports sharing rules and manual sharing.
- Archive instead of delete when referenced.
- Product Family drives forecasting by category; Product Schedules drive revenue or quantity installments.
- List Price is read-only from the entry; Sales Price is editable and governed by validation rules, layouts, or approvals.

Master these relationships and rules, and you will be able to answer virtually any Products and Price Books question on the Advanced Administrator exam with confidence.