StoreConnect uses Salesforce Price Books1.
The advantage of using Price Books allows the Salesforce Administrator2 to use multiple prices for the one product.
This means that where you have one or more client-types, for example, wholesale and retail clients, you can define prices specifically for each client.
Considering StoreConnect’s ability to create multiple stores within the one Salesforce Org3, the advantage of using Price Books means no matter how many stores you create, you will always be able to create a suitable pricing structure for your store.
Change the Price Book Page Layout
The advantage of the storeConnect / Salesforce dependancy is utilising the power & customisability of Salesforce.
When you first create your store, you will need to adapt the StoreConnect Price Book Page Layout to make the most of it’s built-in features.
This video will guide you through changing the Price Book Page Layout.
Create Custom Price Books within Salesforce
Price book: A “price book” is best explained as a catalogue price. A business selling widgets may have different catalogues depending on the client-base. For instance, you could have three catalogues: 1) a wholesale, 2) retail and 3) online. Each of these catalogues, or Price Books, may have different prices for the same product depending on the client-base. Price books are inherent within Salesforce. See Product Pricing for more information. ↩
Administrator: Someone who manages something. For example, a Salesforce Administrator would be the person responsible for managing and configuring a Salesforce Org. ↩
Salesforce Org: The virtual space provided to an individual customer of Salesforce. It includes all of your data, records, etc and applications. A Salesforce Org, or “Org” for short is an abbreviation of “organisation”. ↩
Trailhead: The Salesforce learning platform. The platform has many free courses, modules and “trails” (learning paths) designed to help anyone learn more about Salesforce and its related products. See the Trailhead website for more information. ↩
Back to Documentation