Understand the Order of Execution for Place Sales Transaction

When you create or update a quote or order using the Place Sales Transaction API, Revenue Cloud processes the request through a defined order of execution. This order describes how configuration, pricing, Apex hooks, and automation run during transaction processing. Understanding this order helps you determine where pricing logic runs and how context data is processed when using Place Sales Transaction.

1. Saves the sales transaction header.
   1. Executes triggers associated with the transaction header.
   2. Synchronizes supported context data back into the transaction context when context data is included in the request payload.
2. Hydrates the transaction with data required for configuration and pricing.
3. Applies applicable configuration logic to the transaction.
4. Performs pricing.
   1. Runs the pre-pricing Apex hook, if defined.
   2. Runs pricing logic.
   3. Runs the post-pricing Apex hook, if defined.
5. Persists data from the transaction context.
   1. Executes triggers for affected records.
   2. Synchronizes supported context data back into the response when context data is included in the request payload.
6. Executes record-triggered flows and other custom logic based on the persisted data.