# Send StoresFlow's events to other SmartFACT products

What StoresFlow tells SmartFACT Data's floor boards and ParcelOffice's wirings, the notice under Finish pick, connecting ParcelOffice and the Events page.

Source: https://help.smartfact.ai/manuals/storesflow/events-to-other-products

Review edition: 18 November 2026

Roles: owner, supervisor, operator

StoresFlow tells your other SmartFACT products what happens on its floor as it happens: a pick ticket sent to the printer, a pick opened, a line picked or short, a pick left for later and a pick finished. A product receives these events only while it subscribes to them, and only once its link with StoresFlow is connected. SmartFACT Data uses them for its floor boards, and ParcelOffice for a wiring you approve there, such as booking a sample's label when its pick is finished. StoresFlow starts nothing in another product by itself, and no event names a person or a customer.

## What StoresFlow tells other products

| Event | When |
| --- | --- |
| Pick ticket sent to the printer | PrintStation's print system accepted a shop order's pick ticket, or someone confirmed it came out. Nothing can see paper, so a ticket counts as printed only once it is scanned. |
| Pick ticket not printed | The ticket became **Not printed**, with the reason StoresFlow shows. |
| Pick ticket output uncertain | The ticket became **Output uncertain**, with the reason. |
| Pick opened | A picker scanned or typed the ticket's number and the pick opened on their device, new or left open earlier. |
| Pick line confirmed | A line was picked in full or short, by a scan, **Picked**, **Fewer**, **Picked all** or a Warehouse override. |
| Pick left for later | The picker chose **Leave for later**, or scanned a Leave card. |
| Pick finished | Every line was picked or short and the pick was finished, by **Finish pick** or a Finish card, with the place of the card and how many lines were confirmed by a scan and how many by hand. A wiring can act only on picks with no line confirmed by hand. |

Each event names the order by its number, the one SmartFACT Data gave it, and the pick or ticket it is about. A person's event carries their SmartFACT identity and the station they work at, never their name.

## What it shows on floor boards

SmartFACT Data's floor boards follow each shop order across the floor. From StoresFlow a board shows when the pick ticket was sent to the printer, a ticket that was not printed or whose output is uncertain, the pick being picked with its lines done of lines to pick, a short line, a pick left for later, and the pick finished with the place it was finished. A board shows the station, never the picker.

Data's link with StoresFlow is the site's approved sales channel from Data: a board starts receiving StoresFlow's events once the Owner has published it in Data. Nothing more is set up in StoresFlow.

## What a press can start in ParcelOffice

A wiring is a rule your organisation approves in ParcelOffice: when a pick is finished in StoresFlow, and its condition holds, ParcelOffice does its action, such as booking the shipping label at the despatch box. The wiring lives in ParcelOffice, with its checks, its limits and its own record of each run. StoresFlow only tells ParcelOffice that the pick was finished.

While a pick is open on the handheld and ParcelOffice holds a live wiring for this site, a line under **Finish pick** says what the press may start there. Where ParcelOffice answers StoresFlow's question, the line is in its own words, such as "Will book Royal Mail Tracked 24, about £3.40, on the company's account", or a "may" with its condition while lines remain; where SmartFACT Data is holding what that product needs for this order, the line says the work will wait and why, such as "Label will wait: customer code missing in Data"; a line about a cost is in bold, and a wiring whose condition already fails shows nothing. Otherwise the line reads "May start work in ParcelOffice". **Finish pick** works the same whatever the line says, and before it appears.

## Connect ParcelOffice

1. Open **Connections** under Site. The Owner sees **ParcelOffice** there when the organisation has both products in SmartFACT Accounts, or one sentence about ParcelOffice when it does not.
2. Give a reason and choose **Connect ParcelOffice**. Recent Accounts verification is required.
3. In ParcelOffice, connect StoresFlow with the **Site ID for ParcelOffice** this section shows. A wiring's condition can name a sales channel by the ID listed under it.

Once ParcelOffice subscribes, the section says how many subscriptions it holds and which of its sites the events go to. **Disconnect ParcelOffice**, with a reason and recent verification, ends every subscription it holds here, and nothing more is sent to it.

## The Events page

**Events** under Site, for the Owner and supervisors, lists what StoresFlow sends, the facts each event carries, and which product receives it and why: a floor board, a wiring or a connection. Below are the events waiting to be sent, the latest sent and any **parked**.

StoresFlow sends each event straight after the work that made it true, and tries again on its own if the other product does not answer, for up to a day. An event the other product refuses, or that got no answer for a day, is parked and waits for a person. When the other product has been put right, a supervisor chooses **Send again**: the same event goes again. A parked event is never lost, because the other product can also read every event it subscribes to.

When events wait because StoresFlow has no event key yet, or because sending to other products is switched off for this installation, the Events page says so: these are your administrator's to set up. **Health** shows whether **Events to other SmartFACT products** are working and how many events are parked.
