Published at: 2026-09-17
LTO business process overview
LTO (Lead-to-Order) is the end-to-end sales process from Sales Lead to Sales Order. It progressively turns prospects acquired by marketing and sales into Accounts for long-term development, manageable Opportunities, confirmed Product and Price proposals, and executable Sales Orders.
This page first describes LTO in its strict sense. It then shows how the process extends after order confirmation to contracts, fulfillment, delivery, and receivables.
Process scope
Core LTO
flowchart LR
A[Customer acquisition] --> B[Lead intake]
B --> C[Lead assignment and validation]
C --> D[Accounts and Contacts]
D --> E[Opportunity progression]
E --> F[Product configuration and Quoting]
F --> G[Sales Order]
Core LTO ends when the order is confirmed. It answers four questions:
- Where do prospects come from, and who follows up?
- When should you Convert a Lead into an Account or Opportunity?
- Is the Opportunity advancing through a consistent method, and is the likelihood of closing realistic?
- Are the Product, Price, and Promotion correct, and has the order received the required confirmation?
Extended post-order chain
flowchart LR
A[Sales Order] --> B[Inventory and shipping]
A --> C[Receivable]
D[Sales Contract] --> A
D --> C
B --> E[Actual delivery or Settlement]
E --> C
The post-order sequence is not fixed. A Contract can precede an order as a framework agreement or be created from an order scenario. You can create a Receivable from a Contract, order, or actual Settlement result. Inventory can be managed in CRM or integrated with ERP.
Process foundations
LTO does not rely on transaction records alone. Stable operation also requires three foundational capabilities:
| Foundation | Purpose | Typical rules |
|---|---|---|
| Account data foundation | Unify Account, Contact, and relationship data for long-term development | Duplicate Rules, ownership, Account Pool, Record Holding Limit, and influence maps |
| Transaction foundation | Unify Product, Price, selling boundaries, and transaction policies | Products and Units, Price Books, Selling Scope, Pricing Policies, and Credit rules |
| Process analytics | Use real process data to assess efficiency and risk | Marketing Attribution, stage conversion, stagnation, loss, and win/loss analysis |
Stage 1: Customer acquisition
| Item | Description |
|---|---|
| Goal | Record acquisition activities and retain prospect information as actionable Sales Leads |
| Primary inputs | Campaigns, Campaign Members, external channel data, tender information, or other prospect data |
| Key objects | Campaign, Campaign Member, Sales Lead |
| Key actions | Create Campaigns, maintain members, associate Leads, record Sources, and view Campaign performance |
| Stage output | Sales Leads with Source information |
| Primary roles | Marketing users and Sales Operations |
| Configuration dependencies | Campaign rules, Lead intake rules, and Marketing Attribution trigger rules |
A Campaign records one specific acquisition activity. Campaign Members and Campaign Leads support subsequent conversion. Account discovery and tender intelligence can also provide prospect or Lead sources. To measure investment results, keep the relationships among Campaigns, Sources, and conversion data complete.
Start with Campaign overview to learn about this stage.
Stage 2: Lead Management: intake, assignment, and validation
| Item | Description |
|---|---|
| Goal | Remove Duplicate or Invalid information, assign the right Leads to the right users, and validate their value |
| Primary inputs | New, imported, or channel-sourced Sales Leads |
| Key objects | Sales Lead and Lead Pool |
| Key actions | Duplicate detection, scoring, Claim, Assign, Transfer, Reclaim, Return, follow-up, and processing |
| Stage output | Converted Leads, or Leads marked Invalid, Voided, or Returned for further nurturing |
| Primary roles | Sales representatives, Lead Pool administrators, and Sales Operations |
| Configuration dependencies | Duplicate Rules, Behavior Points, Lead Pool, assignment, Reclaim, conversion, and Record Holding Limit rules |
Lead statuses
flowchart LR
A[Not Assigned] -->|Assign or Claim| B[Pending]
B -->|Start follow-up| C[In Follow-Up]
C -->|Successful conversion| D[Converted]
C -->|No current value| E[Invalid]
E -->|Reactivate| C
A --> F[Voided]
B --> F
C --> F
- Not Assigned: An Assigned Owner has not been specified.
- Pending: An Owner exists, but follow-up has not started.
- In Follow-Up: A follow-up record or processing result exists.
- Invalid: The Lead currently has no follow-up value. You can reactivate it according to permissions.
- Converted: The Lead has been converted into downstream Account, Contact, or Opportunity data.
- Voided: The data is classified as spam or no longer used. Usually, only an administrator can restore it.
Before conversion, confirm the Account, Contact information, and buying intent. Do not move unvalidated data directly into Account and Opportunity records. For details, see Sales Lead overview.
Stage 3: Account Management: create Accounts and Contacts
| Item | Description |
|---|---|
| Goal | Create Account master data and real communication relationships for long-term development |
| Primary inputs | Validated Leads or Account information obtained directly by Sales users |
| Key objects | Account, Contact, Account Address, and Account Financial Information |
| Key actions | Convert Leads, create or check for Duplicate Accounts, maintain Contacts, and add Address and financial information |
| Stage output | Account and Contact records with clear ownership and usable information |
| Primary roles | Sales representatives, Account administrators, and Sales managers |
| Configuration dependencies | Duplicate Rules, ownership, creation Approval, Address, Business Registry Lookup, and Data Access rules |
Accounts retain long-term relationships, while Contacts record specific communication counterparts. One Account can have multiple Contacts and Opportunities. Check for an Existing Account before creating or converting one to avoid Duplicate records.
Account resource routing
flowchart LR
A[Account in Account Pool] -->|Claim or Assign| B[Sales-owned Account]
B -->|Continuous follow-up| C[Closed or continued development]
B -->|Return or rule-based Reclaim| A
C -->|Renewal, expansion, or new Opportunity| B
C -->|Reassign for development| A
Account Pools, Record Holding Limits, and Reclaim rules improve resource use. They do not represent the Account life cycle itself. A closed Account can still produce new development Opportunities. For details, see Account life cycle and Account Pool routing.
Stage 4: Identify and advance Opportunities
| Item | Description |
|---|---|
| Goal | Manage a clear buying need as an independent sales Opportunity and advance it consistently |
| Primary inputs | Account needs, Lead conversion results, or Opportunities identified proactively by Sales |
| Key objects | Opportunity, Opportunity details, Opportunity Contact, and Opportunity decision chain |
| Key actions | Create and check for Duplicates, select a Sales Process, complete stage tasks, update Amount and Date, maintain the decision chain, and close the Opportunity |
| Stage output | Closed Won, Closed Lost, or Invalid Opportunities with complete stage transition records |
| Primary roles | Sales representatives and Sales managers |
| Configuration dependencies | Opportunity Duplicate Rules and Approval, Sales Process, stage tasks, Record Holding Limit, decision-chain templates, and close rules |
A Sales Process contains In Progress stages and final stages. Each stage can define a hold duration, reminders, Approval, Entry Criteria, Completion Criteria, and whether skipping is allowed. Enterprises can Configure multiple Sales Processes for different record types.
Sales users must keep the Amount, Estimated Closing Date, stage, and key relationships current. Sales managers should assess Opportunity health using stage duration, task completion, and decision-chain coverage. Opportunity count alone cannot produce a reliable forecast.
For concepts and starting paths, see Opportunity Management overview and Quickly use the Opportunity Process.
Stage 5: Configure Products, Sales Scope, Pricing, and Quotes
| Item | Description |
|---|---|
| Goal | Select Products within the permitted Sales Scope, calculate the correct Price, and create a customer proposal |
| Primary inputs | Account needs, Opportunity data, Product information, and Pricing Rules |
| Key objects | Product, Item, Unit, Product Attribute, Sales BOM, Price Book, Selling Scope, and Quote |
| Key actions | Select Products, Configure attributes or bundles, match Prices, Confirm Sales Scope, Edit Quote lines, and Print or Send the Quote |
| Stage output | A Quote that can be confirmed by the Account and converted to an order |
| Primary roles | Sales representatives, quoting or commercial users, and Approvers |
| Configuration dependencies | Product and Unit modes, attributes, BOMs, Price Books, Selling Scope, Quotes, and Nonstandard Product settings |
CPQ combines multiple capabilities:
flowchart LR
A[Products and Categories] --> B[Attributes and Sales BOM]
B --> C[Selling Scope]
C --> D[Price Book]
D --> E[Quote]
E --> F[Sales Order]
- Products and Categories determine what you sell and how users find it.
- Attributes and Sales BOM determine how complex Products are configured.
- Selling Scope determines which Products the current organization, Account, or Partner can sell.
- Price Book determines the source of the base Product Price.
- Pricing Policy determines whether Discounts, price reductions, Buy-and-Get Promotions, or other Promotions apply in transaction scenarios. It is different from a Price Book.
- Quote carries these results forward and can be converted to an order after Account confirmation.
If you do not need complex configuration, use basic Products and Quotes. If you enable CPQ, Price Books, or Selling Scope, complete configuration and testing first. See Product overview and core terms and Quote overview.
Stage 6: Confirm the transaction
| Item | Description |
|---|---|
| Goal | Convert confirmed transaction terms into executable internal records |
| Primary inputs | Quote results, Contract terms, or direct order information |
| Key objects | Sales Order, Sales Order Product, and Sales Contract |
| Key actions | Create or convert orders, check Products and Prices, submit for Approval, Confirm the order, and add an Associated Contract |
| Stage output | A confirmed Sales Order associated with the Contract, Account, and downstream processes |
| Primary roles | Sales representatives, commercial or order-entry users, and Approvers |
| Configuration dependencies | Order types, Approval Processes, settlement Components, confirmation and shipping rules, and Contract Management configuration |
Common transaction confirmation models include:
| Model | Use case | Typical relationship |
|---|---|---|
| Quote to order | The Account confirms Products and Prices through a Quote | Quote → Sales Order |
| Framework Contract with batch execution | Sign a total-value Contract first, then place orders in batches | Sales Contract → multiple Sales Orders |
| Order Associated Contract | Create a specific order first, then add or associate a Contract | Sales Order ↔ Sales Contract |
| Direct order | Products and Prices are clear, and a separate Quote is not required | Account or Opportunity → Sales Order |
Order Status, Approval, and confirmation rules depend on enterprise Configuration. After confirmation, an order usually enters shipping, Settlement, or receivables. For details, see the Sales Order overview and Basic Contract Operations.
Fulfillment and receivables after the order
Inventory, shipping, and delivery
| Scenario | Handling |
|---|---|
| CRM Self-management of inventory | Manage Warehouses, inbound, outbound, transfers, stocktakes, and inventory changes in CRM |
| ERP integration | ERP handles core inventory operations, and CRM synchronizes inventory or shipping results |
| Standard shipping | Create a Shipping Order from an order or shipping request, then track logistics and receipt |
| Project delivery | Create a delivery project from a Contract or business relationship, then manage plans, WBS, costs, and progress |
Determine the inventory model before designing the connections among orders, shipping, and ERP. See Inventory Management overview.
Create receivables
| Scenario | Use case | Data source |
|---|---|---|
| Recurring Receivable | Subscription or recurring Billing | Recurring rules |
| Contractual Receivable | The transaction Amount is already clear in a Contract or order | Contract or Sales Order |
| Settlement-based Receivable | The Amount must be confirmed from actual delivery or Service results | Settlement Record |
Quick Receivable simplifies Amount calculation and allocation for one-time receivables. It is not a separate business scenario. See Receivables Management scenario comparison.
Primary responsibilities by role
| Role | Acquisition and Leads | Accounts and Opportunities | Quotes and transactions | Fulfillment and receivables | Analytics and Configuration |
|---|---|---|---|---|---|
| Marketing user | Create Campaigns, maintain Sources, and retain Leads | Monitor Lead quality | — | — | Analyze Campaign and Channel performance |
| Sales representative | Claim, follow up on, and Convert Leads | Maintain Accounts and Contacts and advance Opportunities | Select Products, create Quotes, and create or coordinate orders | Track orders and Account-side progress | Maintain accurate process data |
| Sales manager | Assign resources and check follow-up | Review key Opportunities and risks | Review Price or transaction requests | Monitor fulfillment and receivable risks | Analyze conversion, stagnation, and close results |
| Commercial or order-entry user | — | Check Account and Opportunity data | Maintain Quotes, contracts, and orders | Coordinate Settlement | Check record completeness |
| Finance user | — | — | Monitor Accounts, Credit, and transaction terms | Create or review receivables | Check Amounts and data sources |
| Warehouse or delivery user | — | — | Receive confirmed transactions | Process inventory, shipping, or delivery projects | Report execution results |
| CRM administrator | Configure intake and routing rules | Configure Accounts, Account Pools, and Opportunity Processes | Configure Products, Prices, contracts, and orders | Configure inventory, delivery, and receivables rules | Manage permissions and organize validation |
Key data and analytics loop
Process analytics depend on front-end data quality. Keep at least the following data current:
| Stage | Key data | Supported analysis |
|---|---|---|
| Marketing and Leads | Source, Campaign, Owner, Status, and conversion result | Channel performance and Campaign Lead conversion |
| Accounts | Ownership, follow-up, Deal Behavior, and Account Pool routing | Account coverage and resource use |
| Opportunities | Sales Process, stage, Amount, Estimated Closing Date, tasks, decision chain, and close reason | Stage conversion, stagnation, loss, Sales Pipeline, and win/loss results |
| Quotes and orders | Product, Price, Discount, Status, and related Source | Product sales, transaction Amount, and execution |
| Fulfillment and receivables | Shipping, Settlement, receivable Amount, and Status | Delivery progress and Pending receivables |
When viewing stage transition analysis, Sales managers should consider conversion rate, stagnation, loss, and average time in stage together. Do not judge Sales Pipeline quality only by total Opportunity Amount. See Stage transition analysis metric definitions.
Go-live and validation recommendations
Minimum viable process
Do not enable every capability at once for the first launch. Run this minimum chain first:
- Prepare a test Sales team and a small amount of test data.
- Configure one Lead intake and assignment method.
- Confirm Account Duplicate Rules, ownership, and basic permissions.
- Configure one Opportunity Sales Process with In Progress and final stages.
- Prepare basic Products and available Prices.
- Run the chain: Lead → Account/Contact → Opportunity → Quote or order.
- Check object relationships, Owners, Statuses, Amounts, and Data Access.
- Add Account Pool Reclaim, CPQ, Pricing Policy, Credit, inventory, delivery, and receivables automation as needed.
Validation checklist
- Leads enter the target Lead Pool correctly and are Claimed or Assigned according to rules.
- After Lead conversion, Account, Contact, and Opportunity records have no unexpected Duplicates.
- Opportunities enter the correct Sales Process and follow stage criteria and task constraints.
- Users can select only Products within the current Selling Scope, and the Price source matches expectations.
- After Quote-to-order conversion or a Contract Associated Order, key fields and detail relationships are correct.
- Post-order shipping, Settlement, or receivable entry points match the enterprise model.
- Sales representatives, managers, commercial users, finance users, and administrators see the data ranges allowed by the permission design.
- Analytics Reports use real stages, Amounts, Dates, and close results.
Next steps
- New users should read Sales Management quick start and select a role path.
- Sales users should see Sales representative quick start.
- Sales managers should see Sales manager quick start.
- When you encounter an unfamiliar term, see Core Sales Management terms.