Early-access requests open

MANUFACTURING ORDER CONTROL

Every order clear.
Every change traced.

Turn incoming orders into work your factory can act on. Check customer-specific requirements, resolve the exceptions and send the approved revision to the right production destination.

Request early access Explore the workflow

No payment. Start with your workflow.

ORDER RELEASE EXAMPLEOrderFlow

ORDER CHECKS · ILLUSTRATION

Northway / NW-1042

Order scenario

Release checksHeld for review

Customer and optionsKnown customer; recognised option codes

Pass

Purchase order referenceRequired by the Northway acceptance rule

Missing

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 of the intended workflow. This illustration does not run the product or release an order.

Change the scenario. See what holds the order.

BUILT AROUND YOUR KNOWLEDGE

For manufacturers managing configured orders from dealers, ecommerce and repeat customers.

FROM KNOWLEDGE TO A WORKING PROCESS

Less chasing. Fewer surprises at release.

A missing reference. An unfamiliar option code. An amendment after work has started. OrderFlow brings the checks, decisions and handoffs into one controlled process, so your team can see what needs attention and why.

Bring the order together

Receive an order through an agreed data connection. Keep the original values alongside the reviewed customer, product and option mappings.

Resolve what needs attention

Apply approved acceptance and routing rules. Give each exception a reason and a clear next action before work reaches production.

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

Receive. Resolve. Release.

Customer-specific checks

Make PO references, required options and approval conditions explicit for each customer, rather than relying on someone remembering the exceptions.

Reviewed order mappings

Bring different customer codes into your agreed order vocabulary. Preserve the source values and hold unfamiliar values for review.

Rules in plain English

Use SmartFACT to draft supported conditions, review their interpretation and test expected outcomes before approving a version.

Controlled production routing

Choose destinations through approved rules. Keep the release decision and receiving system acknowledgement visible, with unresolved handoffs needing attention.

Amendments with context

Compare revisions and identify what has already reached production. Review the impact before accepting a change or releasing replacement work.

A clear fulfilment picture

Keep released, completed and despatched quantities distinct. Agree how partial deliveries and linked remakes are recorded for your workflow.

SMARTFACT, WITH HUMAN REVIEW

Your order rules. In your own words.

Describe when an order should be held or routed. SmartFACT helps prepare a structured rule using your agreed fields and actions. Your team checks the meaning and examples before approval. Ordinary processing then applies the approved rule without asking AI to decide each order.

How configuration works

EXAMPLE CONDITION

“For Northway orders, hold production release until a purchase order reference is present.”

DraftReviewRelease

Approved content. Known fields. A version you can return to.

IS IT A FIT?

Start with one
clear workflow.

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 for an initial evaluation.

The initial scope

Start alongside your existing factory software with a clearly 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.

Read the service guide →

BEFORE YOU START

A few useful answers.

Can we keep our current factory software?

Yes. Start with one agreed order source, set of checks and receiving system. We confirm the data exchange, responsibilities and recovery process during onboarding. A new connection is scoped work, not a promise of an existing connector for every ERP.

What does SmartFACT add?

SmartFACT helps express customer-specific acceptance and routing conditions in plain English. The interpretation and independent examples are reviewed before approval. OrderFlow then applies the approved version and records the reason for a hold or routing decision.

Can it handle an order changed after release?

The workflow is designed to keep the original release and proposed amendment separate. Your team checks the affected work and receiving system before accepting the change. Physical work already completed cannot simply be undone by editing an order.

Does this replace an MRP system?

The initial focus is 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.

How does early access work?

Tell us about one order workflow. We review the fit, agree the evaluation and confirm supported scope, timing, pricing and support before you commit. Requesting access is free and does not create an instant production account.

Does it connect to the other SmartFACT products?

The suite is designed around separate responsibilities: ConfigSheets for reviewed mappings, FactorySpec for product requirements, and LabelLogic, 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.

A PRACTICAL STARTING POINT