TL;DR — Summer ’25 finally lets you raise change orders against activated orders. Using Dynamic Revenue Orchestrator (DRO), you can add or remove products, tweak quantities or dates, and keep fulfillment on track without resorting to cancel-and-rebill gymnastics. This post walks through why the feature matters, how to switch it on, and the pitfalls you should test for before rolling it out.
Why It Matters
- Customer-first agility. Modify orders mid-stream instead of forcing customers through a brand-new order cycle.
- Clean audit trail. The original order moves to a new Superseded status; the change order inherits the history.
- Seamless fulfillment. DRO lanes freeze and respawn automatically so warehouse, shipping, and billing teams stay in sync. :contentReference[oaicite:0]{index=0}
- No more cancel-rebill. Avoid revenue leakage, split invoices, and manual credit memos.
Feature at a Glance
| Capability | What It Does | Business Win |
|---|---|---|
| Change button | Creates a draft change order from the active order. | One-click workflow; no separate Flow/Apex needed. |
| Place Supplemental Orders permission set | Grants users the right to initiate change orders. | Granular security; easy rollout to pilot group. |
| In-Flight Amendments toggle (DRO settings) | Globally activates the feature. | SaaS-style opt-in; no metadata package required. |
| “Superseded” status category | Marks the original order when the change order goes live. | Clear reporting and compliance trail. |
| Point of No Return on fulfillment steps | Stops edits after assetization (or your chosen step). | Prevents downstream data corruption. |
Prerequisites & Compatibility
- Revenue Cloud Summer ’25 (API v96.0 or later) with DRO enabled.
- User permissions:
DRO | Place Supplemental Orders. - Order Status field extended with a new pick-list value:
Superseded(Status Category = Superseded). - Fulfillment Plans reviewed and flagged with Points of No Return (see below).
- No assets were created from the order you intend to change. Once assetization happens, use the traditional amendment path instead.
Step-by-Step Configuration Guide
1 — Enable In-Flight Amendments
Setup ▶ Dynamic Revenue Orchestrator Settings ▶ In-Flight Amendments ✔️2 — Assign the Permission Set
Setup ▶ Permission Sets ▶ Place Supplemental Orders ▶ Manage Assignments3 — Expose the Change Button
- Edit the Order page layout or Lightning record page.
- Add the standard
Changequick action to the Salesforce Mobile & Lightning Experience Actions section.
4 — Add a “Superseded” Status
- Object Manager ▶ Order ▶ Fields & Relationships ▶
Status. - New → Value:
Superseded; Status Category = Superseded.
5 — Prepare Fulfillment Plans
Open each Fulfillment Step in the plan:
- Stage Assetize (or equivalent finalization step)
Point of No Return= Changes Denied
- Any step before assetization
Force Plan Freeze During Execution= Yes, Forcefully Complete Step
Demo Walkthrough
- Activate Order #106. Submit to fulfillment. Step 1 completes; Step 2 starts (In Progress).
- Customer requests changes. Click
Change. Draft change order #107 is created; original order freezes. - Modify Order #107. Add Predictive Maintenance Analytics, adjust quantities, etc.
- Activate Order #107. System automatically:
- Sets Order #106 status to Superseded.
- Unfreezes fulfillment plan, spawns new swim lane for remaining steps.
- Resume fulfillment. Continue processing until assetization occurs.
Diagram 1 — How DRO lanes split and re-merge during in-flight changes.
Best Practices & Gotchas
- Pilot first. Start with a single product line and a handful of users to observe downstream effects.
- Always test fulfillment freeze. If a step is stuck in Freezing, revisit the Force Plan Freeze flags.
- Train on status meanings. Sales Ops and Finance must understand that Superseded orders are historical, not live.
- Audit reports. Update dashboards to exclude superseded orders from pipeline totals.
- Billing timing. In-flight changes do not retroactively adjust invoices already generated. Decide whether to credit back or create delta invoices.
- Integration touchpoints. If ERP or 3PL systems subscribe to
Orderevents, include logic to ignore superseded orders.
Frequently Asked Questions
Can I change an order after assets exist?
No. Once the Stage Assetize step (or your chosen Point of No Return) completes, use the traditional amendment/cancellation flow instead.
Does the feature work for partial fulfillments?
Yes, as long as the fulfillment plan hasn’t hit the assetization step for that product line.
What if I need to change prices?
You can adjust line-item pricing on the change order draft just like you would on a fresh order, subject to your approval matrix.