
A restaurant group can run supply and purchase requests between its branches on Microsoft 365. A branch manager fills in a request on a phone, a Power Automate approval goes to the person who signs it off, and the central kitchen or purchasing team sees approved requests in one list. Every request keeps its history, so you can see what each branch asked for and when.
In most groups this runs through WhatsApp messages and phone calls. It is fast until a request is forgotten, two branches order the same thing, or the accounts team asks why one branch's spend doubled last month.
What should a request system handle?
Two kinds of request that look similar but are approved differently. Stock transfers from a central kitchen or store, which mostly need checking against what is available. Purchases from outside suppliers, which need a spending sign-off. Keep them as two types in the same system so branch managers have one place to go.
| Request type | Who approves | What happens next |
|---|---|---|
| Stock from the central kitchen or store | Store or kitchen lead | Picked and sent with the next delivery |
| Purchase from a supplier, under your limit | Branch or area manager | Ordered by the branch |
| Purchase over your limit | Operations or finance | Ordered centrally |
| Urgent request | Area manager, with a shorter deadline | Escalated if not answered in time |
The spending limits are yours to set. The flow just applies them.
How does a branch manager make a request?
Open the app, pick the items from a list or type what is needed, set the quantity and the date it is needed by, and submit. The branch fills itself in from who is signed in. A request for a new piece of equipment can include a photo or a supplier quote as an attachment.
Picking items from a list rather than typing them matters more than it seems. "Chicken breast 5kg" written four different ways cannot be totalled at the end of the month.
How does the approval work?
Power Automate sends an approval to the right person based on the request type and the amount. They approve or reject from Outlook, Teams or the Power Automate app, and can add a comment. The branch manager is told the result straight away, and approved requests move into the list for the store or purchasing team.
If an approval sits unanswered, the flow reminds the approver and then escalates to their manager. One limit to design around: a cloud flow run lasts at most 30 days, and pending approvals time out after that, according to Power Automate's limits and configuration page (checked November 2026). Set your own deadline well inside that. The full pattern with reminders and escalation is in How to Build a Power Automate Approval Flow.
What does head office see?
Every request from every branch in one list: what was asked for, who approved it, and when it was fulfilled. Filtered by branch and month, that becomes a simple view of spending and stock movement per branch, without anyone rebuilding it from messages.
For deeper reporting, the same list can feed a Power BI report, but most groups get what they need from a filtered view and a monthly export first.
What licences does this need?
On SharePoint lists with the Approvals, Outlook and Teams connectors, everything uses standard connectors, so Microsoft classes the app as Standard and it runs under most Microsoft 365 business plans. The Approvals connector itself is standard, as Microsoft notes in its approvals guide. Connecting to an accounting or inventory system through a premium or custom connector changes that, so check what you want to connect before the build starts.
Frequently asked questions
Can approvers answer from their phone? Yes. Approvals arrive in Outlook, in Teams and in the Power Automate mobile app, and can be approved or rejected from any of them.
Can it connect to our inventory or accounting system? Sometimes. It depends on whether that system has a connector or an API, and whether the connector is premium. That is worth checking on the first call, before anything is promised.
What if a branch manager is on leave? The approval can go to a named deputy for that branch, kept in a small routing list that the operations manager edits without changing the flow.
Can we start with one branch? Yes, and it is the better way to start. Run it in one branch for a few weeks, fix what staff trip over, then roll it out to the rest.
Getting it set up for your group
I've built request and approval systems for restaurants, and the same approach runs daily checklists across branches, covered in Daily Opening, Closing and Food Safety Checklists for Restaurant Branches. If you want to talk through how your branches order today, book a 30-minute call.
Last updated
- Power Automate
- Power Apps
- Restaurants
