A shared kitchen can place one supplier order for several restaurant brands. The harder job is keeping each brand's needs visible when the supplier changes a pack, delivers short, or sends an invoice that differs from the order.
Consider a fictional commissary buying tomatoes for pizza, burgers and salads. The buyer needs a consolidated order, the receiving team needs to know what should arrive, and the operator needs to understand which ingredients each concept actually used. Those are connected tasks, but they are different records.
Quick answer: connect shared purchasing to receiving and usage
For a multi-brand ghost kitchen, start with a shared purchasing workflow that preserves requested, supplier-confirmed and received quantities. Then decide how your inventory or production system records ingredients issued to each concept, remaining stock and waste.
A living purchase order keeps supplier changes connected to the order. Brand-level food cost also requires usage and costing records; the PO alone cannot establish what each kitchen consumed or whether a concept was profitable.
Separate planned allocation from actual consumption
Classify ingredients and supplies before choosing software:
| Purchase | Planning question | Record to verify later |
|---|---|---|
| Ingredient dedicated to one brand | Which concept requested it? | Quantity received, held, used or wasted |
| Ingredient shared across brands | How much does each concept expect to need? | Actual issues or production usage by concept |
| Shared operating supplies | Who owns the budget and allocation policy? | Approved expense coding and allocation basis |
A purchase earmarked for one brand may still be sitting in storage at the end of the week. A shared ingredient may be used in different proportions from the original plan. Preserve both the plan and the actual movement instead of overwriting one with the other.
Have finance define how food, packaging and operating supplies are classified. A purchasing article cannot prescribe the same account treatment for every business.
Build one supplier order from several brand requests
Use this fictional consolidated order as a planning example:
| Ingredient | Facility order | Planned use |
|---|---|---|
| Chicken breast | 50 lb | 35 lb for bowls; 15 lb for wraps |
| Salmon fillet | 30 lb | Seafood concept |
| Mozzarella | 12 lb | Pizza concept |
| Roma tomatoes | 40 lb | 22 lb pizza; 12 lb burgers; 6 lb salads |
Before sending the order, check stock already available, open deliveries, usable shelf life and the supplier's ordering units. Make sure a case quantity has not been mistaken for pounds or individual items.
Consolidation may simplify ordering and deliveries. Check the supplier's actual price breaks, minimums, freight and terms before treating it as a saving. Larger orders can also leave ingredients unused.
Keep the concept requests available beside the supplier PO or in the connected planning system. If demand changes after ordering, record the revised plan and who needs to know. Do not assume a change in the brand's forecast automatically changes an order already sent to the supplier.
For supplier cutoffs and delivery preparation, see how restaurants order from food distributors.
Review supplier changes before the kitchen relies on them
Three changes deserve an explicit owner:
- Short shipment: If 25 lb of fish was requested and the supplier confirms 17 lb, the buyer has an 8 lb planning gap. Notify the affected kitchen, then decide whether to source elsewhere, adjust production or arrange a later quantity explicitly. The eight pounds not accepted by the supplier are not a confirmed backorder.
- Different pack: Compare the usable quantity and unit price. A cheaper case is not necessarily a cheaper ingredient if its size differs.
- Substitute: Have the responsible kitchen reviewer assess recipe suitability and applicable ingredient or allergen requirements before acceptance. Supplier confirmation is not kitchen approval.
Keep the original request, the supplier's message and the reviewed decision. A promised dispatch date should not silently become an expected arrival date.
The supplier-email guide shows how to separate quantity, timing, price and substitute decisions in one reply.
Receive the delivery that actually arrived
The receiver should work from the latest reviewed order state and record the physical delivery. In the fish example, a confirmation of 17 lb does not prove that 17 lb arrived.
Record received quantities in consistent units, identify rejected or damaged items, and retain any remaining supplier commitment. Capture differences for the buyer to resolve rather than adjusting the record to make the invoice match.
If the commissary stores ingredients centrally, record the storage location at receipt and the later issue to a concept. If deliveries go directly to dedicated brand storage, the receipt may also identify that destination. Choose the process that reflects the physical operation; forcing every shared ingredient into a final brand allocation at the dock can create false precision.
Try the fictional kitchen receiving checklist to inspect a partial delivery. Then use your own example to evaluate the order–receive–count workflow.
A worked example: ingredient yield and concept allocation
The following is a fictional ingredient-only calculation. It assumes the full batch is used by two concepts, with no usable inventory left over. It excludes labor, overhead and other recipe ingredients.
| Step | Calculation | Result |
|---|---|---|
| Raw ingredient purchase | 80 lb × $6.50 | $520.00 |
| Usable cooked yield | 80 lb × 78% | 62.4 lb |
| Ingredient cost per usable pound | $520 ÷ 62.4 lb | About $8.33/lb |
| Burger concept usage | 48 lb × ($520 ÷ 62.4 lb) | $400.00 |
| Wrap concept usage | 14.4 lb × ($520 ÷ 62.4 lb) | $120.00 |
| Check | $400 + $120 | $520.00 |
Use the unrounded cost per pound for allocation, then round the final amounts. If some usable product remains in storage, keep that quantity separate instead of allocating the entire batch to consumption.
A new supplier price can change the estimated cost of the next batch. Whether it changes an existing stock valuation or a historical report depends on the costing method and system configuration. Verify that behavior with finance and your recipe or inventory system.
For the underlying recipe structure, see bill of materials. For ingredient-price changes, see purchase price variance.
Compare expected usage with actual usage
Recipe-based expectations and actual usage answer different questions. Restaurant365's Actual vs Theoretical Analysis documentation describes comparing expected ingredient quantities and costs with actual records. Its periodic inventory documentation explains using beginning inventory, purchases and ending counts to establish period usage.
The Actual vs Theoretical documentation also notes that its report is intended to investigate quantity and approximate-cost variances, not tie perfectly to inventory counts or financial reports. Check the selected cost settings and included transactions before using it as a financial reconciliation.
For a shared kitchen, ask the reporting owner how transfers, production, waste and concept assignments enter that calculation. Make sure the sales period and inventory period align before comparing brands.
Investigate a variance before changing menu prices or portions. Possible questions include: Was the count complete? Did a shared ingredient move to another concept? Did the recipe yield change? Was waste recorded? Was the supplier's new price approved and entered correctly?
Set targets using your own menu, operating model and financial plan. A generic food-cost percentage cannot establish that one concept is healthy or another is losing money. Ingredient cost is only part of profitability.
What to test in ghost kitchen procurement software
Use one shared ingredient and one dedicated ingredient in a demonstration. Ask the vendor to show:
- Two brand requests consolidated into a supplier order, with the originating needs still traceable.
- A supplier changing price, pack size and delivery quantity, followed by a review decision.
- A partial receipt that leaves the undelivered balance visible.
- A central-stock issue to a concept, or a documented handoff to the system that records it.
- A usage and cost report that distinguishes planned allocation, actual consumption and remaining stock.
- An invoice discrepancy passed to the responsible reviewer with supporting order and receipt records.
Name the owner and system for each step. Confirm whether capabilities are included, configured, integrated or outside the proposed product. If multiple legal entities share the facility, include finance in the evaluation of ownership and intercompany treatment.
See food cost management software when recipe costing and production reporting are central requirements.
Where LineNow fits
LineNow's restaurant purchasing workflow connects purchase orders, supplier replies, receiving and the accounting handoff. Start the demonstration with an order that changes after it is sent, then inspect what the buyer and receiver can see.
Confirm brand permissions, concept allocation, recipe costing and accounting ownership separately. A general purchasing workflow does not establish that dedicated multi-brand production or cost-allocation capabilities are available. Some requirements may belong in your existing inventory system or require another tool.
For the pilot, choose one supplier and a small set of shared ingredients. Track time spent following up, unresolved delivery differences and whether the next order uses accurate stock information. Expand once the team can follow the full history from request to receipt and identify who owns the remaining cost records.
Explore restaurant purchasing with LineNow, or review the food-cost use case with the person responsible for recipes and reporting.