Write the rule once. See it tested, approved and applied.
A business rules management system keeps the decisions a business makes again and again, such as which checks a unit needs, where an order goes or who must approve a purchase, outside the software, so the people responsible can write, test, approve and change them. SmartFACT Automation is that system for the SmartFACT suite. Your team describes a rule in plain English or builds it in a structured editor, tests it against agreed examples, has it reviewed and releases it to the products that apply it, with every version, approval and decision on record.
No payment or self-service sign-up. Start with a demonstration.
AUTOMATION WORKSPACESmartFACT Automation
POLICY RELEASE · ILLUSTRATION
Before a rule reaches production
Release checksQuestion
01
RequirementHold kits for priority customers without a PO
As written
02
Proposed ruleWhich field marks a priority customer?
Asked
03
ReleaseCannot be submitted with an open question
Waiting
An unclear requirement becomes a question for your team. The AI does not guess which customers are meant.
Fictional examples. This illustration changes no rule and contacts no product.
↳ The proposal, the tests and the approval stay separate.
BUILT AROUND YOUR KNOWLEDGE
For manufacturers running one or more SmartFACT products, where office staff decide the checks, kit contents, routes, stores policies and approvals that the floor relies on.
FROM KNOWLEDGE TO A WORKING PROCESS
The rules live in people’s heads, spreadsheets and a different settings screen in every product.
Nobody can see the whole set, a change is tried on real work, and when a job is held it takes a phone call to find out why. Automation gives every rule one home: its purpose, owner, agreed examples, approvals and the products running it.
01
Describe it, or build it
Write the requirement in your own words, or pick the decision, outcome and conditions in the structured editor. Automation asks about anything it cannot settle, such as which field identifies a customer group or what missing data should mean.
02
Test and review
Check the rule against examples your team agreed before seeing the result, including boundaries, missing data and conflicts. A reviewer sees exactly what changes and approves it with a fresh sign-in. Where a product requires it, that reviewer must be someone else.
03
Release and explain
Each product adopts the approved release and confirms it is running it. From any held job or decision, open the exact rule version and the facts it used, and follow the change history back to who approved it.
THE SERVICE
Every rule written, tested and approved in one place. Every decision explained.
01
Plain English or structured
AI turns a written requirement into a proposed rule with a plain restatement. The structured editor builds the same rule without AI, with the same checks and review.
02
Questions, not guesses
A requirement that is unclear becomes a specific question. AI never fills in an engineering limit, a fact or a permission from general knowledge.
03
Tests agreed in advance
Acceptance cases come from your team, regression cases from the approved release and suggested cases stay suggestions until someone sets the expected result.
04
Independent review
Approval names who contributed and who reviewed. A self-review is refused where the product requires a second person, and owner status alone cannot approve a production rule.
05
One definition, several products
Define a classification such as ‘enhanced verification’ once and use the same approved version in WorkSteps, KitProof and other products. Each product shows which version it runs.
06
Every decision explained
A held job opens to the rule version and recorded facts that held it, not today’s rules rerun over old data. Policies, approvals and decisions export in full.
AI DRAFTS. PEOPLE APPROVE. PRODUCTS APPLY.
Describe the requirement. Get a rule you can check.
AI is used only to help write rules. It reads your requirement, the decisions each product allows and the context you choose to share, then proposes a rule with a plain restatement and examples. A person checks it, a reviewer approves it, and each product applies the approved rule exactly, with no AI call when the decision is made. If the AI service is unavailable, approved rules keep running and the structured editor still works.
“For customer 00017 and for returned units, add the approved inspection step and the serialised component to the kit.”
Describe→Test and approve→Apply in each product
Automatic result: WorkSteps adds the approved inspection step and KitProof adds the serialised component for customer 00017 and returned units, each through its own reviewed release. Customer 17 is not 00017, so that work is unchanged. These values illustrate a policy, not a default.
IS IT A FIT?
Start with one clear workflow.
A good starting point
One or more paid SmartFACT products whose rules change as customers, products and suppliers change.
Office authors who know the requirement and a reviewer who can approve it.
A wish to see, test and explain every automated decision rather than trust a settings screen.
Scope
Not a script runner, SQL console or general workflow tool. Rules choose only the outcomes each product allows.
Not a stock, quality, order or shipment ledger. Each product keeps its own records and checks.
No AI decisions in production and no rule that changes itself.
No instant change across every product at once. A rule is active in a product when that product confirms the exact release.
Each SmartFACT product runs its own approved rules. Automation is where those rules are written, tested, approved and explained, so the products keep working even if Automation is unavailable.
Does AI make decisions on the shop floor?+
No. AI helps write a proposed rule. Once a reviewer approves it, the product applies the rule exactly as approved, with no AI call when the decision is made.
Can we use it without AI?+
Yes. The structured editor builds the same rules with the same tests and review, and you can switch AI proposals off.
Who can approve a rule?+
A reviewer with access to every product the rule changes, using a fresh sign-in. Where a product requires independent review, the reviewer must be someone who did not contribute to the change.
Which products does it cover?+
Every paid SmartFACT product, from LabelRules and WorkSteps to StoresFlow, ParcelOffice and SmartFACT Purchasing, plus PrintStation’s delivery settings. The free tools keep their own local, no-account model.
How is Automation priced?+
Automation is included with the paid plan of every SmartFACT product, and is also available on its own. Trial scope, duration, support and any charges are agreed before access.
Is it like Power Automate or Zapier?+
No. Those connect applications in general. Automation manages the business rules inside SmartFACT products, with tests, approvals and an audit record for each one.
Which rules would you like to manage in one place?
Tell us which SmartFACT products you use or are considering and which decisions you set by hand today. We arrange a demonstration and discuss an invited trial that starts with one real policy.