Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: SmartFACT Data

Propose StoresFlow home bins from a release

Make the drawer and home-bin files StoresFlow's reviewed imports read, from a release's expected drawer, and keep their evidence.

Review edition · 18 November 2026 · For Owner, Supervisor

On this page

Each item's drawer in StoresFlow is its home bin. A release of a shop connection proposes the drawers, and each item's home bin, to StoresFlow as two files that StoresFlow's own reviewed imports read. Data makes the files and keeps a record of what they were made from. It does not change StoresFlow: StoresFlow's Owner adds the drawers and its Supervisor applies the home bins, each after StoresFlow's own preview. Nothing in a release or a table creates an item, a drawer or any stock by itself.

Before you start

You need a release of the connection, a draft or the active one, that fills the expected drawer by a form: looked up in a location table, read from the line, or given by reviewed rules (see "Roles, contracts and the three forms"). Each item comes from the release's SKU table; each drawer is what the release's form gives for it. A draft proposes too, so StoresFlow can have the home bins before the release that sends each line's expected drawer is activated. Owners and Supervisors can make proposals.

Preview the proposal

Under Propose StoresFlow home bins on the connection's page, choose the release, the role that gives the drawer and the StoresFlow store that new drawers belong to, then choose Preview the home-bin proposal.

  • When the drawer depends only on the line's key, such as a lookup of additional_data.product_sku in a location table, the preview reads every key of the release's SKU table, so the proposal is complete.
  • When it reads more of the line, such as a drawer the shop sends with each line, it reads every retained order line instead, and says so: only what the shop has sent is proposed.

The preview says how many items it proposes in how many drawers, and which drawers are shared by more than one item. Sharing a drawer is allowed; StoresFlow shows the same warning and moves no stock. A key or line is left out, and counted, when it has no item in the SKU table, the SKU table marks it not stocked, the drawer is held (for example no row matches or the row's location is empty), or the drawer is not a StoresFlow code of 1 to 80 characters.

An item reached with two different drawers holds the proposal. StoresFlow refuses a file that names an item twice, so no file is offered until each item has one drawer. Correct the table or the release, then preview again.

Record it and stage the files in StoresFlow

Choose Record this proposal. Data keeps the release, the role and its form, the table versions it read and the hash of every file. Under Recorded proposals, download the Drawers files first and give them to StoresFlow's Owner, who stages them under Reviewed imports as stockflow-locations/v1; then the Home bins files for StoresFlow's Supervisor, as stockflow-home-bins/v1. Each file holds at most 5,000 rows; a larger proposal comes in numbered parts, staged in order.

A drawer StoresFlow already has must match exactly, with the store, its code as its name, kind bin and no walk sequence, or StoresFlow refuses the file. Check the preview in StoresFlow before accepting it.

Later changes

Your first proposal for a connection, role and store offers everything. After that, a proposal offers only what changed since the last one recorded: new drawers and items whose drawer moved. An item no longer proposed is listed, because an import cannot take a home bin away; change it in StoresFlow.