# Receive released units from OrderRun

Connect the site, map OrderRun's fields, and accept or refuse each delivery as a reviewed import, with any FactorySpec result kept and shown.

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

Review edition: 16 November 2026

Roles: owner, author, reviewer, supervisor

Use this when your organisation also has OrderRun and its released units should arrive here for final inspection without a file. OrderRun tells CheckStation that a delivery is ready, CheckStation fetches it, and a Supervisor accepts or refuses it as an import. Four people take part: the Owner connects the site, an author prepares the field mapping, a different reviewer approves it, and a Supervisor decides each delivery. Nothing arrives until all three set-up steps are done.

## Connect the site to OrderRun

The Owner opens Team and stations. The OrderRun connection appears only while Accounts confirms that the organisation has both products. If the organisation does not have OrderRun, the Owner alone sees one sentence about it and a link, and nothing else changes.

Select Connect this site to OrderRun. It needs a second-factor check from the last five minutes. One real site of the organisation takes OrderRun's deliveries; the sample workspace never does. If the panel says this server is not registered with OrderRun yet, the site cannot be connected: SmartFACT support sets up the registration.

The connection is also the permission for OrderRun to read each accepted unit's released inspection, so OrderRun can check it before despatch. Each accepted unit's read permission is listed with the [evidence-read permissions](/manuals/checkstation/evidence-read-permissions), where the Owner can withdraw it.

To stop, select Disconnect this site and give a reason. New deliveries and messages stop, and deliveries not yet decided close. Accepted units, their records and the read permissions already given stay.

## Map OrderRun's fields to the unit import

An author opens Plans and releases and finds Units from OrderRun: field mapping. OrderRun sends each released unit with the fields its own set-up for CheckStation discloses. Some columns are fixed: the unit code is OrderRun's unit ID, the source revision is OrderRun's revision number, and the order and line come from the delivery. Enter the source namespace the units are registered under. For each of the other seven columns (item code, lot code, family, drawing revision, supplier status, customer group and finish) choose an OrderRun field by its exact name or a fixed value. Lot code may be No lot.

Use the exact values your approved plan declares for family, drawing revision, supplier status, customer group and finish, because an inspection cannot start on a unit whose context the approved plan does not cover. Agree the field names with the OrderRun Owner. Select Save draft for review.

A different reviewer reads the draft, enters a review reason and selects Approve this mapping, with a recent second-factor check. The author cannot approve their own draft. Deliveries wait until a mapping is approved, and only the approved revision maps them.

## Accept or refuse a delivery

A Supervisor opens Units and context. Under Units from OrderRun, each delivery says where it stands: waiting to be fetched, fetched and ready to preview, or could not be fetched.

Select Validate and preview on a fetched delivery. The prepared import shows the same preview a file import gives: the row count and the first 50 rows. Check the source namespace, the order codes and the family, drawing revision, supplier status, customer group and finish of the rows shown. A sentence says how many units are already here and stay exactly as they are, and how many units here OrderRun has replaced.

Select Confirm this import only when these are the units you expect. Every unit in the delivery is accepted together, or none is. A preparation lasts 15 minutes; if it has expired, or a unit changed while you were reading, validate and preview again.

To refuse, select Refuse this delivery and give a reason of up to 500 characters. OrderRun receives the reason, so describe the delivery, not people. A delivery whose mapping or validation failed is refused as such; any other refusal is your own decision. Refuse a delivery that could not be fetched, so that OrderRun knows.

## What acceptance does and does not do

Each unit is registered under the mapping's namespace, with OrderRun's unit ID as its unit code. Acceptance records no measurement, starts no inspection and releases nothing. Inspection begins when an Operator confirms the physical unit at a station, as [start an inspection](/manuals/checkstation/start-an-inspection) describes.

An Operator can scan OrderRun's unit label at the station. Both forms OrderRun prints, the bare `ORR:UNIT:` code and the address in its QR code, find the unit. Nothing looser does: a label with anything added or changed finds nothing.

OrderRun is told when an inspection of the unit starts, when it is released and when it fails. It is not sent readings, results or the names of people.

## Units sent again and replaced units

OrderRun may send a unit again in a later delivery with the same requirement. That unit stays as it is: its record, its source revision, its inspections and any release are unchanged.

OrderRun may also send a unit that replaces one already here, for a remake or an amended requirement. Confirming that delivery holds the replaced unit's open and released inspections, revokes its release, stops its label finding it and stops any new inspection starting on it. Its history stays readable. A new requirement for the same unit reaches you as a new source revision; follow the changed-context steps in [register exact unit context](/manuals/checkstation/register-unit-context).

## A unit released on a FactorySpec result

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 unit shows one.

Once a family is qualified, where OrderRun released a unit on an engineering result from FactorySpec, and OrderRun's set-up for CheckStation shares it, the unit shows FactorySpec result and its reference, such as `FS-01JC…`, under Registered units on Units and context. A unit sent again shows the result its latest accepted delivery carried.

CheckStation keeps the reference, the result, the release it came from and both of its checksums exactly as OrderRun delivered them, and the site's complete export includes them. It calculates nothing from the result and never reads FactorySpec. The result does not change the unit's context, the checks your plan selects or any limit: your approved plan still decides what is inspected and what conforms. If a dimension in FactorySpec's result seems to disagree with your approved method, raise it with the OrderRun Supervisor or whoever owns the product model. Do not change the plan to match it.

OrderRun's result is checked when the delivery is fetched. If any part of it does not hold together, the delivery cannot be fetched intact and says Not ready: the delivery is not in OrderRun's agreed format. Refuse it, so that OrderRun knows. OrderRun receives that refusal as failed validation.

## When a delivery waits

A delivery that says OrderRun is not available, could not be reached or asked for fewer requests is fetched again automatically. One that says Accounts could not confirm the organisation's products waits for Accounts, and while it waits no delivery can be accepted or refused; deliveries stay listed. A delivery whose mapping failed names the column and the OrderRun field: put the mapping right with the author and reviewer, or refuse the delivery.

For OrderRun's side of the connection, see the [OrderRun handbook](/manuals/orders).
