Salesforce Order Management Administrator AP flashcards
Salesforce Order Management Administrator AP · Build recall with a focused review session.
33 cards. Read the term and the definition here. The deck at the top of this page is optional.
- OrderSummary vs Order
- Order is the pre-activation intake record; OrderSummary is the post-activation runtime record that drives fulfillment, payments, and changes. Do not edit Order after activation.
- FulfillmentOrder purpose
- A FulfillmentOrder is the unit of work sent to a fulfillment location. One OrderSummary can create multiple FulfillmentOrders split by location or delivery group.
- Order Lifecycle Manager
- OLM drives OrderSummary and FulfillmentOrder state transitions using OrderLifecycleType settings and Apex extension classes that run on each transition.
- Delivery Group
- A Delivery Group groups OrderItemSummary records that ship together and carries the shipping address, delivery method, and delivery group type.
- Fulfillment plan routing
- Fulfillment plans and routing rules select fulfillment locations for a FulfillmentOrder. Rules match on location group, priority, or custom order criteria.
- Change order
- A change order captures post-submission edits such as quantity decrease or cancel. Each change creates OrderItemSummaryChange records for audit.
- OrderSummary status flow
- OrderSummary moves Draft to Activated to In Progress to Completed or Canceled. Activated is set when the order is submitted and fulfillment begins.
- FulfillmentOrder status flow
- FulfillmentOrder moves Draft to Submitted to Allocated to Fulfilled. Partial allocation yields Partially Allocated until remaining quantity is allocated or canceled.
- FulfillmentOrderLineItem quantities
- Each line item holds OrderedQuantity, AllocatedQuantity, and FulfilledQuantity. Fulfilled quantity cannot exceed allocated quantity at any time.
- Return order
- ReturnOrder and ReturnOrderLineItem represent a return. A return references the original OrderItemSummary and can be created from a FulfillmentOrder.
- Cancellation after allocation
- Canceling an allocated FulfillmentOrder sets it to Canceled and creates OrderItemSummaryChange records that reduce the order item quantity.
- AvailableToFulfill formula
- AvailableToFulfill equals QuantityOnHand minus QuantityReserved minus SafetyStock, subject to the InventoryPolicy. It is the metric used for allocation decisions.
- Inventory reservation
- Allocation creates an inventory reservation that reduces AvailableToFulfill but not QuantityOnHand. Reservations are tied to FulfillmentOrderLineItem records.
- InventoryPolicy
- InventoryPolicy defines whether overselling is allowed and how availability is computed. The default policy blocks overselling at the location level.
- LocationGroup
- LocationGroup and LocationGroupAssignment associate fulfillment locations with inventory pools so routing can select eligible locations for a FulfillmentOrder.
- External inventory
- When an external system is authoritative, Order Management reads inventory via the Inventory API and local ProductInventory records become read-only.
- PaymentAuthorization
- A PaymentAuthorization records an authorization against a PaymentMethod. It must be captured to create a Payment and can be voided or expire.
- OrderSummary totals
- OrderSummary carries TotalAmount, TotalTaxAmount, and GrandTotalAmount, calculated from OrderItemSummary records and summarized at the order level.
- Invoice and InvoiceLine
- Invoices are generated from FulfillmentOrder or OrderSummary records and contain InvoiceLine records. Invoice statuses include Draft, Posted, and Canceled.
- Refund representation
- A refund is a Payment with type Refund or a negative amount tied to the original PaymentAuthorization, referencing the original captured payment.
- PaymentGateway
- PaymentGateway records configure the external payment provider. Payment API and PaymentGatewayProvider calls handle authorization and capture against that gateway.
- Core object chain
- The core chain is Order to OrderSummary to OrderItemSummary to FulfillmentOrder to FulfillmentOrderLineItem to Shipment to ShipmentItem. Each link carries the order context.
- Order Management APIs
- REST endpoints for Order, FulfillmentOrder, Inventory, and Payment expose lifecycle operations to external systems using OAuth-authenticated Connected Apps.
- Platform Events
- OrderSummaryEvent and FulfillmentOrderEvent publish lifecycle changes asynchronously. Subscribers consume them via CometD or the Pub/Sub API.
- Change Data Capture
- CDC on OrderSummary and FulfillmentOrder streams near-real-time record changes to external systems, useful for replication and reconciliation.
- OriginalOrderItemId
- OrderItemSummary links back to its source OrderItem via OriginalOrderItemId. This mapping enables reconciliation between pre- and post-activation records.
- Fulfillment cycle time
- Fulfillment cycle time is measured from FulfillmentOrder CreatedDate to Shipment CreatedDate and is the basis for fulfillment performance reporting.
- Returns analytics
- Return rate equals returned quantity divided by fulfilled quantity over the reporting period, using ReturnOrderLineItem and FulfillmentOrderLineItem data.
- Order Management permission set
- Users need the Order Management User permission set plus object permissions. Access also requires the Order Management permission set licenses.
- Integration user security
- Integration users should use a dedicated Connected App with scoped OAuth and least-privilege permission sets rather than admin credentials.
- Field History Tracking
- Enable Field History Tracking on OrderSummary and FulfillmentOrder for status and quantity fields to audit order changes for compliance.
- FulfillmentOrder stuck in Draft
- A FulfillmentOrder remains Draft when no fulfillment plan matches routing criteria or the target location is inactive or outside a LocationGroup.
- Allocation failure cause
- Allocation fails when AvailableToFulfill at the location is insufficient or a restrictive InventoryPolicy blocks overselling for the requested quantity.