Designing a Purchase Approval Workflow to Keep Restaurant Budgets Under Control

Managing ingredient purchases across multiple restaurant outlets is not simply about keeping stock available. Owners also need to ensure that spending meets operational needs and stays within approved budgets.

As the number of outlets grows, purchasing becomes harder to control. Outlet Managers submit requests through WhatsApp, Area Managers approve them in chats, and procurement and finance teams must search through conversations to verify that each purchase was authorized.

To make this process more structured, restaurants need a purchasing approval workflow that defines who may approve each request, the spending limit for each role, and when a request must be escalated.

How can restaurants design an effective approval process without slowing down operations? The following steps provide a practical starting point.

Why Should Different Purchases Have Different Approval Requirements?

Imagine a restaurant group with ten outlets. Each branch submits purchase requests every day, with different needs and order values.

Buying vegetables for daily service does not involve the same risk as purchasing a refrigeration unit or ordering a large quantity of ingredients.

If every purchase must wait for owner approval, procurement can slow down. But if outlets can buy anything without authorization limits, costs become difficult to control.

That is why approval levels should reflect the value and risk of a purchase. Routine, low-value purchases can be approved by an Outlet Manager who did not initiate the request. Larger purchases or requests outside the approved budget should involve a higher level of management.

This division of responsibility allows owners to retain control without having to review every purchase request themselves.

Read also: What Is Procurement and How to Optimize It in the Culinary Business?

Steps for Designing an Effective Restaurant Purchasing Approval Process

Once you recognize that different purchases require different approval levels, the next step is to establish rules that can be applied consistently across outlets.

These rules should go beyond identifying approvers. They must also ensure that purchases are necessary and within budget.

1. Set Approval Criteria Based on Amount, Item Category, Outlet, and Urgency

Before designing the approval workflow, determine which factors decide where a purchase request (PR) should be routed.

There are four main factors. First, purchase amount: higher-value transactions generally require approval from more senior roles. Second, item category: routine ingredients, operating supplies, kitchen equipment, and capital assets carry different levels of risk.

Third, the outlet: each branch may have its own purchasing budget and authorization limits. Fourth, urgency: routine needs can follow the standard schedule, while a critical stock shortage may require faster approval.

These factors should be reflected in the approval rules. A request must be assessed not only by its amount, but also by its purpose, outlet, and operational impact.

2. Build an Approval Matrix Based on Authority Levels

An approval matrix identifies which role may authorize a purchase within a defined limit.

For example, a restaurant group could use the following thresholds:

Note: These amounts are illustrative, not universal benchmarks. Thresholds should reflect the company’s size, budget, organizational structure, and policies. The approver must be different from the requester. If an Outlet Manager creates a PR, the request should be escalated to an Area Manager.

A request is not automatically valid simply because its amount falls within someone’s approval limit.

For example, an outlet employee submits an ingredient PR worth IDR 800,000. Although the amount is within the Outlet Manager’s authority, the manager must still verify stock needs and available budget. If the manager submitted the PR personally, they cannot approve it themselves.

Certain categories, such as capital assets or strategically important items, may also require an additional approval even when their value is relatively low.

An effective approval matrix therefore considers both authorization limits and purchasing risk.

3. Check the Budget Before Approving a Request

Approval should not stop at asking whether the items are needed. Management must also check whether sufficient budget remains.

Suppose an outlet has a monthly ingredient budget of IDR 50 million. By mid-month, its purchases total IDR 38 million, and the Outlet Manager submits another PR for IDR 15 million.

The request may seem reasonable from an inventory perspective. However, the total would reach IDR 53 million, exceeding the IDR 50 million budget by IDR 3 million, before accounting for any other pending requests.

A budget check should therefore take place before approval. Ideally, the system shows the allocated budget, purchases already made, PRs awaiting approval, and the remaining budget after the new request.

Pending PRs should also be considered as potential budget commitments so multiple requests do not reserve the same remaining funds.

If a request would exceed the budget, the system can hold it or route it to an authorized person for an exception approval.

4. Separate the Requester, Approver, Purchaser, and Receiver

A common procurement risk arises when one person controls too many stages of a purchase.

For example, if an Outlet Manager submits a request, approves it, contacts the supplier, and receives the goods, the company has less assurance that the purchase was necessary and properly fulfilled.

To reduce this risk, separate the following responsibilities:

• Requester: Identifies what is needed and creates a purchase request based on stock levels or operational requirements.
• Approver: Reviews the need, budget, amount, and compliance with policy before authorizing the request.
• Purchaser: Contacts suppliers, places orders, and issues the purchase order (PO) against the approved PR.
• Receiver: Checks the delivered items against the PO, including their quantity, quality, and condition.

Separating these roles creates cross-checks. For instance, procurement should not unilaterally increase the quantity after PR approval without following the change-control process.

If a small restaurant group must combine some roles, assign an independent review for higher-risk or higher-value purchases.

5. Establish an Emergency Purchasing Procedure

Not every restaurant purchase can wait for the standard approval cycle.

For example, the main supplier may delay a chicken delivery while an outlet has only a few hours of stock left. Without a quick alternative, the restaurant may have to stop selling certain dishes.

Situations like this require an emergency purchasing procedure.

An emergency process is not permission to bypass every control. Define qualifying situations, emergency spending limits, and the roles authorized to grant expedited approval.

If approval must be given by phone or another channel because the system is unavailable, keep evidence of that authorization.

After the purchase, the requester should complete the PR, explain the emergency, and attach approval evidence, the invoice, and proof of goods receipt.

This approach enables urgent purchases while preserving a traceable record for later review.

6. Define When a Changed PR Needs Reapproval

An approved PR may not match the final order value. Prices, quantities, or specifications can change during supplier negotiations.

For example, an outlet requests 50 kg of meat at an estimated IDR 80,000 per kg. After receiving a supplier quote, the price rises to IDR 90,000 per kg.

The total increases from IDR 4 million to IDR 4.5 million, a 12.5% rise. Both amounts are still within the Area Manager’s approval tier in this example. However, if the company permits changes of no more than 10% without reapproval, the revised PR must be approved again. If the new total exceeds IDR 5 million, it must also be escalated to the Procurement Manager.

Restaurants should define reapproval triggers for several situations:

• Price change: Seek fresh approval when an increase exceeds the company’s tolerance.
• Quantity increase: Reassess the need and the effect on the budget.
• Specification change: Confirm that the substitute item meets quality and operational standards.
• Supplier change: Perform additional checks if the change affects price, quality, or purchasing terms.

A sound approval system should retain both the original and revised PR versions, allowing approvers to see what changed and whether reapproval or escalation is required before a PO is issued.

7. Set Approval SLAs So Purchasing Does Not Stall

Slow approvals can disrupt outlet operations. Ingredients may arrive late, production schedules may slip, and sales opportunities may be lost.

To prevent this, set service-level agreements (SLAs) that define the maximum time allowed to process approval requests.

For illustration, a restaurant could set the following targets:

These targets should be adapted to operating hours, urgency, and approver availability.

The system should also notify the relevant team when a PR is awaiting action. If an approver exceeds the SLA, the request can be routed to an authorized substitute under company policy.

This keeps purchasing moving without making every decision depend on one person.

8. Retain an Audit Trail for Every Purchasing Decision

As transaction volumes grow, companies need a clear history showing how each purchase was processed.

An audit trail helps owners trace every step, from the initial request to receipt of the goods.

At a minimum, the record should include:

• The requester’s identity and the outlet submitting the PR.
• The date and time the PR was created.
• The identity of the person who approved or rejected it.
• Reasons for approval, rejection, or revision.
• Changes to the amount, quantity, or item specifications.
• Details of the PO issued and the supplier selected.
• Goods receipt evidence and the supplier invoice.

These details should ideally be recorded in the system rather than scattered across WhatsApp screenshots and messages.

With a reliable audit trail, owners can analyze purchasing patterns, identify repeatedly revised requests, and spot outlets that frequently exceed their budgets.

Example: An Approval Workflow from Outlet PR to PO

Once the approval rules are in place, everyone involved must understand how the process works in daily operations.

Imagine an outlet needs an additional 30 kg of chicken for the coming week. The purchasing process could follow these steps:

1. The Outlet Manager creates a PR. The manager checks current stock and production requirements, then requests 30 kg of chicken with an estimated cost of IDR 2.4 million.
2. The system checks the budget. It compares the request with the outlet’s ingredient budget, completed purchases, and outstanding commitments.
3. The Area Manager approves the PR. Because the Outlet Manager is the requester and the amount also exceeds the outlet-level threshold, the PR is routed to the Area Manager.
4. Procurement processes the request. Once approved, procurement checks the supplier, price, and item availability.
5. A PO is issued. Procurement creates the PO using the approved quantity, price, and specifications.
6. The outlet receives and checks the goods. The designated receiver checks the delivered chicken against the PO before recording receipt.

This workflow gives each person a clear responsibility and allows owners to track purchasing status without requesting updates through individual chats.

Read also: A Vendor Evaluation Checklist for Multi-Outlet Restaurant Management Software

FAQs About Restaurant Purchasing Approvals

1. What is a restaurant purchasing approval process?

It is a process for authorizing procurement based on purchase amount, item category, budget, and the responsibilities of the people involved. The requester and approver should be different people.

2. Who should approve ingredient purchases?

An Outlet Manager may approve routine, low-value purchases submitted by another employee. Larger purchases and requests beyond the budget should be routed to the Area Manager, Procurement, Finance, or another authorized decision-maker.

3. Should every purchase have a purchase request?

Ideally, all purchases should be documented through PRs, giving the company a record of the need, estimated cost, approver, and completed procurement.

4. What happens if a purchase exceeds an outlet’s budget?

The request should be held or escalated to an authorized person for exception approval. Any additional spending must have a clear justification.

5. Can purchasing approvals be automated?

Yes. An ERP system can route requests according to roles, transaction amounts, item categories, and available budgets, helping the appropriate approver review each purchase.

Conclusion

An effective purchasing approval process does not force every expense through multiple approval layers. It makes sure the right person authorizes each transaction based on its amount, category, and budget. An approval matrix, budget checks, separation of duties, SLAs, and audit trails help restaurants limit uncontrolled spending without delaying essential supplies.

ESB Core is an ERP solution that connects purchasing activities from purchase requests through payment, with role-based access controls and budget monitoring. Each restaurant should still configure approval rules to fit its own policies and organizational structure.

Contact the ESB team to learn how ESB Core can help your restaurant manage purchases, budgets, and approval history through a more integrated process