Multi-Location Restaurant Inventory: Catalogs, Transfers, Commissary

To manage inventory across multiple restaurant locations, run every site from one shared item catalog and recipe book, count all sites on the same day with the same units, and record every transfer between stores or from a central kitchen as a document that moves cost out of one location and into another. With that in place, food cost, waste, and variance become comparable site by site, and central purchasing and par levels can be set from real data instead of each manager's habits.

Most multi-unit operators do not fail at counting. They fail at the handoffs between sites: the case of chicken borrowed on a busy Saturday, the sauces the commissary sends out without a price, the item that is called "chx thigh" at one store and "boneless thighs 40 lb" at another. This guide focuses on those handoffs, with a worked example showing how one undocumented transfer can make your worst location look like your best.

Why Inventory Gets Harder With the Second Location

A single restaurant can survive on a chef who knows the walk-in by heart. Two or more cannot, because the numbers you use to run the group only mean something if every site produces them the same way. Common problems when a group grows:

Common Multi-Location Inventory Problems

Different names and units for the same item

One store counts ground beef in pounds, another in 10 lb chubs. Totals cannot be added up, and price comparisons are meaningless.

Informal transfers

Product moves between stores in a manager's car with no record, so one site's food cost is overstated and the other's understated.

Unpriced commissary output

The central kitchen ships soups, doughs, and sauces, but stores receive them at zero cost or at a guessed price.

Local buying

Each location orders from its own vendors at its own prices, and the group loses the volume it has on paper.

Pars copied from the first store

A suburban site with half the volume carries the flagship's par levels and throws away the difference.

Build One Item Catalog and One Recipe Book

Everything else depends on this step. Every location should buy, count, and cost the same item under the same name, with the same units and the same conversion between them.

✓One master item list for the group, with a single name per product (for example, "Chicken thigh, boneless, fresh")

✓A purchase unit, a count unit, and a recipe unit for every item, plus the conversions (1 case = 40 lb; recipes use ounces)

✓Approved vendors and vendor item codes mapped to each master item

✓One recipe book, edited centrally, with portion specs and yields that every site uses for costing

✓A short list of site-specific items, flagged as local, for regional specials

✓A rule that new items are added by one person or team, not by each store

Recipe yields matter more than they seem. If the flagship trims a whole tenderloin to 70% usable and the newer store gets 60%, the same recipe costs more at the second site. The free food yield calculator helps you set a standard yield per item, so you can see which site is off the standard rather than arguing about it.

Standardize Counts Across Sites

A group's inventory report is only as good as its least careful count. Standardize the method, not just the deadline:

A Group-Wide Counting Standard

1Same cutoff for every site

Count all locations on the same day, at the same point before or after service, and never with a delivery half put away. Month-end counts should all fall on the last day of the period.

2Same count sheet order

Each site's sheet follows its own shelf layout, but uses master item names and count units so the lines roll up.

3Count the commissary too

The central kitchen holds raw stock and finished batches. If it is not counted, its losses disappear into the stores' numbers.

4Value everything at one price source

Use the latest group invoice price for each item, not whatever each manager remembers paying.

5Spot-check with a second counter

Have an area manager or a manager from another site recount the A items at one location each month. Differences show where the method is drifting.

For the basics of running each individual count, setting pars, and calculating turnover, see our guide to restaurant inventory management.

How to Handle Transfers Between Locations

Transfers are normal and useful: a busy site borrows from a quiet one, a closing store sends its short-dated dairy to a neighbor, a new location gets its opening stock from established ones. The problem is not the transfer, it is the missing paperwork. Every transfer should be one document that reduces stock and cost at the sending site and adds the same stock and cost at the receiving site.

What Every Transfer Records

✓Sending and receiving location

✓Items and quantities in count units

✓Unit cost, taken from the sender's latest price

✓Who sent it and who received it

✓Date, before the next count cutoff

What Goes Wrong Without It

✗Sender shows high food cost and variance

✗Receiver looks cheaper than it really is

✗Missing product looks like theft

✗Frequent borrowing hides bad pars

✗Nobody can tell which store runs well

Worked Example: One Undocumented Transfer

These numbers are illustrative. A three-store cafe group compares monthly food cost. Store B ran short on proteins and dairy several times and picked up $1,800 of product from Store A, with no transfer recorded. Here is what the report shows, and what actually happened:

•Store A: $95,000 sales. Reported COGS $31,200, a 32.8% food cost. Remove the $1,800 that left for Store B and true COGS is $29,400, or 30.9%.
•Store B: $70,000 sales. Reported COGS $19,600, a 28.0% food cost. Add the $1,800 it used from Store A and true COGS is $21,400, or 30.6%.
•Store C: $55,000 sales. COGS $17,300, a 31.5% food cost, with no transfers either way.

On the report, Store B looks like the best-run kitchen in the group and Store A looks like the problem. In reality, Store A is the most efficient, and Store B's pars are too low for its volume. A group that acts on the report would put pressure on the wrong manager and copy the wrong store's habits. One transfer document would have prevented both mistakes.

Frequent transfers are a forecasting signal

If one site borrows the same items every week, fix its par levels or delivery days instead of making transfers routine. Review transfers by item and site each month.

Central Kitchen and Commissary Transfers

A commissary turns raw purchases into batches such as soups, sauces, doughs, dressings, and portioned proteins, and ships them to stores. For inventory, treat it as its own location that "sells" to the stores at a set transfer price. That keeps the commissary's efficiency visible and gives every store a real cost for what it receives.

Cost each batch from its recipe: ingredients at current prices, divided by the tested yield
Choose a transfer price policy and apply it everywhere: ingredient cost only, or ingredient cost plus an allocation for commissary labor and packaging
Ship on a transfer document, so the store receives the item into stock at that price
Count finished batches at the commissary and at the stores on the regular cutoff
Compare the commissary's actual yield with the recipe yield every month

Example: a 5-gallon batch of tomato soup uses $38 of ingredients and yields 20 quarts, so the ingredient cost is $1.90 per quart. If the group adds about $0.60 per quart for commissary labor and containers, the transfer price is $2.50 per quart. Whichever policy you pick, keep it consistent. If some items move at ingredient cost and others with labor added, store food cost percentages stop being comparable.

The commissary also has its own waste and variance: batches that do not hit yield, product lost to over-trimming, and returns of short-dated items from stores. Record those as write-offs at the commissary rather than letting them flow into store food cost.

Centralize Purchasing Without Losing Control of Pars

Combined volume is the clearest benefit of more locations. Negotiate prices for the group, keep an approved vendor list, and have every site order against it, while each store still orders to its own par levels.

Example: three stores each buy about 120 lb of chicken thighs a week at $2.89 per pound. A group contract for 360 lb a week at $2.59 per pound saves $0.30 x 360 = $108 a week, or roughly $5,600 a year on one item. Results depend on your market and vendors, but most groups find their biggest savings in a handful of high-volume proteins, dairy, and paper goods. Our guide to negotiating with restaurant suppliers covers how to approach those talks.

•Set pars per site from that site's own usage, not the flagship's
•Keep a short list of items each store may buy locally, and cap the spend
•Receive every delivery at the store against the invoice, so a short case is credited, not absorbed
•Compare the price paid for the same item across stores monthly to catch sites off contract

Compare Sites With the Same Metrics

Once catalogs, counts, and transfers are consistent, a weekly or monthly scorecard shows where to spend attention:

Per-Location Inventory Scorecard

Food cost %

COGS / food sales, after transfers in and out. Read it next to menu mix, since a store selling more steak will run higher.

Variance by item

Theoretical usage from sales and recipes vs actual usage from counts. The same item drifting at one site points to portioning, receiving, or theft there.

Waste in dollars

Recorded write-offs by reason. A store with almost no recorded waste but high variance is probably not recording it.

Days on hand

Average inventory relative to usage. High days on hand means cash on the shelves and aging product.

Transfers in and out

Value and frequency by site. Constant borrowing means pars or delivery days need work.

Price compliance

Share of spend with approved vendors at contract prices.

To put waste on the same footing across stores, the food waste calculator converts each site's write-offs into a percentage of purchases. Recorded write-offs also let you separate honest waste from missing product; our guide to tracking inventory theft explains how.

How Mid-Market Restaurant Groups Manage Inventory Across Sites

Groups with roughly 3 to 30 locations usually outgrow spreadsheets for the same reason: the head office needs one version of the numbers, and store managers need tools fast enough to use during a busy week. In practice, the groups that manage inventory well tend to share a few habits:

•A cloud inventory system where every site uses the same item catalog and recipes
•Counts on phones or tablets, in shelf order, submitted by the same cutoff
•Receiving, transfers, and write-offs recorded as documents, not as notes or texts
•A weekly review of variance and waste by site, with one or two items to fix per store
•Monthly unannounced recounts of high-value items by someone from outside the store
•A written opening playbook, so a new location starts with the catalog, pars, and procedures already in place

MiseKit supports this setup with separate storage locations, each with its own inventory counts, receiving documents, and write-off acts built from the same product list, so per-site food cost and waste come from the same kind of records everywhere.

Opening a New Location

A new site is the easiest time to get inventory right, because there are no old habits yet. Load the catalog, recipes, vendors, and storage layout before opening. Set opening pars from a comparable store and adjust them weekly for the first month. Send any opening stock from existing locations on transfer documents, so the new site starts with a real opening inventory value and the senders' food cost is not distorted. After about 30 days, add the store to the regular scorecard.

Multi-Location Inventory FAQ

How do you manage inventory across multiple restaurant locations?

Use one item catalog and recipe book for all sites, count every location on the same day with the same units, and record receiving, transfers, and write-offs as documents. Then compare food cost, variance, waste, and days on hand by site each week, and set par levels from each location's own usage rather than copying the flagship's.

How should inventory transfers between restaurant locations be recorded?

Record each transfer as one document listing the sending and receiving site, items, quantities, unit cost, and who sent and received it. It should reduce stock and cost at the sender and add the same amount at the receiver before the next count. Without it, the sender's food cost looks too high and the receiver's too low.

How do you price items from a commissary or central kitchen?

Cost each batch from its recipe at current ingredient prices, divide by the tested yield, and use that as the transfer price. Some groups add an allocation for commissary labor and packaging. Either approach works if it is applied consistently to every item, so food cost percentages stay comparable across stores.

Should each restaurant location have its own par levels?

Yes. Par levels should come from each site's own usage and delivery schedule. A store with half the flagship's volume, or deliveries on different days, needs different pars. Sharing a catalog and recipes keeps items comparable, while location-specific pars keep each store from overstocking or running out.

Should purchasing be centralized for a restaurant group?

For most groups, a hybrid works best. The head office negotiates prices and keeps an approved vendor list for high-volume items like proteins, dairy, and paper goods, while each store orders to its own pars and receives deliveries itself. A small allowance for local purchases covers specials, and monthly price checks catch stores buying off contract.

What inventory metrics should a multi-unit restaurant group compare?

Compare food cost percentage after transfers, variance by item, waste in dollars by reason, days of inventory on hand, transfers in and out, and the share of spend at contract prices. Review them weekly or monthly by site, and look for items that drift at one location rather than ranking stores on a single number.

When does a restaurant group need multi-location inventory software?

Usually from the second or third location, once more than one person counts, product moves between sites, or a central kitchen ships to stores. At that point, spreadsheets struggle to keep one catalog, current prices, and transfer records in sync, and the head office cannot trust that every site's numbers were produced the same way.

Key Takeaway

Multi-location inventory works when every site speaks the same language: one catalog, one recipe book, one count cutoff, and a document for every delivery, transfer, and write-off. Price commissary output consistently, set pars per store, and compare sites on food cost, variance, and waste after transfers.

One Set of Numbers for Every Location

MiseKit keeps counts, receiving, and write-offs for each storage location on one product list, so you can compare food cost and waste across sites.

Start Free with MiseKit