PO approval step before they go out

There’s no approval step for purchase orders in D-Tools Cloud right now. “Draft Completed” is just a status — nothing’s attached to it, nobody gets told a PO is sitting there, and there’s no record of who actually cleared it to go out. Today that means manually copying every PO’s details into an email and waiting to hear back, with nothing in D-Tools itself to show it ever happened.

Here’s the workflow I’d actually want to see, and I think it’s simpler than it sounds:

Let me set up approvers in Settings — one or more people who are allowed to sign off on POs, company-wide or maybe by project if you want to take it further. Once a PO hits Draft Completed, give it a “Send for Approval” button right there. Click it, the assigned approver(s) get notified, and any one of them can Approve or Reject it.

And here’s the part that matters most to me: the approver shouldn’t need a D-Tools account to do this. You already do this for suppliers — when a PO gets emailed out, they get a clean view of it without needing a login. Do the exact same thing for approvers. Send the notification to their email with the PO details right there, and either let them approve/reject straight from the email or send them to the same kind of no-login web portal a supplier gets. A lot of the people who need to sign off on spend — an owner, a controller, whoever holds the checkbook — aren’t going to be D-Tools users day to day, and shouldn’t have to become one just to click approve. Making that require a seat is going to be the difference between people actually using this and it getting ignored.

Once it’s approved, flag the PO clearly — something like “Approved for Order” — so anyone looking at it knows it’s cleared without having to ask around. Even better, drop a task on it automatically, like “Place order with supplier,” so it shows up wherever the team’s already watching their task list instead of living only as a status nobody thinks to check.

This matters because right now the only way to get any of this is to build it outside the platform — stitching together a spreadsheet and an email chain just to get a basic yes/no on money leaving the business, with no real record of who approved what or when. For a small shop that’s a hassle. For anyone running procurement across multiple PMs and projects, it’s a real gap — and requiring every approver to be a licensed D-Tools user would kill adoption for exactly the people who need to be in the loop. You’ve already built the no-login pattern for suppliers — reuse it here.