Keep both versions visible
A revised option or quantity does not erase the original agreement. OrderRun keeps the new revision from your order system alongside the accepted one, so the order team can compare what changed.
Arrival time alone does not decide which revision is current. The source history records the authorised starting point, with the evidence behind it.
Review the work affected
Before replacement work goes out, every affected unit needs a decision: unchanged and compatible, not yet issued, stopped before it started, completed and held, already despatched, or needing replacement. A unit whose requirements changed needs compatibility evidence before it can stay as it is.
Work already despatched stays in its history. A reduction below what has already been fulfilled goes back to your order system's return or credit process.
Separate a change from its consequences
A cancelled balance and a remake have different meanings. OrderRun records each decision with its own units, and a remake is separate work linked to the original.
Agree the boundary with your current system
During onboarding we agree who may accept a change, where production progress comes from and how the receiving system acknowledges a revision. Completed work stays part of the history.
What OrderRun does not do
- Accept a customer's change on its own. A material amendment needs a new revision from your order system.
- Recall instructions already sent. Holding affected work does not withdraw a pack the destination already has.
- Returns or credits. They stay with your order system.
Common questions
Can it handle an order changed after release?
Yes. The new revision is kept alongside the released one, and affected work is held until a Supervisor records a decision for each affected unit. Work already completed or despatched stays in the history; editing an order cannot undo it.
Start free at one station and pay when you grow. While SmartFACT is in early access, we set your first workflow up with you.
