Describe your customer checks and routing rules in plain English. OrderRun applies the approved rules to incoming orders automatically, flags what needs attention and selects the right production destination for the approved revision.
Free for real production at one station. While SmartFACT is in early access, we set your first workflow up with you.
A REQUIRED REFERENCE
“For Northway orders, hold the order until a purchase order reference is present.”
Describe→Approve→Check each order
Automatic result: An incoming Northway order without a purchase order reference is held automatically, so it cannot be accepted, released or despatched. When the updated order arrives with the reference, the check passes: a supervisor accepts it as usual, and production release still needs its required approval.
A SECOND APPROVER
“Any order for more than 40 units needs a second supervisor to approve its release.”
Describe→Approve→Check each order
Automatic result: A 60-unit Northway order is prepared for release as usual, then waits under Releases waiting for approval until a second, different supervisor approves it; only then does it go to production. One person cannot approve twice, and the 40-unit limit illustrates a policy, not a default.
CHECKS BEFORE DESPATCH
“Orders with fire doors need a passed inspection and a checked kit before despatch, and go out complete.”
Describe→Approve→Check each order
Automatic result: Each unit on such an order needs passed inspection and kit-check evidence before it can be despatched. Finished units wait until the whole order can go together, even when the customer allows part deliveries. Someone still records the despatch.
↳ Approved rules hold and route orders as written, but do not accept, release or despatch one.
WHO IT IS FOR
For manufacturers managing configured orders from dealers, ecommerce and repeat customers.
AUTOMATION FROM PLAIN ENGLISH
Your rules hold an order or choose its destination.
Tell SmartFACT when an order should be held or which destination it should use. It converts supported plain English conditions into executable rules. Check example orders and approve the version; OrderRun then applies it automatically to incoming work, recording the reason for each hold or routing decision. Your team handles exceptions and the required release approvals.
Customer and optionsKnown customer; recognised option codes
Pass
02
Purchase order referenceRequired by the Northway acceptance rule
Missing
03
Production releaseResolve the missing reference before approval
Held
The options are recognised, but Northway requires a PO reference. The order stays held with a specific action for the order team.
Fictional examples. This illustration does not run the product or release an order.
↳ Change the scenario. See what holds the order.
HOW IT WORKS
Less chasing and fewer surprises at release.
An order arrives without its reference, or with an option code nobody recognises, or it is amended after work has started. OrderRun brings the checks, decisions and handoffs into one process, so your team can see what needs attention and why.
01
Bring the order together
Receive an order from an agreed order file, the Shopify, WooCommerce or PrestaShop connector, or a paid integration with your own system built through data.smartfact.ai. Keep the original values alongside the reviewed customer, product and option mappings.
02
Resolve what needs attention
Apply approved acceptance and routing rules. Give each exception a reason and a clear next action before work reaches production.
03
Release the right revision
Approve the exact order version and record the destination and its acknowledgement. Keep later amendments connected to the work already released.
THE SERVICE
Automate the checks. Resolve exceptions. Release the right revision.
01
Customer-specific checks
Make PO references, required options and approval conditions explicit for each customer, rather than relying on someone remembering the exceptions.
02
Reviewed order mappings
Bring different customer codes into your own order vocabulary. Preserve the source values and hold unfamiliar values for review.
03
Rules in plain English
Describe customer checks and routing conditions in plain English. Test and approve the rules, then let OrderRun apply them automatically to incoming orders.
04
Controlled production routing
Automatically select destinations through approved rules. Keep release approval and the receiving system’s acknowledgement visible, with unresolved handoffs needing attention.
05
Amendments with context
Compare revisions and identify what has already reached production. Review the impact before accepting a change or releasing replacement work.
06
A clear fulfilment picture
Keep released, completed and despatched quantities distinct. Agree how partial deliveries and linked remakes are recorded for your workflow.
IS IT A FIT?
Starting points and scope.
A good starting point
You receive repeatable product orders with customer-specific formats or checks.
Your team spends time correcting, forwarding or chasing order information.
You can choose one input source and production destination to start with.
Scope
Start alongside your existing factory software with an agreed source of truth.
Your product expert or FactorySpec provides the engineering definition.
Stock allocation, finite-capacity scheduling and accounting need their own authoritative systems.
Orders from one agreed source: a file in OrderRun’s agreed format, a shop through SmartFACT Data, or your ERP or factory software through SmartFACT Data as a paid integration
The engineering definition from your product expert, or from FactorySpec where both are in use and the link is agreed at onboarding
Sends data to
Released orders to the agreed production destination, with the reason for every decision
Receiving acknowledgements and release records
Does not exchange with
WorkSteps or KitProof automatically: each takes its own job file, and a link is agreed at onboarding, not assumed
Stock, scheduling or accounting systems
Any destination it has not been given: a conflict holds the order
Every SmartFACT product keeps its own records. A link between two products is used only when your organisation has both, and is agreed at onboarding.
Yes. Start with one agreed order source, set of checks and receiving system. We confirm the data exchange, responsibilities and recovery process during onboarding. Shop orders come through the Shopify, WooCommerce and PrestaShop connectors on data.smartfact.ai, and connecting an ERP or other order system is a paid integration that we scope with you. Tell us about the system at https://data.smartfact.ai/integration-enquiry.
What does SmartFACT add?+
SmartFACT turns supported plain English acceptance and routing conditions into executable rules. After your team checks and approves them, OrderRun applies them automatically to each incoming order. Staff resolve exceptions and approve releases instead of repeating the same checks and destination lookups.
Can it handle an order changed after release?+
OrderRun keeps the original release and the proposed amendment separate. Your team checks the affected work and receiving system before accepting the change. Physical work already completed cannot be undone by editing an order.
Does this replace an MRP system?+
No. OrderRun covers order intake, exceptions, revisions and controlled release alongside existing software. Stock, purchasing and finite-capacity scheduling are separate responsibilities. We agree which system owns each record before onboarding.
What happens if the connection drops?+
OrderRun records nothing until the connection is back, and the page says whether anything may have been saved; checking the original request never records it twice, a floor scan that repeats the unit’s last one or a report sent again while the first still stands records nothing more, and a station whose control lapsed meanwhile is resumed by the operator who holds it or released by a Supervisor, with everything recorded kept, as the Help article at https://help.smartfact.ai/manuals/orders/when-the-network-drops explains.
How do we start?+
Tell us about one order workflow. While SmartFACT is in early access, we review the fit, set your first order source and destination up with you and enable your organisation through SmartFACT Accounts. Starting is free and the form does not create an account by itself.
Does it connect to the other SmartFACT products?+
The suite is designed around separate responsibilities: SmartFACT Data at data.smartfact.ai for shop connectors and maintained tables through its ConfigSheets facet, FactorySpec for product requirements, and LabelRules, WorkSteps and KitProof for their factory tasks. Specific connections and availability are agreed during onboarding; a suite listing does not mean every integration is already available.
Tell us how orders arrive, what your team checks and where approved work needs to go. While SmartFACT is in early access, we set your first order workflow up with you, free.
Free at one station. Set up with you while SmartFACT is in early access.
THE SMARTFACT SUITE
SmartFACT services and free tools.
Automate factory decisions with rules you describe in plain English. Explore focused SmartFACT services, plus free tools for everyday checks. The free tools need no account.