# Save, prove and activate mappings and routing rules

Keep supported rule outputs and independently expected results tied to the exact saved version.

Source: https://help.smartfact.ai/manuals/orders/mappings-and-rules

Review edition: 25 October 2026

Roles: author, reviewer

Open **Mappings and routing**. Author saves and proves configuration. Reviewer activates or withdraws it with recent authentication. Activation must be performed by a person who did not contribute to that draft version.

## Define the intended behaviour

Confirm source identities and the available fields in **Source contract**. Agree customer and item mappings, permitted destinations and the supported rule actions. A manufacturing route is not authority to change prices, stock or engineering requirements in another system.

The native draft editor labels its input **Mapping, rules and independent examples**. Use the supported structure displayed there. Unknown fields and unsupported actions are refused; do not describe free-form text as an accepted replacement for that format.

## Build meaningful cases

State expected eligibility, holds, destination, priority and other applicable outputs independently of the proposed result. Include:

- A normal order that should proceed to the agreed destination.
- Missing or unknown mappings that should hold.
- Conflicting routing conditions.
- A boundary such as a required approval or partial-despatch rule.

Keep examples fictional and within the supported source contract. Actual production data is not necessary to explain a general rule in public documentation.

## Save and prove the revision

Use **Save draft**, confirm the returned revision and run the offered proof action. Inspect its complete expected/actual outcomes. If a change is needed, save and prove again; do not approve a verbal explanation absent from the saved version.

Where plain-English proposal controls are available, describe a supported condition, inspect the proposal and explicitly adopt it. A proposal is not an active rule. Where offered, **Open in SmartFACT Automation** uses the same source-owned draft and native authority.

## Review and activate

An independent Reviewer opens the exact version, checks its current proof and uses **Activate a proven release** with a reason. OrderRun rechecks independence and proof at activation.

Check the resulting active release and inform the Supervisor. A policy change is separate from accepting a source candidate or approving factory release.

## Withdraw with an operational handover

Use **Withdraw this release** for the identified release and record why. Affected prepared approvals can be invalidated and exposed work held. Have the Supervisor account for that work; withdrawal does not send a physical stop acknowledgement from a factory.