Managing Order Status Setup & Delayed Provisioning with Dynamic Revenue Orchestration (DRO)

/0 Comments/in /by

In complex B2B and enterprise order management environments—such as cybersecurity, telecommunications, and SaaS—orders often consist of a combination of hardware items requiring physical shipment/configuration and software licenses that depend on those physical endpoints being configured first.

This blog post walks through the end-to-end process in Salesforce Revenue Cloud, from configuring custom Order Status picklist values in Setup to using Dynamic Revenue Orchestration (DRO) to manage dependent fulfillment steps, manual tasks, and dynamic start date adjustments without requiring order cancellations or re-submissions.

1. Configuring Custom Order Status Picklist Values

Before submitting an order to DRO, your organization may require custom stage gates or custom status values on the standard Order object to align with internal compliance or review procedures.

To add a new status value to the Order object:

  1. In Salesforce Setup, open Object Manager and select Order.
  2. Click Fields & Relationships and open the Status picklist field.
  3. Under the Order Status Picklist Values section, click New.
  4. Add your custom status label (e.g., Review) and associate it with the appropriate Status Category (Draft, Activated, or Processed).
  5. Save the new value and verify that it is enabled for your Order record types.

Figure 1: Customizing Order Status picklist values (Review) in Object Manager.

2. Structure of a Multi-Product Enterprise Order

Once the custom status is active, you can create and review your order. Consider an enterprise cybersecurity order containing three distinct product lines:

  • Hardware Product:Hardware Security Key Kit (Requires shipping and security key enrollment)[cite: 1, 2]
  • Dependent Software Service:Endpoint Security Suite (Requires endpoint license configuration and activation)[cite: 1, 2]
  • Standalone Feed:Threat Intel Feed (Can be activated immediately)[cite: 1, 2]
[ Customer Order ]
 ├── Order Status: Draft ──> Review (Submit to DRO) ──> Activated
 ├── 1. Hardware Security Key Kit ──────────> Requires Shipping & Key Enrollment
 ├── 2. Endpoint Security Suite ─────────────> Hold until Hardware/License Ready
 └── 3. Threat Intel Feed ───────────────────> Activate & Assetize Immediately

Figure 2: Order Details page showing line products and status progression before submission

3. Order Submission & Decomposition in DRO

Update the order status to Review and click Submit Order to send it directly into DRO.

Important Note on Automation Rules: Because the order status is updated to Review rather than Activated, any system rules, triggers, or automation flows configured specifically to fire upon reaching the standard Activated state will not fire during this submission. This allows fulfillment orchestration to commence under a review lifecycle without triggering prematurely activated downstream triggers.

Upon submission, DRO decomposes the order into fulfillment plans and orchestration steps:

  • Immediate Path (Threat Intel Feed): Bypasses hardware dependencies, proceeds through assetization, and creates a billing schedule immediately starting on the order date.
  • Delayed / Gated Path (Hardware & Endpoint Security Suite): Triggers dependent manual fulfillment tasks such as Ship Security Keys and Configure License[cite: 1, 2].

4. Progressing Manual Fulfillment Steps

As physical hardware is shipped and processed, administrators or automated systems update individual task statuses within the DRO Orchestration Plan:

  1. Ship Security Keys: Status moved from In Progress to Completed[cite: 1, 2].
  2. Enroll Security Keys: Processed and updated[cite: 1, 2].
  3. Staged Assetization: Hardware assets are created and linked to the account.

Figure 5: Completing manual fulfillment tasks (Ship Security Keys & Enroll Security Keys)

5. Adjusting Subscription Start Dates, Repricing & Order Activation

If software endpoint configuration takes longer than anticipated (or is scheduled for a future rollout date), charging the customer from the original order date will result in inaccurate invoices.

DRO allows order product subscription start and end dates to be edited directly prior to completing the final activation gate:

  1. Edit Order Product Dates: Open the Order Product record for Endpoint Security Suite, locate Subscription Information, adjust Start Date and End Date to align with the new projected rollout date, and save[cite: 1, 2].
  2. Reprice All: Return to the Order Details page and click the Reprice All button to recalculate pricing and billing values based on the updated dates[cite: 1, 2].
  3. Activate the Order: Advance the Order Status bar from Review to Activated and save the order state[cite: 1, 2].

6. Finalizing Activation and Billing Schedule Generation

With the order repriced and activated, return to the DRO Plan Orchestration tab and complete the remaining gate tasks (e.g., Configure License)[cite: 1, 2].

DRO processes the remaining automated steps:

  • Activate Endpoint
  • Staged Assetization
  • Create Billing Schedule

7. Verification Across Billing Schedules and Account Assets

Upon refreshing the Order and Account views, all components reflect synchronized timelines:

Billing Schedules

Each product line item has a dedicated billing schedule record reflecting its true active timeline[cite: 1, 2]:

  • Threat Intel Feed: Billing starts from the initial submission date.
  • Endpoint Security Suite: Billing schedule start date matches the newly adjusted start date[cite: 1, 2].

Figure 8: Order Billing Schedules list displaying distinct start dates and itemized totals

Figure 9: Individual Billing Schedule record showing adjusted Billing Schedule Start Date

Account Managed Assets

Navigating to the Account record under Managed Assets verifies that all three assets are active, with lifecycle start and end dates accurately mapped to actual fulfillment timelines[cite: 1, 2].

Figure 10: Account Managed Assets showing adjusted Lifecycle Start and End dates per line item

Key Takeaways

  • Custom Order Lifecycle: Standard Order Status picklist values can be easily extended in Object Manager Setup to match organizational workflow stages prior to execution[cite: 1, 2].
  • Bypassing Activation Triggers: Submitting an order under a non-activated status (like Review) allows DRO fulfillment to initiate while bypassing rules that strictly target the Activated state[cite: 1, 2].
  • Repricing & Activation: Hitting Reprice All after updating line product dates ensures pricing accuracy before advancing the status to Activated[cite: 1, 2].
  • Dependency Handling: DRO holds dependent software activation and billing until prerequisite hardware steps complete[cite: 1, 2].
  • Seamless Integration: Assets and Billing Schedules automatically inherit updated order product dates without needing complex order amendments[cite: 1, 2].