# Send refills to StoresFlow

Switch the StoresFlow link on, choose the paper and what an issue means, and work refills that StoresFlow reserves, picks and issues.

Source: https://help.smartfact.ai/manuals/refillflow/send-refills-to-storesflow

Review edition: 13 November 2026

Roles: owner, supervisor, stores, operator

When your organisation also uses StoresFlow, RefillFlow can send each refill of a stocked item to StoresFlow. StoresFlow reserves the stock, a stores person picks and issues it there, and StoresFlow tells RefillFlow what happened. RefillFlow keeps the request, the board, the container and the line's confirmation; StoresFlow keeps the stock. None of this works until two Owners have connected the products: nothing is sent to StoresFlow until an owner has switched the link on here and StoresFlow's owner has connected RefillFlow there, and an item is sent only when StoresFlow has mapped it. Until then every refill is supplied from the stores board as before.

## Switch it on

1. An owner opens **StoresFlow** under **Site**. If your organisation does not have StoresFlow, the page says so in one sentence. If it says "Not available on this installation", the installation has not been set up to reach StoresFlow yet.
2. Confirm it's you if you signed in more than five minutes ago.
3. Under **Send my requests there**, choose **On**, give a reason and save. RefillFlow publishes its active items to StoresFlow and shows **Items in StoresFlow**: which of your items StoresFlow has mapped, and when it last said so.
4. StoresFlow's owner connects RefillFlow there and maps each item to a StoresFlow item with the same unit. Until then nothing is sent.

## While SmartFACT Accounts does not confirm it

The link works only while SmartFACT Accounts confirms that your organisation has both RefillFlow and StoresFlow. If Accounts stops confirming that, because StoresFlow is switched off for your organisation or Accounts cannot be reached, the StoresFlow page shows none of the choices and says so. The link stays as the owner left it, but no new refill is sent to StoresFlow: each one is supplied from the stores board, with RefillFlow's refill ticket, and the line requests refills as usual. RefillFlow also stops publishing its items to StoresFlow, so **Items in StoresFlow** shows the last answer StoresFlow gave. Refills already sent to StoresFlow are still sent there, finish there and still report back. Once Accounts confirms again, new refills of mapped items go to StoresFlow as before.

## Choose the paper and what an issue means

On the same page the owner chooses:

- **Which paper stores work from**: RefillFlow's refill ticket, printed as today, or StoresFlow's pick document. One or the other, never both.
- **When StoresFlow issues a refill**: **The line records the delivery** (the default: the line scans it in, as today, so the record proves it arrived) or **Issuing it counts as delivered** (for stores staff who take refills to the line themselves; the line records nothing, so the record proves only that stores issued it for that location).

Each change needs a reason and a recent second factor and is kept in the page's history, with the number of refills in StoresFlow that stay on the choice they were requested under. A change applies only to refills requested after it.

## On the stores board

A refill of a mapped item shows:

- **Sent to StoresFlow, not yet confirmed** until StoresFlow answers. If StoresFlow cannot be reached, RefillFlow keeps sending the same request, and nothing else changes for the line.
- **In StoresFlow**, with what StoresFlow has reserved, picked and issued for it.
- **Back from StoresFlow**, with the reason, when StoresFlow refused it (for example, the item is not mapped there any more), cancelled it or closed it short, or when someone took it back. It is then supplied from the board as before.

While a refill is in StoresFlow, RefillFlow does not let anyone pick, cancel, short-close or reroute it here, so the two products never supply or close the same refill at once. Its "not accepted" escalations wait while StoresFlow has it: nobody is told it is waiting until StoresFlow sends a result or the refill is taken back, and then the board treats it as any other refill. A refill stopped by a connection problem shows under **Exceptions**; the owner sees why on the StoresFlow page.

**Take back from StoresFlow** is for stores people in the refill's queue and supervisors. Give a reason. The refill comes back to the board when StoresFlow says the request is closed, or straight away if StoresFlow cannot be reached; StoresFlow is told when it answers, so a late request creates nothing there. If stores already have the stock in hand in StoresFlow, the refill stays there until they issue it or put it back, and the board says so. To cancel a refill that is in StoresFlow, take it back first.

## When StoresFlow issues it

Each confirmed issue in StoresFlow becomes a leg on the refill, picked and dispatched in one step, with StoresFlow's lot code where the item is lot-tracked. No dispatch ticket is printed for it.

- With **The line records the delivery**, the line receives it as usual. At the station, scan the paper that came with the stock: the refill ticket or StoresFlow's pick document both carry the refill ticket's code. RefillFlow offers that refill's leg in transit. If the line scans before StoresFlow's word has arrived, RefillFlow asks StoresFlow there and then.
- With **Issuing it counts as delivered**, the issue is recorded as delivered, with StoresFlow's issue as the evidence, and the refill completes on the last part as usual.

If StoresFlow closes a refill short, RefillFlow records a shortage with StoresFlow's reason and its next review time. It has no owner until someone in RefillFlow takes it with **Change the shortage**; the board says **Shortage not owned yet**. What StoresFlow did not issue is back on the board, where stores supply it or a supervisor short-closes it by RefillFlow's own rules.

## When something cannot be applied

A result RefillFlow cannot apply, such as one for a refill already closed here, is kept and shown to owners and supervisors to resolve. It is never applied to another refill. It is kept for as long as the refill's history: where old history is deleted, it is deleted with its refill once that refill's retention period has passed, so resolve it before then. Returns stay each product's own action: a return in StoresFlow is not sent to RefillFlow, and a return recorded here is not sent to StoresFlow.
