Considerations for Working with Multiple Pricing Recipes

If your org uses both Revenue Cloud and B2B Commerce, you likely have a Revenue Cloud default pricing recipe and a B2B Commerce default recipe. Note these considerations when managing multiple pricing recipes:

• Only one pricing recipe can be set as the org’s default at a time. The pricing procedure uses values and mappings from the default recipe.
• Add custom decision tables to the default recipe. B2B pricing procedures use these values without code changes.
• B2B pricing procedures use mappings only from the default recipe. To use mappings from non-default recipes, update the pricing procedure code.
• Sync decision tables from the Pricing Recipes page to refresh data for a specific recipe. From Setup, in the Quick Find box, enter Pricing Recipes, and select Pricing Recipes. Locate the recipe, click the arrow icon, and select Sync. You can sync active and inactive recipes.