Quoting & pricing · Quote-to-Order Pack
Quoting & pricing: quotes with pricing and availability from the ERP.
Sales requests the quote in the CRM, for example Salesforce. The agent pulls pricing and availability from the ERP, such as SAP, checks discounts against your rules and asks for approval only where it’s needed. Once the customer accepts, order processing takes over.
- Salesforce
- SAP
- Microsoft
How a quote comes together.
Prices and availability come straight from the ERP. Discounts within your range go out immediately, anything above goes to approval.
- Current prices and availability from SAP
- Quote inside the sales process, no copy and paste
- Special terms only with approval
- Quote request by email
- Prices and availability fetched✓
- Quote created and sentautomatic
- Customer asks for 15% discount
- Special discount for approvalApproval
- Quote with special terms sentapproved
Every step in the audit trail
The pack at a glance.
| Element | Quoting & pricing |
|---|---|
| Problem | For every quote, sales asks inside sales for prices and delivery dates. Discount approvals sit in inboxes, and at order time the quote often doesn’t match the ERP. |
| Trigger | Quote request on the opportunity in the CRM |
| Inputs | Products and quantities; account and business partner; framework agreements and previous terms; pricing and availability from the ERP; requested discount and payment terms |
| Automated actions | Bring the context together, get pricing and availability per line item, check the discount, create and send the quote in the CRM, hand the accepted quote to order processing |
| Boundaries | Replaces neither your CPQ nor your pricing strategy. The agent does not release terms outside your rules on its own; negotiation stays with sales. |
| Approvals (Guarded Autonomy) | In the example, a special discount above 10% or a quote value from €50,000 goes to the sales manager; from €250,000 or with non-standard payment terms it goes to finance and sales. For a blocked customer, the agent stops. |
| Target KPI | Time from quote request to quote sent; share of quotes without a manual price inquiry |
| Example systems | Salesforce (including CPQ), SAP S/4HANA or ECC, Microsoft 365. Other systems after a case-by-case check. |
| Implementation effort | Depends mainly on how ERP pricing and availability can be reached via interfaces and how clearly your discount rules are documented today. Starts with a fixed-scope proof of value. |
| Maturity | Demo on request. For your landscape, we measure in the proof of value with your systems. |
Less waiting for prices and approvals.
Today
- For every quote, sales asks inside sales for prices and delivery dates.
- List prices in the CRM differ from ERP pricing.
- Discount approvals go by email and get stuck.
- At order time it turns out the quote and the ERP don’t match.
With Nexus
- Pricing and availability come straight from the ERP into the quote.
- Discounts within your rules go through immediately.
- Special terms reach the responsible person, for example in Teams or Outlook, with the reasoning attached.
- The accepted quote matches the ERP and becomes an order without re-keying.
How a quote is created in the pack.
Shown with Salesforce, SAP and Microsoft 365.
Request the quote
Sales starts the quote on the opportunity in Salesforce, with products and quantities.
Load context
Account, SAP business partner, framework agreements and previous terms are brought together.
Get pricing and availability
The agent uses SAP pricing and the availability check for each line item.
Check the discount
Requested discounts and payment terms are checked against your policies.
Request approval
If a term falls outside the rules, the request goes to the decision-maker with margin and reasoning.
Create the quote
The quote is generated in Salesforce, documented and sent to the customer.
Hand over to order processing
Once the customer accepts, the order processing pack starts with validated data.
Approvals: discount policies with Guarded Autonomy.
Automatic, as long as your rules allow it. Otherwise approval. An example:
| Situation | Decision |
|---|---|
| List price or discount up to 10%, quote value below €50,000 | Automatic |
| Special discount above 10% or quote value from €50,000 | Sales manager approval |
| Quote value from €250,000 or non-standard payment terms | Finance and sales approval |
| Blocked customer: credit or order block in the ERP | Stopped |
Example. You define thresholds, roles and exceptions in Nexus.
Optional: preparation for sales.
Beyond the quote itself, the pack helps sales prepare. These functions are optional and can be switched on individually. Sales reviews and sends anything that reaches the customer.
Optional in the pack
- Account research from CRM history and ERP revenue before a customer meeting
- Drafts of quote cover letters and follow-ups for sales to review
- Reminders for open quotes shortly before they expire
Example systems and objects.
This is what the connection looks like in a landscape with Salesforce, SAP and Microsoft 365. Other systems are connected via suitable APIs, events or MCP, after a case-by-case check.
Salesforce
- Opportunity
- Quote
- Account
- Products
SAP S/4HANA or ECC
- Business partner
- Pricing
- Availability check
- Credit limit and blocks
Microsoft 365
- Teams (approvals)
- Outlook (approvals, sending)
Before and after.
Order processing
The next step: the accepted quote becomes the sales order.
AI agents for Salesforce
What agents handle in Sales Cloud and CPQ when ERP data is needed.
Questions about quoting & pricing.
We use Salesforce CPQ. Does the pack replace it?
No. The pack uses your existing quote objects and adds ERP pricing, availability and approval rules. We define which fields the agent reads and writes during implementation.
Who decides which discounts go through automatically?
You do. You set the limits as policies in Nexus, for example per role, customer group or product line. Every automatic decision and every approval is recorded in the audit trail.
Do we also need the order processing pack?
No, each pack works on its own. Together they cover the stretch from quote to sales order, because the accepted quote already contains validated data.
Start with one process.
30 minutes · free · with a senior architect. You get a verbal initial assessment and concrete next steps.