How Order Management Works

Overview

Order Management for Agentforce Life Sciences moves a field visit from assessment to a finalized, priced order. Store Check surfaces only the products and checks relevant to the store being visited. Quotes and Pricing builds on that same visit to capture a priced, discounted order. Each stage surfaces the actions relevant to the person doing the work—reps assess and quote in the field, and sales managers review and approve unlock requests.

Order Management also handles the pricing and compliance dimensions of a sale. Admins define price books, pricing recipes, and pricing procedures that determine how list prices, volume discounts, and condition-based discounts apply to a quote. Every pricing decision is captured in a Price Waterfall record, giving a line-by-line price breakdown from list price to final net price. Validation rules and configurable approval workflows enforce business policy before a quote is finalized.

Order Management integrates the tools reps use in the field. Reps complete a store check, review Price Waterfall breakdowns, capture an electronic signature, and generate a quote PDF all from the Visit record—only from the web.

In Agentforce Life Sciences, Order Management combines store check, and quotes and pricing into a single flow. Before you delve into the details of each component, understand the order lifecycle, object relationships, pricing engine, and more for a quicker implementation.

Order Lifecycle

An order moves through two connected lifecycles: the visit's store-check stages, and the quote's approval stages. Based on your business requirements, you can configure these stages. Here's an example of the stages that an order moves through.

Planned

A field rep schedule or opens a visit. Store check tasks aren't recorded yet.

In Progress

The rep captures store-check responses—availability, display, and promotional compliance—against the assortment and assessment tasks configured for that account. They can still edit the record.

Completed

The visit closes and its store-check data rolls up into KPI records. The field rep can't change captured responses retroactively.

Draft

From the same visit or account, the rep builds a quoted order, adding products, quantities, and discounts.

Submitted

The quote and its line items lock when the rep submits it for approval or fulfillment. The rep can't edit a submitted quote directly.

Request for Unlock

If the rep must change a submitted quote, they request an unlock. The request routes to their manager while the quote stays locked—even if the rep is offline when they request it.

Approved or Rejected

The manager's decision either returns the quote to Draft status for edits, or to Rejected for locked, and notifies the rep either way.

Objects and Relationships

Every quoted order and store check traces back to a visit, and a small set of objects carries the data between them.

Visit

The entry point for a store check or a quoted order. Its record type determines which experience opens and which assortment and price book apply.

Quote and Quote Line Item

The quoted order and its individual products. The Status field of a quote drives the lock and unlock behavior.

Price Book and Price Book Entry

Define which products and list prices are available to a rep's territory or account.

Assortment, Assortment Product, and Store Assortment

Define which products a rep sees and checks during a store visit, scoped by account or territory.

Assessment Task Definition and Assessment Indicator Definition

Define the checks that a rep performs during a store check. For example, a display compliance check or an out-of-stock check, and also the values a rep can record for each.

Retail Store KPI

Stores the rolled-up result of a completed store check, so you can report on compliance by account or territory.

Sales Transaction Type

Ties a quote to the pricing procedure and validation rules that apply to it, so reps don't select a procedure manually.

Pricing and Discount Engine

Pricing runs as a chain of configurable elements, not a single calculation.

A pricing recipe determines which pricing operations run for a quoted order. Within that recipe, a pricing procedure defines the sequence of pricing elements that run against each line. A pricing procedure contains elements such as list price, volume discounts, and manual line or header-level discounts. The sales transaction type on the quote determines which pricing procedure applies. So, you can have different pricing behavior for different products or territories.

Every pricing element that runs against a line in the order those adjustments happened and writes to that line's Price Waterfall. Price waterfall is a record of list price, each discount applied, and the resulting net price. Sales reps tap or hover over a line item to see this breakdown. This breakdown is preserved as line-by-line breakup even after the quote is submitted and locked.

Approval and Locking Workflow

Two systems work together to enforce quote integrity after submission.

A workflow (if configured) locks the quote and its line items based on the quote's Status field. So, field reps can't edit a submitted quote before the quote is approved. A record-triggered approval flow (if configured) handle unlock requests: when a rep requests an unlock, the flow routes the request to the rep's manager, and updates the quote's status after the manager approves or rejects it. Both systems rely on the same Status field, so a quote is never simultaneously editable and pending approval. Notifications keep reps and managers informed at submission, unlock request, and decision.

Mobile and Offline Behavior

Sales reps capture store checks and quoted orders without a live connection, and the underlying records are reconciled when the connectivity returns.

Price Waterfall data persists locally on the device, so a rep can review a line's pricing breakdown offline the same way they can online. Electronic signatures captured offline are encrypted and stored on the device, then synced to the quote record when the device reconnects. The Admin Console controls the mobile-specific configuration—product views, priority products, disclaimers, and layout—that determines what a rep sees in the mobile app, independent of the underlying pricing and assessment metadata.