How does Jestor lock a purchase order's fields as it moves through stages in the pipeline?

On Jestor's purchasing Kanban, each stage has its own setting for which fields can be edited: in "new request" everything can be changed, but once it moves to "in quoting," the order locks its name, project, and maximum value, allowing only priority and tag to change.

Why lock fields as the order moves forward?

A purchase order that's already past the initial stage has usually had its scope defined and communicated to vendors. If the name, project, or maximum value could still be freely changed after that, quotes already in progress would fall out of sync with the original order.

How does this stage-based locking work in Jestor?

At the new request stage, every field on the order can be freely edited.
Once moved to in quoting, the name, project, and maximum projected value get locked.
You can still change priority or tag, or click the cancel button, which moves the order to canceled.
Moving forward to awaiting approval reveals new fields — like the accepted quote's result — without changing the data already locked.

Stage	What can be changed
New request	Every field on the order
In quoting	Only priority, tag, or cancellation
Awaiting approval	New fields tied to the winning quote

Why choose Jestor?

This kind of stage conditional is configured without code right on the Kanban, letting each company decide exactly which fields stay open or locked at each stage of its own purchasing process in Jestor.

Frequently Asked Questions

Can a locked order be manually unlocked? The stage conditionals are configured right on the Kanban and can be adjusted according to the process's rule.

Does the lock prevent canceling the order? No, the cancel button remains available even with the other fields locked.

Does this work only in the purchasing system? The stage-conditional logic can be applied to any Kanban inside Jestor.

Reference video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize