RELEX announced new agentic operating capabilities for RELEX Open on November 2, 2026. The company describes agents sharing context across supply chain planning, merchandising and operations so one function’s recommendation accounts for its effect elsewhere. A useful evaluation question is whether a proposed promotion respects the store’s actual receiving constraint.
RELEX’s November 2 announcement
Establish the capability available to your project
The announcement describes deployment, extension and orchestration as connected capabilities. Its extension section uses future wording about customers and partners connecting external systems through APIs and MCP. Ask the provider to identify which parts of a proposed demonstration are available for your project, which are custom work and which remain planned.
RELEX’s October 28 platform overview describes shared business context and configurable business rules. It also uses future wording for an Agentic Operating System and a tool for resolving agent conflicts and recording approvals. Those descriptions are useful questions for a demonstration; they are not proof that a particular customer configuration already includes every component.
RELEX’s October 28 platform overview
Use one explicit conflict
Here is an original fictional exercise, not a RELEX test result. A retailer wants a promotion that would require 60 cases of an item on Monday. The store can receive at most 40 cases that day. For this exercise, assume no opening stock, no alternative delivery and no permission to exceed that limit. The requested delivery exceeds capacity by 20 cases.
Write those assumptions beside the request before the demonstration. Ask the presenter to show how the proposed workflow represents the promotion requirement and receiving limit, identifies the conflict and presents an alternative for a planner to consider. Do not accept a changed assumption silently: an extra delivery would create a different scenario.
One possible proposal is to revise the promotion’s scope to fit the 40-case limit. Another is to keep the original request unresolved while an authorized planner considers a different date. These are illustrative choices, not recommendations generated by RELEX or proof that either would be commercially suitable.
Review the decision record
Ask for the inputs used, the constraint applied, the proposed change and the person responsible for deciding. Keep the recommendation and any approved downstream change as separate entries. A suggestion to reduce an order does not by itself establish that a saved order changed.
For a second walkthrough, change only the stated receiving limit from 40 to 50 cases. The arithmetic gap becomes 10 cases. Ask the presenter to explain which recommendation changes and why. Record any unavailable evidence as unknown rather than filling it in from a confident explanation.
This small exercise cannot establish production reliability, integration readiness or financial return. It can make a sales discussion more concrete: the team can see whether the demonstrated workflow carries a business constraint through a recommendation and into a reviewable decision record. Confirm the applicable software scope and operating responsibilities separately before using real orders.