Feature Request - Usability Essentials - Undo single stages for PO, SO, MO, TR

daniel

The current system only allows users to undo an entire workflow instead of undoing only the specific stage where the mistake occurred.

This creates unnecessary operational pain. A small error in a later stage (e.g., a single fulfillment, receipt, invoice stage, or production run) forces users to roll back every preceding step, even when those steps are perfectly correct. This is inefficient, increases risk, and leads to avoidable rework. Additionally, a full rollback may unintentionally trigger automations running through the API, causing further disruption and compounding the issue.

Sequential stages obviously must respect their order, but that does not justify forcing a rollback all the way to the beginning when only a downstream stage needs correction.

In Manufacturing Orders, this becomes even more problematic because production runs may run in parallel, meaning the enforced all-or-nothing rollback makes even less sense.

Allowing stage-level undo would dramatically improve usability and align the system with real operational workflows.

The current full-rollback requirement is unnecessarily rigid. Granular stage-level undo is essential.

13

Comments

3 comments

  • Comment author
    Nicolas Noakes

    This would be helpful

    1
  • Comment author
    rachel

    We are finding this particularly limiting in SO's. Our staff have the ability to use the SO undo button, which undoes the entire SO back to ordering stage. Or alternatively they can use the stage undo button at pick, pack, ship. There is no way to control this in permissions, that I've found. We either allow the ability for both undo functions or none.
    Our staff are often faced with the need to undo at the pick/pack/ship stage and we allow that but we don't want them to have the ability to undo an invoice as this can cause sync issues etc across integrations like Xero.
    The same issues occur with PO's.

    We are about to trial using the production module and this concerns me as a functionality restriction.

    1
  • Comment author
    daniel
    • Edited

    @rachel: unfortunately it's the same for production… you have to be very careful. it's a pity.

    0

Please sign in to leave a comment.