Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: RefillFlow

How to route one family to a queue, and escalate

Use a starter rule to send one family's requests for one location to its own stores queue, and escalate unaccepted ones.

Review edition · 13 November 2026 · For Author, Reviewer

On this page

Some material should go to a stores queue of its own, such as packaging for a packing line, and nobody should leave its requests waiting. The starter rule Route one family to a queue, and escalate adds one rule that sends one item family's requests for one receiving location to the stores queue you choose, and an escalation policy that gives the supervisors a task if nobody accepts a request in time.

Use the starter rule

You need the Author or Reviewer role at the site, and a saved draft: the card copies the draft's default outcome. Nothing changes for new refills until a reviewer activates a release with the rule.

  1. Open Rules and releases. Starter rules comes before the draft.
  2. Find Route one family to a queue, and escalate. It is under Recommended and Where requests go; you can also type a word from its title in Search starter rules and Help.
  3. Fill in the blanks in the card's sentence, "For … going to …, send the request to …, and give the supervisors a task if nobody accepts it within … working minutes.":
    • Item family: one of this site's item families, such as packaging.
    • Receiving location: one of this site's receiving locations, such as LINE-2 (Packing line two).
    • Stores queue: one of this site's enabled stores queues, such as PACK (Packing Stores).
    • Working minutes: 1 to 10,080; the card starts at 30.
  4. Choose Use this rule. The button waits until every blank has a value.

If the draft below has changes you have not saved, the cards wait: save the draft, or reload the page to discard the changes, first.

What is added

The draft gains a new revision with two additions, saved exactly as you would save them by hand:

  • An escalation policy named "Not accepted within 30 working minutes: supervisors", with one stage: while the refill is not accepted, 30 working minutes after the request, a task for the supervisors.
  • A rule after every rule the draft already has, as Add a rule places one. It matches when the item family and the receiving location are the ones you chose. Its outcome is the draft's default outcome with your stores queue and the new policy. A ticket for that queue prints by the queue's own approved print mapping.

The rule belongs to the decision which stores queue gets a refill, its priority and its due time. Because it comes last, any earlier rule that also matches still decides first: change the precedence in the draft if you want this rule to decide first.

On Free, a rule keeps the default queue and names no escalation; Pro allows both. Under What the plan must allow, the review says what the release needs, and activation is refused where the plan does not allow it.

Check the examples

A card saves no example: the examples are your own statement of what the release must decide. After the card, the page names the new rule and offers examples prepared from this site's loops for that family and location, each expecting the new rule to decide it. Choose Add the prepared examples, check each one, then choose Save draft. The proof also needs an example the default decides, an urgent request and an invalid or missing input, as for any release.

Release it

Choose Prove the saved draft and read the review: what changed against the active release, every input of every loop, and any example that disagreed. Then a reviewer activates it, as for any release; see rules and releases.

If the card is refused

  • The card has changed since the page was read, or a record it names was retired. Choose it again.
  • The draft already has a rule that tests exactly this. Change that rule instead. A draft that already sends packaging for LINE-2 to Packing Stores refuses the card with those two values for this reason.
  • A loop the card names may not be supplied by that stores queue. Allow the queue on the loop on Loops first, or choose another queue.
  • Save the draft with its default outcome first. The card copies it.

Nothing was added after any of these. To remove the rule later, delete it and the examples that expect it from the draft, then prove and activate as usual. A rule from a starter rule is an ordinary rule: you can loosen it or remove it in any later release.

Arriving from SmartFACT Automation

Where SmartFACT Automation is connected, choosing Use this rule on this card there brings you to Rules and releases with the card filled in as you left it. Nothing is added until you choose Use this rule here. If you had to sign in first, RefillFlow keeps the card for ten minutes and opens it once you are in.