22

Oct

When you work on a Salesforce Revenue Cloud project, few things save more time during debugging than knowing which element fired, in what sequence, and under which scenario.

If every pricing element is simply called “ListOperation,” “Assignment,” or “FormulaBasedPricing,” it becomes difficult to understand what actually happened during a pricing run.

A clear naming and numbering convention for your Pricing Procedure makes easier to maintain, faster to debug, and clearer for everyone who works with it.

Why it matters

When pricing behaves unexpectedly, for example when a discount does not apply or a tier fails to recalculate, the Pricing API Executions show which elements are executed.

With a consistent naming convention, you immediately know where to look.

Add descriptive tags that explain the purpose of each pricing element. A clear tag helps anyone reading the logs immediately understand what the element does, whether it sets a list price, derives price, performs a tier lookup, applies a discount, or recalculates totals. These tags form the readable, human-facing part of your Pricing Procedure.

Follow the tag with an identifier in square brackets to show the sequence and context of execution. The numeric part defines the order in which elements run, while an optional letter can indicate the transaction type.

For example:

Reprice Support Level [N-1920] for a new sale or ApplyManual Discount [550].

You can use:

  • N for New Sale
  • A for Amendment
  • R for Renewal

Tip: Leave gaps of 50 to 100 between number ranges, for example 100, 200, 300. This gives you flexibility to insert new elements later without renumbering the rest of the procedure.

Why this works

  • Readable in logs. When you see Reprice Support Level [N-1920] in the Pricing API Executions, you immediately know where it belongs.
  • Expandable. You can add new elements anywhere within a procedure without having to renumber the rest of the elements.
  • Contextual. The ordered numbering helps you see at a glance which elements of the procedure executed and which did not.
  • Team-friendly. New admins can easily follow the pricing logic without extra explanation.

Bottom Line

A structured naming convention keeps your Pricing Procedure clear, maintainable, and easy to debug. It’s a small investment that pays off every time you troubleshoot or expand your pricing logic.

Reach out to Milo Massimo for expert help with your Revenue Cloud Implementation