Procurement

Restaurant Purchase Order Approval Limits: Control Spend by Location

Curran Dye

October 1, 2026

What a Purchase Order Approval Limit Controls

A purchase order approval limit decides which orders a location can send on its own and which need sign-off first. You set it by order value, category, branch and supplier. An order inside the limit reaches the supplier; one above it waits for an approver, so head office controls spend across multiple locations without hovering over every order.

A limit is not a blanket lock. The aim is the opposite: let the everyday ordering a site has always done run untouched, and spend the attention only where it changes the number at month-end. Most orders should clear with no approval at all. The ones that wait are the exceptions worth a person's time.

Supy keeps two flows separate here. A requisition is the internal request a site raises to replenish stock, and it carries its own approval policy. A purchase order is what actually goes to the supplier. You can set a limit on each, so an internal request and the spend it becomes are both governed rather than only one of them.

The control that matters most for a group is the order-value threshold. Below it, routine orders flow. Above it, a purchase order routes to an approver before it reaches the supplier. You can set separate thresholds by branch and supplier, so a busy flagship is not held to the same ceiling as a week-old site.

Purchase order approval runs up to five levels of sign-off per policy

Set a Value Threshold So Small Orders Don't Wait

Start with the number that unblocks daily ordering: the amount a location can spend without asking. Set it just above the routine replenishment a manager places every shift. A $300 produce top-up then submits to the supplier the moment they order it. A larger purchase order, say $2,000, routes to an approver first.

Pick the number from order history, not a guess. Look at what each site actually spends per order on a normal week and set the limit just above the common case. Set it too low and approvers drown in sign-off they add nothing to. Set it too high and real overspend walks straight through.

One multi-site operator found internal approvals were averaging four days, because every order waited in the same queue whatever its size. A value threshold ends that. The small, repeatable spend never enters the queue, and the approver only sees what is worth a second look.

You can also tie the limit to a time window. Supy supports rules by day, week, month or quarter, so a site can run freely within a weekly budget and only hit approval once it has spent past it. That catches the slow drift of many small orders that each clear the per-order limit but add up over a month.

An order under the value threshold ships while an order over it waits for an approver

Route Off-Budget and Off-Category Spend to the Right Person

Order value is one control, not the only one. Some spend needs a second pair of eyes whatever its size, so route it by category, branch and supplier as well. Supy's restaurant procurement software applies each rule inside the ordering screen, so the buyer meets the limit as they order rather than after.

Flag a category and any order touching it needs sign-off. A crockery or cleaning order goes to the branch manager even when it is small, because it sits outside the food budget. Tie a limit to a supplier and a new or off-contract vendor gets caught before a purchase order goes out.

Combine the controls and one order is checked against value, category and the branch's own ceiling in a single pass. A $150 order of cleaning supplies clears the value threshold but trips the category rule, so it still routes to the manager. A $900 produce order from an approved supplier, well inside budget, goes straight through. The buyer never has to work out which rule applies; the order meets the right one on its own.

When an order does need more than one yes, a multi-level approval ladder decides who signs, and in what order. Head office sets these policies centrally and pushes them to every location, rather than configuring each site by hand. The same rules reach the mobile app, so a manager ordering from the floor during service meets the limit there too and cannot route around it by switching device.

Four controls that set a purchase approval limit: order value, category, branch and supplier

See Where Every Approval Is Stuck

A limit only helps if nobody can quietly route around it and a held order does not vanish. Supy shows the full approval trail on every requisition: who approved, who rejected and why, and who still has it. A regional manager sees exactly where a request is blocked instead of chasing people one by one.

Every action is logged with a timestamp and the person who took it, so the audit trail holds up at month-end. Underneath sit 200+ permissions that decide who can order, approve and set a limit, so you grant each site exactly as much ordering freedom as it has earned.

The approval trail showing each level a purchase request passes through

Set one threshold this week. Pick the order value most of your locations clear every day, put the limit just above it, and leave everything under it to submit on its own. Watch which orders pile up above the line for a fortnight, then add a category or supplier rule for the ones that keep needing a second look. The limit earns its place when the small orders stop waiting and the large ones stop slipping through.

Book a Demo with Supy - restaurant purchase order approval limits

Get weekly insights and tips delivered straight to your inbox.

Ready to optimize your restaurant operations?

Book a demo



Blog

Our operational insights





Procurement

Restaurant Procurement: A Complete Guide for Multi-Location Operators

Curran Dye

April 1, 2026



Watch episode

Seven multi-site restaurant supplier ordering mistakes and their fixes

Procurement

Restaurant operations

Restaurant Supplier Ordering Process: Seven Multi-Site Mistakes to Fix

Curran Dye

October 2, 2026



Watch episode

Procurement

Inventory

Restaurant Transfer Pricing Between Sites: Keep Group Costs Accurate

Curran Dye

October 2, 2026



Watch episode

Your questions  answered

Everything you need to know about Supy — from setup to integrations, pricing, and daily use. If it’s not covered here, just ask.

What is a purchase order approval limit in a restaurant?

A purchase order approval limit is a rule that sets how much a location can order before someone has to approve it. You set the limit by order value, and you can narrow it further by category, branch or supplier. An order inside the limit goes to the supplier straight away. One above it is held until an approver signs off. The point is to let routine ordering run while keeping larger or unusual spend under control across every site.

How do approval limits speed up ordering instead of slowing it down?

Approval limits speed up ordering by keeping small, routine orders out of the approval queue entirely. You set a value threshold just above the everyday replenishment a manager places, so a produce top-up or a bar restock submits on its own. Only orders above the threshold, or ones that touch a flagged category or supplier, wait for a person. Managers stop queuing for sign-off they never needed, and approvers see a short list of orders that genuinely merit a look.

Can approval limits be different for each branch?

Yes. You can set a separate threshold for each branch, and separate rules by supplier and category on top of it. A high-volume flagship can carry a higher limit than a new site still finding its feet, so neither is held to a ceiling that does not fit it. Head office sets the policy centrally, and each location orders within the limit that matches how it actually trades. Branches can also share one policy where that makes sense, so you standardise a region once rather than rebuilding the same rules site by site.

What stops staff from splitting an order to stay under the limit?

Visibility and the audit trail are what stop it. Every requisition records who raised it, what it contained and when, so a pattern of orders landing just under the threshold is easy to spot in review. You can also set category and supplier rules that trigger approval regardless of value, which removes the incentive to split in the first place. The limit is a control, not a loophole, because the record of every order sits next to it, and a reviewer can question an odd run of orders the following day.

How many approval levels can a purchase order pass through?

A purchase order can pass through up to five approval levels in Supy. A requisition can require, for example, a site manager to approve first and a regional manager second before it becomes an active order. You decide how many levels a given policy needs and who sits at each one. Most orders clear at the first level or need no approval at all; the deeper ladder exists for the larger or more sensitive spend that warrants it, so routine ordering is never slowed by a level it does not need.

Do approval limits work for central kitchen and supplier orders too?

Yes. The same limits govern requisitions from a branch, orders to a central kitchen and purchase orders to outside suppliers. You set the value threshold, category and supplier rules once, and they apply wherever the order originates. A central kitchen ordering on behalf of several branches is covered the same way, so an internal transfer meets the same ceiling as outside spend. That matters for a group because spend leaks through whichever route has no control on it, and a limit that covered only one path would miss the others.

Where should a multi-site group start with approval limits?

Start with a single value threshold per location. Pick the order value most sites clear on a normal day and set the limit just above it, so routine orders flow and anything larger waits. Run it for a couple of weeks and watch which orders stack up above the line. Then add a category or supplier rule for the spend that keeps needing a second look. Building the policy in that order gives you control without a flood of approvals on day one.