Automated Negotiation for Future Supply Chains
Before: labor-intense supplier order management
Delayed confirmations; poor end-to-end visibility.
After: always-on digital worker( SOM)
Faster cycle times, real-time visibility, reduced supply risk.
Error-prone manual ERP updates. ERP updated automatically with confirmed changes.
Table Five Deployment Patterns-2: Supplier Order Management before and after IFS Loops Supplier Order Manager( SOM).
Architectural decisions. Three architectural choices in the IFS partnership are worth surfacing because they generalize to other ERP integrations. First, the negotiation agent is implemented as a skill of the digital worker connected directly to the ERP rather than bolted alongside it: SOM lives within IFS Loops and reads and writes the same purchase orders, MRP plans and supplier-master data the human planner sees. This collapses what used to be a multi-system, multi-day human workflow into a single transaction. Second, the architecture is HITL-first: the agent is given explicit guardrails for when to act autonomously, when to flag a discrepancy for human review, and when to escalate for approval— reflecting the reality that most enterprises will not, in 2026, hand over fully autonomous commitment authority to an agent. Third, the offering is hosted on NEC ' s Inzai Data Center for Japanese customers with data-sovereignty requirements, recognizing that automated negotiation will increasingly be a regulated activity— not an unregulated technology demonstration.
IFS, is one of the world ' s largest enterprise application providers; NEC has deployed IFS solutions for over 200 companies in a partnership relationship dating to 1997. The strategic point is that automated negotiation reaches its full benefit only when it is not a stand-alone app. The negotiation agent is implemented as a skill of the digital worker and is provided in collaboration with IFS Cloud, FSM, etc. allowing it to close, post and trigger downstream replenishment in one transaction.
4.5 PATTERN 5— LOGISTICS: EXTENDING DELIVERY-DATE ADJUSTMENT AND IFS SOM( EARLY-STAGE EXPLORATION)
An important caveat up front. This section reports an exploration at the needsassessment stage. The work described here is not yet a product or service offering of NEC. We include it because it represents a natural extension of the two use cases already covered in this paper— Pattern 1( delivery-date adjustment, § 5.1) and Pattern 4( ERPembedded supplier order management with IFS, § 5.4)— outward from the bilateral factory – supplier interface into the multi-stakeholder logistics layer that physically connects them. Where Patterns 1 and 4 negotiate“ when does this purchase order close” between a buyer and a supplier, Pattern 5 asks the next question: when fluctuations occur in transit, in customs, or at a warehouse, who absorbs the change, on what schedule, and with what compensation? The architectural choices and stakeholder mappings described below should be read as a vision rather than as measurements from a deployed system.
112