Salesforce Order Management Administrator AP key terms

A record that aggregates the pricing, status, and line items of one or more related orders so they can be fulfilled, invoiced, and tracked as a single unit. Multiple orders can roll up into one summary.

The summarized line-level record representing a product on an order summary, holding quantities, pricing, and statuses that fulfillment and invoicing processes act upon rather than the original order line.

A work record created to fulfill a portion of an order summary, grouping line items to be sourced, shipped, or delivered from a particular location through a specific fulfillment process.

The line-level record inside a fulfillment order that tracks the quantity of a product being fulfilled, including shipped, delivered, and remaining amounts. It links back to the related order item summary.

The sequence of states an order passes through from creation through fulfillment, invoicing, and closure, including holds, cancellations, and returns. Transitions are governed by configured status values and rules.

A record used to modify an existing order after it has been submitted, such as adjusting quantities, swapping products, or changing prices. Changes are applied through a defined approval and processing flow.

A record representing a customer return request, capturing items, quantities, and reasons. It drives the return authorization, receipt, and refund or credit processes against the original order.

The line-level record within a return order that specifies which product and quantity is being returned, along with reason codes and disposition details used to process the return.

The data model objects specific to Order Management, such as OrderSummary, FulfillmentOrder, and ReturnOrder, which extend core Salesforce objects and store transactional order data separately from sales order records.

A picklist value indicating the current lifecycle stage of an order summary, such as Created, Allocated, Fulfilled, or Cancelled. Status drives which processes and actions are available.

A configuration that defines the steps and sequence used to fulfill orders, including which fulfillment steps run and in what order, such as create, assign, ship, and invoice.

A configuration that determines how order items are grouped into fulfillment orders, for example by delivery method or by source location, so that each group can be fulfilled independently.

The setup page where administrators enable Order Management features, configure defaults such as order and fulfillment settings, and control behavior for pricing, inventory, and invoicing across the org.

A record that holds a quantity of a product at a location for a specific order or fulfillment order so it cannot be promised to another customer, reducing available-to-promise until released or consumed.

The quantity of a product that can be committed to new orders right now, calculated from on-hand inventory minus reservations and other commitments. ATP drives sourcing and promise dates.

A configured physical or logical place, such as a warehouse or store, where inventory is tracked and from which orders can be sourced. Locations carry their own stock levels and fulfillment capabilities.

Configuration that decides which inventory location should fulfill a given order item, based on criteria such as proximity, priority, or available stock. It produces the sourcing assignment used in fulfillment.

The stored quantity of a product at a specific location, including on-hand and reserved amounts. Inventory records are the source data used to compute availability and reservations.

A record confirming that a payment gateway has approved a charge amount for a period, reserving funds on the customer's payment method before capture. It can later be captured or voided.

The process of collecting previously authorized funds from a customer's payment method, creating a captured payment record that is then eligible for settlement and reconciliation.

A configured integration record that connects the org to an external payment processor, defining credentials, supported payment methods, and how authorization and capture requests are sent and received.

A billing document generated for an order or fulfillment that lists amounts owed, line details, and totals. Invoices feed payment collection and are tracked against the related order summary.

A grouping mechanism that generates invoices for multiple orders or fulfillments at once, typically run on a schedule or triggered by status changes, reducing manual invoicing effort.

A record representing money returned to a customer, often linked to a return order or a canceled item. Refunds are processed through the payment gateway and reconciled against captured payments.

The set of APIs, flows, and middleware connections that move order, inventory, and payment data between Salesforce and external systems such as ecommerce platforms, ERPs, and warehouses.

The process of bringing orders from external channels into Order Management, creating order summaries and item summaries. It may use APIs or connectors and must handle validation and deduplication.

A field on a record that stores the identifier from an outside system, enabling reliable matching and upserts during integrations. External IDs help prevent duplicate records during data loads.

Reports and dashboards built on order, fulfillment, and inventory objects to track metrics such as fulfillment time, cancellation rates, and inventory levels, supporting operational decisions.

A collection of permissions granting access to Order Management objects, fields, and actions. Assigning it to users provides the rights needed to process orders without broad admin access.

Configuration that controls which users can view or edit order summaries, fulfillment orders, and related records, often scoped by role, territory, or criteria to protect sensitive order data.

The practice of diagnosing failures in order processing, such as stuck fulfillments or failed payments, by reviewing statuses, error logs, integration messages, and configuration settings.

An individual action within a fulfillment process, such as creating a fulfillment order, assigning inventory, or marking shipment. Steps run in sequence and can be configured or extended.

A flag or record that pauses processing of an order summary, for example pending payment or fraud review, preventing fulfillment until the hold is released by an authorized user or process.

A record representing goods dispatched for a fulfillment order, capturing carrier, tracking, and shipped quantities. Shipments update fulfillment status and feed customer notifications and invoicing.

Configuration that applies discounts or price changes to order items during order processing, recorded as adjustment records so final totals and invoices reflect the correct amounts.

The overall structure of objects and relationships used by Order Management, linking orders, summaries, fulfillments, returns, payments, and inventory so processes can act on consistent data.