Restaurant Purchasing & Inventory Management: The Complete 2026 Guide

Restaurant purchasing and inventory management is one repeating loop: count what's on the shelf, compare it to how much you need until the next delivery, order the difference from the right vendor before the cutoff, check the delivery against what you ordered, and keep a record of every order so the next one is easier. Each step depends on the one before it. A wrong unit on the count becomes a wrong order, and an unchecked delivery becomes an invoice nobody can explain.

This guide walks through the whole loop, one step at a time, using a single made-up restaurant and a single item so you can see how the numbers carry from one step to the next. Each section gives you enough to act on, then links to a more detailed guide where we have one.

How the pieces fit together

The example used throughout this guide

This is an illustrative example. The restaurant, vendor, item, pack sizes, usage, and prices are made up to show the method. They aren't typical figures for any restaurant or distributor.

• A neighborhood restaurant open 7 days a week.
• A meat purveyor takes orders by email, with cutoffs at Monday 12:00 PM and Thursday 12:00 PM. It delivers Wednesday and Saturday mornings, before service.
• Boneless short rib comes in cases of 6 vacuum packs, about 5 lb each. The kitchen counts it in packs. The vendor bills it by the pound, at an expected $9.40 per lb.
• The kitchen counts on the morning of each cutoff.

We'll follow Thursday's short rib order from the count all the way to a closed purchase order.

Units: what you count, what you order, and what you're billed for

Most ordering mistakes start with units. Every item needs two units written down, and some need a third:

The billing unit is the one people forget. Many proteins and some cheeses are sold by the case but billed by the actual weight in the box, often called catch weight. If your order guide says "$9.40" without saying "per lb," every short rib invoice will look wrong, and the real price changes get lost.

Pick one count unit per item and stick with it. If one person counts cases and the next counts packs, the two counts can't be compared, and the order built from them will be wrong. Convert to order units only when you build the order.

For more on choosing units and handling the conversion, see restaurant inventory units.

Inventory counts: what's on the shelf right now

An inventory count tells you what you have. It's only useful if it's accurate, in the right unit, and done before the order it feeds is due.

The habits that matter most:

• List items in shelf walk order, not alphabetically, so the counter works through the room without doubling back.
• Put the count unit on every line, with the conversion next to it ("pack, 6 per case").
• Break partial cases into count units. Write 11 packs, not "1.8 cases."
• Count before the delivery is put away. A truck that arrives mid-count gets counted twice or not at all.
• Count at the same point in the day each time, so usage between counts makes sense.

Worked example: Thursday's short rib count

At 9:00 AM Thursday, the opening cook finds one unopened case and five loose packs on walk-in shelf 3:

1 full case:  1 × 6 = 6 packs
Loose packs:          5 packs
On hand:      6 + 5 = 11 packs

The cook writes 11 in the pack column, not "1 case + 5."

Full counts and short counts

You don't have to count everything every day. Many kitchens do a short count of high-use, expensive, or perishable items before each order, and a full count of everything less often, for example weekly or at the end of an accounting period. The full count is what you'll use for food cost, covered later in this guide.

Our guide to doing a restaurant inventory count covers setting up the sheet, partial-unit rules, who should count, and includes a free printable and downloadable count sheet.

Par levels: how much you need until the next truck

A par level is how much of an item you want on hand to get through service until the delivery after the one you're ordering. Order day, you compare the count to par and order the difference.

Par = (average daily usage × days of coverage) + safety stock

Days of coverage start on the day you count, not the day the truck arrives, because you keep using product in between.

Worked example: short rib pars for two order days

Measure usage from your own records. Over the last four weeks, the kitchen started with 14 packs, received 18 cases, and ended with 10 packs:

Received:      18 cases × 6 = 108 packs
Usage:         14 + 108 − 10 = 112 packs over 28 days
Daily usage:   112 ÷ 28 = 4 packs per day

Work out days of coverage for each order.

• Thursday order arrives Saturday. The next meat delivery after that is Wednesday, so Thursday's count has to last Thursday through Tuesday: 6 days.
• Monday order arrives Wednesday. The next delivery after that is Saturday, so Monday's count has to last Monday through Friday: 5 days.

Add safety stock. The chef decides on a 4-pack buffer for busy nights or a late truck. That's a judgment call, not a formula.

Thursday par:  (4 × 6) + 4 = 28 packs
Monday par:    (4 × 5) + 4 = 24 packs

Because the gaps between deliveries are uneven, the same item gets two different pars. Using one par for both days would leave the kitchen short over the long weekend gap or overstocked midweek.

Our guide to setting restaurant par levels covers sizing safety stock, checking pars against shelf life and storage space, and when a reorder point works better than a par. If you'd rather not do the math by hand, there's a free par level calculator.

Prepped items get pars too, on a shorter clock: how much dressing or cut romaine you want ready until you make it again. Those prep pars set how fast the kitchen goes through raw product, so they feed straight into the order pars above. Our guide to writing a restaurant prep list shows how to set them from covers and turn them into a daily list by station.

Order quantities: from par to whole cases

Once you have a count and a par, the order quantity is three steps:

1. Short, in count units: par − on hand − anything already ordered and not yet delivered
2. Convert to order units: short ÷ count units per order unit
3. Round to what the vendor sells, usually whole cases

Worked example: Thursday's short rib order

Short:        28 − 11 = 17 packs
In cases:     17 ÷ 6 = 2.83 cases
Order:        3 cases (18 packs)

Without the safety stock, the kitchen would need (4 × 6) − 11 = 13 packs, which is 13 ÷ 6 = 2.17 cases. That still rounds up to 3 cases. Rounding up already gave this order some cushion, which is worth noticing before you add more.

Rounding is a decision, not a rule

Rounding up is the safe default for items you can't run out of. It isn't always right:

• Perishables with short shelf life. Rounding a 1.2-case need up to 2 cases may mean throwing product away. Some kitchens round down and accept being slightly under par until the next truck.
• Split cases. If the vendor sells by the each or half case, you may not need to round at all. Ask your rep and write the answer on the order guide.
• Vendor minimums. A light order under the vendor's minimum may need something pulled forward, or it may be cheaper to pay a small delivery fee.

Don't forget what's already on order

Your count only sees what's on the shelf. If Monday's order hasn't arrived by the time you count on Wednesday, Wednesday's order will double it unless you subtract what's still on the truck. This matters most with vendors who need two or more days of lead time.

Order guides: what you buy, from whom, in what pack

An order guide is the standing reference behind every order: one list per vendor, with the exact product, pack size, order unit, count unit, conversion, target, storage location, and notes. It's what lets someone other than the usual orderer place a correct order.

Build it from the last four to eight weeks of invoices, not from memory, and copy pack sizes and item numbers exactly as they appear. Sort it in the same shelf walk order as your count sheet so counting and ordering follow the same path.

Worked example: the short rib line

Two details on that line prevent common errors. "Order in: Case" stops someone typing 17 into the email when they mean 17 packs. "Billed per lb" tells whoever checks the invoice what price to expect.

Our guide to building a restaurant order guide covers each column, how to handle items you buy from more than one vendor, and how to keep the guide current when pack sizes or prices change.

Vendors, schedules, and cutoffs

Independent restaurants often order from several vendors, each with its own method (portal, app, email, text, or phone), its own cutoffs, and its own delivery days. Purchasing breaks down when that information lives in one person's head.

For every vendor, write down:

• How you order, and where the order gets sent
• Every cutoff as a day and a time. "Thursday" isn't a cutoff. "Thursday 12:00 PM" is.
• Delivery days, and the usual delivery window
• Lead time, if the truck doesn't come the next day
• Minimums, delivery fees, and holiday changes
• Rep name and number, for when something has to change after the cutoff
• Who places each order, and who backs them up on their day off

Then put every vendor on one weekly grid. The grid shows problems a vendor list doesn't, like five cutoffs landing on the same Monday or a Sunday order nobody owns.

Worked example: the meat vendor's week

The two-day lead time is why each order covers so many days. If this vendor delivered the next day, each order would cover one day less and could be smaller.

Our guide to building a vendor ordering schedule walks through a full five-vendor week, including how to work count times backward from each cutoff.

Purchase orders: a written record of what you asked for

A purchase order (PO) is one specific order to one vendor on one day. It doesn't have to be a formal document. A short, consistent message works, as long as it's saved somewhere you can find it again and has a PO number you can write on the invoice.

Every PO should include:

• A PO number (something like PO-1107 is fine; it's for your records, not the vendor's)
• The vendor, the date and time sent, and who sent it
• Each item, in the vendor's description or item number, with the quantity in the order unit
• The expected delivery date
• The expected price per billing unit, kept in your log even if you don't send it to the vendor

Worked example: Thursday's email to the meat purveyor

At 10:40 AM Thursday, well before the noon cutoff, the kitchen manager sends:

PO-1107 · Delivery Saturday
Short rib, boneless (item # from invoice): 3 cases
Chicken thighs, boneless skinless, 4 × 10 lb: 2 cases
Please confirm. Thanks.

The chicken line came from the same process: a Thursday target of 12 bags, 5 on hand, so 7 bags short, which is 7 ÷ 4 = 1.75, rounded up to 2 cases.

In the PO log, the manager records the expected cost. Because short rib is billed by weight, the total is an estimate:

Short rib:   3 cases × ~30 lb × $9.40/lb = ~$846.00 (estimate)
Chicken:     2 cases × $68.00            = $136.00
Expected:                                  ~$982.00

Whatever way an order is sent, copy it into one log. Vendor portals only show their own orders, and texted or phoned-in orders leave no record unless someone writes them down.

Receiving: checking the delivery before you sign

Receiving is where a correct order can still go wrong. A case is missing, a pack is torn, the chicken is warm, or the price changed. Once the invoice is signed and the driver leaves, most of those problems get harder to fix. This step deserves its own routine and its own owner.

Before the truck arrives

• Know what's coming. Have the PO for each expected delivery printed or open on a phone by the back door.
• Clear space in the walk-in and freezer so cold product can go straight in.
• Have the tools ready: a probe thermometer that's been checked for accuracy, a scale if you buy anything by weight, and a pen.
• Schedule it. If deliveries arrive during prep, decide in advance who stops to check them in. A delivery dropped by the back door during a rush is a delivery nobody checked.

What to check at the back door

Check cold and frozen product first and get it put away first. Dry goods and paper can wait a few minutes. Proteins and dairy can't.

Food safety checks at receiving

Most state and local food codes in the U.S. are based on some version of the FDA Food Code. Under the 2022 Food Code and the state codes adopted from it:

• Refrigerated food that requires temperature control for safety (such as raw meat, poultry, and cut leafy greens) generally has to be received at 41°F (5°C) or below, unless another law for that specific food sets a different temperature (Delaware's adopted section 3-202.11; FDA guidance on cut leafy greens).
• Raw shell eggs have to be received in refrigerated equipment holding an ambient air temperature of 45°F (7°C) or below (FDA, Key Temperatures for Egg Safety).
• Food labeled and shipped frozen has to arrive frozen, and food that's cooked and delivered hot has to arrive at 135°F (57°C) or above (same Delaware section).
• Shellstock (live oysters, clams, and mussels) comes with identification tags that have to stay with the container until it's empty and then be kept on file. The Food Code sets that retention period at 90 days, and states differ on when the 90 days start (Oregon Health Authority shellfish fact sheet).

The FDA published a 2026 edition of the Food Code, and states adopt new editions on their own schedules. Some foods, such as milk and molluscan shellfish, are also covered by separate rules. Confirm the receiving requirements with your local health department rather than relying on this summary.

Refusing product and getting it on the invoice

If something is short, damaged, warm, or not what you ordered:

1. Refuse it while the driver is still there, and send refused product back on the truck.
2. Write it on the invoice before you sign: the item, the quantity refused or missing, and why. Ask the driver to initial it if that's your vendor's process.
3. Ask how the vendor handles credits. Some issue a credit memo, some adjust the next invoice, and some want a call to the rep. Write that process on the order guide so whoever receives knows it.
4. Decide right away whether you need a replacement. A missing case is a purchasing problem now, not just a credit to chase later.

Putting product away

• Cold and frozen first, straight into storage.
• First in, first out (FIFO). Put new product behind or below older product of the same item, so the oldest gets used first.
• Date it. Write the received date on cases or labels if they aren't already clearly dated.
• Put it where the count sheet says it lives. Product stored in a new spot gets missed on the next count.

For shelf layout, storage order in the walk in, and date marking, see our guide to restaurant FIFO and storage organization.

Worked example: Saturday's meat delivery

The truck arrives at 8:15 AM Saturday. The prep cook checking it in has PO-1107 on a phone.

• Chicken thighs, 2 cases. Probe reads 37°F. Pack size matches. Accepted.
• Short rib, 3 cases. Case labels read 29.8 lb, 30.4 lb, and 29.4 lb. Inside, one vacuum pack has a torn seal. The cook refuses that pack, sends it back with the driver, and writes on the invoice: "1 pack short rib refused, torn seal, 4.9 lb per pack label. Credit requested."

The numbers:

Short rib billed:     29.8 + 30.4 + 29.4 = 89.6 lb
Billed amount:        89.6 × $9.40 = $842.24
Refused pack:         4.9 lb × $9.40 = $46.06 credit
Short rib accepted:   89.6 − 4.9 = 84.7 lb, 17 packs
Accepted value:       84.7 × $9.40 = $796.18

Invoice total:        $842.24 + $136.00 = $978.24
Less credit:          $978.24 − $46.06 = $932.18

Does the kitchen need a replacement pack? It used about 8 packs on Thursday and Friday, so roughly 3 packs were left Saturday morning.

On hand after delivery:    3 + 17 = 20 packs
Needed Sat through Tue:    4 days × 4 packs = 16 packs
Cushion:                   20 − 16 = 4 packs

The safety stock absorbed the refused pack, so there's no emergency run. The cook notes it for Monday's count so the kitchen manager isn't surprised.

Tracking orders and building a purchasing history

A purchase order isn't finished when the truck leaves. It's finished when what you ordered, what arrived, and what you were billed all match, or every difference has a credit or an explanation. Give every order a status so anyone can see where it stands:

Keep Received and Closed separate. Orders that get closed when the truck leaves are how credits get forgotten.

Worked example: closing PO-1107

The kitchen manager updates the log Saturday afternoon:

• Chicken: ordered 2, received 2, $136.00 as expected.
• Short rib: ordered 3 cases, received 17 of 18 packs. Billed $9.40/lb, which matches the order guide. Open issue: $46.06 credit for the refused pack.
• Status: Received.

The following week, the credit memo arrives for $46.06. The manager writes its number in the log and marks PO-1107 Closed.

Check line by line, not just totals. Here the invoice total is close to the $982.00 estimate, but that's partly because short rib weights vary. A short case and a price increase can also offset each other in the total and hide both problems.

Our guide to tracking restaurant purchase orders covers setting up a PO log on paper or in a spreadsheet, reconciling the order against the invoice, and a weekly review of open orders.

What your order history tells you

After a few weeks, the log becomes a purchasing history. Once a month, look for:

• Price changes. Sort an item's lines by date and compare the price per billing unit.
• Shorts and refusals by vendor. If one vendor keeps shorting or sending damaged product, that's a conversation with the rep.
• Spend by vendor, from closed orders.
• What you ordered for the same week last time, as a starting point for holidays and events.

Illustrative price check: last month's short rib invoices were $8.95/lb. This month's are $9.40/lb.

Increase per lb:    $9.40 − $8.95 = $0.45
Percent increase:   $0.45 ÷ $8.95 = 5.0%
Monthly volume:     4 packs/day × 30 days = 120 packs = 20 cases ≈ 600 lb
Monthly impact:     600 × $0.45 ≈ $270

That's worth a call to the rep, a comparison with another vendor, or a menu price review. Without a history, it just shows up as a higher food cost with no clear cause.

Counts plus purchases give you cost of goods

Your full counts and your purchasing records together give you cost of goods sold (COGS) for a period:

COGS = beginning inventory + purchases − ending inventory

Value each count by multiplying quantities by the current price per unit, and use invoice totals net of credits for purchases.

Illustrative example for one month:

Beginning inventory (full count, value):   $8,200
Purchases (invoices, net of credits):      $21,450
Ending inventory (full count, value):      $7,900

COGS:          $8,200 + $21,450 − $7,900 = $21,750
Food sales:    $68,000
Food cost %:   $21,750 ÷ $68,000 = 32.0%

These numbers are made up to show the formula, not a benchmark. The point is that food cost is only as accurate as your counts and your purchase records. A missed credit or a stale count changes the result directly.

Who does what

In a small restaurant one person may do most of this. That works, but write down who owns each job so nothing depends on memory, and name a backup for every day the owner is off.

Some operators prefer that the person who places an order isn't the only person who receives and approves its invoice, so a second set of eyes sees every order. Whether that's practical depends on your staffing.

A weekly purchasing rhythm

Most of the work happens on a regular schedule. Here's how the example restaurant's week might look:

Weekly purchasing checklist

Each order day

• Count the items for this order, in count units, before the cutoff
• Check for anything already on order and not yet delivered
• Calculate short quantities against par and convert to order units
• Check the vendor minimum
• Send the order and save a copy with a PO number
• Log the PO with expected delivery date and expected prices

Each delivery

• Check items, pack sizes, quantities, weights, temperatures, condition, and dates
• Mark shorts, refusals, and substitutions on the invoice before signing
• Put cold and frozen product away first, oldest product in front
• Update the PO with what arrived and any open issues

Once a week

• Review every order that isn't Closed
• Follow up on missing credits
• Confirm next week's cutoffs and delivery days, especially around holidays

Once a month

• Compare prices per billing unit against last month
• Count shorts and refusals by vendor
• Do a full count and calculate cost of goods
• Adjust pars on items you ran out of or threw away

Common purchasing and inventory mistakes

Units

• Writing "3" without a unit, or counting in cases one day and packs the next.
• Storing price per case for items billed by the pound.

Counts and pars

• Counting after the cutoff, so the order is built from old numbers.
• One par for every order day when delivery gaps are uneven.
• Raising pars to cover a vendor that's late or short, instead of dealing with the vendor.

Ordering

• Ordering from memory instead of the order guide.
• Forgetting what's already on a truck and ordering it twice.
• Cutoffs written as a day with no time.

Receiving

• Signing the invoice before checking the delivery.
• Checking dry goods first while the proteins sit on the dock.
• Putting new product in front of old product.

Tracking

• Logging portal orders but not texted or phoned-in ones.
• Closing orders when the truck leaves, before credits arrive.
• Comparing only invoice totals instead of each line.

Moving from paper or spreadsheets to a repeatable system

Paper and spreadsheets can both run good purchasing. What matters is that the same information exists in one place, everyone works from it, and it gets updated. If you're starting from scratch or cleaning up a messy setup, build it in this order, because each step depends on the last:

1. Item list. Every item you buy, built from invoices, with vendor, pack size, order unit, count unit, and conversion.
2. Vendors. Ordering method, every cutoff with a time, delivery days, contacts, and owner.
3. Count sheet. In shelf walk order, pulled from the item list.
4. Targets. Start with your top 10 or 20 items, then add more.
5. PO log. One line per order, with a status.
6. Receiving routine. A checklist by the back door and a trained receiver for each delivery window.
7. Monthly review. Prices, shorts, and pars.

If you're working in a spreadsheet, our guide to setting up a restaurant purchasing spreadsheet lays out a five-tab structure that follows this order, with formulas and the places these sheets usually break.

Signs your current setup is costing you

• Only one person can place orders correctly.
• Nobody can answer "what did we order from the meat vendor last Thursday, and did it all come?" without checking texts, email, and a portal.
• There are several copies of the order guide, and they disagree.
• Credits get forgotten.
• Someone spends part of every week fixing the spreadsheet.

None of these means you need software. They mean the information is scattered. Sometimes the fix is a cleaner spreadsheet with one shared copy. Sometimes it's a tool built for the job.

Where Proteus Kitchen fits

Proteus Kitchen is purchasing software for independent restaurants and small groups. It keeps the records in this guide together in one place:

• Inventory items with their vendor, category, storage location, order unit, count unit and how many count units are in one order unit, a target quantity, the last vendor price, and notes.
• Vendors with their ordering method, delivery days, one or more order deadlines (each a day and a time), contact information, and notes. The purchasing home screen lists which vendors have orders due today.
• Daily Count on a phone, with a plus/minus stepper for the items your team counts every day.
• Purchase orders built by vendor, showing each item's current amount, its target, and a suggested quantity. You can save a draft, then copy the order as text for the vendor's portal, a text message, or an email, or print it. On a phone it can open a pre-filled text to the vendor's number. You mark the order submitted once it's sent.
• Purchasing history you can search and filter by vendor, status, and date range, and duplicate a past order as the starting point for the next one.

Proteus doesn't place orders with vendors for you, and it doesn't require a POS integration. Checking deliveries at the back door still happens with the invoice in hand, using the receiving routine above.

If you already have an inventory spreadsheet, order guide, or vendor list, Free Restaurant Setup means you can send it over and the Proteus team will help import your inventory and vendors. There's also a 30-day free trial.

FAQ

What's the difference between restaurant purchasing and inventory management?

Inventory management is knowing what you have: counts, units, storage, and how fast things get used. Purchasing is getting what you need: order guides, vendors, purchase orders, receiving, and invoices. In practice they're one workflow, because every order starts from a count and every delivery changes what's on hand.

Where should I start if I have nothing written down?

Start with your biggest vendor's invoices from the last month. List every item with its pack size, order unit, and count unit. That one list becomes your order guide, your count sheet, and the basis for pars.

How often should a restaurant order?

As often as your vendors deliver and your shelf life and storage require. Produce, fish, and bread often need more frequent deliveries than dry goods. More frequent orders mean less product on the shelf, but each one is another count and another cutoff to manage.

Should the person who orders also receive the delivery?

It's common in small kitchens, and it can work. The receiver does need the PO in hand, so they're checking against what was ordered, not just what the invoice says. If you have the staff, having a second person review invoices against POs adds a useful check.

Sources

Food safety receiving requirements in this guide come from the following. Your state or local code may differ.

• U.S. Food and Drug Administration, Food Code 2022
• U.S. Food and Drug Administration, Summary of Changes in the 2026 FDA Food Code
• U.S. Food and Drug Administration, Key Temperatures for Egg Safety in Food Service Operations and Retail Food Stores
• U.S. Food and Drug Administration, Recommendations for the Temperature Control of Cut Leafy Greens during Storage and Display in Retail Food Establishments
• Delaware Administrative Code, 16 Del. Admin. Code § 3-202.11, Temperature (a state adoption of the Food Code's receiving temperature section)
• Oregon Health Authority, Shellfish fact sheet

Next step: run one full loop this week

Pick one vendor and one order day, and take it all the way through:

1. Confirm the vendor's cutoff time and delivery days with your rep.
2. Check that every item from that vendor has a count unit, order unit, and conversion written down.
3. Count before the cutoff, calculate the order from your targets, and send it with a PO number.
4. Check the delivery against the PO before signing, and mark anything short or refused.
5. Close the order once the invoice and any credits match.

Fix whatever went wrong, then do the same with your next vendor.