Delivery exceptions · Delivery Exception Pack
Handle delivery exceptions before the customer calls.
The agent detects delivery, pricing and stock exceptions in the ERP, for example SAP, assesses the impact on the customer and proposes a resolution, such as a partial delivery or a re-allocation. After approval it executes the change and informs sales and the customer.
- SAP
- Salesforce
- Microsoft
How a delivery exception gets resolved.
The agent spots the deviation early, assesses the impact and proposes a solution. Your team approves any rescheduling.
- Deviation spotted before the customer asks
- Affected orders and customers assessed
- Sales and customer informed
- Deviation in the ERP
- Impact assessed✓
- Solution proposed✓
- Rescheduling for approvalApproval
- Delivery adjusted in SAPapproved
- Sales and customer informedautomatic
Every step in the audit trail
The pack at a glance.
| Element | Delivery exceptions |
|---|---|
| Problem | Shortages, price deviations or delivery blocks surface when the customer asks. Planners look for alternatives in the ERP, Excel and email, and sales and service hear about it late. |
| Trigger | Exception from the ERP, such as a shortage in the availability check, or a regular check of open orders |
| Inputs | Order and delivery; stock per plant; delivery blocks; customer class and contract terms; open opportunities and cases in the CRM |
| Automated actions | Detect the exception, assess customer impact, check alternatives, prepare a decision brief, adjust delivery or order after approval, update the CRM and inform everyone involved |
| Boundaries | Does not replace production or demand planning. The agent works with the stock and rules held in the ERP. |
| Approvals (Guarded Autonomy) | Extra costs and date changes go to the responsible person with the reasoning. Only what your policies allow runs automatically, such as a partial delivery at no extra cost. |
| Target KPI | Time from detection to resolution; share of customers informed before they ask |
| Example systems | SAP S/4HANA or ECC, Salesforce, Microsoft 365. Other ERP and logistics systems after a case-by-case check. |
| Implementation effort | Depends on whether exceptions in the ERP are available as events or via queries, how current stock data is and how clear your prioritization rules are. 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. |
Manage exceptions before they escalate.
Today
- Shortages or price deviations surface when the customer asks.
- Planners look for alternatives in the ERP, Excel and email.
- Sales and service learn late that a delivery is slipping.
- Who decided what is hard to trace afterwards.
With Nexus
- The agent detects exceptions directly from the ERP.
- Impact and proposed resolution are ready as a decision brief.
- After approval the agent updates the ERP and informs everyone involved.
- Every decision is in the audit trail.
How does the pack resolve a delivery exception?
Shown with SAP, Salesforce and Microsoft 365.
Detect the exception
Shortage in the availability check, price deviation or delivery block: SAP reports the issue, or the agent finds it while checking open orders.
Assess customer impact
Customer class, delivery date, contract terms and open opportunities in Salesforce feed into the assessment.
Propose a resolution
The agent checks stock in other plants and proposes, for example, a partial delivery or a re-allocation.
Request approval
Extra costs or date changes go to the responsible person in Teams, with the reasoning.
Execute and inform
After approval the agent adjusts the delivery or order in SAP, updates Salesforce and informs sales and the customer.
Approvals: when does the agent decide on its own?
Automatic, as long as your rules allow it. Otherwise approval. An example:
| Situation | Decision |
|---|---|
| Partial delivery at no extra cost, customer accepts partial deliveries | Automatic |
| Re-allocation from another plant with extra costs | Planning approval |
| Delivery date slips beyond the agreed window | Sales approval |
| Order with a credit block | Stopped |
Example. You define rules, thresholds and roles in Nexus.
Example systems and objects.
This is what the connection looks like with SAP, Salesforce and Microsoft 365. Other systems are connected via suitable APIs, events or MCP, after a case-by-case check.
SAP S/4HANA or ECC
- Availability check
- Stock per plant
- Deliveries
- Delivery blocks
- Sales order
Salesforce
- Account
- Opportunity
- Case
Microsoft 365
- Teams (approvals)
- Outlook (customer updates)
Custom packs for other processes.
Not every process fits one of our four packs. For other processes we build individual agents on Nexus together with your team. They use the same agent tools, the same Guarded Autonomy policies and the same monitoring as the packs. System actions you connect once can be reused in the next process, as far as your landscape allows.
What stays the same
- Agent tools from the interfaces of your systems
- Policies: execute, request approval or stop
- Transaction-safe execution with audit trail
- Separate DEV, TEST and PROD environments
- Development in the Agent Builder, with enablement from voluro
More on SAP and custom agents.
Order processing
The step before: how the order reaches the ERP already checked.
AI agents for SAP
How agents check and change stock, deliveries and orders in S/4HANA or ECC.
Agent Builder
Where your team builds its own agents on Nexus.
Questions about delivery exceptions.
Does the agent decide on re-allocations on its own?
Only if your policies allow it, for example a partial delivery at no extra cost. Anything beyond that goes to approval with a proposed resolution.
How does the agent know which customer has priority?
From your data and rules: customer class in the ERP, contract terms, delivery dates and open opportunities in the CRM. We define the weighting with you.
Can we build our own agents?
Yes. Your team works in the Agent Builder on Nexus with the same tools and guardrails. We support this with Continuous Enablement.
Start with one process.
30 minutes · free · with a senior architect. You get a verbal initial assessment and concrete next steps.