Order Management Configuration
What to know
Order Management configuration starts with the objects that describe how orders should be processed: Order Summary, Order, Order Item Summary, Order Item, Fulfillment Order, and Fulfillment Order Line Item. Candidates must understand the difference between the summary layer (order summary/order item summary) and the detail layer (order/order item), and when each is created or updated.
Key configuration areas include fulfillment order creation rules, order activation, routing and orchestration (fulfillment plans, delivery groups, and the rule-based steps in the orchestration flow), and order lifecycle settings. Know that routing rules determine which location fulfills an item, and that fulfillment plans are the reusable templates that orchestration applies.
Traps
- Questions often blur configuration with code. Remember that many behaviors (routing, split/merge, fulfillment order creation) are driven by declarative settings and orchestration flows, not custom Apex.
- Distinguish Order Summary (the customer-facing aggregate) from Order (the operational record).
- Know that a delivery group groups fulfillment order line items by shared delivery characteristics (e.g., same ship-to or delivery method).
- Watch for questions implying routing picks the best location automatically with no rules - routing follows configured rules and priorities.
Rule of thumb
If a question asks "what decides where an item ships from?" the answer is the fulfillment plan and its routing rules applied during orchestration, not the product record or the order item alone.
Worked example
An order has two items that must ship from different warehouses. Orchestration evaluates the fulfillment plan, applies routing rules, and splits the items into separate fulfillment orders, each grouped into a delivery group with its own delivery method.