Multi-location restaurant procurement starts with a separate view of each site's usable stock, expected ingredient use and next delivery. Central buying can combine supplier work, but it must preserve destinations, accepted quantities and receiving responsibilities.
This guide is for an independent restaurant group choosing how much to centralize. The right structure depends on supplier delivery options, local knowledge, prep operations and finance requirements, rather than a fixed number of locations.
Calculate the site requirement before consolidating
Menu sales can inform ingredient demand when recipes, portions, usable yield and modifiers are mapped. Apply the relevant demand at each site. Shared menus do not establish identical sales mix, counts or delivery timing.
For a fictional ingredient, suppose the reviewed targets already cover the correct demand period and buffer:
| Input, in cartons | Location A | Location B |
|---|---|---|
| Target | 96 | 48 |
| Usable on hand | 30 | 18 |
| Incoming before the need date | 24 | 0 |
| Net requirement | 42 | 30 |
| Order in 12-carton cases | 4 cases / 48 cartons | 3 cases / 36 cartons |
If the supplier delivers whole cases to each site, the combined request is seven cases. Rounding the combined 72-carton net requirement to six cases would miss the separate destination pack constraint. If a commissary can split cases, six might instead cover the net requirement, but the receiving, handling and allocation plan must support that choice.
Each site's six-carton rounding surplus needs a storage and expected-use check. Confirm incoming dates and avoid counting reservations twice. The restaurant order guide and café PAR example explain the units and protection period.
Choose the physical delivery model
| Model | When to evaluate it | What must stay visible |
|---|---|---|
| Local buying within shared rules | Local staff have useful supplier or service knowledge | Purchasing authority, shared records and local commitments |
| Central buying with direct site delivery | The supplier can serve each destination | Site quantities, dates, order references and separate receipts |
| Commissary or warehouse supply | Central prep, storage or case splitting has a useful role | External receipt, internal allocations, movements and site receipt |
| A mixed model | Some categories benefit from central handling and others do not | Which route owns each item and who prevents duplicate orders |
A consolidated supplier relationship does not require every purchase to use one physical PO or invoice. Confirm what the supplier accepts: separate site orders, a consolidated order with destination lines, or another documented arrangement.
For central stock handling, use the warehouse procurement guide. A transfer from a commissary is distinct from an additional external supplier purchase.
Assign decisions centrally or locally
Name the person who reviews quantities, sends each order, accepts price or product changes, and follows up when confirmation is missing. Give local receiving staff a usable way to record what arrived even if a central buyer operates the purchasing software.
Shared visibility matters more than requiring one particular inbox arrangement. Messages can arrive through different supported channels as long as the responsible team can identify the order, destination, proposal and next action. A supplier reply that says “only six available” needs clarification if it could refer to several sites or purchase packs.
Do not force the same PAR or waste assumption onto every site. Check local demand, counts, review schedules, supplier timing and observed loss. Recipe estimates and statistical allowances do not establish actual physical stock or safe-use limits.
Test a supplier change across sites
After the seven-case request in the example, suppose the supplier offers only five cases for the first delivery. That proposal does not tell the locations how much they will receive.
The buyer must agree the allocation, later balance and usable dates. If three cases are accepted for A and two for B, record those expectations separately. If A receives only two, its receiver records two and raises the one-case discrepancy; B's receipt must not be altered to make the group total match.
Review substitutes for the relevant kitchen use, units and price before acceptance. Preserve the original request, supplier proposal, buyer decision and actual receipts on the living purchase order.
Agree the finance allocation before rollout
Retain destination, actual receipt and accepted price evidence for finance. Shared charges need an agreed allocation method; do not assume a single supplier bill can carry every location or tracking dimension your reporting needs.
Agree with finance how purchase records and corrections reach the accounting system. Finance may need commitments before receipt and later credits after delivery, so the handoff must preserve events rather than wait for one final state.
A location's purchase spend is not automatically its food consumed in that period. Counts, transfers, actual usage and the accounting policy still matter to the cost review.
Pilot the handoff with another shift
Start with two representative sites and a supplier cycle that includes a changed quantity or short receipt. Have the central buyer, a local receiver and finance explain the same order independently. Then let a covering employee take over the next action.
Measure active work, duplicate orders, allocation questions and unresolved discrepancies. Include setup and correction time. Expand when the team can operate the normal path and recover from the tested exception.
LineNow connects configured demand inputs, purchasing drafts, supported supplier messages and receiving context. Demonstrate your proposed consolidation and allocation route rather than assuming every setup creates the same documents. Review current pricing for business units and add-ons, then use the restaurant purchasing workflow to evaluate the agreed process.
