Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: StoresFlow

Export evidence for LotTrail

Download this site's lots, supplier receipts and issues as files LotTrail admits, and admit them in order.

Review edition · 18 November 2026 · For Owner, Supervisor

On this page

Use this when your organisation traces lots in LotTrail and wants StoresFlow's records there: which lots were received against which purchase documents, and which lots left stores for which jobs, with the quantities. StoresFlow writes them as files LotTrail admits as they stand. It sends nothing and connects to nothing: you download the files here and a LotTrail Supervisor admits them there, one at a time. You need the Owner or Supervisor role, at the real site, and a second factor verified in the last hour (StoresFlow asks for it in place if it is older). The export works whatever your plan, including after it has ended.

Register this site in LotTrail once

Open Health and find Evidence for LotTrail, at the end of the page. Under To register this source in LotTrail it shows four values, named as LotTrail's Create a declared dataset form names them:

  • Source instance ID, such as storesflow:01JC3Z5K8Q4N7R2T6V9X0B1D3F. It is this site's, and it never changes.
  • Source generation, which is the history: 1 to begin with.
  • Declared scope code: storesflow.lottrail-evidence/v1.
  • Relationships this source can record. Tick exactly context reference, and nothing else.

Copy each value with its Copy button and give them to the person who creates the dataset in LotTrail, with the data owner and permitted readers your organisation chooses. A dataset in LotTrail keeps these values for good. LotTrail's own steps are in admit a SmartFACT product's export.

Export new records

Select Export new records. StoresFlow prepares the export within about a minute; select Check again to see it. The first export holds every lot this site has received from a supplier or issued, the purchase documents and jobs they name, and each receipt and issue of a lot; each later export holds what is new since the one before, and corrections for anything that changed. Records are numbered from 1, with no gaps, and every file says which numbers it holds.

Before the export is written, StoresFlow checks that you are still signed in and still hold the Owner or Supervisor role here. If the export did not finish, the panel says why. No record was given a number, so the next export starts where that one did. While the site is under a restore hold, nothing new is exported; parts already written can still be downloaded.

A busy site's first export is several parts, each a file. Select Download on each part. Each file's name starts storesflow-lottrail-, sorts in the order the parts are admitted, and is kept here for a day. After that, Write again writes the same file, byte for byte, with the same checksum.

Admit the parts in order, one at a time

The panel lists the exports newest first, and each export's parts in order. Start with the oldest export and with part 1 of each. Every part says which part to admit before it. In LotTrail, stage one part, compare its File checksum with the Checksum the panel shows for that part, accept it, and only then stage the next.

LotTrail does not stop a part being admitted out of turn. If you stage a part that skips records, LotTrail warns that records are missing and asks for a second tick before it will accept the file. Do not tick it for a StoresFlow part: admit the earlier part first.

A part marked Corrections replaces records already exported. Admit it in its place in the order, like any other part.

When a part was skipped or lost

If a later part was accepted in LotTrail before an earlier one, LotTrail refuses the earlier part as it was written. Open If a part was skipped or lost, choose the skipped part and the latest part LotTrail has accepted, and select Write this part. The file holds exactly the skipped part's records, stated as the later part stated its coverage, so LotTrail accepts it and the gap closes. It is listed under the parts written that way.

If a part's file is no longer kept here, select Write again on that part.

When the history starts again

After this installation is restored from a backup, the record numbers given since that backup cannot be trusted, so the panel asks you to start the next history before anything more is exported. Select Start history 2 (or the next number). Everything is then exported again from record 1 under the new source generation, and LotTrail needs a new dataset with that generation: register it as before. The same happens if StoresFlow's mapping ever changes its scope code.

You can also start a new history yourself, with a reason, under Start a new history, for example when a dataset in LotTrail cannot be put right. Do this only when the LotTrail data owner has agreed, because it means a new dataset and admitting every part again.

What the export says, and what it does not

A lot is stated once, under its supplier namespace and item code, with its lot code. A purchase document is the document a receipt was recorded against, under the name typed beside it, such as purchase/manual or purchase/purchasing. A job is the job a demand named, such as job/manual, so a purchase order and a job with the same number stay two things. A receipt links the document to the lot, with the quantity received in the item's own unit; an issue links the lot to the job, with the quantity issued less what came back. When a named receipt correction changes what was received, or stock comes back from an issue, the next export corrects the quantity. A lot that came back in full keeps its link to the job with quantity 0, because it did leave stores for that job.

The export never says that a lot was used in a job or went into a product: an issue records that stock left stores, not that it was consumed. It holds no untracked items, no opening stock, no moves between bins, no counts or adjustments, no reservations or picks, no expiry dates and no people. In LotTrail, start from a lot to see the jobs it left stores for, from a job to see the lots issued to it, or from a purchase document to see the lots received against it. LotTrail's view of physical inputs and outputs has no answer from StoresFlow, because StoresFlow does not record them.

A record whose values a LotTrail file cannot hold, such as a supplier namespace and item code together longer than 120 characters, is left out and listed on the panel with the reason, with any receipt or issue that names it. Every file from then on says the history is incomplete. Correct the record if you can; it is tried again at every export.

How much LotTrail can investigate

LotTrail refuses an investigation over 50,000 events across the datasets chosen. A StoresFlow lot with one receipt and three issues is about five events, so that is about 10,000 such lots, and fewer when StoresFlow's dataset is investigated together with another. The panel shows how many events this history has exported, so you can compare.