Material requests on WhatsApp are a sign that the formal process is harder than the informal one. Site teams aren’t resisting D365. They’re choosing the fastest way to keep work moving. The fix is a request process in D365 F&O that is quicker than a message, not more training.
Why material requests on WhatsApp win
The system is live, and it took most of a year to deploy. Yet site teams still request materials over WhatsApp. The easy answer is “change management”. The honest answer is that, for this task, the system is often harder to use than WhatsApp.
A site engineer needs 30 meters of conduit, a junction box and four breakers by Friday. On WhatsApp, that takes 45 seconds. He types the message, and the storekeeper confirms.
Through a standard purchase requisition, the same request means finding the right screen, choosing items from a long catalog, filling in financial dimensions, waiting for approval and chasing it. Then he hopes the warehouse sees it before Friday.
That’s not the site team failing. It’s a process designed for a different job. Until the ERP route is faster than the message, D365 isn’t competing on equal terms.
The shadow system your site engineers have built
Spend a day on site with an engineer and you’ll see a personal system that works for him. The elements are usually familiar:
- The storekeeper group. A WhatsApp line to the warehouse for anything urgent.
- The personal tracker. A notes app or an Excel file listing what was requested, what arrived and what’s still pending.
- The walk-in. For urgent items, he goes to the stores counter. No paperwork, just a handshake.
- The chasing call. A weekly call to purchasing, because neither side can see the status in the system.
In other words, each tool solves a real need: fast communication, status tracking and knowing whose turn it is. Those are exactly the needs a good request process should meet inside the ERP.
Meanwhile, the stores team has the same problem from the other side. They track open requests across several chat groups, with no system of record. Items get missed, some are issued twice, and stock leaves with no record of where it went.
What the shadow system costs
WhatsApp is free, and Excel is already installed. However, the shadow system has real costs that never appear on an invoice:
- Wrong inventory. Stock leaves the warehouse without a transaction, so D365 quantities drift from reality and buyers order against wrong numbers.
- Unallocated project costs. Issued materials don’t post to the project, and finance has to rebuild the picture at month-end.
- No approval record. Nobody can show who authorized an issue, at what value or against which budget.
- Duplicate requests. Two sites ask for the same items, so one runs short while the other holds surplus.
- No real priorities. Every message feels urgent, so the loudest requester gets served first.
- Knowledge that walks out the door. When the engineer moves on, his tracker and his history leave with him.
Five signs your D365 setup wasn't built for site requests
These signals usually appear one or two years after go-live:
- Sites run a parallel request system. WhatsApp groups, shared spreadsheets or a separate form outside D365.
- Project costs are fixed at month-end, not posted in real time. Finance spends days moving costs between projects.
- Nobody can list open requests across all sites. The status lives in chats and in people’s heads.
- Stock counts keep showing large gaps. Materials leave the warehouse without an inventory transaction.
- You can’t trace an issue back to its request. Rebuilding the chain for a past project means searching old emails.
For a quick test, ask your warehouse team how they receive requests from sites. If the answer is anything other than D365, the gap is there.
Why more training doesn't fix it
The usual response is more training, a policy memo and a warning from management. That sometimes produces short-term compliance. It rarely lasts, because people don’t keep using a process that’s slower than the alternative, especially under deadline pressure.
So, the goal isn’t to ban the informal route. It’s to make the formal route easier:
- A short request form with only the fields a site needs
- Items picked from a short list, not the whole item master
- An approver who can act from a notification, without hunting through screens
- A warehouse queue that shows approved requests before anyone arrives
- A status the engineer can check himself, instead of calling purchasing
When the formal route is quicker and clearer, the shadow system fades on its own. That’s not a change management challenge. It’s a design decision.
We describe the full process, step by step, in our guide to site material requests in D365. Moreover, if your current setup relies on purchase requisitions, see purchase requisition vs material request.
How SysMaterialRequest replaces the chat
SysMaterialRequest gives site teams a request form in D365 F&O that holds only what they need. The request is checked against the project budget, approved through D365 workflow and issued by the warehouse in one click, which creates the journal.
It runs inside standard D365 F&O, with the screens and access your users already have. There’s no separate mobile app; D365 adapts its standard layout to the device. For background on the workflow engine it builds on, see Microsoft’s overview of workflows in D365 F&O.
Frequently asked questions
Why do site teams use WhatsApp instead of D365?
Because it’s faster. A message takes seconds, while a purchase requisition takes several screens and an approval wait. When the formal process is slower than the informal one, people choose the informal one.
Is banning WhatsApp requests the answer?
Usually not. Bans work for a short time, then the workarounds return under deadline pressure. A lasting fix makes the D365 request quicker and clearer than a message.
What does informal requesting cost?
It leads to inaccurate stock, project costs that need manual correction, missing approval records and duplicate orders across sites. These costs rarely show up as one line, so they’re easy to underestimate.
How quickly can a D365 request process go live?
It depends on your setup. A ready-made add-on such as SysMaterialRequest works with your existing projects, warehouses and workflow, so the main work is configuration and a short pilot on one site.
Make the formal route the easy one
Bring a typical site request from your team. We’ll show you how it looks as a D365 material request, from the site to the project cost. Book a SysMaterialRequest demo.