A catering buyer needs to turn a confirmed menu and guest count into ingredients, supplier orders and deliveries that arrive before preparation starts. When several events share ingredients, a change to one booking can affect a consolidated order and the kitchen's allocation plan.
The purchasing job is to keep those dependencies visible. The chef needs the latest quantities, the buyer needs supplier confirmation, and the receiver needs to know which delivery differences could affect an event.
Quick answer: connect the event plan to supplier orders
Start with the event menu, confirmed headcount, preparation schedule and available stock. Build ingredient requirements, group purchases by supplier, and preserve which events need each item. Review supplier changes before the kitchen relies on them, then record what actually arrives.
A living purchase order helps keep the requested, supplier-confirmed and received states connected. It supports event cost review, but a PO and receipt alone do not establish actual consumption or event profit. Labor, rentals, transport, unused stock and other costs need their own records.
Build the event ingredient plan before the supplier order
For each menu item, record the portion specification and whether ingredient quantities refer to raw purchased food or usable prepared food. Include the confirmed guest count and the date of the latest menu revision.
The following is a fictional planning example, not a serving recommendation. It assumes a recipe requires 0.3 lb of usable chicken per guest and the kitchen has validated a 75% usable yield for its chosen product and preparation:
The USDA Food Buying Guide's yield examples illustrate this distinction between purchased and edible quantities. The guide serves child nutrition programs; use product- and preparation-appropriate yield data for your own recipes rather than adopting its meal requirements for a catering event.
Do not apply yield loss twice if the recipe already specifies the raw purchase quantity. Subtract suitable stock assigned to this requirement and confirmed incoming quantities arriving before preparation, using the same raw or usable quantity basis as the calculation. Do not subtract stock reserved for another event. Then round the remaining need to supplier packs. Keep any contingency allowance explicit so the buyer can distinguish it from preparation yield.
A bill of materials can organize this relationship. It does not mean every supplier order should change automatically when someone edits the booking.
Plan backward from preparation, not only the event date
Use actual supplier cutoffs, available delivery appointments, receiving access and the kitchen's approved handling plan. There is no universal Monday order or Thursday receipt that fits every Saturday event.
Question
Owner to confirm it
When must the ingredient be available for prep?
Chef or production lead
What product and holding conditions are acceptable?
Responsible food-safety lead
What is the supplier's cutoff and confirmed arrival window?
Buyer and supplier
Who can receive and inspect the delivery?
Commissary or venue receiving lead
What happens if the delivery is short or late?
Event lead and buyer
Plan rentals and non-food purchases alongside ingredients, but keep their costs and return obligations distinguishable. Confirm venue access and supplier availability rather than assuming day-of deliveries can always be replaced.
Consolidate shared ingredients without losing event ownership
Suppose a wedding and a luncheon both need the same ingredient. One supplier order may be convenient, but the kitchen still needs to know what is reserved for each event and what remains unallocated.
Keep three quantities visible:
The event's current requirement.
The quantity committed to the supplier, including reviewed changes.
The quantity physically available and assigned to the event.
If a booking increases after an order is sent, calculate the difference and confirm whether the supplier can fulfill it. Record the accepted revision; editing the internal plan does not amend the supplier's commitment.
For example, two events need 40 lb and 24 lb of the same raw ingredient. If 14 lb of suitable stock is available for those events and 20 lb is confirmed to arrive before preparation, the additional need is 40 + 24 − 14 − 20 = 30 lb, before pack rounding. Assign the existing supply once. If the first event later falls to a 32 lb requirement, the total need falls by eight pounds, but a supplier order already accepted does not shrink automatically. Confirm a revision or record how the surplus will be used under the approved handling plan.
When a delivery is short, decide which event receives the available stock and who owns the replacement purchase. Retain the original discrepancy so it can be resolved with the supplier instead of disappearing during reallocation.
Review substitutions with the kitchen and event owner
A different product can change usable yield, pack size, ingredient suitability, presentation and cost. The buyer should not treat a supplier's proposed substitute as an approved replacement.
Use a clear review sequence:
Record the proposed product, quantity, price and arrival window.
Have the responsible kitchen reviewer check suitability and applicable ingredient or allergen requirements.
Identify affected events and ask the event owner whether client approval is needed under the agreed menu and terms.
Recalculate the purchase requirement and estimated ingredient cost where necessary.
Confirm the decision with the supplier and make it visible to receiving and preparation staff.
For critical ingredients, investigate a backup source before an urgent shortage. Confirm availability and terms; a supplier's contact details alone do not establish a viable replacement. See dual sourcing for SMBs.
Receive against the latest reviewed order
Whether delivery goes to a commissary or venue, name the receiver and provide the current order details. Record actual quantities, rejected items and unresolved balances separately from the supplier's promise.
If 24 lb was ordered and 22 lb arrived, retain the 2 lb difference. The buyer needs to establish whether it is still due, canceled or requires an invoice correction. A short receipt does not by itself prove that the supplier has issued a credit.
Capture the handling and traceability information required by your operation in the system that supports it. Confirm lot, expiry and stock-rotation capabilities in a demonstration rather than assuming they are included in a general receiving feature.
Keep ingredient cost separate from total event margin
Use a consistent definition for each event report. Ingredient cost, total purchasing spend and event profit are different measures. Disposables, rentals and labor should remain identifiable rather than being silently counted as food ingredients.
For a fictional event with $12,500 of food revenue, $3,750 of ingredient cost represents 30%. If ingredient cost becomes $4,200 while that revenue stays unchanged, the ratio becomes 33.6%: a $450 increase and a 3.6 percentage-point change. This does not establish the event's final profit.
For actual event costing, reconcile ingredients used, stock returned or retained, waste and the approved allocation of shared purchases. Compare the result with the original estimate on the same basis. Have finance define revenue, cost classification and timing for your reporting.
Bring two overlapping events to a demonstration. Ask the vendor to show a guest-count change, a shared ingredient order, a proposed substitute, a partial delivery and an invoice discrepancy.
Check which system owns each task:
Task
Evidence to request
Event and menu planning
Revision history and current confirmed requirements
Recipe scaling
Purchase units, usable yield and pack rounding
Supplier purchasing
Original order, reviewed changes and outstanding quantities
Receiving
Actual delivery and unresolved discrepancies
Event allocation
Shared stock assignment and unused stock treatment
Accounting handoff
Supported fields, coding and responsible reviewer
Ask which steps are native, configured, integrated or manual. Event scheduling, automatic recipe scaling, lot tracking and accounting project codes are separate capabilities to verify.
Where LineNow fits
LineNow's restaurant purchasing workflow connects purchase orders, supplier replies, receiving and the accounting handoff. Evaluate it where the buyer and kitchen lose track of changed orders, deliveries and follow-up work.
Confirm event allocation, recipe scaling and accounting mappings separately. Your booking or recipe system may continue to own those records. A purchasing demonstration should show the handoffs and their limits clearly.
Start with one supplier serving two events. Measure time spent preparing and following up orders, unresolved delivery differences, and whether receivers have the latest information. Use that evidence to decide whether to expand.
