A refund succeeds but its response times out.
Detect: Payment lookup finds the original operation key with a completed refund.
Recover: Return the existing receipt and never create a replacement key for the same approved action.
E-commerce · INDUSTRY BLUEPRINT
Order recovery and returns coordination
Coordinate order status, shipment evidence, and return eligibility before committing a customer-approved resolution.
Explore in the architecture studioThe business situation
Illustrative reference architecture. Validate requirements for your organization.
Illustrative architecture: An online merchant receives a support request for an order split across two warehouses. One parcel is late, another item is damaged, and a promotion complicates refund allocation. The proposed system prepares specific resolution options without inventing shipment status or refund eligibility.
Problem
A simple refund chatbot can cancel the wrong order line, duplicate a refund after a timeout, or promise replacement inventory that is already reserved. Customer messages and uploaded images also contain untrusted instructions that must not control tools.
Why a multi-agent system?
Separate order reconciliation, shipping investigation, policy retrieval, and resolution drafting. A deterministic monetary calculator and transactional adapters own amounts and inventory reservations; agents explain the options and surface unresolved evidence.
Intended outcome
The intended result is a reviewable operational decision with source evidence and explicit ownership. Compare handling effort and customer recontacts while auditing financial effects. Faster response generation is useful only when customers receive accurate per-item status and the underlying order remains financially consistent.
Specialist agent team
Order reconciler
Resolve line items, payments, promotions, and prior adjustments.
Tools
- Order management read API
- refund allocation calculator
Authority boundary
Cannot issue refunds or modify paid order lines.
Shipment investigator
Compare carrier scans, delivery evidence, and warehouse handoff events.
Tools
- Carrier tracking adapter
- warehouse event query
Authority boundary
Cannot assert delivery from an estimated date alone.
Returns policy agent
Retrieve terms effective for the item, purchase date, and market.
Tools
- Policy index
- product restriction lookup
Authority boundary
Cannot waive restrictions or decide disputed damage evidence.
Resolution coordinator
Draft replacement, return, or investigation options with exact prerequisites.
Tools
- Support case draft API
- reservation quote API
Authority boundary
Requires customer confirmation and policy-authorized approval before consequential actions.
Enterprise systems
Order and payment services
Own purchased quantities, refundable balances, adjustments, and payment operation identifiers.
Warehouse and carrier systems
Provide fulfillment events and separately versioned shipment status.
Customer support platform
Retains customer identity, approved correspondence, resolution consent, and escalation ownership.
Architecture diagrams
flowchart LR
N0["Order recovery and returns coordination"]
N1["Order reconciler"]
N2["Shipment investigator"]
N3["Returns policy agent"]
N4["Resolution coordinator"]
N5["Evidence ledger"]
N6["Human decision"]
N7["Authorized adapter"]
N0 --> N1
N0 --> N2
N3 --> N4
N1 --> N4
N2 --> N4
N4 --> N5
N5 --> N6
N6 --> N7sequenceDiagram
participant O as "Case orchestrator"
participant S as "Order and payment services"
participant H as "Accountable reviewer"
O->>S: Load refundable order balance
O->>H: Present exact refund proposal
H-->>O: Confirm line and amount
O->>S: Submit approved operation key
S--xO: Response timeout
O->>S: Query original operation
S-->>O: Existing refund receiptRuntime flow
- 1
Authenticate request
Bind the customer to the order and requested lines before retrieving payment or address information.
- 2
Read order snapshot
Fetch order revision, remaining refundable balance, and existing return or refund operations to avoid duplicate work.
- 3
Investigate each parcel
Parallelize shipment checks while preserving the distinction between estimated, scanned, delivered, and unknown states.
- 4
Calculate valid options
Use current inventory and deterministic amount allocation; attach the policy clause and expiry of each option.
- 5
Confirm resolution
Show the customer and support reviewer exact items, amounts, fees, and next steps; preserve unresolved damage disputes for staff.
- 6
Execute and reconcile
Submit approved actions with stable operation keys, query uncertain payment results, and report each order line's final or pending state.
Failure recovery
Replacement stock disappears during confirmation.
Detect: Reservation service rejects the previously quoted stock version.
Recover: Refresh options and request new confirmation rather than silently substituting another product.
Security & decision boundaries
- Validate customer ownership independently of order numbers pasted into chat.
- Keep refund arithmetic and eligibility checks outside model-generated prose.
- Bind approval to order lines, currency, amounts, and shipping destination.
- Treat customer uploads as evidence with no authority to change system instructions.
- Separate promised resolution from pending carrier or payment confirmation in responses.
Operational metrics
Measurement definitions, not promised improvements.
Resolution preparation time
Elapsed time from authenticated request to valid options, segmented by split-order complexity.
Refund duplication rate
Duplicate financial effects per approved refund operation, reconciled against payment records.
Promise accuracy
Audited customer commitments supported by current inventory and policy evidence divided by audited commitments.
Partial resolution backlog
Open order lines awaiting external confirmation after another line has completed.
Architecture tradeoffs
| Decision | Benefit | Cost |
|---|---|---|
| Line-level workflows | Support mixed outcomes within split orders. | Require explicit partial-success state and customer communication. |
| Live inventory reservation | Avoids promising unavailable replacements. | Adds expiry handling and temporary stock contention. |
| Policy-grounded options | Keeps resolution terms inspectable. | Unusual disputes still need experienced support staff. |
Rollout plan
Synthetic transaction replay
Support staff validate split shipments, promotions, partial refunds, and duplicate-payment recovery.
Draft support pilot
A small queue evaluates factual accuracy and customer ownership enforcement without financial writes.
Approved resolution launch
Selected return types enable execution after timeout reconciliation and expired-reservation tests pass.