Task flow: Setting up an existing store to use Management Center price rules and price lists
To use the Catalog Filter and Pricing tool to manage price rules and price lists, there are a number of setup tasks to perform. Refer to this task flow to understand the tasks and the order in which to perform them.
You can use this task flow for the following business models:- B2C
- B2B
- Extended sites
About this task
- Using this task flow in the development and runtime environments
Complete the applicable steps in this task flow in the development environment first, and then test your changes. When you are satisfied with the results, you can use the same task flow for your runtime environment. In the runtime environment:
- Redo tasks 1 though 7, if they apply.
- Deploy the changes that you made in the development environment in tasks 8 and 9 to the runtime environment.
- Test your changes in the runtime environment.
- Using this task flow for extended sites
To assist you in completing this task flow, look for the special instructions for extended sites near the beginning of each task, where applicable. These instructions tell you which stores to perform the task on, and any other relevant details. For example, some tasks do not apply to catalog asset stores, and others do not apply to storefront asset stores.
- How this task flow affects price customization on your siteIf you customize one or more price commands, your customization might be affected by completing this task flow. If you want to continue to use the customized commands, you might be required to update the new command registry entry for the related interface. You add these command registry entries as part of this task flow, for example:
orcom.ibm.commerce.price.commands.GetProductContractUnitPriceCmd+AfterCompositeSecondary
orcom.ibm.commerce.price.commands.GetContractUnitPriceCmd+AfterCompositeSecondary
If you have existing customized command implementations that you want to continue to use, this task flow provides a procedure to add them to the registry. See Registering custom command implementations in the command registry. Afterward, your existing contracts will continue to work as before, and new contracts can use your customized commands or price rules as required.com.ibm.commerce.price.commands.GetContractSpecialPriceCmd+AfterCompositeSecondary