Multi-site procurement: how to control buying across every location

Put an eight-campus school group with $32 million of yearly spend through our Maverick Spend Calculator's education inputs, and it estimates $4.03 million a year lost to buying that goes around contracts and approvals. That is 12.6% of everything the group buys, or about $504,000 per campus.

No single campus causes it. The money leaks because eight sites each buy in their own way, with their own suppliers and their own habits, and head office learns what happened when the invoices arrive. Multi-site procurement is the work of putting one set of rules in front of every one of those purchases.

What is multi-site procurement?

Multi-site procurement is how an organisation with many locations buys goods and services under one shared process. Each site still raises its own requests and receives its own deliveries, but the rules, prices and records are the same everywhere. It is also called multi-location purchasing.

It covers schools in a trust, kitchens in a restaurant group, clinics in a regional network, shops in a retail chain and jobsites run by one contractor. In each case someone at a site needs something, someone else has to say yes, and finance has to pay the right amount for goods that actually arrived. Across 8 or 80 sites, each of those people works in a different building. The controls in this guide keep the chain intact over that distance.

What changes when buying happens at many sites?

The steps stay the same, but the people doing them change. Most buying at a site is done by managers whose real job is something else: running a kitchen, a campus or a jobsite.

That shifts the pressures in four ways.

• Site managers buy under time pressure. A principal with a broken boiler or a head chef short of oil on a Friday night will buy whatever arrives fastest. When the approved route is slower, the faster one wins.
• Local suppliers fill the gaps. Every site has a hardware shop, a cash-and-carry or a contractor nearby. They are convenient, they are rarely on contract, and their prices are rarely checked against the contract rate.
• The same item costs different amounts. Without a shared catalogue, one campus pays one price for printer paper and the next pays another. Nobody sees the gap until someone compares invoices line by line.
• Head office sees spending late. A purchase made on a card or by phone shows up as an invoice or an expense claim weeks later, once the money is already committed.

Each of these is a reasonable choice at the moment it is made. Added up across sites and months, they become what the guide to maverick spend measures: purchases outside the agreed supplier, price or approval route.

Sites also use different words for the same thing. A school calls its locations campuses and its approver a principal. A dining group has units and unit managers. A retailer has branches. A process written in one vocabulary gets ignored by people who use another. That is a quiet reason multi-site rules fail.

Should procurement be centralised, local or hybrid?

Many multi-site organisations land on a hybrid. Head office owns suppliers, contracts and rules, while sites raise their own requests and receive their own goods. Fully central and fully local buying each break in predictable places.

What matters most is where the rules live. In a hybrid model, a campus can still order its own lab supplies, but only from the approved list, at the contract price, through an approval chain head office has agreed. Central buying can still pool demand where it pays. In the education configuration of Bollard, the central store groups faculty orders into bulk purchases, so one supplier order can cover several departments.

Our guide to centralised vs decentralised procurement compares the models in detail.

How much does uncontrolled buying across sites cost?

The cost has two parts. You pay more than the contract price on purchases made off contract, and each of those purchases costs extra staff time to chase, code and approve after the fact.

For each spend category:

Leakage = off-contract spend × missed contract discount + (off-contract spend ÷ average order size) × extra handling cost per order

Off-contract spend is the category's spend multiplied by the share not bought on contract. Add up the categories for the total.

A worked example: eight campuses, $32 million of spend

The example uses the calculator's education inputs: eight campuses, each spending $4 million a year. Across all categories, 58.8% of the spend goes through contracts.

Split by cause, the total is:

• Price premium: $1,934,400, the contract discounts the group didn't get.
• Handling cost: $2,100,000, from about 60,000 off-contract orders at $35 of extra work each.

Handling costs more than the price premium here whenever each stray order takes more than $32.24 of staff time to sort out. If your team spends less than that per order, the price premium is the bigger half.

Look at where the leak sits. Facilities and repairs is 25% of spend and 31% of the leakage. Lab and classroom supplies is 15% of spend and 21% of the leakage. Dining services, which is already well contracted, is 20% of spend and only 10% of the leakage. The categories that leak are the ones bought urgently, in small amounts, by people at the site.

What raising compliance is worth

The table below holds every category to at least the share shown, leaving the categories already above it alone.

Left alone, the number grows. With spend rising 4% a year and compliance slipping 2 points a year, the calculator projects $4,394,518 in year two and $4,776,991 in year three.

Free tool

Maverick Spend Leakage Calculator

Pick your sector, set your number of sites and spend per site, then adjust compliance and discounts by category. See three years of leakage and download a PDF brief for your board.

Runs in your browser. No sign-up.

Size your own leak

Which controls matter at each step?

Seven controls carry most of the load. Each one sits at the step where a site makes a decision, so it works before money is committed instead of after.

The full sequence from request to payment is covered in our procure-to-pay process guide, and the wider procurement process, from sourcing to supplier management, has its own guide. Below is what each control looks like across many sites. The Bollard platform page shows all seven working as one loop.

Requisitions from a shared item master

A site should request from a list. The item master holds each item's description, unit and cost, and each site sees only the items it is approved to buy. The requester picks lines, adds quantities and a required date, and enters a budget code and a reason.

It ends the habit of ordering from a favourite website, because the contracted item is right there with its price. It also gives head office the same data from every site, so two campuses can be compared line for line. Purchase requisition vs purchase order explains how this request differs from the order a supplier sees. Bollard's version is on the purchase requisitions page.

Approval limits by amount, site and role

Every request should go to a named approver chosen by rules. Nobody should be able to pick the friendliest one. Three inputs set the route: how much it costs, which site it is for and who raised it. A small consumables order at one site might need one sign-off. A large equipment purchase might need three.

Site matters as much as amount. Two campuses of different sizes can have different limits, and a site manager should approve only for their own site. Our approval matrix guide covers setting limits and catching split orders, and the Approval Matrix Builder turns them into a shareable table. The purchase order approval process guide follows a request through the chain. Limits also need segregation of duties in purchasing, so the person who orders isn't the person who receives or pays. Bollard's routing is on the approval workflows page.

Purchase orders with a locked price

The purchase order is where the agreed price becomes the price the supplier will be held to. If a site agrees a price by phone and the invoice comes a month later, nobody can easily say whether the bill is right. A price fixed on the PO gives finance a number to check against.

For quoted purchases, compare the quotations and raise the PO from the winning one, so the number that won is the number on the order. For contracted items, the contract price should land on the PO without anyone typing it. Our guide to contract price compliance shows how prices creep when this step is skipped.

Every approved PO is also money the group has promised to a supplier but not yet been billed for. Tracking it as committed spend is how finance sees each site's budget before the invoices land. See purchase orders for how Bollard handles RFQs and the price lock.

Receiving with accepted and rejected quantities

Each site receives its own deliveries, so receiving discipline has to hold at every door. The receiver should record three numbers per line: how much arrived, how much was accepted and how much was turned away.

If only "received" is recorded, a damaged case gets stocked and paid for. With acceptance recorded separately, the group owes only for goods a site agreed to keep. A short delivery should leave the rest of the order open. The paper version of this record is a goods received note. In Bollard it is the goods receiving step.

Three-way match before payment

Before an invoice is paid, each line should agree with two other records: the price on the PO and the quantity accepted at the site. A higher price fails on value. Billing for more than was accepted fails on quantity.

Across many sites, the match is the last place a mistake from any one site can be caught. It only works if it runs line by line, because errors on separate lines can cancel out on the total. Our explainer on what three-way matching is covers the mechanics, and the accounts payable process guide covers the rest of the work in AP. Bollard's version is on the three-way match page.

Transfers between sites

Many groups move stock as well as buy it: from a central store to campuses, from a commissary to units, or from one branch to another. A transfer should be recorded twice, once when it leaves and once when it arrives, and the receiving site's stock should rise only when it confirms the goods.

Stock records drift easily without that. In one study of a retailer, more than 65% of inventory records across 37 stores didn't match what was physically there (Chicago Booth Review). In a multi-site group, one common cause is a transfer recorded at one end only. Our guides to multi-location inventory management and inventory transfers between sites go further. Bollard's version is on the inventory and transfers page.

An audit trail and access by site

Every change should leave a record that nobody can edit: who did it, to which document, when, and what it looked like before and after. Corrections should be added as new entries, not written over old ones.

Access matters too. A site manager should see their own site's requests, orders and stock, while head office and finance see the network. When access is limited by site, a shared report can't leak one campus's figures to another. See audit trail for how Bollard records changes.

What should you measure across sites?

Measure the same few numbers at every site, every month, and compare sites with each other. A number that is fine for the group can hide one site that has stopped following the process.

• Spend on contract, by site and category. A site that drops from 80% to 65% in a quarter is telling you about a supplier, a manager or a missing catalogue item.
• Purchase order coverage. The share of spend with a PO raised before the invoice arrived. Invoices with no PO behind them are purchases nobody approved in advance.
• Approval time, by level and site. Slow approvals push site managers toward local suppliers and cards. Where requests wait is where the process needs fixing.
• Invoice match failures, by site and cause. Price failures point at suppliers or contracts. Quantity failures point at receiving.
• Committed spend against budget, by site. Open orders plus invoices already received, compared with each site's budget, shows overspends while they can still be stopped.
• Transfer discrepancies. Stock sent but not confirmed, or confirmed short, by route.

Our guide to procurement KPIs covers how to define and report each one.

How do you roll out multi-site procurement?

Start with one site, prove the process on real orders, then add the rest. A rollout that starts everywhere at once finds its problems everywhere at once, when they are most expensive to fix.

1. Write down the rules. Who may buy what, from whom, up to what amount, and what counts as an emergency. A procurement policy template gives you a starting structure.
2. Build the approval matrix. Turn the policy into roles, limits and category rules, set by amount, site and role. Use your own role names, so a principal sees "principal" and a unit manager sees "unit manager".
3. Clean the item master and supplier list. Remove duplicates, set one unit per item, attach contract prices and decide which items each site may order. This is slow work, and every later step depends on it.
4. Pick a pilot site. Choose one that buys a typical mix, with a manager willing to report what doesn't work. Avoid the most unusual site in the group.
5. Run real orders through the full loop. Request, approve, order, receive, match and pay, for a few weeks. Watch where people get stuck or work around the process.
6. Fix what the pilot finds. Missing catalogue items, limits set too low, approvers who are never at a desk. Each fix now saves the same problem later.
7. Add the other sites in waves. Group sites that buy alike, and bring each wave live with the item lists and approvers already set.
8. Review by site every month. Use the measures above. Compare each site with the group and with its own previous months.

Software holds the rules in place once you have written them. If you are comparing systems, our purchase order software checklist lists what a multi-site group should test before it signs.

How does buying across sites differ by sector?

The controls are the same in every sector. What changes is the vocabulary, the approval chain and which details matter at the door.

• Education. Sites are campuses or schools, and approval often runs from a principal or head of department to finance. Academy trusts in England must also follow the procurement rules and thresholds in the Procurement Act 2023 (Academy trust handbook), which our guide to the Procurement Act 2023 covers. See Bollard for education.
• Food service and contract dining. Sites are units or kitchens, approval runs from a unit manager to a district manager, and a central commissary may supply them. Contract prices on every delivery matter most, and so does keeping rejected perishables off the invoice. Our guide to restaurant inventory management goes deeper. See food service.
• Healthcare clinic networks. Sites are clinics or practices, and controlled supplies may need two sign-offs. Lot numbers and expiry dates matter on receipt. See healthcare.
• Specialty retail. Sites are branches or stores, a distribution centre supplies them, and moving stock between branches can prevent one running out while another holds plenty. See specialty retail.
• Construction. Sites are jobsites, every order is coded to a project and cost code, and plant hire needs tracking from on-hire to off-hire. See construction.

A good test of any process is whether a site manager in each sector would recognise their own words on the screen. If they wouldn't, expect workarounds.

When doesn't this apply?

Not every purchase needs the full loop, and not every organisation needs it at all.

• One site, or a handful of small ones. If one person can see every purchase, a written policy and a shared spreadsheet may be enough. The controls earn their cost as sites, buyers and suppliers multiply.
• Real emergencies. A burst pipe at night needs a plumber now. Give emergencies a route that allows the purchase first and requires approval within a set time, so the spend stays visible.
• Spend with nothing to receive. Utilities, rent and subscriptions don't have a delivery to count. Many groups handle them through invoice approval instead of a PO and a receipt.
• Sites that are separate businesses. Where each site is independently owned, as in some franchise models, the group may be able to recommend suppliers but not enforce approvals. The tools still help, but each site follows the rules by agreement.

Sources

• Chicago Booth Review, First measure, then manage: inventory record accuracy at a retailer with 37 stores.
• Department for Education, Academy trust handbook 2026: paragraph 2.25 on following the Procurement Act 2023 rules and thresholds.