A purchase order has sat with one approver for four days. The buyer thinks it’s moving.
Business Central sent it to the right approver under the rules you set. OpsGrid puts every PO still waiting, the approver it sits with and the days it has waited into one Teams card, for the person who has to chase them.
Supplier deliveries to US manufacturers were “slower in October for the 11th consecutive month”, and production-material lead times averaged 87 days (ISM October 2026 Manufacturing PMI Report). A PO that waits four days for a signature turns an 87-day lead time into 91.
Two purchasing signals, live in the beta today.
Purchase order approval status your team checks PO by PO today. OpsGrid checks Business Central on a schedule, every 6 hours as planned, and lists every PO still waiting on an approver.
- POs stuck in approval Each PO waiting on an approval step, the approver it sits with, and the days it has waited
- Open POs by vendor Every open purchase order, grouped by vendor
OpsGrid Beta · Dynamics 365 Business Central · sample data
Waiting POs surface in Teams, with a name on each.
Business Central decides who signs. Nobody watches how long they take.
BC’s approval workflow already handles amount limits, the approver chain, due dates and delegation, and OpsGrid leaves those rules alone. It puts every waiting PO, its approver and its days waiting in front of one named person in Teams, and logs what happened next.
From one active OpsGrid beta deployment · Dynamics 365 Business Central · mid-market manufacturer · baseline at project start, outcomes at 30 and 90 days. Decision latency: calendar time from the event’s record in Business Central to the owner acting on it.