Routing rules, review and SmartFACT

What the rules decide

For every new request, the approved rules choose:

• Which of the loop's approved stores queues receives it.
• Its priority, routine or urgent, and whether urgency needs a supervisor.
• Its due time, counted in your working hours.
• Which approved stores printer receives the ticket.
• Which escalation applies if nobody accepts it in time.

From plain English to a working rule

Choose the outcome, then describe when it applies, such as “For packaging going to Line 2”. SmartFACT turns the description into a precise condition on the fields RefillFlow supplies: item, item family, destination, loop and whether the request is urgent. You see the condition restated in plain English and which example requests it matches. A structured editor gives the same result without AI.

Predictable when the answer is unclear

Rules are checked in a fixed order, and the first rule that matches decides. Every release has one approved default for requests no rule covers. A rule that cannot be checked, for example because a field is missing, stops the request with a reason a supervisor can act on, instead of falling back to the default. Rules never change the item, quantity, destination or what a delivery must prove.

Approve once, apply on every request

Your team checks the examples and releases the rules, with a recent second-factor check. RefillFlow then applies them exactly as approved, with no AI call when anyone scans, picks or receives. Each request keeps the rules and route it started with, so a later release changes new requests only.