If you've spent any time in Salesforce Industries or Agentforce Revenue Management (formerly Revenue Cloud), you know the pattern: an order comes in, it needs to be fulfilled, and at some point in that fulfillment process you have to talk to one or more systems outside of Salesforce: a billing platform, a provisioning system, or a network inventory tool. The question is always the same: how much custom code and effort will be needed to support this requirement?

What Dynamic Revenue Orchestrator (DRO) Actually Does

Dynamic Revenue Orchestrator (DRO) orchestrates the steps required to fulfill an order, tracks the status of each step, and knows when a step requires calling out to an external system before it can be marked complete.

That "calling out" is where Integration Procedures come in. Integration Procedures drastically speed up delivery and simplify maintenance by handling outbound payloads and inbound API responses. Teams can build, update, and manage fulfillment flows in minutes without writing or maintaining complex Apex code.

The Architecture, Step by Step

  1. Fulfillment Step: a step in the fulfillment orchestration plan invokes an Integration Definition.

  2. Integration Definition: this is the piece responsible for connecting to the external system. It invokes a Named Credential to authenticate, then invokes an input Integration Procedure to build the outbound payload.

  3. Callout: Salesforce calls the external system (in the demo, a billing platform) with that payload.

  4. Output Integration Procedure: processes the response coming back.

Each fulfillment step definition represents one task in the larger orchestration plan, start the process, perform an installation, update the order status, bill the customer, confirm billing, move to the next step. It's a clean, auditable chain, and Integration Procedures are what enable each link in that chain to communicate with the outside world.

Seeing it in Action: A Real Billing Callout Using TMF-622

To make this concrete, Lindemberg runs a live demo using an order with three bundled products. He starts the fulfillment process, opens the orchestration plan, and walks through completing each fulfillment step, including the one that matters most for this session: a callout to an external billing system.

A few details worth highlighting for anyone building something similar:

  • The integration uses the TMF622 standard (TM Forum's Product Ordering API) for the request payload, important for organizations standardizing on TM Forum APIs for industry standard integrations.

  • Rather than storing the payload in a long text field (as in managed package Vlocity), Integration Procedures save the request as a Content Document, which can be downloaded and inspected as properly formatted JSON.

  • The input Integration Procedure uses an Extract action to query related information and a Transform action to shape the final payload — and because it accepts parameters like the Order ID or Fulfillment Step ID, the same Integration Procedure can be reused across different records rather than rebuilt for each one.

That reusability point is easy to miss but worth calling out: a well-parameterized Integration Procedure isn't a one-off. It's infrastructure you build once and reuse across your entire orchestration model.

Why This Matters

Teams evaluating Salesforce Industries or Agentforce Revenue Management (formerly Revenue Cloud) often assume that any real-time integration with a billing or provisioning system is going to require significant custom development. What this session demonstrates is that, for the majority of use cases, it doesn't have to. Standard Integration Definitions and Integration Procedures give you a declarative path to the same outcome with better maintainability and easier error handling to show for it.

About the Author

Lindemberg Venancio is a Salesforce Industries Developer at Stratus Carta and a Certified Agentforce Revenue Management Consultant as well as OmniStudio Developer and Consultant. With over 25 years of experience in the telecommunications industry and deep expertise in Salesforce Industries, he specializes in designing and delivering scalable, high-performance OmniStudio solutions.

Connect with Stratus Carta

If you’re designing and building fulfillment integrations as part of Dynamic Revenue Orchestrator, our team can help you make the right architectural decisions at the right time. Reach out to us on LinkedIn.