EARLY-ACCESS GUIDE · UPDATED 29 September 2026
Order rules, AI and human approval
How plain English rules automate order checks and destination selection, with separate release approval.
This guide describes the service scope. Access and the workflow supported for your site are confirmed during onboarding.
Describe supported conditions
Use known order fields and permitted actions. A request outside the supported vocabulary needs clarification. AI assists authoring; it is not a substitute for product engineering knowledge or an authority to approve arbitrary operations.
Review meaning with independent examples
Check missing values, overlapping matches and boundary cases as well as normal orders. Expected results come from the people who own the process, not from accepting whatever a proposed rule produces.
Apply the approved rules automatically
OrderFlow automatically evaluates each order against the approved acceptance and routing rules. It identifies holds and destinations and records the rule and mapping versions behind each result. Staff handle exceptions and required approvals. A later rule change does not silently reinterpret an earlier release, and routine checks need no fresh AI response.
Treat release as a separate decision
Passing checks establishes readiness. Approval, transmission, acknowledgement, production completion and despatch are separate events. Agree who can perform each action and which system supplies its evidence.