Restaurant purchasing is one loop, run weekly (or daily), across every vendor you buy from: know what you need, order it per vendor before each cutoff, receive what actually arrives, reconcile what it actually cost, and let that feed the next order. Most restaurants run pieces of this loop well and other pieces from memory — and food cost drifts in the gaps between the pieces.
This is the hub for the whole loop. Each section gives you the working version in a few paragraphs, then links the deep guide, the template, and the tool for that step. Read it straight through if you're setting up purchasing from scratch; jump to the broken step if you're here to fix one thing.
Step 1: Know your vendors and how ordering actually works
The structure of restaurant supply: a broadline distributor for 40–70% of purchases, plus produce, protein, bread, dairy, and beverage specialists — each with its own cutoff, delivery days, minimum, and ordering channel. Every vendor is its own workflow, and nothing about your Sysco account helps you order from the produce house.
- Deep guide: How Restaurants Order from Food Distributors — accounts, terms, pricing basis, portals, credits
- Choosing software for this step: Restaurant Vendor Ordering Software — the closed-loop vs form-filler test
Step 2: Build one order guide per vendor
The order guide is the load-bearing document: every item you buy from that vendor, in shelf order, with pack size, last price, and par. Someone walks the walk-in with it before the cutoff, and par minus on-hand — rounded to whole packs — is the order.
- Deep guide: How to Build a Restaurant Order Guide
- Template: Order Guide CSV · Interactive: Order Guide Builder
Step 3: Set pars that track reality
A par is expected usage between deliveries plus a cushion — which means the Friday par isn't the Monday par, and the March par isn't the November par. Pars set once and never reviewed are how you stock out of the new best-seller while carrying three cases of the 86'd special.
- Deep guide: Par Levels That Track Weekly Sales
- Concepts: par level · safety stock · reorder point
- Template: Par Sheet CSV · Tools: Par Level Calculator, Reorder Point Calculator
Step 4: Count on a schedule
Counts anchor everything: pars, orders, food cost, and theft detection all assume the on-hand number is real. Count by storage area in shelf order, in one unit per item, at a consistent time, and enter it the same day.
- Deep guide: Restaurant Inventory Management, End to End
- Template: Inventory Count Sheet CSV
Step 5: Receive like the margin depends on it (it does)
The truck is where the order meets reality: shorts, substitutions, catchweight variance, temperature failures, and price changes all land at the back door. Check against what was confirmed, get discrepancies on the invoice with the driver present, and track every credit until it lands.
- Deep guide: Why the Invoice Never Matches the PO
- Template: Receiving Checklist CSV
- Control model: Three-Way Matching vs Living POs
Step 6: Reconcile costs before the bookkeeper
Food cost is made at order time and receiving time, then merely reported at month end. Price creep per item per vendor, unlanded credits, and invoices that match neither the order nor the delivery are the three quiet leaks. The goal: your bookkeeper pays bills instead of investigating them.
- Deep guides: Best Food Cost Management Software · Invoice OCR vs Supplier Email Automation
- The category argument: Every Restaurant Tool Reads Invoices Now. Almost None of Them Order.
Where your POS fits — and where it stops
Toast, Square, Clover, and Lightspeed are the demand record: they know what sold. Their inventory features (and partner add-ons) are genuinely useful for stock visibility — and every one of them stops at the same boundary: the vendor loop after the order is sent. The honest per-POS breakdowns:
- Toast Inventory Management: The Three Surfaces · Toast procurement layer
- Square Inventory Purchase Orders · Square procurement layer
- Clover procurement layer
- The Lightspeed Reorder Report · Lightspeed procurement layer
Scaling past one location
Multi-location adds the questions single stores never face: central ordering vs per-store ordering, commissary transfers, per-location pars, and consolidated vendor negotiations with per-store delivery.
- Deep guides: Multi-Location Restaurant Procurement · Central Warehouse Procurement
- If you're evaluating suites: When Restaurant365 Feels Too Big · Best Purchase Order Software for Restaurants
Running the whole loop in one system
Every step above has a manual version — that's what the templates are for, and a disciplined operator can run the paper loop indefinitely. The structural upgrade is connecting the steps so they feed each other automatically: POS sales drive pars through your recipes, pars drive suggested orders, orders go out per vendor in their channel, vendor replies update a living purchase order, receiving reconciles against the confirmed state, and accounting gets the finished story. That connected loop is closed-loop procurement, and running it for restaurants is what LineNow is — every location in one flat plan, with a 90-day free trial that's long enough to run your messiest vendor through real cycles.
Start where the leak is worst. If you don't know where that is, start with the receiving checklist for two weeks — the discrepancy log will tell you.