# Receive units from OrderRun

Connect the site, map OrderRun's fields, and accept or refuse each delivery of released units, with FactorySpec's result where a unit carries one.

Source: https://help.smartfact.ai/manuals/worksteps/receive-units-from-orderrun

Review edition: 13 November 2026

Roles: owner, supervisor

Use this when your organisation plans its orders in OrderRun and wants released units to arrive in WorkSteps without a CSV import. OrderRun sends each released order's units; a Supervisor here previews them as an import and accepts or refuses the whole delivery. Accepting issues nothing: you issue travellers as usual. Each unit's progress through its steps goes back to OrderRun's floor view, and WorkSteps sends OrderRun no evidence, readings or names of people.

An Owner connects the site once. Supervisors prepare and approve the field map, then decide each delivery. Everyone else sees the units under Work and changes nothing here.

## Connect the site

Open Team & stations as the Owner. The OrderRun section appears only while SmartFACT Accounts says your organisation has OrderRun. Without it you see one sentence about OrderRun and a link, and nothing to set up.

Select Connect to OrderRun. It asks for your authenticator if you have not used it in the last five minutes. The section then says when the site was connected and by whom.

Disconnect from OrderRun stops new deliveries and progress at once; deliveries, units and their history stay. After WorkSteps is restored from a backup, the section says the connection was made before the restore and offers Connect to OrderRun again. Reconcile the restore first.

If the section says WorkSteps cannot check OrderRun with SmartFACT Accounts just now, nothing new arrives from OrderRun or goes to it until Accounts answers. Units already received stay readable under Work.

## Map OrderRun's fields

A field map says how each delivered unit becomes one row of WorkSteps' own unit import. Three columns are fixed: job_id is the order's reference, unit_id is OrderRun's unit ID and source_revision is the order's revision in OrderRun. You place the rest.

Open Work and find Units from OrderRun, then Prepare a field map.

| Field or control | What to enter | Checks and limits | If it is refused |
| --- | --- | --- | --- |
| Source | The source these units are imported under, such as orderrun. | Not empty, at most 64 characters, no spaces at either end. | Shorten it or remove the spaces. |
| family_id and drawing_revision | Always required. For each, choose From OrderRun field and type the field's name, or Fixed text and type the value every unit should carry. | A field name is lower case letters, digits and underscores, starting with a letter. A fixed text is at most 128 characters with no line break. | Ask OrderRun's Supervisor for the exact field name its profile for WorkSteps discloses. |
| customer_code and `option.<name>` | Optional columns, added with Add a column, from a field or a fixed text in the same way. | The option name must be one your procedures use, in lower case. | Check the name in your procedure's options. |

Select Save field map. Nothing changes until a Supervisor selects Approve this field map, which asks for the authenticator if it has not been used in the last five minutes. The map in force is shown with its revision and who approved it. Only the latest approved revision is used: deliveries not yet decided are previewed again with it.

## Decide a delivery

Deliveries are listed under Units from OrderRun with the time they arrived, the order and its revision, the number of units and their state. Open one to see it headed Units from OrderRun.

| State | What it means | What to do |
| --- | --- | --- |
| Waiting to be fetched and previewed | OrderRun has told WorkSteps about it; WorkSteps fetches it within a minute or two. A reason after the state says what it waits for, such as an approved field map or SmartFACT Accounts. | Approve a field map if that is what it waits for. Otherwise wait, or ask whoever looks after this installation. |
| Ready to accept or refuse | The units are previewed as an import. | Check the preview and decide. |
| Fetch refused | WorkSteps could not take what OrderRun sent. The reason follows the state. | Select Fetch again once OrderRun has put it right, or refuse it. |
| Accepted, Refused, Replaced by a later delivery, Withdrawn by OrderRun | Decided. | Nothing; the page keeps the decision. |

Read the summary and the rows as you would for an upload, as [import and issue](/manuals/worksteps/import-and-issue) describes. Field map problems are listed above the summary and stop acceptance: a mapped field the delivery does not disclose, or a unit already accepted here under another source or order. The delivery is accepted whole or not at all.

Select Accept all, which names the number of units, to accept every unit together. A unit that is already here from an earlier delivery, with the same requirement, stays exactly as it is, work included, and is not imported again. A unit OrderRun says it replaced has its open work held for a Supervisor to cancel, and no new work is issued for it. The page says how many of each before you decide.

To refuse, type a reason and select Refuse this delivery. OrderRun sees the reason, so do not name people. The page says what OrderRun is told: the field map cannot place the delivery, the delivered units fail the import checks, or a Supervisor refused it.

## FactorySpec's result on a unit

FactorySpec's results are for evaluation only today, and OrderRun releases no unit on one. A result appears here only once FactorySpec has qualified a product family for production. Until then no delivery carries a result and the column described below does not appear.

Once a family is qualified, and if your organisation also uses FactorySpec, OrderRun may release a unit of that family on FactorySpec's result for it: the components and cut sizes FactorySpec worked out from your approved product model. OrderRun then sends that result with the unit, and WorkSteps keeps it exactly as it arrived.

Once you accept the delivery, Imported units on Work shows a FactorySpec result column with each such unit's reference, which starts FS-. A unit without a result shows nothing there, and the column appears only once some unit has one. OrderRun and FactorySpec know the result by the same reference, so quote it when you ask either of them about the unit.

WorkSteps keeps the result as a record of what the unit was released on, and nothing more. It does not change which steps the unit gets, fill an option or check anything against it, and it is not evidence that work was done. The steps still come from your approved procedure and the unit's imported values. WorkSteps does not show the components and cut sizes; read them in OrderRun or FactorySpec. The complete export holds the reference, the result, the release and their hashes for each unit that has one, beside the exact delivery OrderRun sent.

A delivery whose FactorySpec result does not hold together is shown as Fetch refused: delivery invalid. Fetching it again fetches the same thing, so refuse it; OrderRun is told the delivered units fail the import checks. Ask OrderRun's Supervisor to send the units again.

## After acceptance

Issue travellers for the accepted units as usual. The order's reference is the job and OrderRun's unit ID is the unit. At a station, scanning the unit's OrderRun label finds its work, and the unit's identification step takes the same label. Each first claim, completion and hold goes back to OrderRun's floor view, naming the station but no person, reading or result.

If OrderRun later sends a unit with a new requirement, its work here is held as for any new source revision; see [holds and handovers](/manuals/worksteps/holds-and-handovers).
